[PATCH 4.14 140/143] rtnetlink: Disallow FDB configuration for non-Ethernet device

4.14-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.14 104/143] selftests: rtnetlink.sh explicitly requires bash.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3c718e677c2b35b449992adc36ecce883c467e98 ] the script rtnetlink.sh requires a bash-only features (sleep with sub-second precision). This may cause random test failure if the default

[PATCH 4.14 113/143] perf tools: Disable parallelism for make clean

4.14-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.14 110/143] media: uvcvideo: Fix driver reference counting

4.14-stable review patch. If anyone has any objections, please let me know. -- commit f9ffcb0a21e1fa8e64d09ed613d884e054ae8191 upstream kref_init initializes the reference count to 1, not 0. This additional reference is never released since the conversion to reference counters.

[PATCH 4.14 112/143] Revert "netfilter: ipv6: nf_defrag: drop skb dst before queueing"

4.14-stable review patch. If anyone has any objections, please let me know. -- This reverts commit 28c74ff85efd192aeca9005499ca50c24d795f61. >From Florian Westphal : It causes kernel crash for locally generated ipv6 fragments when netfilter ipv6 defragmentation

[PATCH 4.14 108/143] kvm: x86: fix WARN due to uninitialized guest FPU state

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 5663d8f9bbe4bf15488f7351efb61ea20fa6de06 upstream [ cut here ] Bad FPU state detected at kvm_put_guest_fpu+0xd8/0x2d0 [kvm], reinitializing FPU registers. WARNING:

[PATCH 4.14 132/143] bonding: fix length of actor system

4.14-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.14 139/143] net/mlx5e: fix csum adjustments caused by RXFCS

4.14-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.14 138/143] net: fix pskb_trim_rcsum_slow() with odd trim offset

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dimitris Michailidis [ Upstream commit d55bef5059dd057bd077155375c581b49d25be7e ] We've been getting checksum errors involving small UDP packets, usually 59B packets with 1 extra non-zero

[PATCH 4.14 133/143] ip6_tunnel: Fix encapsulation layout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit d4d576f5ab7edcb757bb33e6a5600666a0b1232d ] Commit 058214a4d1df ("ip6_tun: Add infrastructure for doing encapsulation") added the ip6_tnl_encap() call in

[PATCH 4.14 107/143] mtd: spi-nor: Add support for is25wp series chips

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d616f81cdd2a21edfa90a595a4e9b143f5ba8414 ] Added support for is25wp032, is25wp064 and is25wp128. Signed-off-by: Kimmo Rautkoski Reviewed-by: Marek Vasut Signed-off-by: Boris

[PATCH 4.14 139/143] net/mlx5e: fix csum adjustments caused by RXFCS

4.14-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.14 138/143] net: fix pskb_trim_rcsum_slow() with odd trim offset

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dimitris Michailidis [ Upstream commit d55bef5059dd057bd077155375c581b49d25be7e ] We've been getting checksum errors involving small UDP packets, usually 59B packets with 1 extra non-zero

[PATCH 4.14 133/143] ip6_tunnel: Fix encapsulation layout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit d4d576f5ab7edcb757bb33e6a5600666a0b1232d ] Commit 058214a4d1df ("ip6_tun: Add infrastructure for doing encapsulation") added the ip6_tnl_encap() call in

[PATCH 4.14 107/143] mtd: spi-nor: Add support for is25wp series chips

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d616f81cdd2a21edfa90a595a4e9b143f5ba8414 ] Added support for is25wp032, is25wp064 and is25wp128. Signed-off-by: Kimmo Rautkoski Reviewed-by: Marek Vasut Signed-off-by: Boris

[PATCH 4.14 132/143] bonding: fix length of actor system

4.14-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.14 135/143] net/mlx5: Take only bit 24-26 of wqe.pftype_wq for page fault type

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Huy Nguyen [ Upstream commit a48bc513159d4767f9988f0d857b2b0c38a4d614 ] The HW spec defines only bits 24-26 of pftype_wq as the page fault type, use the required mask to ensure that. Fixes:

[PATCH 4.14 136/143] net: sched: Fix for duplicate class dump

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Phil Sutter [ Upstream commit 3c53ed8fef6881a864f0ee8240ed2793ef73ad0d ] When dumping classes by parent, kernel would return classes twice: | # tc qdisc add dev lo root prio | # tc class

[PATCH 4.14 137/143] net: drop skb on failure in ip_check_defrag()

