[PATCH 4.4 092/114] net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 4ba4c566ba8448a05e6257e0b98a21f1a0d55315 ] The loop wants to skip previously dumped addresses, so loops until current index >= saved index. If the message fills

[PATCH 4.4 089/114] net: bridge: remove ipv6 zero address check in mcast queries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov commit 0fe5119e267f3e3d8ac206895f5922195ec55a8a upstream. Recently a check was added which prevents marking of routers with zero source address, but for IPv6 that cannot

[PATCH 4.4 087/114] perf tools: Disable parallelism for make clean

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit da15fc2fa9c07b23db8f5e479bd8a9f0d741ca07 ] The Yocto build system does a 'make clean' when rebuilding due to changed dependencies, and that consistently fails for me (causing the

[PATCH 4.4 091/114] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit ee1abcf689353f36d9322231b4320926096bdee0 ] Commit a61bbcf28a8c ("[NET]: Store skb->timestamp as offset to a base timestamp") introduces a neighbour control

[PATCH 4.4 083/114] MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68fe55680d0f3342969f49412fceabb90bdfadba ] Fix a commit 3021773c7c3e ("MIPS: DEC: Avoid la pseudo-instruction in delay slots") regression and remove assembly errors:

[PATCH 4.4 088/114] bridge: do not add port to router list when receives query with source 0.0.0.0

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu commit 5a2de63fd1a59c30c02526d427bc014b98adf508 upstream. Based on RFC 4541, 2.1.1. IGMP Forwarding Rules The switch supporting IGMP snooping must maintain a list of

[PATCH 4.4 083/114] MIPS: DEC: Fix an int-handler.S CPU_DADDI_WORKAROUNDS regression

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68fe55680d0f3342969f49412fceabb90bdfadba ] Fix a commit 3021773c7c3e ("MIPS: DEC: Avoid la pseudo-instruction in delay slots") regression and remove assembly errors:

[PATCH 4.4 088/114] bridge: do not add port to router list when receives query with source 0.0.0.0

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu commit 5a2de63fd1a59c30c02526d427bc014b98adf508 upstream. Based on RFC 4541, 2.1.1. IGMP Forwarding Rules The switch supporting IGMP snooping must maintain a list of

[PATCH 4.4 097/114] sctp: fix race on sctp_id2asoc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit b336decab22158937975293aea79396525f92bb3 ] syzbot reported an use-after-free involving sctp_id2asoc. Dmitry Vyukov helped to root cause it and it is

[PATCH 4.4 094/114] net: socket: fix a missing-check bug

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit b6168562c8ce2bd5a30e213021650422e08764dc ] In ethtool_ioctl(), the ioctl command 'ethcmd' is checked through a switch statement to see whether it is necessary to

[PATCH 4.4 097/114] sctp: fix race on sctp_id2asoc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner [ Upstream commit b336decab22158937975293aea79396525f92bb3 ] syzbot reported an use-after-free involving sctp_id2asoc. Dmitry Vyukov helped to root cause it and it is

[PATCH 4.4 094/114] net: socket: fix a missing-check bug

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit b6168562c8ce2bd5a30e213021650422e08764dc ] In ethtool_ioctl(), the ioctl command 'ethcmd' is checked through a switch statement to see whether it is necessary to

[PATCH 4.4 100/114] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit da71577545a52be3e0e9225a946e5fd79cfab015 ] When an FDB entry is configured, the address is validated to have the length of an Ethernet address, but the device

[PATCH 4.4 099/114] vhost: Fix Spectre V1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit ff002269a4ee9c769dbf9365acef633ebcbd6cbe ] The idx in vhost_vring_ioctl() was controlled by userspace, hence a potential exploitation of the Spectre variant 1

[PATCH 4.4 098/114] net: drop skb on failure in ip_check_defrag()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 7de414a9dd91426318df7b63da024b2b07e53df5 ] Most callers of pskb_trim_rcsum() simply drop the skb when it fails, however, ip_check_defrag() still continues to pass

[PATCH 4.4 100/114] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit da71577545a52be3e0e9225a946e5fd79cfab015 ] When an FDB entry is configured, the address is validated to have the length of an Ethernet address, but the device

[PATCH 4.4 099/114] vhost: Fix Spectre V1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit ff002269a4ee9c769dbf9365acef633ebcbd6cbe ] The idx in vhost_vring_ioctl() was controlled by userspace, hence a potential exploitation of the Spectre variant 1

