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 rfkill_gpio_platfor
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]
arch/hexagon/include/ua
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 ob
(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 symb
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 processe
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->dev);
>>
>> - down_write(&pci_bus_sem);
>> - list_del(&dev->bus_list);
>> - up_write(&pci_bus_sem);
>> -
>> - pci_free_re
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 PM
'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: 'packet_i
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 01
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 appraised,
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 occup
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 sma
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 I
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 non-SUID_DUMP_USE
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 AC
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 fibsiz
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 behavio
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 poi
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 th
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 R
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
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
nam
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
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 go
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 loop.
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 info
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
> device_del
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.
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 out
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
Signe
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 expire
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
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 (sh
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, data);
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,
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 c
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 nice
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 newlin
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 cb4506
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
Signed-off-b
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 system
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 operation
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 k
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 B
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 region
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 th
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 loop
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 -
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 simila
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 behavi
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
---
Docum
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 operatio
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 inf
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
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 we
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 fibsi
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 'sh_veu_reg_rea
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,
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 A
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 resc
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
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. W
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 d
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 proces
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,
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 receiv
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 thre
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
Sign
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 a
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 c
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
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
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 c
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 acpi_bus_hot_remove_d
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 +0200
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 non-SUID_DUMP_US
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 rt2800_link_tune
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 -
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 occu
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
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 in
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 n
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.
R
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
na
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 t
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 suspe
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 po
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. An
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: Christoph
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 the
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 appraised
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 nfs4_g
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 g
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 -
arch/m6
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 ou
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 inv
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 worki
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 update
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, not
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 Ad
101 - 200 of 951 matches
Mail list logo