4.14-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.14 134/143] openvswitch: Fix push/pop ethernet validation

4.14-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.14 135/143] net/mlx5: Take only bit 24-26 of wqe.pftype_wq for page fault type

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Huy Nguyen [ Upstream commit a48bc513159d4767f9988f0d857b2b0c38a4d614 ] The HW spec defines only bits 24-26 of pftype_wq as the page fault type, use the required mask to ensure that. Fixes:

[PATCH 4.14 136/143] net: sched: Fix for duplicate class dump

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Phil Sutter [ Upstream commit 3c53ed8fef6881a864f0ee8240ed2793ef73ad0d ] When dumping classes by parent, kernel would return classes twice: | # tc qdisc add dev lo root prio | # tc class

[PATCH 4.14 137/143] net: drop skb on failure in ip_check_defrag()

4.14-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.14 134/143] openvswitch: Fix push/pop ethernet validation

4.14-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.14 126/143] r8169: fix NAPI handling under high load

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high

[PATCH 4.14 126/143] r8169: fix NAPI handling under high load

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high

[PATCH 4.14 128/143] udp6: fix encap return code for resubmitting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 84dad55951b0d009372ec21760b650634246e144 ] The commit eb63f2964dbe ("udp6: add missing checks on edumux packet processing") used the same return code convention

[PATCH 4.14 127/143] sctp: fix race on sctp_id2asoc

4.14-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.14 125/143] net: udp: fix handling of CHECKSUM_COMPLETE packets

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

[PATCH 4.14 131/143] ethtool: fix a privilege escalation bug

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit 58f5bbe331c566f49c9559568f982202a278aa78 ] In dev_ethtool(), the eth command 'ethcmd' is firstly copied from the use-space buffer 'useraddr' and checked to see

[PATCH 4.14 129/143] vhost: Fix Spectre V1 vulnerability

4.14-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.14 128/143] udp6: fix encap return code for resubmitting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 84dad55951b0d009372ec21760b650634246e144 ] The commit eb63f2964dbe ("udp6: add missing checks on edumux packet processing") used the same return code convention

[PATCH 4.14 127/143] sctp: fix race on sctp_id2asoc

4.14-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.14 125/143] net: udp: fix handling of CHECKSUM_COMPLETE packets

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

[PATCH 4.14 131/143] ethtool: fix a privilege escalation bug

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit 58f5bbe331c566f49c9559568f982202a278aa78 ] In dev_ethtool(), the eth command 'ethcmd' is firstly copied from the use-space buffer 'useraddr' and checked to see

[PATCH 4.14 129/143] vhost: Fix Spectre V1 vulnerability

4.14-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.14 106/143] sch_netem: restore skb->dev after dequeuing from the rbtree

4.14-stable review patch. If anyone has any objections, please let me know. -- Upstream commit bffa72cf7f9d ("net: sk_buff rbnode reorg") got backported as commit 6b921536f170 ("net: sk_buff rbnode reorg") into the v4.14.x-tree. However, the backport does not include the

[PATCH 4.14 123/143] net: socket: fix a missing-check bug

4.14-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.14 124/143] net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules

4.14-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.14 124/143] net: stmmac: Fix stmmac_mdio_reset() when building stmmac as modules

4.14-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.14 106/143] sch_netem: restore skb->dev after dequeuing from the rbtree

4.14-stable review patch. If anyone has any objections, please let me know. -- Upstream commit bffa72cf7f9d ("net: sk_buff rbnode reorg") got backported as commit 6b921536f170 ("net: sk_buff rbnode reorg") into the v4.14.x-tree. However, the backport does not include the

[PATCH 4.14 123/143] net: socket: fix a missing-check bug

4.14-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.14 121/143] net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs

4.14-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.14 121/143] net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs

4.14-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.14 120/143] net: fec: dont dump RX FIFO register when not available

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Fugang Duan [ Upstream commit ec20a63aa8b8ec3223fb25cdb2a49f9f9dfda88c ] Commit db65f35f50e0 ("net: fec: add support of ethtool get_regs") introduce ethool "--register-dump" interface to dump

[PATCH 4.14 122/143] net: sched: gred: pass the right attribute to gred_change_table_def()

4.14-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.14 120/143] net: fec: dont dump RX FIFO register when not available

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Fugang Duan [ Upstream commit ec20a63aa8b8ec3223fb25cdb2a49f9f9dfda88c ] Commit db65f35f50e0 ("net: fec: add support of ethtool get_regs") introduce ethool "--register-dump" interface to dump