[PATCH 4.4 098/114] net: drop skb on failure in ip_check_defrag()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 7de414a9dd91426318df7b63da024b2b07e53df5 ] Most callers of pskb_trim_rcsum() simply drop the skb when it fails, however, ip_check_defrag() still continues to pass

[PATCH 4.4 101/114] mremap: properly flush TLB before releasing the page

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds Commit eb66ae030829605d61fbef1909ce310e29f78821 upstream. This is a backport to stable 4.4.y. Jann Horn points out that our TLB flushing was subtly wrong for the mremap()

[PATCH 4.4 103/114] ahci: dont ignore result code of ahci_reset_controller()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d312fefea8387503375f728855c9a62de20c9665 ] ahci_pci_reset_controller() calls ahci_reset_controller(), which may fail, but ignores the result code and always returns success. This may

[PATCH 4.4 101/114] mremap: properly flush TLB before releasing the page

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds Commit eb66ae030829605d61fbef1909ce310e29f78821 upstream. This is a backport to stable 4.4.y. Jann Horn points out that our TLB flushing was subtly wrong for the mremap()

[PATCH 4.4 103/114] ahci: dont ignore result code of ahci_reset_controller()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d312fefea8387503375f728855c9a62de20c9665 ] ahci_pci_reset_controller() calls ahci_reset_controller(), which may fail, but ignores the result code and always returns success. This may

[PATCH 4.4 105/114] ptp: fix Spectre v1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit efa61c8cf2950ab5c0e66cff3cabe2a2b24e81ba upstream. pin_index can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.4 076/114] spi: xlp: fix error return code in xlp_spi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9a6b94796ae6feaf275ec6200e9b2964db208182 ] platform_get_irq() returns an error code, but the spi-xlp driver ignores it and always returns -EINVAL. This is not correct and, prevents

[PATCH 4.4 075/114] spi/bcm63xx: fix error return code in bcm63xx_spi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ba8afe94723e9ba665aee9cca649fb2c80f7304c ] platform_get_irq() returns an error code, but the spi-bcm63xx driver ignores it and always returns -ENXIO. This is not correct and,

[PATCH 4.4 104/114] cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 169b803397499be85bdd1e3d07d6f5e3d4bd669e upstream. the victim might've been rmdir'ed just before the lock_rename(); unlike the normal callers, we do not look the source up after

[PATCH 4.4 102/114] crypto: shash - Fix a sleep-in-atomic bug in shash_setkey_unaligned

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9039f3ef446e9ffa200200c934f049add9e58426 ] The SCTP program may sleep under a spinlock, and the function call path is: sctp_generate_t3_rtx_event (acquire the spinlock) sctp_do_sm

[PATCH 4.4 077/114] ASoC: spear: fix error return code in spdif_in_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 27d30400c448264c1ac9434cb836de0c230af213 ] platform_get_irq() returns an error code, but the spdif_in driver ignores it and always returns -EINVAL. This is not correct, and prevents

[PATCH 4.4 075/114] spi/bcm63xx: fix error return code in bcm63xx_spi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ba8afe94723e9ba665aee9cca649fb2c80f7304c ] platform_get_irq() returns an error code, but the spi-bcm63xx driver ignores it and always returns -ENXIO. This is not correct and,

[PATCH 4.4 104/114] cachefiles: fix the race between cachefiles_bury_object() and rmdir(2)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 169b803397499be85bdd1e3d07d6f5e3d4bd669e upstream. the victim might've been rmdir'ed just before the lock_rename(); unlike the normal callers, we do not look the source up after

[PATCH 4.4 102/114] crypto: shash - Fix a sleep-in-atomic bug in shash_setkey_unaligned

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9039f3ef446e9ffa200200c934f049add9e58426 ] The SCTP program may sleep under a spinlock, and the function call path is: sctp_generate_t3_rtx_event (acquire the spinlock) sctp_do_sm

[PATCH 4.4 077/114] ASoC: spear: fix error return code in spdif_in_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 27d30400c448264c1ac9434cb836de0c230af213 ] platform_get_irq() returns an error code, but the spdif_in driver ignores it and always returns -EINVAL. This is not correct, and prevents

[PATCH 4.4 105/114] ptp: fix Spectre v1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit efa61c8cf2950ab5c0e66cff3cabe2a2b24e81ba upstream. pin_index can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.4 076/114] spi: xlp: fix error return code in xlp_spi_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9a6b94796ae6feaf275ec6200e9b2964db208182 ] platform_get_irq() returns an error code, but the spi-xlp driver ignores it and always returns -EINVAL. This is not correct and, prevents

