[PATCH 4.9 048/171] rxe: Fix a sleep-in-atomic bug in post_one_send

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07d432bb97f19dd5e784175152f9fce3b2646133 ] The driver may sleep under a spin lock, and the function call path is: post_one_send (acquire the lock by spin_lock_irqsave)

[PATCH 4.9 067/171] ARM: 8677/1: boot/compressed: fix decompressor header layout for v7-M

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 06a4b6d009a1b74a6ec46c5418b46cc53a79fcb8 ] As reported by Patrice, the header layout of the decompressor is incorrect when building for v7-M. In this case, the __nop macro resolves

[PATCH 4.9 052/171] tipc: Fix tipc_sk_reinit handling of -EAGAIN

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6c7e983b220f89e03286dc70a41c7ef3a8b409df ] In 9dbbfb0ab6680c6a85609041011484e6658e7d3c function tipc_sk_reinit had additional logic added to loop in the event that function

[PATCH 4.9 048/171] rxe: Fix a sleep-in-atomic bug in post_one_send

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07d432bb97f19dd5e784175152f9fce3b2646133 ] The driver may sleep under a spin lock, and the function call path is: post_one_send (acquire the lock by spin_lock_irqsave)

[PATCH 4.9 054/171] bnxt_en: Dont use rtnl lock to protect link change logic in workqueue.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e2dc9b6e38fa3919e63d6d7905da70ca41cbf908 ] As a further improvement to the PF/VF link change logic, use a private mutex instead of the rtnl lock to protect link change logic. With

[PATCH 4.9 051/171] net/mlx5: Fix command completion after timeout access invalid structure

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 061870800efb4e3d1ad4082a2569363629bdfcfc ] Completion on timeout should not free the driver command entry structure as it will need to access it again once real completion event from

x86_64 INIT/SIPI Bug

I apologize upfront if this is the wrong place to post this, pretty new to this. We are working on the Bareflank Hypervisor (www.bareflank.org), and we are passing through the INIT/SIPI process (similar to how a VMX rootkit from EFI might boot the OS) and we noticed that on Arch Linux, the

[PATCH 4.9 054/171] bnxt_en: Dont use rtnl lock to protect link change logic in workqueue.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e2dc9b6e38fa3919e63d6d7905da70ca41cbf908 ] As a further improvement to the PF/VF link change logic, use a private mutex instead of the rtnl lock to protect link change logic. With

[PATCH 4.9 051/171] net/mlx5: Fix command completion after timeout access invalid structure

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 061870800efb4e3d1ad4082a2569363629bdfcfc ] Completion on timeout should not free the driver command entry structure as it will need to access it again once real completion event from

x86_64 INIT/SIPI Bug

I apologize upfront if this is the wrong place to post this, pretty new to this. We are working on the Bareflank Hypervisor (www.bareflank.org), and we are passing through the INIT/SIPI process (similar to how a VMX rootkit from EFI might boot the OS) and we noticed that on Arch Linux, the

[PATCH 4.9 050/171] net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c505873eaece2b4aefd07d339dc7e1400e0235ac ] 88E1145 also need this autoneg errata. Fixes: f2899788353c ("net: phy: marvell: Limit errata to 88m1101") Signed-off-by: Zhao Qiang

[PATCH 4.9 050/171] net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c505873eaece2b4aefd07d339dc7e1400e0235ac ] 88E1145 also need this autoneg errata. Fixes: f2899788353c ("net: phy: marvell: Limit errata to 88m1101") Signed-off-by: Zhao Qiang

[PATCH 4.9 053/171] tipc: fix a race condition of releasing subscriber object

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fd849b7c41f0fabfe783d0691a63c5518e8ebc99 ] No matter whether a request is inserted into workqueue as a work item to cancel a subscription or to delete a subscription's subscriber

[PATCH 4.9 045/171] IB/ipoib: Do not warn if IPoIB debugfs doesnt exist

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 14fa91e0fef8e4d6feb8b1fa2a807828e0abe815 ] netdev_wait_allrefs() could rebroadcast NETDEV_UNREGISTER event multiple times until all refs are gone, which will result in calling

[PATCH 4.9 053/171] tipc: fix a race condition of releasing subscriber object

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fd849b7c41f0fabfe783d0691a63c5518e8ebc99 ] No matter whether a request is inserted into workqueue as a work item to cancel a subscription or to delete a subscription's subscriber