[PATCH 4.14 122/143] net: sched: gred: pass the right attribute to gred_change_table_def()

4.14-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.14 119/143] llc: set SOCK_RCU_FREE in llc_sap_add_socket()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 5a8e7aea953bdb6d4da13aff6f1e7f9c62023499 ] WHen an llc sock is added into the sk_laddr_hash of an llc_sap, it is not marked with SOCK_RCU_FREE. This causes that

[PATCH 4.14 117/143] ipv6: mcast: fix a use-after-free in inet6_mc_check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit dc012f3628eaecfb5ba68404a5c30ef501daf63d ] syzbot found a use-after-free in inet6_mc_check [1] The problem here is that inet6_mc_check() uses rcu and

[PATCH 4.14 116/143] net: bridge: remove ipv6 zero address check in mcast queries

4.14-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.14 118/143] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

4.14-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.14 119/143] llc: set SOCK_RCU_FREE in llc_sap_add_socket()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang [ Upstream commit 5a8e7aea953bdb6d4da13aff6f1e7f9c62023499 ] WHen an llc sock is added into the sk_laddr_hash of an llc_sap, it is not marked with SOCK_RCU_FREE. This causes that

[PATCH 4.14 117/143] ipv6: mcast: fix a use-after-free in inet6_mc_check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit dc012f3628eaecfb5ba68404a5c30ef501daf63d ] syzbot found a use-after-free in inet6_mc_check [1] The problem here is that inet6_mc_check() uses rcu and

[PATCH 4.14 116/143] net: bridge: remove ipv6 zero address check in mcast queries

4.14-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.14 118/143] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

4.14-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.14 114/143] drm/i915/gvt: fix memory leak of a cmd_entry struct on error exit path

4.14-stable review patch. If anyone has any objections, please let me know. -- commit ffdf16edfbbe77f5f5c3c87fe8d7387ecd16241b upstream The error exit path when a duplicate is found does not kfree and cmd_entry struct and hence there is a small memory leak. Fix this by

[PATCH 4.14 115/143] bridge: do not add port to router list when receives query with source 0.0.0.0

4.14-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.14 105/143] fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()

4.14-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.14 114/143] drm/i915/gvt: fix memory leak of a cmd_entry struct on error exit path

4.14-stable review patch. If anyone has any objections, please let me know. -- commit ffdf16edfbbe77f5f5c3c87fe8d7387ecd16241b upstream The error exit path when a duplicate is found does not kfree and cmd_entry struct and hence there is a small memory leak. Fix this by

[PATCH 4.14 115/143] bridge: do not add port to router list when receives query with source 0.0.0.0

4.14-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.14 105/143] fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()

4.14-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.14 068/143] IB/mlx5: Avoid passing an invalid QP type to firmware

4.14-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.14 068/143] IB/mlx5: Avoid passing an invalid QP type to firmware

4.14-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.14 077/143] tpm: tpm_crb: relinquish locality on error path.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1fbad3028664e114d210dc65d768947a3a553eaa ] In crb_map_io() function, __crb_request_locality() is called prior to crb_cmd_ready(), but if one of the consecutive function fails the

[PATCH 4.14 077/143] tpm: tpm_crb: relinquish locality on error path.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1fbad3028664e114d210dc65d768947a3a553eaa ] In crb_map_io() function, __crb_request_locality() is called prior to crb_cmd_ready(), but if one of the consecutive function fails the

[PATCH 4.14 073/143] KVM: x86: Update the exit_qualification access bits while walking an address

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ddd6f0e94d3153951580d5b88b9d97c7e26a0e00 ] ... to avoid having a stale value when handling an EPT misconfig for MMIO regions. MMIO regions that are not passed-through to the guest

[PATCH 4.14 072/143] test_bpf: Fix testing with CONFIG_BPF_JIT_ALWAYS_ON=y on other arches

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 52fda36d63bfc8c8e8ae5eda8eb5ac6f52cd67ed ] Function bpf_fill_maxinsns11 is designed to not be able to be JITed on x86_64. So, it fails when CONFIG_BPF_JIT_ALWAYS_ON=y, and commit