[PATCH 4.4 071/114] usb: ehci-omap: fix error return code in ehci_hcd_omap_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 99dbff202e28ad1dadf55b058bcae7908678e963 ] platform_get_irq() returns an error code, but the ehci-omap driver ignores it and always returns -ENODEV. This is not correct and, prevents

[PATCH 4.4 071/114] usb: ehci-omap: fix error return code in ehci_hcd_omap_probe()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 99dbff202e28ad1dadf55b058bcae7908678e963 ] platform_get_irq() returns an error code, but the ehci-omap driver ignores it and always returns -ENODEV. This is not correct and, prevents

[PATCH 4.4 107/114] IB/ucm: Fix Spectre v1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 0295e39595e1146522f2722715dba7f7fba42217 upstream. hdr.cmd can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.4 107/114] IB/ucm: Fix Spectre v1 vulnerability

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 0295e39595e1146522f2722715dba7f7fba42217 upstream. hdr.cmd can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.4 113/114] x86/percpu: Fix this_cpu_read()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b59167ac7bafd804c91e49ad53c6d33a7394d4c8 upstream. Eric reported that a sequence count loop using this_cpu_read() got optimized out. This is wrong, this_cpu_read() must

[PATCH 4.9 010/171] ARM: dts: BCM63xx: Fix incorrect interrupt specifiers

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3ab97942d0213b6583a5408630a8cbbfbf54730f ] A number of our interrupts were incorrectly specified, fix both the PPI and SPI interrupts to be correct. Fixes: b5762cacc411 ("ARM:

[PATCH 4.4 113/114] x86/percpu: Fix this_cpu_read()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit b59167ac7bafd804c91e49ad53c6d33a7394d4c8 upstream. Eric reported that a sequence count loop using this_cpu_read() got optimized out. This is wrong, this_cpu_read() must

[PATCH 4.9 010/171] ARM: dts: BCM63xx: Fix incorrect interrupt specifiers

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3ab97942d0213b6583a5408630a8cbbfbf54730f ] A number of our interrupts were incorrectly specified, fix both the PPI and SPI interrupts to be correct. Fixes: b5762cacc411 ("ARM:

[PATCH 4.9 001/171] xfrm: Validate address prefix lengths in the xfrm selector.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 4.9 003/171] mac80211: Always report TX status

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8682250b3c1b75a45feb7452bc413d004cfe3778 ] If a frame is dropped for any reason, mac80211 wouldn't report the TX status back to user space. As the user space may rely on the

[PATCH 4.9 001/171] xfrm: Validate address prefix lengths in the xfrm selector.

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 4.9 003/171] mac80211: Always report TX status

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8682250b3c1b75a45feb7452bc413d004cfe3778 ] If a frame is dropped for any reason, mac80211 wouldn't report the TX status back to user space. As the user space may rely on the

[PATCH 4.9 005/171] mac80211: fix pending queue hang due to TX_DROP

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6eae4a6c2be387fec41b0d2782c4fffb57159498 ] In our environment running lots of mesh nodes, we are seeing the pending queue hang periodically, with the debugfs queues file showing

[PATCH 4.9 005/171] mac80211: fix pending queue hang due to TX_DROP

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6eae4a6c2be387fec41b0d2782c4fffb57159498 ] In our environment running lots of mesh nodes, we are seeing the pending queue hang periodically, with the debugfs queues file showing

[PATCH 4.9 004/171] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24f33e64fcd0d50a4b1a8e5b41bd0257aa66b0e8 ] Core regulatory hints didn't set wiphy_idx to WIPHY_IDX_INVALID. Since the regulatory request is zeroed, wiphy_idx was always implicitly

[PATCH 4.9 004/171] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24f33e64fcd0d50a4b1a8e5b41bd0257aa66b0e8 ] Core regulatory hints didn't set wiphy_idx to WIPHY_IDX_INVALID. Since the regulatory request is zeroed, wiphy_idx was always implicitly

[PATCH 4.9 018/171] qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d3a315795b4ce8b105a64a90699103121bde04a8 ] Clang warns when one enumerated type is implicitly converted to another. drivers/net/ethernet/qlogic/qed/qed_roce.c:153:12: warning:

