3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Colin King
commit d505ad1d66c9cd31db5ab0d2c7bcb2a47e5bb29e upstream.
Building with clang:
CC arch/x86/kernel/rtc.o
arch/x86/kernel/rtc.c:173:29: warning:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Colin King
commit d505ad1d66c9cd31db5ab0d2c7bcb2a47e5bb29e upstream.
Building with clang:
CC arch/x86/kernel/rtc.o
arch/x86/kernel/rtc.c:173:29: warning: duplicate 'const' declaration
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit c6e83cac3eda5f7dd32ee1453df2f7abb5c6cd46 upstream.
pm_genpd_remove_subdomain() iterates over domain's master_links list and
removes matching
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit c6e83cac3eda5f7dd32ee1453df2f7abb5c6cd46 upstream.
pm_genpd_remove_subdomain() iterates over domain's master_links list and
removes matching element thus it has to
Arnd, Cyrille,
I am working on fixing spi-bcm-qspi.c as per Cyrill's suggestion as
mentioned here : https://patchwork.kernel.org/patch/9624585/.
And remove the use of SPINOR_OP_READ* and there by remove need to
include spi-nor.h.
Thanks
Kamal
On Fri, Jul 21, 2017 at 6:00 PM, Arnd Bergmann
Arnd, Cyrille,
I am working on fixing spi-bcm-qspi.c as per Cyrill's suggestion as
mentioned here : https://patchwork.kernel.org/patch/9624585/.
And remove the use of SPINOR_OP_READ* and there by remove need to
include spi-nor.h.
Thanks
Kamal
On Fri, Jul 21, 2017 at 6:00 PM, Arnd Bergmann
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Pavel Shilovsky
Commit 99e214e006cf ("Handle mismatched open calls") was applied with
errors that result in initializing handle_cancelled_mid callback twice
in
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Pavel Shilovsky
Commit 99e214e006cf ("Handle mismatched open calls") was applied with
errors that result in initializing handle_cancelled_mid callback twice
in smb21_operations and
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit bd664f6b3e376a8ef4990f87d08271cc2d01ba9a upstream.
I made the mistake of upgrading my desktop to the new Fedora 26 that
comes with
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit bd664f6b3e376a8ef4990f87d08271cc2d01ba9a upstream.
I made the mistake of upgrading my desktop to the new Fedora 26 that
comes with gcc-7.1.1.
There's nothing wrong per
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Miaoqing Pan
commit bde717ab473668377fc65872398a102d40cb2d58 upstream.
The hard coded register 0x9864 and 0x9924 are invalid
for ar9300 chips.
Signed-off-by:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Miaoqing Pan
commit bde717ab473668377fc65872398a102d40cb2d58 upstream.
The hard coded register 0x9864 and 0x9924 are invalid
for ar9300 chips.
Signed-off-by: Miaoqing Pan
Signed-off-by:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 20777bc57c346b6994f465e0d8261a7fbf213a09 upstream.
Commit 7eda8b8e9677 ("NFC: Use IDR library to assing NFC devices IDs")
moved device-id allocation and
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 20777bc57c346b6994f465e0d8261a7fbf213a09 upstream.
Commit 7eda8b8e9677 ("NFC: Use IDR library to assing NFC devices IDs")
moved device-id allocation and struct-device
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Jurczyk
commit a0323b979f81ad2deb2c8836eab506534891876a upstream.
Check that the NFC_ATTR_TARGET_INDEX and NFC_ATTR_PROTOCOLS attributes (in
addition to
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Jurczyk
commit a0323b979f81ad2deb2c8836eab506534891876a upstream.
Check that the NFC_ATTR_TARGET_INDEX and NFC_ATTR_PROTOCOLS attributes (in
addition to NFC_ATTR_DEVICE_INDEX) are
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Denys Vlasenko
commit 3876488444e71238e287459c39d7692b6f718c3e upstream.
Suggested by Andy.
Suggested-by: Andy Lutomirski
Signed-off-by: Denys
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Denys Vlasenko
commit 3876488444e71238e287459c39d7692b6f718c3e upstream.
Suggested by Andy.
Suggested-by: Andy Lutomirski
Signed-off-by: Denys Vlasenko
Acked-by: Linus Torvalds
Cc: Alexei
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Jurczyk
commit 608c4adfcabab220142ee335a2a003ccd1c0b25b upstream.
Fix the sockaddr length verification in the connect() handler of NFC/LLCP
sockets, to compare
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Jurczyk
commit 608c4adfcabab220142ee335a2a003ccd1c0b25b upstream.
Fix the sockaddr length verification in the connect() handler of NFC/LLCP
sockets, to compare against the size of the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maurizio Lombardi
commit 62e62ffd95539b9220894a7900a619e0f3ef4756 upstream.
The enclosure_add_device() function should fail if it can't create the
relevant sysfs links.
This patchset expands set-timer-lat to cover one-shot timers. This is
inspired by a recent regression in the -stable tree, which caused one-shot
alarm timers to repeat at a 1 ns interval.
The first patch adjusts how early-firing timers are reported, so faulty
kernels won't cause the test to spam
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maurizio Lombardi
commit 62e62ffd95539b9220894a7900a619e0f3ef4756 upstream.
The enclosure_add_device() function should fail if it can't create the
relevant sysfs links.
Signed-off-by:
This patchset expands set-timer-lat to cover one-shot timers. This is
inspired by a recent regression in the -stable tree, which caused one-shot
alarm timers to repeat at a 1 ns interval.
The first patch adjusts how early-firing timers are reported, so faulty
kernels won't cause the test to spam
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
commit 8c7fbe5795a016259445a61e072eb0118aaf6a61 upstream.
Commit 3876488444e7 ("include/stddef.h: Move offsetofend() from vfio.h
to a generic kernel header")
Rather than printing an error inside the alarm signal handler, set a
flag that we check later. This keeps the test from spamming the console
every time the alarm fires early. It also fixes the test exiting with
error code 0 if this was the only test failure.
Signed-off-by: Greg Hackmann
Rather than printing an error inside the alarm signal handler, set a
flag that we check later. This keeps the test from spamming the console
every time the alarm fires early. It also fixes the test exiting with
error code 0 if this was the only test failure.
Signed-off-by: Greg Hackmann
---
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
commit 8c7fbe5795a016259445a61e072eb0118aaf6a61 upstream.
Commit 3876488444e7 ("include/stddef.h: Move offsetofend() from vfio.h
to a generic kernel header") added offsetofend
These testcases are motivated by a recent alarmtimer regression, which
caused one-shot CLOCK_{BOOTTIME,REALTIME}_ALARM timers to become
periodic timers.
The new testcases are very similar to the existing testcases for
repeating timers. But rather than waiting for 5 alarms, they wait for 5
These testcases are motivated by a recent alarmtimer regression, which
caused one-shot CLOCK_{BOOTTIME,REALTIME}_ALARM timers to become
periodic timers.
The new testcases are very similar to the existing testcases for
repeating timers. But rather than waiting for 5 alarms, they wait for 5
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit b556b15dc04e9b9b98790f04c21acf5e24f994b2 upstream.
of_genpd_del_provider() iterates over list of domain provides and
removes matching element thus
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Jurczyk
commit f6a5885fc4d68e7f25ffb42b9d8d80aebb3bacbb upstream.
Verify that the caller-provided sockaddr structure is large enough to
contain the sa_family
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Satish Babu Patakokila
commit 01b8cedfd0422326caae308641dcadaa85e0ca72 upstream.
Currently compress driver hardcodes direction as playback to get
substream from the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit b556b15dc04e9b9b98790f04c21acf5e24f994b2 upstream.
of_genpd_del_provider() iterates over list of domain provides and
removes matching element thus it has to use
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Jurczyk
commit f6a5885fc4d68e7f25ffb42b9d8d80aebb3bacbb upstream.
Verify that the caller-provided sockaddr structure is large enough to
contain the sa_family field, before accessing
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Satish Babu Patakokila
commit 01b8cedfd0422326caae308641dcadaa85e0ca72 upstream.
Currently compress driver hardcodes direction as playback to get
substream from the stream. This results in
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 87c4b83e0fe234a1f0eed131ab6fa232036860d5 upstream.
The mcrf emulation code was using the CR field number directly as the shift
value, without taking
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 87c4b83e0fe234a1f0eed131ab6fa232036860d5 upstream.
The mcrf emulation code was using the CR field number directly as the shift
value, without taking into account that
On 07/25/2017 04:46 PM, Serge E. Hallyn wrote:
On Tue, Jul 25, 2017 at 04:11:29PM -0400, Stefan Berger wrote:
On 07/25/2017 03:48 PM, Mimi Zohar wrote:
On Tue, 2017-07-25 at 12:08 -0700, James Bottomley wrote:
On Tue, 2017-07-25 at 14:04 -0500, Serge E. Hallyn wrote:
On Tue, Jul 25, 2017 at
On 07/25/2017 04:46 PM, Serge E. Hallyn wrote:
On Tue, Jul 25, 2017 at 04:11:29PM -0400, Stefan Berger wrote:
On 07/25/2017 03:48 PM, Mimi Zohar wrote:
On Tue, 2017-07-25 at 12:08 -0700, James Bottomley wrote:
On Tue, 2017-07-25 at 14:04 -0500, Serge E. Hallyn wrote:
On Tue, Jul 25, 2017 at
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Miaoqing Pan
commit cf8ce1ea61b75712a154c93e40f2a5af2e4dd997 upstream.
One scenario that could lead to UAF is two threads writing
simultaneously to the "tx99" debug
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Miaoqing Pan
commit cf8ce1ea61b75712a154c93e40f2a5af2e4dd997 upstream.
One scenario that could lead to UAF is two threads writing
simultaneously to the "tx99" debug file. One of them would
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Yoshihiro Shimoda
commit 59a0879a0e17b2e43ecdc5e3299da85b8410d7ce upstream.
This patch fixes an issue that some registers may be not initialized
after resume
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Yoshihiro Shimoda
commit 59a0879a0e17b2e43ecdc5e3299da85b8410d7ce upstream.
This patch fixes an issue that some registers may be not initialized
after resume if the USBHSF_RUNTIME_PWCTRL is
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit f9c79bc05a2a91f4fba8bfd653579e066714b1ec upstream.
The function flush_signals clears all pending signals for the process. It
may be used by kernel
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 64e756c55aa46fc18fd53e8f3598b73b528d8637 upstream.
>From POWER4 onwards, mfocrf() only places the specified CR field into
the destination GPR, and the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit f9c79bc05a2a91f4fba8bfd653579e066714b1ec upstream.
The function flush_signals clears all pending signals for the process. It
may be used by kernel threads when we need
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 64e756c55aa46fc18fd53e8f3598b73b528d8637 upstream.
>From POWER4 onwards, mfocrf() only places the specified CR field into
the destination GPR, and the rest of it is set
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver O'Halloran
commit 2400fd822f467cb4c886c879d8ad99feac9cf319 upstream.
The workaround for the CELL timebase bug does not correctly mark cr0 as
being clobbered. This
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver O'Halloran
commit 2400fd822f467cb4c886c879d8ad99feac9cf319 upstream.
The workaround for the CELL timebase bug does not correctly mark cr0 as
being clobbered. This means GCC doesn't
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 01e6a61aceb82e13bec29502a8eb70d9574f97ad upstream.
Although it's not documented anywhere, there is an expectation that
atomic64_inc_not_zero()
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 01e6a61aceb82e13bec29502a8eb70d9574f97ad upstream.
Although it's not documented anywhere, there is an expectation that
atomic64_inc_not_zero() returns a result which
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Xiao Ni
commit b5d27718f38843a74552e9a93d32e2391fd3999f upstream.
The raid5 md device is created by the disks which we don't use the total size.
For example,
the size of the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Xiao Ni
commit b5d27718f38843a74552e9a93d32e2391fd3999f upstream.
The raid5 md device is created by the disks which we don't use the total size.
For example,
the size of the device is 5G and
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit 446230f52a5bef593554510302465eabab45a372 upstream.
When us->extra is null the driver is not initialized, however, a
later call to
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit a54408d0a004757789863d74e29c2297edae0b4d upstream.
A uncleared PLC (port link change) bit will prevent furuther port event
interrupts for
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit 446230f52a5bef593554510302465eabab45a372 upstream.
When us->extra is null the driver is not initialized, however, a
later call to osd200_scsi_to_ata is made that
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit a54408d0a004757789863d74e29c2297edae0b4d upstream.
A uncleared PLC (port link change) bit will prevent furuther port event
interrupts for that port. Leaving it uncleared
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit fe855789d605590e57f9cd968d85ecce46f5c3fd upstream.
Add device-id entry for DATECS FP-2000 fiscal printer needing the
NO_UNION_NORMAL quirk.
Reported-by:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit fe855789d605590e57f9cd968d85ecce46f5c3fd upstream.
Add device-id entry for DATECS FP-2000 fiscal printer needing the
NO_UNION_NORMAL quirk.
Reported-by: Anton Avramov
On Sat, Apr 1, 2017 at 7:18 AM, Wu Hao wrote:
Hi Hao,
> On Fri, Mar 31, 2017 at 12:01:13PM -0700, matthew.gerl...@linux.intel.com
> wrote:
>> On Fri, 31 Mar 2017, Wu Hao wrote:
>> >On Fri, Mar 31, 2017 at 08:09:09AM +0200, Greg KH wrote:
>> >>On Thu, Mar 30, 2017 at
On Sat, Apr 1, 2017 at 7:18 AM, Wu Hao wrote:
Hi Hao,
> On Fri, Mar 31, 2017 at 12:01:13PM -0700, matthew.gerl...@linux.intel.com
> wrote:
>> On Fri, 31 Mar 2017, Wu Hao wrote:
>> >On Fri, Mar 31, 2017 at 08:09:09AM +0200, Greg KH wrote:
>> >>On Thu, Mar 30, 2017 at 08:08:02PM +0800, Wu Hao
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 4b895868bb2da60a386a17cde3bf9ecbc70c79f4 upstream.
This off by one in stream_id indexing caused NULL pointer dereference and
soft lockup on
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 4b895868bb2da60a386a17cde3bf9ecbc70c79f4 upstream.
This off by one in stream_id indexing caused NULL pointer dereference and
soft lockup on machines with USB attached
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej W. Rozycki
commit a9db101b735a9d49295326ae41f610f6da62b08c upstream.
Complement commit fb6883e5809c ("MIPS: microMIPS: Support handling of
delay slots.") and actually
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej W. Rozycki
commit a9db101b735a9d49295326ae41f610f6da62b08c upstream.
Complement commit fb6883e5809c ("MIPS: microMIPS: Support handling of
delay slots.") and actually decode the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej W. Rozycki
commit 13769ebad0c42738831787e27c7c7f982e7da579 upstream.
Terminate FPU emulation immediately whenever an ISA mode switch has been
observed. This is so
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej W. Rozycki
commit 13769ebad0c42738831787e27c7c7f982e7da579 upstream.
Terminate FPU emulation immediately whenever an ISA mode switch has been
observed. This is so that we do not
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej W. Rozycki
commit 11a3799dbeb620bf0400b1fda5cc2c6bea55f20a upstream.
Fix a regression introduced with commit fb6883e5809c ("MIPS: microMIPS:
Support handling of delay
On 07/25/2017 03:21 PM, Konrad Rzeszutek Wilk wrote:
> Hi Jens,
>
> Please git pull in your branch "for-linus" the following
> branch which is based on 765e40b675a9566459ddcb8358ad16f3b8344bbe
> "blk-mq: map queues to all present CPUs":
>
>
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej W. Rozycki
commit 11a3799dbeb620bf0400b1fda5cc2c6bea55f20a upstream.
Fix a regression introduced with commit fb6883e5809c ("MIPS: microMIPS:
Support handling of delay slots.") and
On 07/25/2017 03:21 PM, Konrad Rzeszutek Wilk wrote:
> Hi Jens,
>
> Please git pull in your branch "for-linus" the following
> branch which is based on 765e40b675a9566459ddcb8358ad16f3b8344bbe
> "blk-mq: map queues to all present CPUs":
>
>
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 096f41d3a8fcbb8dde7f71379b1ca85fe213eded upstream.
The parsing of sadb_x_ipsecrequest is broken in a number of ways.
First of all we're not
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit 096f41d3a8fcbb8dde7f71379b1ca85fe213eded upstream.
The parsing of sadb_x_ipsecrequest is broken in a number of ways.
First of all we're not verifying
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jaegeuk Kim
commit c925dc162f770578ff4a65ec9b08270382dba9e6 upstream.
This patch copies commit b7f8a09f80:
"btrfs: Don't clear SGID when inheriting ACLs" written by Jan.
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jaegeuk Kim
commit c925dc162f770578ff4a65ec9b08270382dba9e6 upstream.
This patch copies commit b7f8a09f80:
"btrfs: Don't clear SGID when inheriting ACLs" written by Jan.
Fixes:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 5d6dee80a1e94cc284d03e06d930e60e8d3ecf7d upstream.
At the point where the kvm-vfio pseudo device wants to release its
vfio group reference,
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 5d6dee80a1e94cc284d03e06d930e60e8d3ecf7d upstream.
At the point where the kvm-vfio pseudo device wants to release its
vfio group reference, we can't always acquire a
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 2ec420b26f7b6ff332393f0bb5a7d245f7ad87f0 upstream.
The inline asm retry check in the MIPS_ATOMIC_SET operation of the
sysmips system call has been
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 2ec420b26f7b6ff332393f0bb5a7d245f7ad87f0 upstream.
The inline asm retry check in the MIPS_ATOMIC_SET operation of the
sysmips system call has been backwards since commit
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Chen Yu
commit e60514bd4485c0c7c5a7cf779b200ce0b95c70d6 upstream.
Currently we saw a lot of "No irq handler" errors during hibernation, which
caused the system hang
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Chen Yu
commit e60514bd4485c0c7c5a7cf779b200ce0b95c70d6 upstream.
Currently we saw a lot of "No irq handler" errors during hibernation, which
caused the system hang finally:
ata4.00: qc
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 4f32a39d49b25eaa66d2420f1f03d371ea4cd906 upstream.
The sys_exit trace event takes a single return value for the system
call, which MIPS passes the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 4f32a39d49b25eaa66d2420f1f03d371ea4cd906 upstream.
The sys_exit trace event takes a single return value for the system
call, which MIPS passes the value of the $v0 (result)
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Seunghun Han
commit dad5ab0db8deac535d03e3fe3d8f2892173fa6a4 upstream.
The bus_irq argument of mp_override_legacy_irq() is used as the index into
the isa_irq_to_gsi[]
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 811642d8d8a82c0cce8dc2debfdaf23c5a144839 upstream.
If vfio_iommu_group_notifier() acquires a group reference and that
reference becomes the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Seunghun Han
commit dad5ab0db8deac535d03e3fe3d8f2892173fa6a4 upstream.
The bus_irq argument of mp_override_legacy_irq() is used as the index into
the isa_irq_to_gsi[] array. The bus_irq
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 811642d8d8a82c0cce8dc2debfdaf23c5a144839 upstream.
If vfio_iommu_group_notifier() acquires a group reference and that
reference becomes the last reference to the group,
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 49955d84cd9ccdca5a16a495e448e1a06fad9e49 upstream.
The MIPS sysmips system call handler may return directly from the
MIPS_ATOMIC_SET case
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 49955d84cd9ccdca5a16a495e448e1a06fad9e49 upstream.
The MIPS sysmips system call handler may return directly from the
MIPS_ATOMIC_SET case (mips_atomic_set()) to
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stephen Boyd
commit 7a3b7cd332db08546f3cdd984f11773e0d1999e7 upstream.
The ULPI bus can be built as a module, and it will soon be
calling these functions when it
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stephen Boyd
commit 7a3b7cd332db08546f3cdd984f11773e0d1999e7 upstream.
The ULPI bus can be built as a module, and it will soon be
calling these functions when it supports probing devices from
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit cc89684c9a265828ce061037f1f79f4a68ccd3f7 upstream.
Since commit bafc9b754f75 ("vfs: More precise tests in d_invalidate")
in v3.18, a return of '0' from
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit cc89684c9a265828ce061037f1f79f4a68ccd3f7 upstream.
Since commit bafc9b754f75 ("vfs: More precise tests in d_invalidate")
in v3.18, a return of '0' from ->d_revalidate() will
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Andersson
commit d50daa2af2618dab6d21634e65a5fbcf4ae437d6 upstream.
Include the OF-based modalias in the uevent sent when registering SPMI
devices, so that
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Andersson
commit d50daa2af2618dab6d21634e65a5fbcf4ae437d6 upstream.
Include the OF-based modalias in the uevent sent when registering SPMI
devices, so that user space has a chance to
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Chunyu Hu
commit db9108e054700c96322b0f0028546aa4e643cf0b upstream.
Hit the kmemleak when executing instance_rmdir, it forgot releasing
mem of tracing_cpumask. With this
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Chunyu Hu
commit db9108e054700c96322b0f0028546aa4e643cf0b upstream.
Hit the kmemleak when executing instance_rmdir, it forgot releasing
mem of tracing_cpumask. With this fix, the warn does
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Olsa
commit c46fc0424ced3fb71208e72bd597d91b9169a781 upstream.
Zorro reported following crash while having enabled
syscall tracing (CONFIG_FTRACE_SYSCALLS):
Unable
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Olsa
commit c46fc0424ced3fb71208e72bd597d91b9169a781 upstream.
Zorro reported following crash while having enabled
syscall tracing (CONFIG_FTRACE_SYSCALLS):
Unable to handle kernel
401 - 500 of 2870 matches
Mail list logo