[PATCH 4.9 045/171] IB/ipoib: Do not warn if IPoIB debugfs doesnt exist

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 14fa91e0fef8e4d6feb8b1fa2a807828e0abe815 ] netdev_wait_allrefs() could rebroadcast NETDEV_UNREGISTER event multiple times until all refs are gone, which will result in calling

[PATCH 4.9 080/171] usb: renesas_usbhs: gadget: fix unused-but-set-variable warning

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b7d44c36a6f6d956e1539e0dd42f98b26e5a4684 ] The commit b8b9c974afee ("usb: renesas_usbhs: gadget: disable all eps when the driver stops") causes the unused-but-set-variable warning.

[PATCH 4.9 080/171] usb: renesas_usbhs: gadget: fix unused-but-set-variable warning

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b7d44c36a6f6d956e1539e0dd42f98b26e5a4684 ] The commit b8b9c974afee ("usb: renesas_usbhs: gadget: disable all eps when the driver stops") causes the unused-but-set-variable warning.

Re: [PATCH] z3fold: fix wrong handling of headless pages

On Thu, 8 Nov 2018 22:45:40 +0900 Jongseok Kim wrote: > Yes, you are right. > I think that's the best way to deal it. > Thank you. I did this: Link: http://lkml.kernel.org/r/20181105162225.74e8837d03583a9b707cf...@gmail.com Signed-off-by: Vitaly Wool Signed-off-by: Jongseok Kim

[PATCH 4.9 091/171] ALSA: hda - No loopback on ALC299 codec

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fa16b69f1299004b60b625f181143500a246e5cb ] ALC299 has no loopback mixer, but the driver still tries to add a beep control over the mixer NID which leads to the error at accessing it.

[PATCH 4.9 088/171] ocfs2: fix deadlock caused by recursive locking in xattr

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8818efaaacb78c60a9d90c5705b6c99b75d7d442 ] Another deadlock path caused by recursive locking is reported. This kind of issue was introduced since commit 743b5f1434f5 ("ocfs2: take

[PATCH 4.9 072/171] ufs: we need to sync inode before freeing it

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 67a70017fa0a152657bc7e337e69bb9c9f5549bf ] Signed-off-by: Al Viro Signed-off-by: Sasha Levin --- fs/ufs/inode.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/ufs/inode.c

[PATCH 4.9 087/171] qed: Warn PTT usage by wrong hw-function

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a50d3518dcba44f8a0f9356b7140fe1499984ea ] PTT entries are per-hwfn; If some errneous flow is trying to use a PTT belonging to a differnet hwfn warn user, as this can break every

[PATCH 4.9 082/171] clk: samsung: Fix m2m scaler clock on Exynos542x

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c07c1a0f68d0f2f7ca9aff924e2772526027b019 ] The TOP "aclk400_mscl" clock should be kept enabled all the time to allow proper access to power management control for MSC power domain

[PATCH 4.9 089/171] net: cdc_ncm: GetNtbFormat endian fix

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6314dab4b8fb8493d810e175cb340376052c69b6 ] The GetNtbFormat and SetNtbFormat requests operate on 16 bit little endian values. We get away with ignoring this most of the time, because

[PATCH 4.9 084/171] staging: wilc1000: Fix problem with wrong vif index

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0e490657c7214cce33fbca3d88227298c5c968ae ] The vif->idx value is always 0 for two interfaces. wl->vif_num = 0; loop { ... vif->idx = wl->vif_num; ...

[PATCH 4.9 072/171] ufs: we need to sync inode before freeing it

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 67a70017fa0a152657bc7e337e69bb9c9f5549bf ] Signed-off-by: Al Viro Signed-off-by: Sasha Levin --- fs/ufs/inode.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/ufs/inode.c

[PATCH 4.9 087/171] qed: Warn PTT usage by wrong hw-function

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a50d3518dcba44f8a0f9356b7140fe1499984ea ] PTT entries are per-hwfn; If some errneous flow is trying to use a PTT belonging to a differnet hwfn warn user, as this can break every

[PATCH 4.9 082/171] clk: samsung: Fix m2m scaler clock on Exynos542x

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c07c1a0f68d0f2f7ca9aff924e2772526027b019 ] The TOP "aclk400_mscl" clock should be kept enabled all the time to allow proper access to power management control for MSC power domain

