[PATCH 4.18 038/150] rxrpc: Fix transport sockopts to get IPv4 errors on an IPv6 socket

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 37a675e768d7606fe8a53e0c459c9b53e121ac20 ] It seems that enabling IPV6_RECVERR on an IPv6 socket doesn't also turn on IP_RECVERR, so neither local errors nor ICMP-transported remote

[PATCH 4.18 036/150] rxrpc: Fix checks as to whether we should set up a new call

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dc71db34e4f3c06b8277c8f3c2ff014610607a8c ] There's a check in rxrpc_data_ready() that's checking the CLIENT_INITIATED flag in the packet type field rather than in the packet flags

[PATCH 4.18 046/150] r8152: Check for supported Wake-on-LAN Modes

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

[PATCH 4.18 040/150] netfilter: nft_set_rbtree: add missing rb_erase() in GC routine

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a13f814a67b12a2f29d1decf4b4f4e700658a517 ] The nft_set_gc_batch_check() checks whether gc buffer is full. If gc buffer is full, gc buffer is released by the

[PATCH 4.18 035/150] scsi: qedi: Initialize the stats mutex lock

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3cc5746e5ad7688e274e193fa71278d98aa52759 ] Fix kernel NULL pointer dereference, Call Trace: [] __mutex_lock_slowpath+0xa6/0x1d0 [] mutex_lock+0x1f/0x2f []

[PATCH 4.18 023/150] nl80211: Fix possible Spectre-v1 for NL80211_TXRATE_HT

4.18-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.18 035/150] scsi: qedi: Initialize the stats mutex lock

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3cc5746e5ad7688e274e193fa71278d98aa52759 ] Fix kernel NULL pointer dereference, Call Trace: [] __mutex_lock_slowpath+0xa6/0x1d0 [] mutex_lock+0x1f/0x2f []

[PATCH 4.18 023/150] nl80211: Fix possible Spectre-v1 for NL80211_TXRATE_HT

4.18-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.18 038/150] rxrpc: Fix transport sockopts to get IPv4 errors on an IPv6 socket

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 37a675e768d7606fe8a53e0c459c9b53e121ac20 ] It seems that enabling IPV6_RECVERR on an IPv6 socket doesn't also turn on IP_RECVERR, so neither local errors nor ICMP-transported remote

[PATCH 4.18 036/150] rxrpc: Fix checks as to whether we should set up a new call

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dc71db34e4f3c06b8277c8f3c2ff014610607a8c ] There's a check in rxrpc_data_ready() that's checking the CLIENT_INITIATED flag in the packet type field rather than in the packet flags

[PATCH 4.18 046/150] r8152: Check for supported Wake-on-LAN Modes

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

[PATCH 4.18 040/150] netfilter: nft_set_rbtree: add missing rb_erase() in GC routine

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a13f814a67b12a2f29d1decf4b4f4e700658a517 ] The nft_set_gc_batch_check() checks whether gc buffer is full. If gc buffer is full, gc buffer is released by the

[PATCH 4.18 042/150] asix: Check for supported Wake-on-LAN modes

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

[PATCH 4.18 043/150] ax88179_178a: Check for supported Wake-on-LAN modes

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

[PATCH 4.18 042/150] asix: Check for supported Wake-on-LAN modes

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

[PATCH 4.18 043/150] ax88179_178a: Check for supported Wake-on-LAN modes

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

[PATCH 4.18 002/150] xfrm6: call kfree_skb when skb is toobig

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 215ab0f021c9fea3c18b75e7d522400ee6a49990 ] After commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ("vti6: fix PMTU caching and reporting on xmit"), some too big skbs might be

[PATCH 4.18 022/150] soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift()

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 96fc74333f84cfdf8d434c6c07254e215e2aad00 ] There is a copy and paste bug so we accidentally use the RX_ shift when we're in TX_ mode. Fixes: bb8b2062aff3 ("fsl/qe: setup clock

[PATCH 4.18 031/150] qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor

4.18-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.18 011/150] xfrm: Fix NULL pointer dereference when skb_dst_force clears the dst_entry.

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9e1437937807b0122e8da1ca8765be2adca9aee6 ] Since commit 222d7dbd258d ("net: prevent dst uses after free") skb_dst_force() might clear the dst_entry attached to the skb. The xfrm

[PATCH 4.18 002/150] xfrm6: call kfree_skb when skb is toobig

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 215ab0f021c9fea3c18b75e7d522400ee6a49990 ] After commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ("vti6: fix PMTU caching and reporting on xmit"), some too big skbs might be