[PATCH 4.9 018/171] qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d3a315795b4ce8b105a64a90699103121bde04a8 ] Clang warns when one enumerated type is implicitly converted to another. drivers/net/ethernet/qlogic/qed/qed_roce.c:153:12: warning:

[PATCH 4.9 016/171] Bluetooth: SMP: fix crash in unpairing

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cb28c306b93b71f2741ce1a5a66289db26715f4d ] In case unpair_device() was called through mgmt interface at the same time when pairing was in progress, Bluetooth kernel module crash was

[PATCH 4.9 025/171] smsc75xx: Check for Wake-on-LAN modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9c734b2769a73eea2e9e9767c0e0bf839ff23679 ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.9 024/171] r8152: Check for supported Wake-on-LAN Modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f2750df1548bd8a2b060eb609fc43ca82811af4c ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.9 026/171] smsc95xx: Check for Wake-on-LAN modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c530c471ba37bdd9fe1c7185b01455c00ae606fb ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.9 014/171] nl80211: Fix possible Spectre-v1 for NL80211_TXRATE_HT

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30fe6d50eb088783c8729c7d930f65296b2b3fa7 ] Use array_index_nospec() to sanitize ridx with respect to speculation. Signed-off-by: Masashi Honma Signed-off-by: Johannes Berg

[PATCH 4.9 016/171] Bluetooth: SMP: fix crash in unpairing

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cb28c306b93b71f2741ce1a5a66289db26715f4d ] In case unpair_device() was called through mgmt interface at the same time when pairing was in progress, Bluetooth kernel module crash was

[PATCH 4.9 025/171] smsc75xx: Check for Wake-on-LAN modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9c734b2769a73eea2e9e9767c0e0bf839ff23679 ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.9 024/171] r8152: Check for supported Wake-on-LAN Modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f2750df1548bd8a2b060eb609fc43ca82811af4c ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.9 026/171] smsc95xx: Check for Wake-on-LAN modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c530c471ba37bdd9fe1c7185b01455c00ae606fb ] The driver does not check for Wake-on-LAN modes specified by an user, but will conditionally set the device as wake-up enabled or not based

[PATCH 4.9 014/171] nl80211: Fix possible Spectre-v1 for NL80211_TXRATE_HT

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30fe6d50eb088783c8729c7d930f65296b2b3fa7 ] Use array_index_nospec() to sanitize ridx with respect to speculation. Signed-off-by: Masashi Honma Signed-off-by: Johannes Berg

[PATCH 4.9 007/171] mac80211: TDLS: fix skb queue/priority assignment

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cb59bc14e830028d2244861216df038165d7625d ] If the TDLS setup happens over a connection to an AP that doesn't have QoS, we nevertheless assign a non-zero TID (skb->priority) and queue

[PATCH 4.9 007/171] mac80211: TDLS: fix skb queue/priority assignment

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cb59bc14e830028d2244861216df038165d7625d ] If the TDLS setup happens over a connection to an AP that doesn't have QoS, we nevertheless assign a non-zero TID (skb->priority) and queue

[PATCH 4.9 019/171] qed: Avoid constant logical operation warning in qed_vf_pf_acquire

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c492a9d55ba99079210ed901dd8a5423f980487 ] Clang warns when a constant is used in a boolean context as it thinks a bitwise operation may have been intended.

[PATCH 4.9 019/171] qed: Avoid constant logical operation warning in qed_vf_pf_acquire

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c492a9d55ba99079210ed901dd8a5423f980487 ] Clang warns when a constant is used in a boolean context as it thinks a bitwise operation may have been intended.

[PATCH 4.9 020/171] asix: Check for supported Wake-on-LAN modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c4ce446e33d7a0e978256ac6fea4c80e59d9de5f ] The driver currently silently accepts unsupported Wake-on-LAN modes (other than WAKE_PHY or WAKE_MAGIC) without reporting that to the user,

[PATCH 4.9 029/171] net: fec: fix rare tx timeout

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 657ade07df72847f591ccdb36bd9b91ed0edbac3 ] During certain heavy network loads TX could time out with TX ring dump. TX is sometimes never restarted after reaching "tx_stop_threshold"

[PATCH 4.9 043/171] ipv6: set rt6i_protocol properly in the route when it is installed

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b91d532928dff2141ea9c107c3e73104d9843767 ] After commit c2ed1880fd61 ("net: ipv6: check route protocol when deleting routes"), ipv6 route checks rt protocol when trying to remove a