[PATCH 4.9 089/171] net: cdc_ncm: GetNtbFormat endian fix

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6314dab4b8fb8493d810e175cb340376052c69b6 ] The GetNtbFormat and SetNtbFormat requests operate on 16 bit little endian values. We get away with ignoring this most of the time, because

[PATCH 4.9 084/171] staging: wilc1000: Fix problem with wrong vif index

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0e490657c7214cce33fbca3d88227298c5c968ae ] The vif->idx value is always 0 for two interfaces. wl->vif_num = 0; loop { ... vif->idx = wl->vif_num; ...

[PATCH 4.9 088/171] ocfs2: fix deadlock caused by recursive locking in xattr

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8818efaaacb78c60a9d90c5705b6c99b75d7d442 ] Another deadlock path caused by recursive locking is reported. This kind of issue was introduced since commit 743b5f1434f5 ("ocfs2: take

Re: [PATCH] z3fold: fix wrong handling of headless pages

On Thu, 8 Nov 2018 22:45:40 +0900 Jongseok Kim wrote: > Yes, you are right. > I think that's the best way to deal it. > Thank you. I did this: Link: http://lkml.kernel.org/r/20181105162225.74e8837d03583a9b707cf...@gmail.com Signed-off-by: Vitaly Wool Signed-off-by: Jongseok Kim

[PATCH 4.9 091/171] ALSA: hda - No loopback on ALC299 codec

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fa16b69f1299004b60b625f181143500a246e5cb ] ALC299 has no loopback mixer, but the driver still tries to add a beep control over the mixer NID which leads to the error at accessing it.

Re: [PATCH 3.18 053/144] ARM: OMAP2+: Fix n900 board name for legacy user space

On Thu 2018-11-08 13:50:24, Greg Kroah-Hartman wrote: > 3.18-stable review patch. If anyone has any objections, please let me know. > > -- > > [ Upstream commit 71c4f6027da75c6c1fd92e05b63108a09ec2b109 ] > > N900 legacy user space apps need the board name in > /proc/cpuinfo to

Re: [PATCH 3.18 053/144] ARM: OMAP2+: Fix n900 board name for legacy user space

On Thu 2018-11-08 13:50:24, Greg Kroah-Hartman wrote: > 3.18-stable review patch. If anyone has any objections, please let me know. > > -- > > [ Upstream commit 71c4f6027da75c6c1fd92e05b63108a09ec2b109 ] > > N900 legacy user space apps need the board name in > /proc/cpuinfo to

[PATCH 4.9 094/171] IB/ipoib: Fix lockdep issue found on ipoib_ib_dev_heavy_flush

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1f80bd6a6cc8358b81194e1f5fc16449947396ec ] The locking order of vlan_rwsem (LOCK A) and then rtnl (LOCK B), contradicts other flows such as ipoib_open possibly causing a deadlock. To

[PATCH 4.9 098/171] IB/mlx5: Avoid passing an invalid QP type to firmware

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e7b169f34403becd3c9fd3b6e46614ab788f2187 ] During QP creation, the mlx5 driver translates the QP type to an internal value which is passed on to FW. There was no check to make sure

[PATCH 4.9 097/171] mm/frame_vector.c: release a semaphore in get_vaddr_frames()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1f704fd0d14043e76e80f6b8b2251b9b2cedcca6 ] A semaphore is acquired before this check, so we must release it before leaving. Link:

[PATCH 4.9 094/171] IB/ipoib: Fix lockdep issue found on ipoib_ib_dev_heavy_flush

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1f80bd6a6cc8358b81194e1f5fc16449947396ec ] The locking order of vlan_rwsem (LOCK A) and then rtnl (LOCK B), contradicts other flows such as ipoib_open possibly causing a deadlock. To

[PATCH 4.9 098/171] IB/mlx5: Avoid passing an invalid QP type to firmware

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e7b169f34403becd3c9fd3b6e46614ab788f2187 ] During QP creation, the mlx5 driver translates the QP type to an internal value which is passed on to FW. There was no check to make sure

[PATCH 4.9 097/171] mm/frame_vector.c: release a semaphore in get_vaddr_frames()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1f704fd0d14043e76e80f6b8b2251b9b2cedcca6 ] A semaphore is acquired before this check, so we must release it before leaving. Link:

