Re: [PATCH v3 1/6] ARM: tegra: add gpiod_lookup table for paz00

On 11/27/2013 05:33 AM, Stephen Warren wrote: On 11/26/2013 03:05 AM, Mika Westerberg wrote: From: Heikki Krogerus This makes it possible to request the gpio descriptors in rfkill_gpio driver regardless of the platform. V2 of the series did the following: static struct

[PATCH] drivers: scsi: scsi_lib.c: add prefix "SCSILIB_" to macro "SP"

the macro "SP" is too common to make conflict with some architectures, so recommend to add prefix for it. The related warning (with allmodconfig for hexagon): CC [M] drivers/scsi/scsi_lib.o drivers/scsi/scsi_lib.c:46:0: warning: "SP" redefined [enabled by default]

Re: [PATCH v2 04/10] PCI: Destroy pci dev only once

On Tue, Nov 26, 2013 at 5:24 PM, Rafael J. Wysocki wrote: > > So assume pci_destroy_dev() is called twice in parallel for the same dev > by two different threads. Thread 1 does the atomic_inc_and_test() and > finds that it is OK to do the device_del() and put_device() which causes > the device

Re: modules, add_kallsyms() && DEFINE_PER_CPU

(2013/11/27 2:50), Oleg Nesterov wrote: > On 11/26, Oleg Nesterov wrote: >> >> Note: this doesn't work for modules, but module's per-cpu data is >> not visible for kallsyms_lookup_name() anyway. > > Rusty, I am just curious if it makes sense to change this or not... > > But DEFINE_PER_CPU'ed

fuse try to freeze with lock held

Hit the below warning when enabling the CONFIG_DEBUG_LOCK_ALLOC, __fuse_request_send == > request_wait_answer == > wait_event_freezable == > try_to_freeze() But here the inode->i_mutex is hold yet in vfs_readdir(). Could anyone give some help? Thanks. [ 3148.552435] Freezing user space

Re: [PATCH v2 03/10] PCI: Move resources and bus_list releasing to pci_release_dev