[PATCH 4.14 073/143] KVM: x86: Update the exit_qualification access bits while walking an address

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ddd6f0e94d3153951580d5b88b9d97c7e26a0e00 ] ... to avoid having a stale value when handling an EPT misconfig for MMIO regions. MMIO regions that are not passed-through to the guest

[PATCH 4.14 072/143] test_bpf: Fix testing with CONFIG_BPF_JIT_ALWAYS_ON=y on other arches

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 52fda36d63bfc8c8e8ae5eda8eb5ac6f52cd67ed ] Function bpf_fill_maxinsns11 is designed to not be able to be JITed on x86_64. So, it fails when CONFIG_BPF_JIT_ALWAYS_ON=y, and commit

[PATCH 4.14 076/143] bpf: sockmap, map_release does not hold refcnt for pinned maps

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ba6b8de423f8d0dee48d6030288ed81c03ddf9f0 ] Relying on map_release hook to decrement the reference counts when a map is removed only works if the map is not being pinned. In the

[PATCH 4.14 074/143] sparc64: Fix regression in pmdp_invalidate().

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cfb61b5e3e09f8b49bc4d685429df75f45127adc ] pmdp_invalidate() was changed to update the pmd atomically (to not lose dirty/access bits) and return the original pmd value. However, in

[PATCH 4.14 075/143] tpm: move the delay_msec increment after sleep in tpm_transmit()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 92980756979a9c51be0275f395f4e89c42cf199a ] Commit e2fb992d82c6 ("tpm: add retry logic") introduced a new loop to handle the TPM2_RC_RETRY error. The loop retries the command after

[PATCH 4.14 076/143] bpf: sockmap, map_release does not hold refcnt for pinned maps

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ba6b8de423f8d0dee48d6030288ed81c03ddf9f0 ] Relying on map_release hook to decrement the reference counts when a map is removed only works if the map is not being pinned. In the

[PATCH 4.14 074/143] sparc64: Fix regression in pmdp_invalidate().

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cfb61b5e3e09f8b49bc4d685429df75f45127adc ] pmdp_invalidate() was changed to update the pmd atomically (to not lose dirty/access bits) and return the original pmd value. However, in

[PATCH 4.14 075/143] tpm: move the delay_msec increment after sleep in tpm_transmit()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 92980756979a9c51be0275f395f4e89c42cf199a ] Commit e2fb992d82c6 ("tpm: add retry logic") introduced a new loop to handle the TPM2_RC_RETRY error. The loop retries the command after

[PATCH 4.14 103/143] net: ena: fix NULL dereference due to untimely napi initialization

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 78a55d05def95144ca5fa9a64c49b2a0636a9866 ] napi poll functions should be initialized before running request_irq(), to handle a rare condition where there is a pending interrupt,

[PATCH 4.14 099/143] rxrpc: Dont check RXRPC_CALL_TX_LAST after calling rxrpc_rotate_tx_window()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c479d5f2c2e1ce609da08c075054440d97ddff52 ] We should only call the function to end a call's Tx phase if we rotated the marked-last packet out of the transmission buffer. Make

[PATCH 4.14 101/143] rxrpc: Fix connection-level abort handling

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 647530924f47c93db472ee3cf43b7ef1425581b6 ] Fix connection-level abort handling to cache the abort and error codes properly so that a new incoming call can be properly aborted if it

[PATCH 4.14 102/143] net: ena: fix warning in rmmod caused by double iounmap

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d79c3888bde6581da7ff9f9d6f581900ecb5e632 ] Memory mapped with devm_ioremap is automatically freed when the driver is disconnected from the device. Therefore there is no need to

[PATCH 4.14 103/143] net: ena: fix NULL dereference due to untimely napi initialization

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 78a55d05def95144ca5fa9a64c49b2a0636a9866 ] napi poll functions should be initialized before running request_irq(), to handle a rare condition where there is a pending interrupt,

[PATCH 4.14 099/143] rxrpc: Dont check RXRPC_CALL_TX_LAST after calling rxrpc_rotate_tx_window()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c479d5f2c2e1ce609da08c075054440d97ddff52 ] We should only call the function to end a call's Tx phase if we rotated the marked-last packet out of the transmission buffer. Make

[PATCH 4.14 101/143] rxrpc: Fix connection-level abort handling

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 647530924f47c93db472ee3cf43b7ef1425581b6 ] Fix connection-level abort handling to cache the abort and error codes properly so that a new incoming call can be properly aborted if it