[PATCH 4.9 030/171] declance: Fix continuation with the adapter identification message

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fe3a83af6a50199bf250fa331e94216912f79395 ] Fix a commit 4bcc595ccd80 ("printk: reinstate KERN_CONT for printing continuation lines") regression with the `declance' driver, which

[PATCH 4.9 033/171] mm/memory_hotplug.c: fix overflow in test_pages_in_a_zone()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d6d8c8a48291b929b2e039f220f0b62958cccfea ] When mainline introduced commit a96dfddbcc04 ("base/memory, hotplug: fix a kernel oops in show_valid_zones()"), it obtained the valid start

[PATCH 4.9 020/171] asix: Check for supported Wake-on-LAN modes

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c4ce446e33d7a0e978256ac6fea4c80e59d9de5f ] The driver currently silently accepts unsupported Wake-on-LAN modes (other than WAKE_PHY or WAKE_MAGIC) without reporting that to the user,

[PATCH 4.9 029/171] net: fec: fix rare tx timeout

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 657ade07df72847f591ccdb36bd9b91ed0edbac3 ] During certain heavy network loads TX could time out with TX ring dump. TX is sometimes never restarted after reaching "tx_stop_threshold"

[PATCH 4.9 043/171] ipv6: set rt6i_protocol properly in the route when it is installed

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b91d532928dff2141ea9c107c3e73104d9843767 ] After commit c2ed1880fd61 ("net: ipv6: check route protocol when deleting routes"), ipv6 route checks rt protocol when trying to remove a

[PATCH 4.9 030/171] declance: Fix continuation with the adapter identification message

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fe3a83af6a50199bf250fa331e94216912f79395 ] Fix a commit 4bcc595ccd80 ("printk: reinstate KERN_CONT for printing continuation lines") regression with the `declance' driver, which

[PATCH 4.9 033/171] mm/memory_hotplug.c: fix overflow in test_pages_in_a_zone()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d6d8c8a48291b929b2e039f220f0b62958cccfea ] When mainline introduced commit a96dfddbcc04 ("base/memory, hotplug: fix a kernel oops in show_valid_zones()"), it obtained the valid start

[PATCH 4.9 011/171] net: macb: Clean 64b dma addresses if they are not detected

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e1e5d8a9fe737d94ccc0ccbaf0c97f69a8f3e000 ] Clear ADDR64 dma bit in DMACFG register in case that HW_DMA_CAP_64B is not detected on 64bit system. The issue was observed when

[PATCH 4.9 011/171] net: macb: Clean 64b dma addresses if they are not detected

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e1e5d8a9fe737d94ccc0ccbaf0c97f69a8f3e000 ] Clear ADDR64 dma bit in DMACFG register in case that HW_DMA_CAP_64B is not detected on 64bit system. The issue was observed when

[PATCH 4.9 041/171] i2c: bcm2835: Avoid possible NULL ptr dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ababb08938df7ac245d30a58b95b94ecf8dc04fc ] Since commit e2474541032d ("bcm2835: Fix hang for writing messages larger than 16 bytes") the interrupt handler is prone to a possible NULL

[PATCH 4.9 038/171] igb: Remove superfluous reset to PHY and page 0 selection

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a83fba6cae89dd9c0625e68ff8791c67ac0 ] This patch reverts two previous applied patches to fix an issue that appeared when using SGMII based SFP modules. In the current state the

[PATCH 4.9 039/171] ACPI: sysfs: Make ACPI GPE mask kernel parameter cover all GPEs

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0f27cff8597d86f881ea8274b49b63b678c14a3c ] The acpi_mask_gpe= kernel parameter documentation states that the range of mask is 128 GPEs (0x00 to 0x7F). The acpi_masked_gpes mask is a

[PATCH 4.9 041/171] i2c: bcm2835: Avoid possible NULL ptr dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ababb08938df7ac245d30a58b95b94ecf8dc04fc ] Since commit e2474541032d ("bcm2835: Fix hang for writing messages larger than 16 bytes") the interrupt handler is prone to a possible NULL

[PATCH 4.9 038/171] igb: Remove superfluous reset to PHY and page 0 selection

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a83fba6cae89dd9c0625e68ff8791c67ac0 ] This patch reverts two previous applied patches to fix an issue that appeared when using SGMII based SFP modules. In the current state the