[PATCH 4.9 096/171] nbd: only set MSG_MORE when we have more to send

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d61b7f972dab2a7d187c38254845546dfc8eed85 ] A user noticed that write performance was horrible over loopback and we traced it to an inversion of when we need to set MSG_MORE. It

[PATCH 4.9 096/171] nbd: only set MSG_MORE when we have more to send

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d61b7f972dab2a7d187c38254845546dfc8eed85 ] A user noticed that write performance was horrible over loopback and we traced it to an inversion of when we need to set MSG_MORE. It

[PATCH 4.9 093/171] ipv6: fix cleanup ordering for ip6_mr failure

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afe49de44c27a89e8e9631c44b5ffadf6ace65e2 ] Commit 15e668070a64 ("ipv6: reorder icmpv6_init() and ip6_mr_init()") moved the cleanup label for ipmr_fail, but should have changed the

[PATCH 4.9 092/171] ath10k: convert warning about non-existent OTP board id to debug message

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7be52c03bbf7c8f53211ed13810d64dcb2bc7168 ] Currently ath10k unncessarily warns about board id not available from OTP: ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0

[PATCH 4.9 090/171] sctp: use right member as the param of list_for_each_entry

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8dd397903a6e57157f6265911f7d35681364427 ] Commit d04adf1b3551 ("sctp: reset owner sk for data chunks on out queues when migrating a sock") made a mistake that using 'list' as the

[PATCH 4.9 093/171] ipv6: fix cleanup ordering for ip6_mr failure

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afe49de44c27a89e8e9631c44b5ffadf6ace65e2 ] Commit 15e668070a64 ("ipv6: reorder icmpv6_init() and ip6_mr_init()") moved the cleanup label for ipmr_fail, but should have changed the

[PATCH 4.9 092/171] ath10k: convert warning about non-existent OTP board id to debug message

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7be52c03bbf7c8f53211ed13810d64dcb2bc7168 ] Currently ath10k unncessarily warns about board id not available from OTP: ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0

[PATCH 4.9 090/171] sctp: use right member as the param of list_for_each_entry

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8dd397903a6e57157f6265911f7d35681364427 ] Commit d04adf1b3551 ("sctp: reset owner sk for data chunks on out queues when migrating a sock") made a mistake that using 'list' as the

[PATCH 4.9 100/171] drm: bochs: Dont remove uninitialized fbdev framebuffer

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4fa13dbe8c86382a846584e65c47bce09297f75b ] In the same spirit of the fix for QXL in commit 861078381ba5 ("drm: qxl: Don't alloc fbdev if emulation is not supported"), prevent the

[PATCH 4.9 100/171] drm: bochs: Dont remove uninitialized fbdev framebuffer

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4fa13dbe8c86382a846584e65c47bce09297f75b ] In the same spirit of the fix for QXL in commit 861078381ba5 ("drm: qxl: Don't alloc fbdev if emulation is not supported"), prevent the

[PATCH 4.9 076/171] perf evsel: Fix probing of precise_ip level for default cycles event

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a1ac110c22eb726684c837544a2d42c33e07be7 ] Since commit 18e7a45af91a ("perf/x86: Reject non sampling events with precise_ip") returns -EINVAL for sys_perf_event_open() with an

[PATCH 4.9 074/171] ip6_tunnel: Correct tos value in collect_md mode

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46f8cd9d2fc1e4e8b82b53a0007f6c92e80c930b ] Same as ip_gre, geneve and vxlan, use key->tos as traffic class value. CC: Peter Dawson Fixes: 0e9a709560db ("ip6_tunnel, ip6_gre: fix

[PATCH 4.9 078/171] net/mlx5: Fix health work queue spin lock to IRQ safe

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6377ed0bbae6fa28853e1679d068a9106c8a8908 ] spin_lock/unlock of health->wq_lock should be IRQ safe. It was changed to spin_lock_irqsave since adding commit 0179720d6be2 ("net/mlx5:

[PATCH 4.9 073/171] net/mlx5e: Fix fixpoint divide exception in mlx5e_am_stats_compare

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e58edaa4863583b54409444f11b4f80dff0af1cd ] Helmut reported a bug about division by zero while running traffic and doing physical cable pull test. When the cable unplugged the ppms