[PATCH 4.14 102/143] net: ena: fix warning in rmmod caused by double iounmap

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d79c3888bde6581da7ff9f9d6f581900ecb5e632 ] Memory mapped with devm_ioremap is automatically freed when the driver is disconnected from the device. Therefore there is no need to

[PATCH 4.14 097/143] ARM: dts: imx53-qsb: disable 1.2GHz OPP

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eea96566c189c77e5272585984eb2729881a2f1d ] The maximum CPU frequency for the i.MX53 QSB is 1GHz, so disable the 1.2GHz OPP. This makes the board work again with configs that have

[PATCH 4.14 098/143] perf python: Use -Wno-redundant-decls to build with PYTHON=python3

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 05a2f54679861deb188750ba2a70187000b2c71f ] When building in ClearLinux using 'make PYTHON=python3' with gcc 8.2.1 it fails with: GEN /tmp/build/perf/python/perf.so In

[PATCH 4.14 097/143] ARM: dts: imx53-qsb: disable 1.2GHz OPP

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eea96566c189c77e5272585984eb2729881a2f1d ] The maximum CPU frequency for the i.MX53 QSB is 1GHz, so disable the 1.2GHz OPP. This makes the board work again with configs that have

[PATCH 4.14 098/143] perf python: Use -Wno-redundant-decls to build with PYTHON=python3

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 05a2f54679861deb188750ba2a70187000b2c71f ] When building in ClearLinux using 'make PYTHON=python3' with gcc 8.2.1 it fails with: GEN /tmp/build/perf/python/perf.so In

[PATCH 4.14 095/143] perf tests: Fix indexing when invoking subtests

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

[PATCH 4.14 096/143] compiler.h: Allow arch-specific asm/compiler.h

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 04f264d3a8b0eb25d378127bd78c3c9a0261c828 ] We have a need to override the definition of barrier_before_unreachable() for MIPS, which means we either need to add

[PATCH 4.14 093/143] kconfig: fix the rule of mainmenu_stmt symbol

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 56869d45e364244a721de34ce9c5dc9ed022779e ] The rule of mainmenu_stmt does not have debug print of zconf_lineno(), but if it had, it would print a wrong line number for the same

[PATCH 4.14 089/143] btrfs: quota: Set rescan progress to (u64)-1 if we hit last leaf

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6f7de19ed3d4d3526ca5eca428009f97cf969c2f ] Commit ff3d27a048d9 ("btrfs: qgroup: Finish rescan when hit the last leaf of extent tree") added a new exit for rescan finish. However

[PATCH 4.14 071/143] cifs: Use ULL suffix for 64-bit constant

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3995bbf53bd2047f2720c6fdd4bf38f6d942a0c0 ] On 32-bit (e.g. with m68k-linux-gnu-gcc-4.1): fs/cifs/inode.c: In function ‘simple_hashstr’: fs/cifs/inode.c:713: warning:

[PATCH 4.14 092/143] net: stmmac: mark PM functions as __maybe_unused

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 81a8b0799632627b587af31ecd06112397e4ec36 ] The newly added suspend/resume functions cause a build warning when CONFIG_PM is disabled:

[PATCH 4.14 094/143] libertas: call into generic suspend code before turning off power

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

[PATCH 4.14 090/143] net: phy: phylink: Dont release NULL GPIO

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3bcd47726c3b744fd08781795cca905cc59a1382 ] If CONFIG_GPIOLIB is disabled, gpiod_put() becomes a stub that produces a warning, this helped identify that we could be attempting to

[PATCH 4.14 095/143] perf tests: Fix indexing when invoking subtests

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

[PATCH 4.14 096/143] compiler.h: Allow arch-specific asm/compiler.h

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 04f264d3a8b0eb25d378127bd78c3c9a0261c828 ] We have a need to override the definition of barrier_before_unreachable() for MIPS, which means we either need to add

[PATCH 4.14 093/143] kconfig: fix the rule of mainmenu_stmt symbol

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 56869d45e364244a721de34ce9c5dc9ed022779e ] The rule of mainmenu_stmt does not have debug print of zconf_lineno(), but if it had, it would print a wrong line number for the same

[PATCH 4.14 089/143] btrfs: quota: Set rescan progress to (u64)-1 if we hit last leaf

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6f7de19ed3d4d3526ca5eca428009f97cf969c2f ] Commit ff3d27a048d9 ("btrfs: qgroup: Finish rescan when hit the last leaf of extent tree") added a new exit for rescan finish. However

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