[PATCH 4.9 039/171] ACPI: sysfs: Make ACPI GPE mask kernel parameter cover all GPEs

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0f27cff8597d86f881ea8274b49b63b678c14a3c ] The acpi_mask_gpe= kernel parameter documentation states that the range of mask is 128 GPEs (0x00 to 0x7F). The acpi_masked_gpes mask is a

[PATCH 4.9 062/171] mac80211: fix TX aggregation start/stop callback race

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a7c0a6438b8e7636d5a22e572892cc234f68297 ] When starting or stopping an aggregation session, one of the steps is that the driver calls back to mac80211 that the start/stop can

[PATCH 4.9 047/171] orangefs: off by ones in xattr size checks

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5f13e58767a53ebb54265e03c0c4a67650286263 ] A previous patch which claimed to remove off by ones actually introduced them. strlen() returns the length of the string not including the

[PATCH 4.9 062/171] mac80211: fix TX aggregation start/stop callback race

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7a7c0a6438b8e7636d5a22e572892cc234f68297 ] When starting or stopping an aggregation session, one of the steps is that the driver calls back to mac80211 that the start/stop can

[PATCH 4.9 047/171] orangefs: off by ones in xattr size checks

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5f13e58767a53ebb54265e03c0c4a67650286263 ] A previous patch which claimed to remove off by ones actually introduced them. strlen() returns the length of the string not including the

[PATCH 4.9 063/171] libata: fix error checking in in ata_parse_force_one()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f7cf69ae171592d133c69b9adaa5de7cfb6038ea ] ata_parse_force_one() was incorrectly comparing @p to @endp when it should have been comparing @id. The only consequence is that it may

[PATCH 4.9 063/171] libata: fix error checking in in ata_parse_force_one()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f7cf69ae171592d133c69b9adaa5de7cfb6038ea ] ata_parse_force_one() was incorrectly comparing @p to @endp when it should have been comparing @id. The only consequence is that it may

[PATCH 4.9 058/171] ata: sata_rcar: Handle return value of clk_prepare_enable

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5dc63fdcc09f47fb226b8bc7d83a61feb787d817 ] Here, Clock enable can failed. So adding an error check for clk_prepare_enable. tj: minor style updates Signed-off-by: Arvind Yadav

[PATCH 4.9 055/171] ath10k: fix NAPI enable/disable symmetry for AHB interface

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a7595a820b07db9ac0d8f479ff62002bdd32a05a ] Move NAPI enable to 'ath10k_ahb_hif_start' from 'ath10k_ahb_hif_power_up'. This is to maintain the symmetry of calling napi_enable() from

[PATCH 4.9 058/171] ata: sata_rcar: Handle return value of clk_prepare_enable

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5dc63fdcc09f47fb226b8bc7d83a61feb787d817 ] Here, Clock enable can failed. So adding an error check for clk_prepare_enable. tj: minor style updates Signed-off-by: Arvind Yadav

[PATCH 4.9 055/171] ath10k: fix NAPI enable/disable symmetry for AHB interface

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a7595a820b07db9ac0d8f479ff62002bdd32a05a ] Move NAPI enable to 'ath10k_ahb_hif_start' from 'ath10k_ahb_hif_power_up'. This is to maintain the symmetry of calling napi_enable() from

[PATCH 4.9 068/171] gpu: ipu-v3: Fix CSI selection for VDIC

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b7dfee2433576f1f030cb84cdb04b70f36554992 ] The description of the CSI_SEL bit in the i.MX6 reference manual is incorrect. It states "This bit defines which CSI is the input to the

[PATCH 4.9 068/171] gpu: ipu-v3: Fix CSI selection for VDIC

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b7dfee2433576f1f030cb84cdb04b70f36554992 ] The description of the CSI_SEL bit in the i.MX6 reference manual is incorrect. It states "This bit defines which CSI is the input to the

[PATCH 4.9 069/171] elevator: fix truncation of icq_cache_name

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9bd2bbc01d17ddd567cc0f81f77fe1163e497462 ] gcc 7.1 reports the following warning: block/elevator.c: In function ‘elv_register’: block/elevator.c:898:5: warning: ‘snprintf’

[PATCH 4.9 069/171] elevator: fix truncation of icq_cache_name

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9bd2bbc01d17ddd567cc0f81f77fe1163e497462 ] gcc 7.1 reports the following warning: block/elevator.c: In function ‘elv_register’: block/elevator.c:898:5: warning: ‘snprintf’

[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

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