[PATCH 4.9 074/171] ip6_tunnel: Correct tos value in collect_md mode

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46f8cd9d2fc1e4e8b82b53a0007f6c92e80c930b ] Same as ip_gre, geneve and vxlan, use key->tos as traffic class value. CC: Peter Dawson Fixes: 0e9a709560db ("ip6_tunnel, ip6_gre: fix

[PATCH 4.9 078/171] net/mlx5: Fix health work queue spin lock to IRQ safe

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6377ed0bbae6fa28853e1679d068a9106c8a8908 ] spin_lock/unlock of health->wq_lock should be IRQ safe. It was changed to spin_lock_irqsave since adding commit 0179720d6be2 ("net/mlx5:

[PATCH 4.9 073/171] net/mlx5e: Fix fixpoint divide exception in mlx5e_am_stats_compare

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e58edaa4863583b54409444f11b4f80dff0af1cd ] Helmut reported a bug about division by zero while running traffic and doing physical cable pull test. When the cable unplugged the ppms

[PATCH 4.9 076/171] perf evsel: Fix probing of precise_ip level for default cycles event

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a1ac110c22eb726684c837544a2d42c33e07be7 ] Since commit 18e7a45af91a ("perf/x86: Reject non sampling events with precise_ip") returns -EINVAL for sys_perf_event_open() with an

[PATCH 4.9 112/171] ALSA: hda - Fix incorrect usage of IS_REACHABLE()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6a30abaa40b62aed46ef12ea4c16c48565bdb376 ] The commit c469652bb5e8 ("ALSA: hda - Use IS_REACHABLE() for dependency on input") simplified the dependencies with IS_REACHABLE() macro,

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On 11/08/2018 02:09 PM, Bjorn Helgaas wrote: > > [EXTERNAL EMAIL] > Please report any suspicious attachments, links, or requests for sensitive > information. > > > [+cc Jonathan, Greg, Lukas, Russell, Sam, Oliver for discussion about > PCI error recovery in general] Has anyone seen seen the

[PATCH 4.9 079/171] usb: renesas_usbhs: gadget: fix spin_lock_init() for >lock

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 14a8d4bfc2102f85ce097563d151370c91c1898a ] This patch fixes an issue that the spin_lock_init() is not called for almost all pipes. Otherwise, the lockdep output the following message

[PATCH 4.9 112/171] ALSA: hda - Fix incorrect usage of IS_REACHABLE()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6a30abaa40b62aed46ef12ea4c16c48565bdb376 ] The commit c469652bb5e8 ("ALSA: hda - Use IS_REACHABLE() for dependency on input") simplified the dependencies with IS_REACHABLE() macro,

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On 11/08/2018 02:09 PM, Bjorn Helgaas wrote: > > [EXTERNAL EMAIL] > Please report any suspicious attachments, links, or requests for sensitive > information. > > > [+cc Jonathan, Greg, Lukas, Russell, Sam, Oliver for discussion about > PCI error recovery in general] Has anyone seen seen the

[PATCH 4.9 079/171] usb: renesas_usbhs: gadget: fix spin_lock_init() for >lock

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 14a8d4bfc2102f85ce097563d151370c91c1898a ] This patch fixes an issue that the spin_lock_init() is not called for almost all pipes. Otherwise, the lockdep output the following message

Re: [Bug 201637] New: hangup sinse 'x86/mm: Expand static page table for fixmap space' with CONFIG_RANDOMIZE_BASE enabled

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 08 Nov 2018 13:48:25 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201637 > > Bug ID: 201637 >Summary: hangup

Re: [Bug 201637] New: hangup sinse 'x86/mm: Expand static page table for fixmap space' with CONFIG_RANDOMIZE_BASE enabled

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 08 Nov 2018 13:48:25 + bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201637 > > Bug ID: 201637 >Summary: hangup

[PATCH 4.9 102/171] Revert "IB/ipoib: Update broadcast object if PKey value was changed in index 0"

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 612601d0013f03de9dc134809f242ba6da9ca252 ] commit 9a9b8112699d will cause core to fail UD QP from being destroyed on ipoib unload, therefore cause resources leakage. On pkey change