[PATCH 4.18 022/150] soc: fsl: qe: Fix copy/paste bug in ucc_get_tdm_sync_shift()

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 96fc74333f84cfdf8d434c6c07254e215e2aad00 ] There is a copy and paste bug so we accidentally use the RX_ shift when we're in TX_ mode. Fixes: bb8b2062aff3 ("fsl/qe: setup clock

[PATCH 4.18 031/150] qed: Avoid implicit enum conversion in qed_roce_mode_to_flavor

4.18-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.18 011/150] xfrm: Fix NULL pointer dereference when skb_dst_force clears the dst_entry.

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9e1437937807b0122e8da1ca8765be2adca9aee6 ] Since commit 222d7dbd258d ("net: prevent dst uses after free") skb_dst_force() might clear the dst_entry attached to the skb. The xfrm

[PATCH 4.18 033/150] qed: Avoid implicit enum conversion in qed_iwarp_parse_rx_pkt

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 77f2d753819b7d50c16abfb778caf1fe075faed0 ] Clang warns when one enumerated type is implicitly converted to another. drivers/net/ethernet/qlogic/qed/qed_iwarp.c:1713:25: warning:

[PATCH 4.18 032/150] qed: Avoid constant logical operation warning in qed_vf_pf_acquire

4.18-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.18 033/150] qed: Avoid implicit enum conversion in qed_iwarp_parse_rx_pkt

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 77f2d753819b7d50c16abfb778caf1fe075faed0 ] Clang warns when one enumerated type is implicitly converted to another. drivers/net/ethernet/qlogic/qed/qed_iwarp.c:1713:25: warning:

[PATCH 4.18 032/150] qed: Avoid constant logical operation warning in qed_vf_pf_acquire

4.18-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.18 008/150] cfg80211: Address some corner cases in scan result channel updating

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 119f94a6fefcc76d47075b83d2b73d04c895df78 ] cfg80211_get_bss_channel() is used to update the RX channel based on the available frame payload information (channel number from DSSS

[PATCH 4.18 010/150] mac80211: fix TX status reporting for ieee80211s

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c42055105785580563535e6d3143cad95c7ac7ee ] TX status reporting to ieee80211s is through ieee80211s_update_metric. There are two problems about ieee80211s_update_metric: 1. The

[PATCH 4.18 009/150] mac80211: TDLS: fix skb queue/priority assignment

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

[PATCH 4.18 008/150] cfg80211: Address some corner cases in scan result channel updating

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 119f94a6fefcc76d47075b83d2b73d04c895df78 ] cfg80211_get_bss_channel() is used to update the RX channel based on the available frame payload information (channel number from DSSS

[PATCH 4.18 010/150] mac80211: fix TX status reporting for ieee80211s

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c42055105785580563535e6d3143cad95c7ac7ee ] TX status reporting to ieee80211s is through ieee80211s_update_metric. There are two problems about ieee80211s_update_metric: 1. The

[PATCH 4.18 009/150] mac80211: TDLS: fix skb queue/priority assignment

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

[PATCH 4.18 005/150] mac80211: Always report TX status

4.18-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.18 007/150] mac80211: fix pending queue hang due to TX_DROP

4.18-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.18 006/150] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.18-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.18 005/150] mac80211: Always report TX status

4.18-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.18 007/150] mac80211: fix pending queue hang due to TX_DROP

4.18-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.18 006/150] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.18-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.18 015/150] drm/i2c: tda9950: set MAX_RETRIES for errors only

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e0dccce1193f87597548d0db6ecc942fb92c04cd ] The CEC_TX_STATUS_MAX_RETRIES should be set for errors only to prevent the CEC framework from retrying the transmit. If the transmit was

[PATCH 4.18 019/150] ARM: dts: BCM63xx: Fix incorrect interrupt specifiers

4.18-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.18 004/150] xfrm: reset crypto_done when iterating over multiple input xfrms

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 782710e333a526780d65918d669cb96646983ba2 ] We only support one offloaded xfrm (we do not have devices that can handle more than one offload), so reset crypto_done in xfrm_input()

[PATCH 4.18 016/150] netfilter: bridge: Dont sabotage nf_hook calls from an l3mdev

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a173f066c7cfc031acb8f541708041e009fc9812 ] For starters, the bridge netfilter code registers operations that are invoked any time nh_hook is called. Specifically, ip_sabotage_in

[PATCH 4.18 020/150] net: macb: Clean 64b dma addresses if they are not detected

4.18-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.18 019/150] ARM: dts: BCM63xx: Fix incorrect interrupt specifiers

