[PATCH 4.4 75/83] ceph: fix race in concurrent readdir

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yan, Zheng commit 84583cfb973c4313955c6231cc9cb3772d280b15 upstream. For a large directory, program needs to issue multiple readdir syscalls to get all dentries. When there

[PATCH 4.4 75/83] ceph: fix race in concurrent readdir

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yan, Zheng commit 84583cfb973c4313955c6231cc9cb3772d280b15 upstream. For a large directory, program needs to issue multiple readdir syscalls to get all dentries. When there are multiple

[PATCH 4.4 80/83] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

4.4-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

[PATCH 4.4 80/83] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

4.4-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

[PATCH 4.4 67/83] MIPS: Fix a typo: s/preset/present/ in r2-to-r6 emulation error message

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 27fe2200dad2de8207a694024a7b9037dff1b280 upstream. This is a user-visible message, so we want it to be spelled correctly. Fixes: 5f9f41c474be

[PATCH 4.4 67/83] MIPS: Fix a typo: s/preset/present/ in r2-to-r6 emulation error message

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 27fe2200dad2de8207a694024a7b9037dff1b280 upstream. This is a user-visible message, so we want it to be spelled correctly. Fixes: 5f9f41c474be ("MIPS: kernel: Prepare

Re: [RFC PATCH 1/5] ima: extend clone() with IMA namespace support

On Tue, 2017-07-25 at 13:31 -0700, James Bottomley wrote: > On Tue, 2017-07-25 at 15:48 -0400, 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 11:49:14AM

Re: [RFC PATCH 1/5] ima: extend clone() with IMA namespace support

On Tue, 2017-07-25 at 13:31 -0700, James Bottomley wrote: > On Tue, 2017-07-25 at 15:48 -0400, 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 11:49:14AM

[PATCH 4.4 81/83] spmi: Include OF based modalias in device uevent

4.4-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

[PATCH 4.4 81/83] spmi: Include OF based modalias in device uevent

4.4-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

[PATCH 4.4 82/83] tracing: Fix kmemleak in instance_rmdir

4.4-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,

[PATCH 4.4 82/83] tracing: Fix kmemleak in instance_rmdir

4.4-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 not

Re: [RFC PATCH 1/5] ima: extend clone() with IMA namespace support

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 11:49:14AM -0700, James Bottomley

Re: [RFC PATCH 1/5] ima: extend clone() with IMA namespace support

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 11:49:14AM -0700, James Bottomley

[PATCH 4.4 83/83] alarmtimer: dont rate limit one-shot timers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg Hackmann Commit ff86bf0c65f1 ("alarmtimer: Rate limit periodic intervals") sets a minimum bound on the alarm timer interval. This minimum bound shouldn't be applied

[PATCH 4.4 83/83] alarmtimer: dont rate limit one-shot timers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg Hackmann Commit ff86bf0c65f1 ("alarmtimer: Rate limit periodic intervals") sets a minimum bound on the alarm timer interval. This minimum bound shouldn't be applied if the interval is 0.

[PATCH 4.9 001/125] disable new gcc-7.1.1 warnings for now

4.9-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

[PATCH 4.9 001/125] disable new gcc-7.1.1 warnings for now

4.9-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

[PATCH 4.4 51/83] vfio: Fix group release deadlock

4.4-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

[PATCH 4.4 51/83] vfio: Fix group release deadlock

4.4-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,

[PATCH 4.9 010/125] NFC: fix broken device allocation

4.9-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

[PATCH 4.9 010/125] NFC: fix broken device allocation

4.9-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

[PATCH 4.9 011/125] NFC: nfcmrvl_uart: add missing tty-device sanity check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 15e0c59f1535926a939d1df66d6edcf997d7c1b9 upstream. Make sure to check the tty-device pointer before trying to access the parent device to avoid

[PATCH 4.9 011/125] NFC: nfcmrvl_uart: add missing tty-device sanity check

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 15e0c59f1535926a939d1df66d6edcf997d7c1b9 upstream. Make sure to check the tty-device pointer before trying to access the parent device to avoid dereferencing a NULL-pointer

[PATCH 4.9 015/125] nfc: Ensure presence of required attributes in the activate_target handler

4.9-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

[PATCH 4.9 014/125] NFC: nfcmrvl: fix firmware-management initialisation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 45dd39b974f663dd5cdcbea7358a077ab0b0 upstream. The nci-device was never deregistered in the event that fw-initialisation failed. Fix this by moving

[PATCH 4.9 015/125] nfc: Ensure presence of required attributes in the activate_target handler

4.9-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

[PATCH 4.9 014/125] NFC: nfcmrvl: fix firmware-management initialisation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 45dd39b974f663dd5cdcbea7358a077ab0b0 upstream. The nci-device was never deregistered in the event that fw-initialisation failed. Fix this by moving the firmware

Re: [PATCH v1 03/13] xen/pvcalls: implement socket command and handle events

On Mon, 24 Jul 2017, Juergen Gross wrote: > On 22/07/17 02:11, Stefano Stabellini wrote: > > Send a PVCALLS_SOCKET command to the backend, use the masked > > req_prod_pvt as req_id. This way, req_id is guaranteed to be between 0 > > and PVCALLS_NR_REQ_PER_RING. We already have a slot in the rsp

[PATCH 4.9 017/125] NFC: Add sockaddr length checks before accessing sa_family in bind handlers

4.9-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

Re: [PATCH v1 03/13] xen/pvcalls: implement socket command and handle events

On Mon, 24 Jul 2017, Juergen Gross wrote: > On 22/07/17 02:11, Stefano Stabellini wrote: > > Send a PVCALLS_SOCKET command to the backend, use the masked > > req_prod_pvt as req_id. This way, req_id is guaranteed to be between 0 > > and PVCALLS_NR_REQ_PER_RING. We already have a slot in the rsp

[PATCH 4.9 017/125] NFC: Add sockaddr length checks before accessing sa_family in bind handlers

4.9-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 it

Re: [PATCH v2 15/23] percpu: introduce bitmap metadata blocks

On Mon, Jul 24, 2017 at 07:02:12PM -0400, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > This patch introduces the bitmap metadata blocks and adds the skeleton > of the code that will be used to maintain these blocks. Each chunk's > bitmap is made up of full

Re: [PATCH v2 15/23] percpu: introduce bitmap metadata blocks

On Mon, Jul 24, 2017 at 07:02:12PM -0400, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > This patch introduces the bitmap metadata blocks and adds the skeleton > of the code that will be used to maintain these blocks. Each chunk's > bitmap is made up of full metadata blocks. These

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tuesday, July 25, 2017 05:59:04 PM Rafael J. Wysocki wrote: > On Tuesday, July 25, 2017 10:05:03 AM Alan Stern wrote: > > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > > > From: Rafael J. Wysocki > > > > > > If HCD_DEAD(hcd) is "true" in

Re: [PATCH] PM / USB: hcd_pci: Skip secondary root hub check for HCD_DEAD()

On Tuesday, July 25, 2017 05:59:04 PM Rafael J. Wysocki wrote: > On Tuesday, July 25, 2017 10:05:03 AM Alan Stern wrote: > > On Tue, 25 Jul 2017, Rafael J. Wysocki wrote: > > > > > From: Rafael J. Wysocki > > > > > > If HCD_DEAD(hcd) is "true" in check_root_hub_suspended(), it is > > > rather

[PATCH 4.9 016/125] nfc: Fix the sockaddr length sanitization in llcp_sock_connect

4.9-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

[PATCH 4.9 016/125] nfc: Fix the sockaddr length sanitization in llcp_sock_connect

4.9-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

[PATCH 4.9 019/125] perf intel-pt: Improve sample timestamp

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 3f04d98e972b59706bd43d6cc75efac91f8fba50 upstream. The decoder uses its current timestamp in samples. Usually that is a timestamp that has already

[PATCH 4.9 019/125] perf intel-pt: Improve sample timestamp

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 3f04d98e972b59706bd43d6cc75efac91f8fba50 upstream. The decoder uses its current timestamp in samples. Usually that is a timestamp that has already passed, but in some

Re: [PATCH -mm -v3 1/6] mm, swap: Add swap cache statistics sysfs interface

On Tue, 25 Jul 2017 09:51:46 +0800 "Huang, Ying" wrote: > The swap cache stats could be gotten only via sysrq, which isn't > convenient in some situation. So the sysfs interface of swap cache > stats is added for that. The added sysfs directories/files are as > follow, >

Re: [PATCH -mm -v3 1/6] mm, swap: Add swap cache statistics sysfs interface

On Tue, 25 Jul 2017 09:51:46 +0800 "Huang, Ying" wrote: > The swap cache stats could be gotten only via sysrq, which isn't > convenient in some situation. So the sysfs interface of swap cache > stats is added for that. The added sysfs directories/files are as > follow, > > /sys/kernel/mm/swap

[PATCH 4.9 018/125] perf intel-pt: Move decoder error setting into one condition

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 22c06892332d8916115525145b78e606e9cc6492 upstream. Move decoder error setting into one condition. Cc'ed to stable because later fixes depend on

[PATCH 4.9 018/125] perf intel-pt: Move decoder error setting into one condition

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 22c06892332d8916115525145b78e606e9cc6492 upstream. Move decoder error setting into one condition. Cc'ed to stable because later fixes depend on it. Signed-off-by: Adrian

[PATCH 4.9 002/125] [media] ir-core: fix gcc-7 warning on bool arithmetic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit bd7e31bbade02bc1e92aa00d5cf2cee2da66838a upstream. gcc-7 suggests that an expression using a bitwise not and a bitmask on a 'bool' variable is better

[PATCH 4.9 012/125] NFC: nfcmrvl: do not use device-managed resources

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 0cbe40112f42cf5e008f9127f6cd5952ba3946c7 upstream. This specifically fixes resource leaks in the registration error paths. Device-managed resources is a

[PATCH 4.9 002/125] [media] ir-core: fix gcc-7 warning on bool arithmetic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit bd7e31bbade02bc1e92aa00d5cf2cee2da66838a upstream. gcc-7 suggests that an expression using a bitwise not and a bitmask on a 'bool' variable is better written using boolean

[PATCH 4.9 012/125] NFC: nfcmrvl: do not use device-managed resources

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 0cbe40112f42cf5e008f9127f6cd5952ba3946c7 upstream. This specifically fixes resource leaks in the registration error paths. Device-managed resources is a bad fit for this

[PATCH 4.9 023/125] perf intel-pt: Ensure never to set last_ip when packet count is zero

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit f952eaceb089b691eba7c4e13686e742a8f26bf5 upstream. Intel PT uses IP compression based on the last IP. For decoding purposes, 'last IP' is not

[PATCH 4.9 023/125] perf intel-pt: Ensure never to set last_ip when packet count is zero

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit f952eaceb089b691eba7c4e13686e742a8f26bf5 upstream. Intel PT uses IP compression based on the last IP. For decoding purposes, 'last IP' is not updated when a branch target

[PATCH 4.9 021/125] perf intel-pt: Ensure IP is zero when state is INTEL_PT_STATE_NO_IP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit ad7167a8cd174ba7d8c0d0ed8d8410521206d104 upstream. A value of zero is used to indicate that there is no IP. Ensure the value is zero when the

[PATCH 4.9 021/125] perf intel-pt: Ensure IP is zero when state is INTEL_PT_STATE_NO_IP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit ad7167a8cd174ba7d8c0d0ed8d8410521206d104 upstream. A value of zero is used to indicate that there is no IP. Ensure the value is zero when the state is

[PATCH 4.9 003/125] dm mpath: cleanup -Wbool-operation warning in choose_pgpath()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit d19a55ccad15a486ffe03030570744e5d5bd9f8e upstream. Reported-by: David Binderman Signed-off-by: Mike Snitzer

[PATCH 4.9 003/125] dm mpath: cleanup -Wbool-operation warning in choose_pgpath()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Snitzer commit d19a55ccad15a486ffe03030570744e5d5bd9f8e upstream. Reported-by: David Binderman Signed-off-by: Mike Snitzer Signed-off-by: Greg Kroah-Hartman --- drivers/md/dm-mpath.c

[PATCH 4.9 004/125] [media] s5p-jpeg: dont return a random width/height

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit a16e37726c444cbda91e73ed5f742e717bfe866f upstream. Gcc 7.1 complains about: drivers/media/platform/s5p-jpeg/jpeg-core.c: In function

[PATCH 4.9 004/125] [media] s5p-jpeg: dont return a random width/height

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit a16e37726c444cbda91e73ed5f742e717bfe866f upstream. Gcc 7.1 complains about: drivers/media/platform/s5p-jpeg/jpeg-core.c: In function 's5p_jpeg_parse_hdr.isra.9':

[PATCH 4.9 005/125] thermal: max77620: fix device-node reference imbalance

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c592fafbdbb6b1279b76a54722d1465ca77e5bde upstream. The thermal child device reuses the parent MFD-device device-tree node when registering a thermal zone,

[PATCH 4.9 005/125] thermal: max77620: fix device-node reference imbalance

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c592fafbdbb6b1279b76a54722d1465ca77e5bde upstream. The thermal child device reuses the parent MFD-device device-tree node when registering a thermal zone, but did not take

[PATCH 4.9 006/125] thermal: cpu_cooling: Avoid accessing potentially freed structures

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 289d72afddf83440117c35d864bf0c6309c1d011 upstream. After the lock is dropped, it is possible that the cpufreq_dev gets freed before we call

[PATCH 4.9 006/125] thermal: cpu_cooling: Avoid accessing potentially freed structures

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 289d72afddf83440117c35d864bf0c6309c1d011 upstream. After the lock is dropped, it is possible that the cpufreq_dev gets freed before we call get_level() and that can cause

[PATCH 4.9 007/125] ath9k: fix tx99 use after free

4.9-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

[PATCH 4.9 020/125] perf intel-pt: Fix missing stack clear

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 12b7080609097753fd8198cc1daf589be3ec1cca upstream. The return compression stack must be cleared whenever there is a PSB. Fix one case where that

[PATCH 4.9 020/125] perf intel-pt: Fix missing stack clear

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 12b7080609097753fd8198cc1daf589be3ec1cca upstream. The return compression stack must be cleared whenever there is a PSB. Fix one case where that was not happening.

[PATCH 4.9 007/125] ath9k: fix tx99 use after free

4.9-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 set

[PATCH 4.9 008/125] ath9k: fix tx99 bus error

4.9-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

[PATCH 4.9 008/125] ath9k: fix tx99 bus error

4.9-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:

[PATCH 4.9 022/125] perf intel-pt: Fix last_ip usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit ee14ac0ef6827cd6f9a572cc83dd0191ea17812c upstream. Intel PT uses IP compression based on the last IP. For decoding purposes, 'last IP' is

[PATCH 4.9 022/125] perf intel-pt: Fix last_ip usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit ee14ac0ef6827cd6f9a572cc83dd0191ea17812c upstream. Intel PT uses IP compression based on the last IP. For decoding purposes, 'last IP' is considered to be reset to zero

[PATCH 4.9 009/125] ath9k: fix an invalid pointer dereference in ath9k_rng_stop()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Miaoqing Pan commit 07246c115801c27652700e3679bb58661ef7ed65 upstream. The bug was triggered when do suspend/resuming continuously on Dell XPS L322X/0PJHXN version

[PATCH 4.9 009/125] ath9k: fix an invalid pointer dereference in ath9k_rng_stop()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Miaoqing Pan commit 07246c115801c27652700e3679bb58661ef7ed65 upstream. The bug was triggered when do suspend/resuming continuously on Dell XPS L322X/0PJHXN version 9333 (2013) with kernel

[PATCH 4.9 024/125] perf intel-pt: Use FUP always when scanning for an IP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 622b7a47b843c78626f40c1d1aeef8483383fba2 upstream. The decoder will try to use branch packets to find an IP to start decoding or to recover from

[PATCH 4.9 024/125] perf intel-pt: Use FUP always when scanning for an IP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit 622b7a47b843c78626f40c1d1aeef8483383fba2 upstream. The decoder will try to use branch packets to find an IP to start decoding or to recover from errors. Currently the FUP

[PATCH 4.9 000/125] 4.9.40-stable review

This is the start of the stable review cycle for the 4.9.40 release. There are 125 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 Thu Jul 27 19:19:43 UTC 2017. Anything

[PATCH 4.9 000/125] 4.9.40-stable review

This is the start of the stable review cycle for the 4.9.40 release. There are 125 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 Thu Jul 27 19:19:43 UTC 2017. Anything

[PATCH 4.9 039/125] powerpc/64: Fix atomic64_inc_not_zero() to return an int

4.9-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()

[PATCH 4.9 039/125] powerpc/64: Fix atomic64_inc_not_zero() to return an int

4.9-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

[PATCH 4.9 041/125] powerpc: Fix emulation of mfocrf in emulate_step()

4.9-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

[PATCH 4.9 036/125] iscsi-target: Add login_keys_workaround attribute for non RFC initiators

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit 138d351eefb727ab9e41a3dc5f112ceb4f6e59f2 upstream. This patch re-introduces part of a long standing login workaround that was recently dropped

[PATCH 4.9 040/125] powerpc: Fix emulation of mcrf in emulate_step()

4.9-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

[PATCH 4.9 040/125] powerpc: Fix emulation of mcrf in emulate_step()

4.9-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 CR

[PATCH 4.9 041/125] powerpc: Fix emulation of mfocrf in emulate_step()

4.9-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

[PATCH 4.9 036/125] iscsi-target: Add login_keys_workaround attribute for non RFC initiators

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit 138d351eefb727ab9e41a3dc5f112ceb4f6e59f2 upstream. This patch re-introduces part of a long standing login workaround that was recently dropped by: commit

[PATCH 4.9 043/125] powerpc/mm/radix: Properly clear process table entry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit c6bb0b8d426a8cf865ca9c8a532cc3a2927cfceb upstream. On radix, the process table entry we want to clear when destroying a context is entry

[PATCH 4.9 043/125] powerpc/mm/radix: Properly clear process table entry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit c6bb0b8d426a8cf865ca9c8a532cc3a2927cfceb upstream. On radix, the process table entry we want to clear when destroying a context is entry 0, not entry 1. This has

[PATCH 4.9 027/125] wlcore: fix 64K page support

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4a4274bf2dbbd1c7a45be0c89a1687c9d2eef4a0 upstream. In the stable linux-3.16 branch, I ran into a warning in the wlcore driver:

[PATCH 4.9 044/125] af_key: Fix sadb_x_ipsecrequest parsing

4.9-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

[PATCH 4.9 027/125] wlcore: fix 64K page support

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 4a4274bf2dbbd1c7a45be0c89a1687c9d2eef4a0 upstream. In the stable linux-3.16 branch, I ran into a warning in the wlcore driver: drivers/net/wireless/ti/wlcore/spi.c: In

[PATCH 4.9 044/125] af_key: Fix sadb_x_ipsecrequest parsing

4.9-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 sadb_x_ipsecrequest_len.

[PATCH 4.9 037/125] xen/scsiback: Fix a TMR related use-after-free

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 9f4ab18ac51dc87345a9cbd2527e6acf7a0a9335 upstream. scsiback_release_cmd() must not dereference se_cmd->se_tmr_req because that memory is

[PATCH 4.9 037/125] xen/scsiback: Fix a TMR related use-after-free

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 9f4ab18ac51dc87345a9cbd2527e6acf7a0a9335 upstream. scsiback_release_cmd() must not dereference se_cmd->se_tmr_req because that memory is freed by target_free_cmd_mem()

Re: [PATCH v4 2/2] of: Add unit tests for applying overlays

On Tue, Apr 25, 2017 at 7:09 PM, wrote: > From: Frank Rowand > > Existing overlay unit tests examine individual pieces of the overlay > code. The new tests target the entire process of applying an overlay. > > Signed-off-by: Frank Rowand

Re: [PATCH v4 2/2] of: Add unit tests for applying overlays

On Tue, Apr 25, 2017 at 7:09 PM, wrote: > From: Frank Rowand > > Existing overlay unit tests examine individual pieces of the overlay > code. The new tests target the entire process of applying an overlay. > > Signed-off-by: Frank Rowand > --- [...] > @@ -1261,6 +1263,8 @@ void __init

[PATCH 4.9 035/125] scsi: Add STARGET_CREATED_REMOVE state to scsi_target_state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ewan D. Milne commit f9279c968c257ee39b0d7bd2571a4d231a67bcc1 upstream. The addition of the STARGET_REMOVE state had the side effect of introducing a race condition that can

[PATCH 4.9 035/125] scsi: Add STARGET_CREATED_REMOVE state to scsi_target_state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ewan D. Milne commit f9279c968c257ee39b0d7bd2571a4d231a67bcc1 upstream. The addition of the STARGET_REMOVE state had the side effect of introducing a race condition that can cause a crash.

[PATCH 4.9 045/125] PCI: Work around poweroff & suspend-to-RAM issue on Macbook Pro 11

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit 13cfc732160f7bc7e596128ce34cda361c556966 upstream. Neither soft poweroff (transition to ACPI power state S5) nor suspend-to-RAM (transition to state

[PATCH 4.9 045/125] PCI: Work around poweroff & suspend-to-RAM issue on Macbook Pro 11

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit 13cfc732160f7bc7e596128ce34cda361c556966 upstream. Neither soft poweroff (transition to ACPI power state S5) nor suspend-to-RAM (transition to state S3) works on the

[PATCH 4.9 047/125] PCI/PM: Restore the status of PCI devices across hibernation

4.9-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

[PATCH 4.9 046/125] PCI: rockchip: Use normal register bank for config accessors

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shawn Lin commit dc8cca5ef25ac4cb0dfc37467521a759767ff361 upstream. Rockchip's RC has two banks of registers for the root port: a normal bank that is strictly

[PATCH 4.9 046/125] PCI: rockchip: Use normal register bank for config accessors

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shawn Lin commit dc8cca5ef25ac4cb0dfc37467521a759767ff361 upstream. Rockchip's RC has two banks of registers for the root port: a normal bank that is strictly compatible with the PCIe spec,

[PATCH 4.9 047/125] PCI/PM: Restore the status of PCI devices across hibernation

4.9-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

<    4   5   6   7   8   9   10   11   12   13   >