[PATCH 4.9 111/171] futex: futex_wake_op, do not fail on invalid op

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e78c38f6bdd900b2ad9ac9df8eff58b745dc5b3c ] In commit 30d6e0a4190d ("futex: Remove duplicated code and fix undefined behaviour"), I let FUTEX_WAKE_OP to fail on invalid op. Namely

[PATCH 4.9 102/171] Revert "IB/ipoib: Update broadcast object if PKey value was changed in index 0"

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 612601d0013f03de9dc134809f242ba6da9ca252 ] commit 9a9b8112699d will cause core to fail UD QP from being destroyed on ipoib unload, therefore cause resources leakage. On pkey change

[PATCH 4.9 111/171] futex: futex_wake_op, do not fail on invalid op

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e78c38f6bdd900b2ad9ac9df8eff58b745dc5b3c ] In commit 30d6e0a4190d ("futex: Remove duplicated code and fix undefined behaviour"), I let FUTEX_WAKE_OP to fail on invalid op. Namely

[PATCH 4.9 122/171] IB/mlx4: Fix an error handling path in mlx4_ib_rereg_user_mr()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3dc7c7badb7502ec3e3aa817a8bdd9e53aa54c52 ] Before returning -EPERM we should release some resources, as already done in the other error handling path of the function. Fixes:

[PATCH 4.9 118/171] bonding: ratelimit failed speed/duplex update warning

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 11e9d7829dd08dbafb24517fe922f11c3a8a9dc2 ] bond_miimon_commit() handles the UP transition for each slave of a bond in the case of MII. It is triggered 10 times per second for the

[PATCH 4.9 119/171] nvmet: fix space padding in serial number

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c73996984902516745bc587d5e8a0b2e034aea05 ] Commit 42de82a8b544 previously attempted to fix this, and it did correctly pad the MN and FR fields with spaces, but the SN field still

[PATCH 4.9 070/171] net: stmmac: ensure jumbo_frm error return is correctly checked for -ve value

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 594238158bf748c285f0a73222cd9b7ccf3c525d ] The current comparison of entry < 0 will never be true since entry is an unsigned integer. Make entry an int to ensure -ve error return

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, Nov 08, 2018 at 01:04:49PM -0800, Greg KH wrote: > > (Also note that even with fast SSD's and/or everything in page cache, > > runnning "tag --contains " will take a good 3-4 seconds, and > > if the git packs are not in the page cache, and/or you're unfortunate > > enough to have your git

[PATCH 4.9 114/171] xen-netfront: Update features after registering netdev

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 45c8184c1bed1ca8a7f02918552063a00b909bf5 ] Update the features after calling register_netdev() otherwise the device features are not set up correctly and it not possible to change

[PATCH 4.9 122/171] IB/mlx4: Fix an error handling path in mlx4_ib_rereg_user_mr()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3dc7c7badb7502ec3e3aa817a8bdd9e53aa54c52 ] Before returning -EPERM we should release some resources, as already done in the other error handling path of the function. Fixes:

[PATCH 4.9 118/171] bonding: ratelimit failed speed/duplex update warning

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 11e9d7829dd08dbafb24517fe922f11c3a8a9dc2 ] bond_miimon_commit() handles the UP transition for each slave of a bond in the case of MII. It is triggered 10 times per second for the

[PATCH 4.9 119/171] nvmet: fix space padding in serial number

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c73996984902516745bc587d5e8a0b2e034aea05 ] Commit 42de82a8b544 previously attempted to fix this, and it did correctly pad the MN and FR fields with spaces, but the SN field still

[PATCH 4.9 070/171] net: stmmac: ensure jumbo_frm error return is correctly checked for -ve value

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 594238158bf748c285f0a73222cd9b7ccf3c525d ] The current comparison of entry < 0 will never be true since entry is an unsigned integer. Make entry an int to ensure -ve error return

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, Nov 08, 2018 at 01:04:49PM -0800, Greg KH wrote: > > (Also note that even with fast SSD's and/or everything in page cache, > > runnning "tag --contains " will take a good 3-4 seconds, and > > if the git packs are not in the page cache, and/or you're unfortunate > > enough to have your git

[PATCH 4.9 114/171] xen-netfront: Update features after registering netdev

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 45c8184c1bed1ca8a7f02918552063a00b909bf5 ] Update the features after calling register_netdev() otherwise the device features are not set up correctly and it not possible to change