4.18-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.18 004/150] xfrm: reset crypto_done when iterating over multiple input xfrms

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 782710e333a526780d65918d669cb96646983ba2 ] We only support one offloaded xfrm (we do not have devices that can handle more than one offload), so reset crypto_done in xfrm_input()

[PATCH 4.18 016/150] netfilter: bridge: Dont sabotage nf_hook calls from an l3mdev

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a173f066c7cfc031acb8f541708041e009fc9812 ] For starters, the bridge netfilter code registers operations that are invoked any time nh_hook is called. Specifically, ip_sabotage_in

[PATCH 4.18 020/150] net: macb: Clean 64b dma addresses if they are not detected

4.18-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.18 015/150] drm/i2c: tda9950: set MAX_RETRIES for errors only

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e0dccce1193f87597548d0db6ecc942fb92c04cd ] The CEC_TX_STATUS_MAX_RETRIES should be set for errors only to prevent the CEC framework from retrying the transmit. If the transmit was

[PATCH 4.18 018/150] arm64: hugetlb: Fix handling of young ptes

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 469ed9d823b7d240d6b9574f061ded7c3834c167 ] In the contiguous bit hugetlb break-before-make code we assume that all hugetlb pages are young. In fact, remove_migration_pte is able to

[PATCH 4.18 017/150] netfilter: conntrack: get rid of double sizeof

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 346fa83d10934cf206e2fd0f514bf8ce186f08fe ] sizeof(sizeof()) is quite strange and does not seem to be what is wanted here. The issue is detected with the help of Coccinelle. Fixes:

[PATCH 4.18 018/150] arm64: hugetlb: Fix handling of young ptes

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 469ed9d823b7d240d6b9574f061ded7c3834c167 ] In the contiguous bit hugetlb break-before-make code we assume that all hugetlb pages are young. In fact, remove_migration_pte is able to

[PATCH 4.18 017/150] netfilter: conntrack: get rid of double sizeof

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 346fa83d10934cf206e2fd0f514bf8ce186f08fe ] sizeof(sizeof()) is quite strange and does not seem to be what is wanted here. The issue is detected with the help of Coccinelle. Fixes:

[PATCH 4.18 000/150] 4.18.17-stable review

This is the start of the stable review cycle for the 4.18.17 release. There are 150 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 Sun Nov 4 18:28:05 UTC 2018. Anything

[PATCH 4.18 012/150] ARM: 8799/1: mm: fix pci_ioremap_io() offset check

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a58ac65e2d7969bcdf1b6acb70fa4d12a88e53e ] IO_SPACE_LIMIT is the ending address of the PCI IO space, i.e something like 0xf (and not 0x10). Therefore, when offset = 0xf

[PATCH 4.18 000/150] 4.18.17-stable review

This is the start of the stable review cycle for the 4.18.17 release. There are 150 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 Sun Nov 4 18:28:05 UTC 2018. Anything

[PATCH 4.18 012/150] ARM: 8799/1: mm: fix pci_ioremap_io() offset check

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3a58ac65e2d7969bcdf1b6acb70fa4d12a88e53e ] IO_SPACE_LIMIT is the ending address of the PCI IO space, i.e something like 0xf (and not 0x10). Therefore, when offset = 0xf

[PATCH 4.19 10/24] bonding: fix length of actor system

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Jungel [ Upstream commit 414dd6fb9a1a1b59983aea7bf0f79f0085ecc5b8 ] The attribute IFLA_BOND_AD_ACTOR_SYSTEM is sent to user space having the length of

[PATCH 4.18 014/150] drm/i2c: tda9950: fix timeout counter check

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d98627d1360d55e3b28f702caca8b6342c4a4e45 ] Currently the check to see if the timeout has reached zero is incorrect and the check is instead checking if the timeout is non-zero and

[PATCH 4.18 003/150] xfrm: reset transport header back to network header after all input transforms ahave been applied

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bfc0698bebcb16d19ecfc89574ad4d696955e5d3 ] A policy may have been set up with multiple transforms (e.g., ESP and ipcomp). In this situation, the ingress IPsec processing iterates in

[PATCH 4.19 19/24] Revert "be2net: remove desc field from be_eq_obj"

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Vecera [ Upstream commit 5ef79151c2fbc401cf38325e9a32e77b9fc593ae ] The mentioned commit needs to be reverted because we cannot pass string allocated on stack to request_irq(). This

[PATCH 4.19 22/24] sparc64: Make corrupted user stacks more debuggable.