On Tue, Nov 26, 2013 at 5:15 PM, Rafael J. Wysocki wrote: >> @@ -36,11 +22,6 @@ static void pci_destroy_dev(struct pci_dev *dev) >> { >> device_del(>dev); >> >> - down_write(_bus_sem); >> - list_del(>bus_list); >> - up_write(_bus_sem); >> - >> - pci_free_resources(dev); >>

Re: nouveau/ NV11: 3.12 freezes if X.org is started headless

On Tue, Nov 26, 2013 at 8:35 PM, Stefan Lippers-Hollmann wrote: > Hi > > On Wednesday 27 November 2013, Ilia Mirkin wrote: >> On Tue, Nov 26, 2013 at 7:18 PM, Stefan Lippers-Hollmann >> wrote: >> > Hi >> > >> > On Tuesday 26 November 2013, Ilia Mirkin wrote: >> >> On Tue, Nov 26, 2013 at 6:03

[PATCH] drivers: input: touchscreen: sur40: use static variable instead of stack varialbe for 'packet_id'

'packet_id' is used for checking sequence whether in order, it need be static variable independent from sur40_poll(). The related warning (with allmodconfig under hexagon): drivers/input/touchscreen/sur40.c: In function 'sur40_poll': drivers/input/touchscreen/sur40.c:297:6: warning:

[PATCH 3.4 02/39] nfs: dont allow nfs_find_actor to match inodes of the wrong type

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Layton commit f6488c9ba51d65410e2dbc4345413c0d9120971e upstream. Benny Halevy reported the following oops when testing RHEL6: <7>nfs_update_inode: inode 892950 mode changed, 0040755 to

[PATCH 3.4 21/39] Revert "ima: policy for RAMFS"

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mimi Zohar commit 08de59eb144d7c41351a467442f898d720f0f15f upstream. This reverts commit 4c2c392763a682354fac65b6a569adec4e4b5387. Everything in the initramfs should be measured and

[PATCH 3.4 23/39] ALSA: 6fire: Fix probe of multiple cards

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 9b389a8a022110b4bc055a19b888283544d9eba6 upstream. The probe code of snd-usb-6fire driver overrides the devices[] pointer wrongly without checking whether it's already

[PATCH 3.4 05/39] ACPICA: Interpreter: Fix Store() when implicit conversion is not possible.

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bob Moore commit 3f654bad3257427bea7ba1c4d43a23d99a03622b upstream. For the cases such as a store of a string to an existing package object, implement the store as a CopyObject(). This is a

[PATCH 3.4 03/39] libertas: potential oops in debugfs

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 upstream. If we do a zero size allocation then it will oops. Also we can't be sure the user passes us a NUL terminated string so

[PATCH 3.4 22/39] exec/ptrace: fix get_dumpable() incorrect tests

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit d049f74f2dbe71354d43d393ac3a188947811348 upstream. The get_dumpable() return value is not boolean. Most users of the function actually want to be testing for

[PATCH 3.4 07/39] ACPICA: Return error if DerefOf resolves to a null package element.

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bob Moore commit a50abf4842dd7d603a2ad6dcc7f1467fd2a66f03 upstream. Disallow the dereference of a reference (via index) to an uninitialized package element. Provides compatibility with other

[PATCH 3.4 04/39] aacraid: prevent invalid pointer dereference

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mahesh Rajashekhara commit b4789b8e6be3151a955ade74872822f30e8cd914 upstream. It appears that driver runs into a problem here if fibsize is too small because we allocate user_srbcmd with

[PATCH 3.4 06/39] ACPICA: DeRefOf operator: Update to fully resolve FieldUnit and BufferField refs.

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Bob Moore commit 63660e05ec719613b518547b40a1c501c10f0bc4 upstream. Previously, references to these objects were resolved only to the actual FieldUnit or BufferField object. The correct

[PATCH 3.4 20/39] rt2x00: check if device is still available on rt2x00mac_flush()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit 5671ab05cf2a579218985ef56595387932d78ee4 upstream. Fix random kernel panic with below messages when remove dongle. [ 2212.355447] BUG: unable to handle kernel NULL

[PATCH 3.4 25/39] NFSv4: Fix a use-after-free situation in _nfs4_proc_getlk()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit a6f951ddbdfb7bd87d31a44f61abe202ed6ce57f upstream. In nfs4_proc_getlk(), when some error causes a retry of the call to _nfs4_proc_getlk(), we can end up with Oopses of

[PATCH 3.4 12/39] 8139cp: re-enable interrupts after tx timeout

3.4-stable review patch. If anyone has any objections, please let me know. -- From: David Woodhouse commit 01ffc0a7f1c1801a2354719dedbc32aff45b987d upstream. Recovery doesn't work too well if we leave interrupts disabled... Signed-off-by: David Woodhouse Acked-by: Francois

[PATCH]: exec: avoid propagating PF_NO_SETAFFINITY into userspace child

Userspace process doesn't want the PF_NO_SETAFFINITY, but its parent may be a kernel worker thread which has PF_NO_SETAFFINITY set, and this worker thread can do kernel_thread() to create the child. Clearing this flag in usersapce child to enable its migrating capability. Signed-off-by: Zhang Yi

[PATCH 3.4 24/39] ALSA: msnd: Avoid duplicated driver name

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 092f9cd16aac7d054af1755c945f37c1b33399e6 upstream. msnd_pinnacle.c is used for both snd-msnd-pinnacle and snd-msnd-classic drivers, and both should have different driver

[PATCH 3.4 26/39] nfsd: split up nfsd_setattr

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 818e5a22e907fbae75e9c1fd78233baec9fa64b6 upstream. Split out two helpers to make the code more readable and easier to verify for correctness. Signed-off-by: Christoph

[PATCH 3.4 27/39] nfsd: make sure to balance get/put_write_access

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 987da4791052fa298b7cfcde4dea9f6f2bbc786b upstream. Use a straight goto error label style in nfsd_setattr to make sure we always do the put_write_access call after we

[PATCH 3.4 11/39] can: c_can: Fix RX message handling, handle lost message before EOB

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Markus Pargmann commit 5d0f801a2ccec3b1fdabc3392c8d99ed0413d216 upstream. If we handle end of block messages with higher priority than a lost message, we can run into an endless interrupt

[PATCH 3.4 15/39] SUNRPC: dont map EKEYEXPIRED to EACCES in call_refreshresult

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Adamson commit f1ff0c27fd9987c59d707cd1a6b6c1fc3ae0a250 upstream. The NFS layer needs to know when a key has expired. This change also returns -EKEYEXPIRED to the application, and the

Re: [PATCH v2 01/10] PCI: Use device_release_driver in pci_stop_root_bus

On Monday, November 25, 2013 05:28:01 PM Yinghai Lu wrote: > To be consistent with change in > | PCI: Move device_del() from pci_stop_dev() to pci_destroy_dev() > > Use device_release_driver for root bus/hostbridge. > > Also use device_unregister() in pci_remove_root_bus() instead of >

[PATCH 3.4 29/39] hwmon: (lm90) Fix max6696 alarm handling

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit e41fae2b1ed8c78283d73651cd65be0228c0dd1c upstream. Bit 2 of status register 2 on MAX6696 (external diode 2 open) sets ALERT; the bit thus has to be listed in alert_alarms.

[PATCH 3.4 28/39] x86/microcode/amd: Tone down printk(), dont treat a missing firmware file as an error

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Renninger commit 11f918d3e2d3861b6931e97b3aa778e4984935aa upstream. Do it the same way as done in microcode_intel.c: use pr_debug() for missing firmware files. There seem to be CPUs

[PATCH 3.4 09/39] USB: mos7840: fix tiocmget error handling

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit a91ccd26e75235d86248d018fe3779732bcafd8d upstream. Make sure to return errors from tiocmget rather than rely on uninitialised stack data. Signed-off-by: Johan Hovold

[PATCH 3.4 14/39] SUNRPC handle EKEYEXPIRED in call_refreshresult

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Adamson commit eb96d5c97b0825d542e9c4ba5e0a22b519355166 upstream. Currently, when an RPCSEC_GSS context has expired or is non-existent and the users (Kerberos) credentials have also

[PATCH 3.4 30/39] block: fix race between request completion and timeout handling

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Moyer commit 4912aa6c11e6a5d910264deedbec2075c6f1bb73 upstream. crocode i2c_i801 i2c_core iTCO_wdt iTCO_vendor_support shpchp ioatdma dca be2net sg ses enclosure ext4 mbcache jbd2 sd_mod

[PATCH 3.10 12/80] ipc,shm: fix shm_file deletion races

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Greg Thelen commit a399b29dfbaaaf91162b2dc5a5875dd51bbfa2a1 upstream. When IPC_RMID races with other shm operations there's potential for use-after-free of the shm object's associated file

[PATCH 3.4 31/39] block: fix a probe argument to blk_register_region

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit a207f5937630dd35bd2550620bef416937a1365e upstream. The probe function is supposed to return NULL on failure (as we can see in kobj_lookup: kobj = probe(dev, index,

[PATCH 3.4 38/39] configfs: fix race between dentry put and lookup

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Junxiao Bi commit 76ae281f6307331aa063288edb6422ae99f435f0 upstream. A race window in configfs, it starts from one dentry is UNHASHED and end before configfs_d_iput is called. In this window,

[PATCH 3.10 14/80] drm/nva3-/disp: fix hda eld writing, needs to be padded

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Ilia Mirkin commit 02d69294a174d7cb6a76080b6d16971ca08728d4 upstream. Commits 0a9e2b959 (drm/nvd0/disp: move HDA codec setup to core) and a4feaf4ea (drm/nva3/disp: move hda codec handling to

[PATCH 3.4 17/39] exec: do not abuse ->cred_guard_mutex in threadgroup_lock()

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Oleg Nesterov commit e56fb2874015370e3b7f8d85051f6dce26051df9 upstream. threadgroup_lock() takes signal->cred_guard_mutex to ensure that thread_group_leader() is stable. This doesn't look

[PATCH 3.4 33/39] powerpc/vio: use strcpy in modalias_show

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Prarit Bhargava commit 411cabf79e684171669ad29a0628c400b4431e95 upstream. Commit e82b89a6f19bae73fb064d1b3dd91fcefbb478f4 used strcat instead of strcpy which can result in an overflow of

linux-next: manual merge of the staging tree with the staging.current tree

Hi Greg, Today's linux-next merge of the staging tree got conflicts in drivers/staging/tidspbridge/pmgr/cmm.c, drivers/staging/tidspbridge/pmgr/dbll.c, drivers/staging/tidspbridge/pmgr/dev.c, drivers/staging/tidspbridge/pmgr/dmm.c and drivers/staging/tidspbridge/pmgr/dspapi.c between commit

[PATCH 3.10 13/80] drm/nv50-/disp: remove dcb_outp_match call, and related variables

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Emil Velikov commit 9a7046d55f319b2dde5d2536cc2adb01ebdbe09e upstream. Unused and irrelavant since the code move of DP training/linkcontrol interrupt Signed-off-by: Emil Velikov

[PATCH 3.4 37/39] rt2800usb: slow down TX status polling

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit 36165fd5b00bf8163f89c21bb16a3e9834555b10 upstream. Polling TX statuses too frequently has two negative effects. First is randomly peek CPU usage, causing overall

[PATCH 3.4 19/39] perf/ftrace: Fix paranoid level for enabling function tracer

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt commit 12ae030d54ef250706da5642fc7697cc60ad0df7 upstream. The current default perf paranoid level is "1" which has "perf_paranoid_kernel()" return false, and giving any

[PATCH v7 0/3] x86, apic, kexec: Add disable_cpu_apic kernel parameter

This patch set is to allow kdump 2nd kernel to wake up multiple CPUs, a continueing work from: [PATCH v3 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP https://lkml.org/lkml/2013/10/16/300. At v4, basic design has changed. Now users need to figure out initial APIC ID of BSP in the 1st

[PATCH v7 1/2] x86, apic: Add disable_cpu_apicid kernel parameter

Add disable_cpu_apicid kernel parameter. To use this kernel parameter, specify an initial APIC ID of the corresponding CPU you want to disable. This is mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to

[PATCH 3.10 11/80] ipc,shm: correct error return value in shmctl (SHM_UNLOCK)

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Jesper Nilsson commit 3a72660b07d86d60457ca32080b1ce8c2b628ee2 upstream. Commit 2caacaa82a51 ("ipc,shm: shorten critical region for shmctl") restructured the ipc shm to shorten critical

[PATCH 3.4 18/39] include/linux/fs.h: disable preempt when acquire i_size_seqcount write lock

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Fan Du commit 74e3d1e17b2e11d175970b85acd44f5927000ba2 upstream. Two rt tasks bind to one CPU core. The higher priority rt task A preempts a lower priority rt task B which has already taken

[PATCH 3.10 10/80] can: c_can: Fix RX message handling, handle lost message before EOB

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Markus Pargmann commit 5d0f801a2ccec3b1fdabc3392c8d99ed0413d216 upstream. If we handle end of block messages with higher priority than a lost message, we can run into an endless interrupt

[PATCH] sh : Kill CONFIG_MTD_PARTITIONS

This patch removes CONFIG_MTD_PARTITIONS in config files for sh. Because CONFIG_MTD_PARTITIONS was removed by commit 6a8a98b22b10f1560d5f90aded4a54234b9b2724. Signed-off-by: Eunbong Song --- arch/sh/configs/ap325rxa_defconfig|1 - arch/sh/configs/apsh4a3a_defconfig|1 -

[PATCH 3.4 16/39] Nest rename_lock inside vfsmount_lock

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 7ea600b5314529f9d1b9d6d3c41cb26fce6a7a4a upstream. ... lest we get livelocks between path_is_under() and d_path() and friends. The thing is, wrt fairness lglocks are more

[PATCH 3.10 01/80] ACPICA: DeRefOf operator: Update to fully resolve FieldUnit and BufferField refs.

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Bob Moore commit 63660e05ec719613b518547b40a1c501c10f0bc4 upstream. Previously, references to these objects were resolved only to the actual FieldUnit or BufferField object. The correct

[PATCH v7 2/2] Documentation, x86, apic, kexec: Add disable_cpu_apicid kernel parameter

Add disable_cpu_apicid kernel parameter to disable the CPU with the specified number of initial APIC ID, mostly used for the kdump 2nd kernel to disable BSP to wake up multiple CPUs without causing system reset or hang due to sending INIT from AP to BSP. Signed-off-by: HATAYAMA Daisuke ---

[PATCH 3.10 20/80] perf/ftrace: Fix paranoid level for enabling function tracer

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt commit 12ae030d54ef250706da5642fc7697cc60ad0df7 upstream. The current default perf paranoid level is "1" which has "perf_paranoid_kernel()" return false, and giving any

[PATCH 3.10 15/80] SUNRPC: dont map EKEYEXPIRED to EACCES in call_refreshresult

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Andy Adamson commit f1ff0c27fd9987c59d707cd1a6b6c1fc3ae0a250 upstream. The NFS layer needs to know when a key has expired. This change also returns -EKEYEXPIRED to the application, and the

[PATCH 3.10 19/80] PCI: Support PCIe Capability Slot registers only for ports with slots

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit 6d3a1741f1e648cfbd5a0cc94477a0d5004c6f5e upstream. Previously we allowed callers to access Slot Capabilities, Status, and Control for Root Ports even if the Root Port did

[PATCH 3.10 17/80] PCI: Allow PCIe Capability link-related register access for switches

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit d3694d4fa3f44f6a295f8ab064937c8a1549d174 upstream. Every PCIe device has a link, except Root Complex Integrated Endpoints and Root Complex Event Collectors. Previously

[PATCH 3.10 03/80] aacraid: prevent invalid pointer dereference

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Mahesh Rajashekhara commit b4789b8e6be3151a955ade74872822f30e8cd914 upstream. It appears that driver runs into a problem here if fibsize is too small because we allocate user_srbcmd with

[PATCH 3.4 39/39] cris: media platform drivers: fix build

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 72a0c5571351f5184195754d23db3e14495b2080 upstream. On cris arch, the functions below aren't defined: drivers/media/platform/sh_veu.c: In function

[PATCH 3.10 18/80] PCI: Remove PCIe Capability version checks

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit c8b303d0206b28c4ff3aecada47108d1655ae00f upstream. Previously we relied on the PCIe r3.0, sec 7.8, spec language that says "For Functions that do not implement the [Link,

[PATCH 3.10 04/80] ACPICA: Return error if DerefOf resolves to a null package element.

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Bob Moore commit a50abf4842dd7d603a2ad6dcc7f1467fd2a66f03 upstream. Disallow the dereference of a reference (via index) to an uninitialized package element. Provides compatibility with other

[PATCH 3.10 16/80] sched, idle: Fix the idle polling state logic

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit ea8117478918a4734586d35ff530721b682425be upstream. Mike reported that commit 7d1a9417 ("x86: Use generic idle loop") regressed several workloads and caused excessive

[PATCH 3.10 07/80] can: kvaser_usb: fix usb endpoints detection

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Olivier Sobrie commit 896e23bd04ea50a146dffd342e2f96180f0812a5 upstream. Some devices, like the Kvaser Memorator Professional, have several bulk in endpoints. Only the first one found must be

[PATCH 3.10 22/80] ACPI / video: Quirk initial backlight level 0

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Aaron Lu commit 2c62333a408f5badd2d2ffd7177f95deeccc5ca4 upstream. Some firmware doesn't initialize initial backlight level to a proper value and _BQC will return 0 on first time evaluation.

[PATCH 3.4 36/39] SUNRPC: Fix a data corruption issue when retransmitting RPC calls

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit a6b31d18b02ff9d7915c5898c9b5ca41a798cd73 upstream. The following scenario can cause silent data corruption when doing NFS writes. It has mainly been observed when doing

[PATCH 3.4 35/39] powerpc/signals: Mark VSX not saved with small contexts

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit c13f20ac48328b05cd3b8c19e31ed6c132b44b42 upstream. The VSX MSR bit in the user context indicates if the context contains VSX state. Currently we set this when the

[PATCH 3.4 34/39] powerpc/powernv: Add PE to its own PELTV

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Gavin Shan commit 631ad691b5818291d89af9be607d2fe40be0886e upstream. We need add PE to its own PELTV. Otherwise, the errors originated from the PE might contribute to other PEs. In the result,

[PATCH 3.10 00/80] 3.10.21-stable review

This is the start of the stable review cycle for the 3.10.21 release. There are 80 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Fri Nov 29 00:56:25 UTC 2013. Anything

[PATCH 3.10 09/80] crypto: s390 - Fix aes-cbc IV corruption

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu commit f262f0f5cad0c9eca61d1d383e3b67b57dcbe5ea upstream. The cbc-aes-s390 algorithm incorrectly places the IV in the tfm data structure. As the tfm is shared between multiple

[PATCH 3.10 06/80] USB: mos7840: fix tiocmget error handling

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit a91ccd26e75235d86248d018fe3779732bcafd8d upstream. Make sure to return errors from tiocmget rather than rely on uninitialised stack data. Signed-off-by: Johan Hovold

[PATCH 3.10 08/80] crypto: ansi_cprng - Fix off by one error in non-block size request

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Neil Horman commit 714b33d15130cbb5ab426456d4e3de842d6c5b8a upstream. Stephan Mueller reported to me recently a error in random number generation in the ansi cprng. If several small requests

[PATCH 3.10 05/80] ACPICA: Fix for a Store->ArgX when ArgX contains a reference to a field.

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Bob Moore commit 4be4be8fee2ee99a52f94f90d03d2f287ee1db86 upstream. This change fixes a problem where a Store operation to an ArgX object that contained a reference to a field object did not

[PATCH 3.10 21/80] ACPI / EC: Ensure lock is acquired before accessing ec struct members

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Puneet Kumar commit 36b15875a7819a2ec4cb5748ff7096ad7bd86cbb upstream. A bug was introduced by commit b76b51ba0cef ('ACPI / EC: Add more debug info and trivial code cleanup') that erroneously

[PATCH 3.10 02/80] libertas: potential oops in debugfs

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 upstream. If we do a zero size allocation then it will oops. Also we can't be sure the user passes us a NUL terminated string so

[PATCH 3.10 24/80] ACPI / hotplug: Do not execute "insert in progress" _OST

3.10-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" commit 176a88d79d6b5aebabaff16734e8b3107efcaaad upstream. According to the ACPI spec (5.0, Section 6.3.5), the "Device insertion in progress (pending)" (0x80) _OST status

[PATCH 3.10 23/80] ACPI / hotplug: Fix handle_root_bridge_removal()

3.10-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" commit 2441191a19039002b2c454a261fb45986df15184 upstream. It is required to do get_device() on the struct acpi_device in question before passing it to

[PATCH 3.10 28/80] rt2x00: fix HT TX descriptor settings regression

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit 3d8bfe141be8e5c21261fc63da8e7964d44f2645 upstream. Since: commit 36323f817af0376c78612cfdab714b0feb05fea5 Author: Thomas Huehn Date: Mon Jul 23 21:33:42 2012

[PATCH 3.10 30/80] exec/ptrace: fix get_dumpable() incorrect tests

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit d049f74f2dbe71354d43d393ac3a188947811348 upstream. The get_dumpable() return value is not boolean. Most users of the function actually want to be testing for

[PATCH 3.10 27/80] rt2x00: rt2800lib: fix VGC adjustment for RT5592

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Gabor Juhos commit 0beb1bbf19c72f17809e42b8f33522a55c2cc18c upstream. In commit 3d81535ea5940446510a8a5cee1c6ad23c90c753 (rt2800: 5592: add chip specific vgc calculations) the

[PATCH] mn10300 : Kill CONFIG_MTD_PARTITIONS

This patch removes CONFIG_MTD_PARTITIONS in config files for mn10300. Because CONFIG_MTD_PARTITIONS was removed by commit 6a8a98b22b10f1560d5f90aded4a54234b9b2724. Signed-off-by: Eunbong Song --- arch/mn10300/configs/asb2303_defconfig |1 - arch/mn10300/configs/asb2364_defconfig |1 -

[PATCH 3.10 31/80] ALSA: 6fire: Fix probe of multiple cards

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 9b389a8a022110b4bc055a19b888283544d9eba6 upstream. The probe code of snd-usb-6fire driver overrides the devices[] pointer wrongly without checking whether it's already

[PATCH 3.10 35/80] ALSA: hda - Add support of ALC255 codecs

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 1d04c9de5c76df113e4af7120feb53c628b5efcc upstream. It's just another variant of ALC269 & co. Signed-off-by: Kailang Yang Signed-off-by: Takashi Iwai Signed-off-by: Greg

[PATCH 3.10 32/80] ALSA: compress: fix drain calls blocking other compress functions

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Vinod Koul commit 917f4b5cba78980a527098a910d94139d3e82c8d upstream. The drain and drain_notify callback were blocked by low level driver untill the draining was complete. Due to this being

[PATCH 3.10 25/80] rt2x00: fix a crash bug in the HT descriptor handling fix

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit b4089d6d8e71a7293e2192025dfa507a04f661c4 upstream. Commit "rt2x00: fix HT TX descriptor settings regression" assumes that the control parameter to rt2x00mac_tx is always

[PATCH 3.10 36/80] ALSA: hda - Enable SPDIF for Acer TravelMate 6293

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 24eff328f65c8ef352c90b6adb7c2f39eb94205d upstream. BIOS on Acer TravelMate 6293 doesn't set up the SPDIF output pin correctly as default, so enable it via a fixup entry.

[PATCH 3.10 34/80] ALSA: msnd: Avoid duplicated driver name

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 092f9cd16aac7d054af1755c945f37c1b33399e6 upstream. msnd_pinnacle.c is used for both snd-msnd-pinnacle and snd-msnd-classic drivers, and both should have different driver

[PATCH 3.10 48/80] NFSv4: Fix a use-after-free situation in _nfs4_proc_getlk()

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit a6f951ddbdfb7bd87d31a44f61abe202ed6ce57f upstream. In nfs4_proc_getlk(), when some error causes a retry of the call to _nfs4_proc_getlk(), we can end up with Oopses of

[PATCH 3.10 37/80] ALSA: hda - Make sure mute LEDs stay on during runtime suspend (Realtek)

3.10-stable review patch. If anyone has any objections, please let me know. -- From: David Henningsson commit d5b6b65e75ce607c2734227524e11574317a1c1a upstream. Some HP machines with Realtek codecs have mute LEDs connected to VREF pins. However when these go into runtime

[PATCH 3.10 26/80] rt2x00: check if device is still available on rt2x00mac_flush()

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit 5671ab05cf2a579218985ef56595387932d78ee4 upstream. Fix random kernel panic with below messages when remove dongle. [ 2212.355447] BUG: unable to handle kernel NULL

[PATCH 3.10 49/80] NFSv4: fix NULL dereference in open recover

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Weston Andros Adamson commit f494a6071d31e3294a3b51ad7a3684f983953f9f upstream. _nfs4_opendata_reclaim_to_nfs4_state doesn't expect to see a cached open CLAIM_PREVIOUS, but this can happen.

[PATCH 3.10 54/80] nfsd: split up nfsd_setattr

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 818e5a22e907fbae75e9c1fd78233baec9fa64b6 upstream. Split out two helpers to make the code more readable and easier to verify for correctness. Signed-off-by:

[PATCH 3.10 53/80] nfsd: return better errors to exportfs

3.10-stable review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 427d6c6646d868fbd3094e7e2e1644d480cd9204 upstream. Someone noticed exportfs happily accepted exports that would later be rejected when mountd tried to give them to

[PATCH 3.10 29/80] Revert "ima: policy for RAMFS"

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Mimi Zohar commit 08de59eb144d7c41351a467442f898d720f0f15f upstream. This reverts commit 4c2c392763a682354fac65b6a569adec4e4b5387. Everything in the initramfs should be measured and

[PATCH 3.10 52/80] NFSv4: Fix state reference counting in _nfs4_opendata_reclaim_to_nfs4_state

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit d49f042aeec99c5f87160bb52dd52088b1051311 upstream. Currently, if the call to nfs_refresh_inode fails, then we end up leaking a reference count, due to the call to

[PATCH 3.10 55/80] nfsd: make sure to balance get/put_write_access

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 987da4791052fa298b7cfcde4dea9f6f2bbc786b upstream. Use a straight goto error label style in nfsd_setattr to make sure we always do the put_write_access call after we

[PATCH] m68k : Kill CONFIG_MTD_PARTITIONS

This patch removes CONFIG_MTD_PARTITIONS in config files for m68k. Because CONFIG_MTD_PARTITIONS was removed by commit 6a8a98b22b10f1560d5f90aded4a54234b9b2724. Signed-off-by: Eunbong Song --- arch/m68k/configs/m5208evb_defconfig |1 - arch/m68k/configs/m5249evb_defconfig |1 -

[PATCH 3.10 56/80] x86/microcode/amd: Tone down printk(), dont treat a missing firmware file as an error

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Renninger commit 11f918d3e2d3861b6931e97b3aa778e4984935aa upstream. Do it the same way as done in microcode_intel.c: use pr_debug() for missing firmware files. There seem to be CPUs

[PATCH 3.10 33/80] ALSA: compress: fix drain calls blocking other compress functions (v6)

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Vinod Koul commit f44f2a5417b2968a8724b352cc0b2545a6bcb1f4 upstream. The drain and drain_notify callback were blocked by low level driver until the draining was complete. Due to this being

[PATCH 3.10 57/80] KVM: x86: fix emulation of "movzbl %bpl, %eax"

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit daf727225b8abfdfe424716abac3d15a3ac5626a upstream. When I was looking at RHEL5.9's failure to start with unrestricted_guest=0/emulate_invalid_guest_state=1, I got it

[PATCH 3.10 58/80] ftrace/x86: skip over the breakpoint for ftrace caller

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Hao commit ab4ead02ec235d706d0611d8741964628291237e upstream. In commit 8a4d0a687a59 "ftrace: Use breakpoint method to update ftrace caller", we choose to use breakpoint method to

[PATCH 3.10 59/80] KVM: IOMMU: hva align mapping page size

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Greg Edwards commit 27ef63c7e97d1e585051c03f8d44cc887f34 upstream. When determining the page size we could use to map with the IOMMU, the page size should also be aligned with the hva,

[PATCH 3.10 50/80] NFSv4: dont fail on missing fattr in open recover

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Weston Andros Adamson commit a43ec98b72aae3e330f0673438f58316c3769b84 upstream. This is an unneeded check that could cause the client to fail to recover opens. Signed-off-by: Weston Andros

<    1   2   3   4   5   6   7   8   9   10   >