[PATCH 4.9 117/171] enic: do not overwrite error code

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 56f772279a762984f6e9ebbf24a7c829faba5712 ] In failure path, we overwrite err to what vnic_rq_disable() returns. In case it returns 0, enic_open() returns success in case of error.

[PATCH 4.9 120/171] iio: buffer: fix the function signature to match implementation

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 92397a6c38d139d50fabbe9e2dc09b61d53b2377 ] linux/iio/buffer-dma.h was not updated to when length was changed to unsigned int. Fixes: c043ec1ca5ba ("iio:buffer: make length types

[PATCH 4.9 120/171] iio: buffer: fix the function signature to match implementation

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 92397a6c38d139d50fabbe9e2dc09b61d53b2377 ] linux/iio/buffer-dma.h was not updated to when length was changed to unsigned int. Fixes: c043ec1ca5ba ("iio:buffer: make length types

[PATCH 4.9 117/171] enic: do not overwrite error code

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 56f772279a762984f6e9ebbf24a7c829faba5712 ] In failure path, we overwrite err to what vnic_rq_disable() returns. In case it returns 0, enic_open() returns success in case of error.

[PATCH 4.9 103/171] Btrfs: incremental send, fix invalid memory access

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24e52b11e0ca788513b945a87b57cc0522a92933 ] When doing an incremental send, while processing an extent that changed between the parent and send snapshots and that extent was an inline

[PATCH 4.9 123/171] libertas: call into generic suspend code before turning off power

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f75cdff0b986195413215eb062b7da6586f ] When powering down a SDIO connected card during suspend, make sure to call into the generic lbs_suspend() function before pulling the plug.

[PATCH 4.9 105/171] module: fix DEBUG_SET_MODULE_RONX typo

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4d217a5adccf5e806790c37c61cc374a08bd7381 ] The newly added 'rodata_enabled' global variable is protected by the wrong #ifdef, leading to a link error when

[PATCH 4.9 103/171] Btrfs: incremental send, fix invalid memory access

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24e52b11e0ca788513b945a87b57cc0522a92933 ] When doing an incremental send, while processing an extent that changed between the parent and send snapshots and that extent was an inline

[PATCH 4.9 123/171] libertas: call into generic suspend code before turning off power

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f75cdff0b986195413215eb062b7da6586f ] When powering down a SDIO connected card during suspend, make sure to call into the generic lbs_suspend() function before pulling the plug.

[PATCH 4.9 105/171] module: fix DEBUG_SET_MODULE_RONX typo

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4d217a5adccf5e806790c37c61cc374a08bd7381 ] The newly added 'rodata_enabled' global variable is protected by the wrong #ifdef, leading to a link error when

[PATCH 4.9 130/171] fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ac081c3be3fae6d0cc3e1862507fca3862d30b67 ] On non-preempt kernels this loop can take a long time (more than 50 ticks) processing through entries. Link:

[PATCH 4.9 125/171] perf tests: Fix indexing when invoking subtests

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aa90f9f9554616d5738f7bedb4a8f0e5e14d1bc6 ] Recently, the subtest numbering was changed to start from 1. While it is fine for displaying results, this should not be the case when the

[PATCH 4.9 124/171] xhci: Fix USB3 NULL pointer dereference at logical disconnect.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2278446e2b7cd33ad894b32e7eb63afc7db6c86e ] Hub driver will try to disable a USB3 device twice at logical disconnect, racing with xhci_free_dev() callback from the first port disable.

[PATCH 4.9 130/171] fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ac081c3be3fae6d0cc3e1862507fca3862d30b67 ] On non-preempt kernels this loop can take a long time (more than 50 ticks) processing through entries. Link:

[PATCH 4.9 125/171] perf tests: Fix indexing when invoking subtests

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aa90f9f9554616d5738f7bedb4a8f0e5e14d1bc6 ] Recently, the subtest numbering was changed to start from 1. While it is fine for displaying results, this should not be the case when the

[PATCH 4.9 124/171] xhci: Fix USB3 NULL pointer dereference at logical disconnect.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2278446e2b7cd33ad894b32e7eb63afc7db6c86e ] Hub driver will try to disable a USB3 device twice at logical disconnect, racing with xhci_free_dev() callback from the first port disable.

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