4.19-stable review patch. If anyone has any objections, please let me know. -- From: David Miller [ Upstream commit 5b4fc3882a649c9411dd0dcad2ddb78e911d340e ] Right now if we get a corrupted user stack frame we do a do_exit(SIGILL) which is not helpful. If under a debugger,

[PATCH 4.19 08/24] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.19-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.19 11/24] openvswitch: Fix push/pop ethernet validation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "Jaime Caama�o Ruiz" [ Upstream commit 46ebe2834ba5b541f28ee72e556a3fed42c47570 ] When there are both pop and push ethernet header actions among the actions to be applied to a packet, an

[PATCH 4.18 013/150] xfrm: validate template mode

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32bf94fb5c2ec4ec842152d0e5937cd4bb6738fa ] XFRM mode parameters passed as part of the user templates in the IP_XFRM_POLICY are never properly validated. Passing values other than

[PATCH 4.19 23/24] sparc64: Wire up compat getpeername and getsockname.

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 1f2b5b8e2df4591fbca430aff9c5a072dcc0f408 ] Fixes: 8b30ca73b7cc ("sparc: Add all necessary direct socket system calls.") Reported-by: Joseph Myers

[PATCH 4.19 07/24] Revert "net: simplify sock_poll_wait"

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Karsten Graul [ Upstream commit 89ab066d4229acd32e323f1569833302544a4186 ] This reverts commit dd979b4df817e9976f18fb6f9d134d6bc4a3c317. This broke tcp_poll for SMC fallback: An AF_SMC

[PATCH 4.19 10/24] bonding: fix length of actor system

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Jungel [ Upstream commit 414dd6fb9a1a1b59983aea7bf0f79f0085ecc5b8 ] The attribute IFLA_BOND_AD_ACTOR_SYSTEM is sent to user space having the length of

[PATCH 4.18 014/150] drm/i2c: tda9950: fix timeout counter check

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d98627d1360d55e3b28f702caca8b6342c4a4e45 ] Currently the check to see if the timeout has reached zero is incorrect and the check is instead checking if the timeout is non-zero and

[PATCH 4.18 003/150] xfrm: reset transport header back to network header after all input transforms ahave been applied

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bfc0698bebcb16d19ecfc89574ad4d696955e5d3 ] A policy may have been set up with multiple transforms (e.g., ESP and ipcomp). In this situation, the ingress IPsec processing iterates in

[PATCH 4.19 19/24] Revert "be2net: remove desc field from be_eq_obj"

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Vecera [ Upstream commit 5ef79151c2fbc401cf38325e9a32e77b9fc593ae ] The mentioned commit needs to be reverted because we cannot pass string allocated on stack to request_irq(). This

[PATCH 4.19 22/24] sparc64: Make corrupted user stacks more debuggable.

4.19-stable review patch. If anyone has any objections, please let me know. -- From: David Miller [ Upstream commit 5b4fc3882a649c9411dd0dcad2ddb78e911d340e ] Right now if we get a corrupted user stack frame we do a do_exit(SIGILL) which is not helpful. If under a debugger,

[PATCH 4.19 08/24] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.19-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.19 11/24] openvswitch: Fix push/pop ethernet validation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "Jaime Caama�o Ruiz" [ Upstream commit 46ebe2834ba5b541f28ee72e556a3fed42c47570 ] When there are both pop and push ethernet header actions among the actions to be applied to a packet, an

[PATCH 4.18 013/150] xfrm: validate template mode

4.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32bf94fb5c2ec4ec842152d0e5937cd4bb6738fa ] XFRM mode parameters passed as part of the user templates in the IP_XFRM_POLICY are never properly validated. Passing values other than

[PATCH 4.19 23/24] sparc64: Wire up compat getpeername and getsockname.

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 1f2b5b8e2df4591fbca430aff9c5a072dcc0f408 ] Fixes: 8b30ca73b7cc ("sparc: Add all necessary direct socket system calls.") Reported-by: Joseph Myers

[PATCH 4.19 07/24] Revert "net: simplify sock_poll_wait"

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Karsten Graul [ Upstream commit 89ab066d4229acd32e323f1569833302544a4186 ] This reverts commit dd979b4df817e9976f18fb6f9d134d6bc4a3c317. This broke tcp_poll for SMC fallback: An AF_SMC

[PATCH 4.19 21/24] sparc64: Export __node_distance.

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 2b4792eaa9f553764047d157365ed8b7787751a3 ] Some drivers reference it via node_distance(), for example the NVME host driver core. ERROR: "__node_distance"

[PATCH 4.19 09/24] vhost: Fix Spectre V1 vulnerability

4.19-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.19 20/24] sctp: check policy more carefully when getting pr status

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 713358369382cebf92f6e98ce2005f94e7344931 ] When getting pr_assocstatus and pr_streamstatus by sctp_getsockopt, it doesn't correctly process the case when policy is

[PATCH 4.18 001/150] xfrm: Validate address prefix lengths in the xfrm selector.

4.18-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.19 24/24] net: bridge: remove ipv6 zero address check in mcast queries

4.19-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.19 21/24] sparc64: Export __node_distance.

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 2b4792eaa9f553764047d157365ed8b7787751a3 ] Some drivers reference it via node_distance(), for example the NVME host driver core. ERROR: "__node_distance"

[PATCH 4.19 09/24] vhost: Fix Spectre V1 vulnerability

4.19-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.19 20/24] sctp: check policy more carefully when getting pr status

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 713358369382cebf92f6e98ce2005f94e7344931 ] When getting pr_assocstatus and pr_streamstatus by sctp_getsockopt, it doesn't correctly process the case when policy is

[PATCH 4.18 001/150] xfrm: Validate address prefix lengths in the xfrm selector.

4.18-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.19 24/24] net: bridge: remove ipv6 zero address check in mcast queries

4.19-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.19 02/24] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

4.19-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.19 02/24] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

4.19-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.19 03/24] net/mlx5e: fix csum adjustments caused by RXFCS

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit d48051c5b8376038c2b287c3b1bd55b8d391d567 ] As shown by Dmitris, we need to use csum_block_add() instead of csum_add() when adding the FCS contribution to skb

[PATCH 4.19 04/24] net: sched: gred: pass the right attribute to gred_change_table_def()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit 38b4f18d56372e1e21771ab7b0357b853330186c ] gred_change_table_def() takes a pointer to TCA_GRED_DPS attribute, and expects it will be able to interpret its

[PATCH 4.19 06/24] net: udp: fix handling of CHECKSUM_COMPLETE packets

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Sean Tranchetti [ Upstream commit db4f1be3ca9b0ef7330763d07bf4ace83ad6f913 ] Current handling of CHECKSUM_COMPLETE packets by the UDP stack is incorrect for any packet that has an incorrect

Re: [PATCH 1/1] Add vhost_blk driver

On Fri, Nov 02, 2018 at 06:21:23PM +, Vitaly Mayatskikh wrote: > This driver accelerates host side of virtio-blk. > > Signed-off-by: Vitaly Mayatskikh > --- > drivers/vhost/Kconfig | 13 ++ > drivers/vhost/Makefile | 3 + > drivers/vhost/blk.c| 510

[PATCH 4.19 00/24] 4.19.1-stable review

This is the start of the stable review cycle for the 4.19.1 release. There are 24 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 Sun Nov 4 18:28:10 UTC 2018. Anything

[PATCH 4.19 05/24] net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Niklas Cassel [ Upstream commit 30549aab146ccb1275230c3b4b4bc6b4181fd54e ] When building stmmac, it is only possible to select CONFIG_DWMAC_GENERIC, or any of the glue drivers, when

[PATCH 4.19 03/24] net/mlx5e: fix csum adjustments caused by RXFCS

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit d48051c5b8376038c2b287c3b1bd55b8d391d567 ] As shown by Dmitris, we need to use csum_block_add() instead of csum_add() when adding the FCS contribution to skb

[PATCH 4.19 04/24] net: sched: gred: pass the right attribute to gred_change_table_def()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Kicinski [ Upstream commit 38b4f18d56372e1e21771ab7b0357b853330186c ] gred_change_table_def() takes a pointer to TCA_GRED_DPS attribute, and expects it will be able to interpret its

[PATCH 4.19 06/24] net: udp: fix handling of CHECKSUM_COMPLETE packets

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Sean Tranchetti [ Upstream commit db4f1be3ca9b0ef7330763d07bf4ace83ad6f913 ] Current handling of CHECKSUM_COMPLETE packets by the UDP stack is incorrect for any packet that has an incorrect

Re: [PATCH 1/1] Add vhost_blk driver

On Fri, Nov 02, 2018 at 06:21:23PM +, Vitaly Mayatskikh wrote: > This driver accelerates host side of virtio-blk. > > Signed-off-by: Vitaly Mayatskikh > --- > drivers/vhost/Kconfig | 13 ++ > drivers/vhost/Makefile | 3 + > drivers/vhost/blk.c| 510

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