[PATCH 5.1 43/62] dma-buf: balance refcount inbalance

2019-07-26 Thread Greg Kroah-Hartman
From: Jérôme Glisse commit 5e383a9798990c69fc759a4930de224bb497e62c upstream. The debugfs take reference on fence without dropping them. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Daniel Vetter Cc: Sumit Semwal Cc: linux-me...@vger.kernel.org Cc: dri-de...@lists.freedesktop.org

[PATCH 5.1 16/62] net/tls: make sure offload also gets the keys wiped

2019-07-26 Thread Greg Kroah-Hartman
From: Jakub Kicinski [ Upstream commit acd3e96d53a24d219f720ed4012b62723ae05da1 ] Commit 86029d10af18 ("tls: zero the crypto information from tls_context before freeing") added memzero_explicit() calls to clear the key material before freeing struct tls_context, but it missed tls_device.c has

[PATCH 5.1 42/62] net/mlx5e: Fix error flow in tx reporter diagnose

2019-07-26 Thread Greg Kroah-Hartman
From: Aya Levin [ Upstream commit 99d31cbd8953c6929da978bf049ab0f0b4e503d9 ] Fix tx reporter's diagnose callback. Propagate error when failing to gather diagnostics information or failing to print diagnostic data per queue. Fixes: de8650a82071 ("net/mlx5e: Add tx reporter support")

[PATCH 5.1 44/62] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc

2019-07-26 Thread Greg Kroah-Hartman
From: Chris Wilson commit f5b07b04e5f090a85d1e96938520f2b2b58e4a8e upstream. If we have to drop the seqcount & rcu lock to perform a krealloc, we have to restart the loop. In doing so, be careful not to lose track of the already acquired exclusive fence. Fixes: fedf54132d24 ("dma-buf: Restart

[PATCH 5.1 21/62] sctp: not bind the socket in sctp_connect

2019-07-26 Thread Greg Kroah-Hartman
From: Xin Long [ Upstream commit 9b6c08878e23adb7cc84bdca94d8a944b03f099e ] Now when sctp_connect() is called with a wrong sa_family, it binds to a port but doesn't set bp->port, then sctp_get_af_specific will return NULL and sctp_connect() returns -EINVAL. Then if sctp_bind() is called to

[PATCH 5.1 12/62] net: openvswitch: fix csum updates for MPLS actions

2019-07-26 Thread Greg Kroah-Hartman
From: John Hurley [ Upstream commit 0e3183cd2a64843a95b62f8bd4a83605a4cf0615 ] Skbs may have their checksum value populated by HW. If this is a checksum calculated over the entire packet then the CHECKSUM_COMPLETE field is marked. Changes to the data pointer on the skb throughout the network

[PATCH 5.1 20/62] sctp: fix error handling on stream scheduler initialization

2019-07-26 Thread Greg Kroah-Hartman
From: Marcelo Ricardo Leitner [ Upstream commit 4d1415811e492d9a8238f8a92dd0d51612c788e9 ] It allocates the extended area for outbound streams only on sendmsg calls, if they are not yet allocated. When using the priority stream scheduler, this initialization may imply into a subsequent

[PATCH 5.1 60/62] sd_zbc: Fix report zones buffer allocation

2019-07-26 Thread Greg Kroah-Hartman
From: Damien Le Moal commit b091ac616846a1da75b1f2566b41255ce7f0e0a6 upstream. During disk scan and revalidation done with sd_revalidate(), the zones of a zoned disk are checked using the helper function blk_revalidate_disk_zones() if a configuration change is detected (change in the number of

[PATCH 5.1 61/62] block: Limit zone array allocation size

2019-07-26 Thread Greg Kroah-Hartman
From: Damien Le Moal commit 26202928fafad8bda8b478edb7e62c885be623d7 upstream. Limit the size of the struct blk_zone array used in blk_revalidate_disk_zones() to avoid memory allocation failures leading to disk revalidation failure. Also further reduce the likelyhood of such failures by using

[PATCH 5.1 50/62] perf/core: Fix race between close() and fork()

2019-07-26 Thread Greg Kroah-Hartman
From: Peter Zijlstra commit 1cf8dfe8a661f0462925df943140e9f6d1ea5233 upstream. Syzcaller reported the following Use-after-Free bug: close() clone() copy_process()

[PATCH 5.1 55/62] ext4: use jbd2_inode dirty range scoping

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 73131fbb003b3691cfcf9656f234b00da497fcd6 upstream. Use the newly introduced jbd2_inode dirty range scoping to prevent us from waiting forever when trying to complete a journal transaction. Signed-off-by: Ross Zwisler Signed-off-by: Theodore Ts'o Reviewed-by: Jan

[PATCH 4.19 10/50] net: make skb_dst_force return true when dst is refcounted

2019-07-26 Thread Greg Kroah-Hartman
From: Florian Westphal [ Upstream commit b60a77386b1d4868f72f6353d35dabe5fbe981f2 ] netfilter did not expect that skb_dst_force() can cause skb to lose its dst entry. I got a bug report with a skb->dst NULL dereference in netfilter output path. The backtrace contains nf_reinject(), so the dst

[PATCH 5.1 57/62] KVM: nVMX: do not use dangling shadow VMCS after guest reset

2019-07-26 Thread Greg Kroah-Hartman
From: Paolo Bonzini commit 88dddc11a8d6b09201b4db9d255b3394d9bc9e57 upstream. If a KVM guest is reset while running a nested guest, free_nested will disable the shadow VMCS execution control in the vmcs01. However, on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync the VMCS12 to

[PATCH 5.1 56/62] ext4: allow directory holes

2019-07-26 Thread Greg Kroah-Hartman
From: Theodore Ts'o commit 4e19d6b65fb4fc42e352ce9883649e049da14743 upstream. The largedir feature was intended to allow ext4 directories to have unmapped directory blocks (e.g., directory holes). And so the released e2fsprogs no longer enforces this for largedir file systems; however, the

[PATCH 5.1 54/62] jbd2: introduce jbd2_inode dirty range scoping

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 6ba0e7dc64a5adcda2fbe65adc466891795d639e upstream. Currently both journal_submit_inode_data_buffers() and journal_finish_inode_data_buffers() operate on the entire address space of each of the inodes associated with a given journal entry. The consequence of this is

[PATCH 4.19 01/50] bnx2x: Prevent load reordering in tx completion processing

2019-07-26 Thread Greg Kroah-Hartman
From: Brian King [ Upstream commit ea811b795df24644a8eb760b493c43fba4450677 ] This patch fixes an issue seen on Power systems with bnx2x which results in the skb is NULL WARN_ON in bnx2x_free_tx_pkt firing due to the skb pointer getting loaded in bnx2x_free_tx_pkt prior to the hw_cons load in

[PATCH 4.19 16/50] r8169: fix issue with confused RX unit after PHY power-down on RTL8411b

2019-07-26 Thread Greg Kroah-Hartman
From: Heiner Kallweit [ Upstream commit fe4e8db0392a6c2e795eb89ef5fcd86522e66248 ] On RTL8411b the RX unit gets confused if the PHY is powered-down. This was reported in [0] and confirmed by Realtek. Realtek provided a sequence to fix the RX unit after PHY wakeup. The issue itself seems to

[PATCH 4.19 19/50] sky2: Disable MSI on ASUS P6T

2019-07-26 Thread Greg Kroah-Hartman
From: Takashi Iwai [ Upstream commit a261e3797506bd561700be643fe1a85bf81e9661 ] The onboard sky2 NIC on ASUS P6T WS PRO doesn't work after PM resume due to the infamous IRQ problem. Disabling MSI works around it, so let's add it to the blacklist. Unfortunately the BIOS on the machine doesn't

Re: LPC 2019 distros microconference proposal: "Distros and Syzkaller - Why bother?"

2019-07-26 Thread Dmitry Vyukov
On Fri, Jul 26, 2019 at 5:21 PM Dhaval Giani wrote: > > Adding a bunch of people. > > On Fri, Jul 26, 2019, 8:06 AM George Kennedy > wrote: >> >> + >> >> On 7/26/2019 10:48 AM, George Kennedy wrote: >> > I have proposed "Distros and Syzkaller - Why bother?" for the LPC 2019 >> > distros

[PATCH 4.19 15/50] nfc: fix potential illegal memory access

2019-07-26 Thread Greg Kroah-Hartman
From: Yang Wei [ Upstream commit dd006fc434e107ef90f7de0db9907cbc1c521645 ] The frags_q is not properly initialized, it may result in illegal memory access when conn_info is NULL. The "goto free_exit" should be replaced by "goto exit". Signed-off-by: Yang Wei Signed-off-by: David S. Miller

[PATCH 4.19 02/50] caif-hsi: fix possible deadlock in cfhsi_exit_module()

2019-07-26 Thread Greg Kroah-Hartman
From: Taehee Yoo [ Upstream commit fdd258d49e88a9e0b49ef04a506a796f1c768a8e ] cfhsi_exit_module() calls unregister_netdev() under rtnl_lock(). but unregister_netdev() internally calls rtnl_lock(). So deadlock would occur. Fixes: c41254006377 ("caif-hsi: Add rtnl support") Signed-off-by: Taehee

[PATCH 4.19 20/50] tcp: be more careful in tcp_fragment()

2019-07-26 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit b617158dc096709d8600c53b6052144d12b89fab ] Some applications set tiny SO_SNDBUF values and expect TCP to just work. Recent patches to address CVE-2019-11478 broke them in case of losses, since retransmits might be prevented. We should allow these flows to

[PATCH 4.19 12/50] net: openvswitch: fix csum updates for MPLS actions

2019-07-26 Thread Greg Kroah-Hartman
From: John Hurley [ Upstream commit 0e3183cd2a64843a95b62f8bd4a83605a4cf0615 ] Skbs may have their checksum value populated by HW. If this is a checksum calculated over the entire packet then the CHECKSUM_COMPLETE field is marked. Changes to the data pointer on the skb throughout the network

[PATCH 4.19 11/50] net: neigh: fix multiple neigh timer scheduling

2019-07-26 Thread Greg Kroah-Hartman
From: Lorenzo Bianconi [ Upstream commit 071c37983d99da07797294ea78e9da1a6e287144 ] Neigh timer can be scheduled multiple times from userspace adding multiple neigh entries and forcing the neigh timer scheduling passing NTF_USE in the netlink requests. This will result in a refcount leak and in

[PATCH 4.19 23/50] vrf: make sure skb->data contains ip header to make routing

2019-07-26 Thread Greg Kroah-Hartman
From: Peter Kosyh [ Upstream commit 107e47cc80ec37cb332bd41b22b1c7779e22e018 ] vrf_process_v4_outbound() and vrf_process_v6_outbound() do routing using ip/ipv6 addresses, but don't make sure the header is available in skb->data[] (skb_headlen() is less then header size). Case: 1) igb driver

[PATCH 4.19 22/50] tcp: Reset bytes_acked and bytes_received when disconnecting

2019-07-26 Thread Greg Kroah-Hartman
From: Christoph Paasch [ Upstream commit e858faf556d4e14c750ba1e8852783c6f9520a0e ] If an app is playing tricks to reuse a socket via tcp_disconnect(), bytes_acked/received needs to be reset to 0. Otherwise tcp_info will report the sum of the current and the old connection.. Cc: Eric Dumazet

[PATCH 4.19 21/50] tcp: fix tcp_set_congestion_control() use from bpf hook

2019-07-26 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit 8d650cdedaabb33e85e9b7c517c0c71fcecc1de9 ] Neal reported incorrect use of ns_capable() from bpf hook. bpf_setsockopt(...TCP_CONGESTION...) -> tcp_set_congestion_control() -> ns_capable(sock_net(sk)->user_ns, CAP_NET_ADMIN) -> ns_capable_common()

[PATCH 4.19 24/50] net/mlx5e: IPoIB, Add error path in mlx5_rdma_setup_rn

2019-07-26 Thread Greg Kroah-Hartman
From: Aya Levin [ Upstream commit ef1ce7d7b67b46661091c7ccc0396186b7a247ef ] Check return value from mlx5e_attach_netdev, add error path on failure. Fixes: 48935bbb7ae8 ("net/mlx5e: IPoIB, Add netdevice profile skeleton") Signed-off-by: Aya Levin Reviewed-by: Feras Daoud Signed-off-by: Saeed

[PATCH 4.19 03/50] hv_netvsc: Fix extra rcu_read_unlock in netvsc_recv_callback()

2019-07-26 Thread Greg Kroah-Hartman
From: Haiyang Zhang [ Upstream commit be4363bdf0ce9530f15aa0a03d1060304d116b15 ] There is an extra rcu_read_unlock left in netvsc_recv_callback(), after a previous patch that removes RCU from this function. This patch removes the extra RCU unlock. Fixes: 345ac08990b8 ("hv_netvsc: pass

[PATCH 4.19 09/50] net: dsa: mv88e6xxx: wait after reset deactivation

2019-07-26 Thread Greg Kroah-Hartman
From: Baruch Siach [ Upstream commit 7b75e49de424ceb53d13e60f35d0a73765626fda ] Add a 1ms delay after reset deactivation. Otherwise the chip returns bogus ID value. This is observed with 88E6390 (Peridot) chip. Signed-off-by: Baruch Siach Reviewed-by: Andrew Lunn Signed-off-by: David S.

[PATCH 4.19 25/50] macsec: fix use-after-free of skb during RX

2019-07-26 Thread Greg Kroah-Hartman
From: Andreas Steinmetz [ Upstream commit 095c02da80a41cf6d311c504d8955d6d1c2add10 ] Fix use-after-free of skb when rx_handler returns RX_HANDLER_PASS. Signed-off-by: Andreas Steinmetz Acked-by: Willem de Bruijn Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.19 00/50] 4.19.62-stable review

2019-07-26 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.62 release. There are 50 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 28 Jul 2019 03:21:13 PM UTC. Anything

[PATCH 4.19 29/50] net_sched: unset TCQ_F_CAN_BYPASS when adding filters

2019-07-26 Thread Greg Kroah-Hartman
From: Cong Wang [ Upstream commit 3f05e6886a595c9a29a309c52f45326be917823c ] For qdisc's that support TC filters and set TCQ_F_CAN_BYPASS, notably fq_codel, it makes no sense to let packets bypass the TC filters we setup in any scenario, otherwise our packets steering policy could not be

[PATCH 4.19 39/50] MIPS: lb60: Fix pin mappings

2019-07-26 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 1323c3b72a987de57141cabc44bf9cd83656bc70 upstream. The pin mappings introduced in commit 636f8ba67fb6 ("MIPS: JZ4740: Qi LB60: Add pinctrl configuration for several drivers") are completely wrong. The pinctrl driver name is incorrect, and the function and group fields

[PATCH 4.19 08/50] net: bcmgenet: use promisc for unsupported filters

2019-07-26 Thread Greg Kroah-Hartman
From: Justin Chen [ Upstream commit 35cbef9863640f06107144687bd13151bc2e8ce3 ] Currently we silently ignore filters if we cannot meet the filter requirements. This will lead to the MAC dropping packets that are expected to pass. A better solution would be to set the NIC to promisc mode when the

[PATCH 4.19 05/50] ipv4: dont set IPv6 only flags to IPv4 addresses

2019-07-26 Thread Greg Kroah-Hartman
From: Matteo Croce [ Upstream commit 2e60546368165c2449564d71f6005dda9205b5fb ] Avoid the situation where an IPV6 only flag is applied to an IPv4 address: # ip addr add 192.0.2.1/24 dev dummy0 nodad home mngtmpaddr noprefixroute # ip -4 addr show dev dummy0 2: dummy0: mtu 1500

[PATCH 4.19 40/50] perf/core: Fix exclusive events grouping

2019-07-26 Thread Greg Kroah-Hartman
From: Alexander Shishkin commit 8a58ddae23796c733c5dfbd717538d89d036c5bd upstream. So far, we tried to disallow grouping exclusive events for the fear of complications they would cause with moving between contexts. Specifically, moving a software group to a hardware context would violate the

[PATCH 4.19 41/50] perf/core: Fix race between close() and fork()

2019-07-26 Thread Greg Kroah-Hartman
From: Peter Zijlstra commit 1cf8dfe8a661f0462925df943140e9f6d1ea5233 upstream. Syzcaller reported the following Use-after-Free bug: close() clone() copy_process()

[PATCH 4.19 06/50] ipv6: rt6_check should return NULL if from is NULL

2019-07-26 Thread Greg Kroah-Hartman
From: David Ahern [ Upstream commit 49d05fe2c9d1b4a27761c9807fec39b8155bef9e ] Paul reported that l2tp sessions were broken after the commit referenced in the Fixes tag. Prior to this commit rt6_check returned NULL if the rt6_info 'from' was NULL - ie., the dst_entry was disconnected from a FIB

[PATCH 4.19 32/50] net: bridge: mcast: fix stale nsrcs pointer in igmp3/mld2 report handling

2019-07-26 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit e57f61858b7cf478ed6fa23ed4b3876b1c9625c4 ] We take a pointer to grec prior to calling pskb_may_pull and use it afterwards to get nsrcs so record nsrcs before the pull when handling igmp3 and we get a pointer to nsrcs and call pskb_may_pull when

[PATCH 4.19 35/50] net: bridge: stp: dont cache eth dest pointer before skb pull

2019-07-26 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit 2446a68ae6a8cee6d480e2f5b52f5007c7c41312 ] Don't cache eth dest pointer before calling pskb_may_pull. Fixes: cf0f02d04a83 ("[BRIDGE]: use llc for receiving STP packets") Signed-off-by: Nikolay Aleksandrov Signed-off-by: David S. Miller

[PATCH 4.19 17/50] rxrpc: Fix send on a connected, but unbound socket

2019-07-26 Thread Greg Kroah-Hartman
From: David Howells [ Upstream commit e835ada07091f40dcfb1bc735082bd0a7c005e59 ] If sendmsg() or sendmmsg() is called on a connected socket that hasn't had bind() called on it, then an oops will occur when the kernel tries to connect the call because no local endpoint has been allocated. Fix

[PATCH 4.19 27/50] netrom: fix a memory leak in nr_rx_frame()

2019-07-26 Thread Greg Kroah-Hartman
From: Cong Wang [ Upstream commit c8c8218ec5af5d2598381883acbefbf604e56b5e ] When the skb is associated with a new sock, just assigning it to skb->sk is not sufficient, we have to set its destructor to free the sock properly too. Reported-by:

[PATCH 4.19 18/50] sctp: fix error handling on stream scheduler initialization

2019-07-26 Thread Greg Kroah-Hartman
From: Marcelo Ricardo Leitner [ Upstream commit 4d1415811e492d9a8238f8a92dd0d51612c788e9 ] It allocates the extended area for outbound streams only on sendmsg calls, if they are not yet allocated. When using the priority stream scheduler, this initialization may imply into a subsequent

[PATCH 4.19 04/50] igmp: fix memory leak in igmpv3_del_delrec()

2019-07-26 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit e5b1c6c6277d5a283290a8c033c72544746f9b5b ] im->tomb and/or im->sources might not be NULL, but we currently overwrite their values blindly. Using swap() will make sure the following call to kfree_pmc(pmc) will properly free the psf structures. Tested with

[PATCH 4.19 26/50] macsec: fix checksumming after decryption

2019-07-26 Thread Greg Kroah-Hartman
From: Andreas Steinmetz [ Upstream commit 7d8b16b9facb0dd81d1469808dd9a575fa1d525a ] Fix checksumming after decryption. Signed-off-by: Andreas Steinmetz Signed-off-by: David S. Miller Signed-off-by: Greg Kroah-Hartman --- drivers/net/macsec.c |1 + 1 file changed, 1 insertion(+) ---

Re: [RFC PATCH 02/40] soundwire: cadence_master: add debugfs register dump

2019-07-26 Thread Pierre-Louis Bossart
+static const struct file_operations cdns_reg_fops = { + .open = simple_open, + .read = cdns_reg_read, + .llseek = default_llseek, +}; DEFINE_SHOW_ATTRIBUTE()? I remember looking at this but can't recall why I left it this way. That was before my Summer break so will

[PATCH 4.19 13/50] net: phy: sfp: hwmon: Fix scaling of RX power

2019-07-26 Thread Greg Kroah-Hartman
From: Andrew Lunn [ Upstream commit 0cea0e1148fe134a4a3aaf0b1496f09241fb943a ] The RX power read from the SFP uses units of 0.1uW. This must be scaled to units of uW for HWMON. This requires a divide by 10, not the current 100. With this change in place, sensors(1) and ethtool -m agree:

[PATCH 4.19 14/50] net: stmmac: Re-work the queue selection for TSO packets

2019-07-26 Thread Greg Kroah-Hartman
From: Jose Abreu [ Upstream commit 4993e5b37e8bcb55ac90f76eb6d2432647273747 ] Ben Hutchings says: "This is the wrong place to change the queue mapping. stmmac_xmit() is called with a specific TX queue locked, and accessing a different TX queue results in a data race

[PATCH 5.1 14/62] net_sched: unset TCQ_F_CAN_BYPASS when adding filters

2019-07-26 Thread Greg Kroah-Hartman
From: Cong Wang [ Upstream commit 3f05e6886a595c9a29a309c52f45326be917823c ] For qdisc's that support TC filters and set TCQ_F_CAN_BYPASS, notably fq_codel, it makes no sense to let packets bypass the TC filters we setup in any scenario, otherwise our packets steering policy could not be

[PATCH 5.1 17/62] nfc: fix potential illegal memory access

2019-07-26 Thread Greg Kroah-Hartman
From: Yang Wei [ Upstream commit dd006fc434e107ef90f7de0db9907cbc1c521645 ] The frags_q is not properly initialized, it may result in illegal memory access when conn_info is NULL. The "goto free_exit" should be replaced by "goto exit". Signed-off-by: Yang Wei Signed-off-by: David S. Miller

[PATCH 5.2 43/66] bnxt_en: Fix VNIC accounting when enabling aRFS on 57500 chips.

2019-07-26 Thread Greg Kroah-Hartman
From: Michael Chan [ Upstream commit 9b3d15e6b05e0b916be5fbd915f90300a403098b ] Unlike legacy chips, 57500 chips don't need additional VNIC resources for aRFS/ntuple. Fix the code accordingly so that we don't reserve and allocate additional VNICs on 57500 chips. Without this patch, the driver

[PATCH 5.2 46/66] mlxsw: spectrum: Do not process learned records with a dummy FID

2019-07-26 Thread Greg Kroah-Hartman
From: Ido Schimmel [ Upstream commit 577fa14d210073ba1ce6237c659a8820312104ad ] The switch periodically sends notifications about learned FDB entries. Among other things, the notification includes the FID (Filtering Identifier) and the port on which the MAC was learned. In case the driver does

[PATCH 5.1 08/62] net: bcmgenet: use promisc for unsupported filters

2019-07-26 Thread Greg Kroah-Hartman
From: Justin Chen [ Upstream commit 35cbef9863640f06107144687bd13151bc2e8ce3 ] Currently we silently ignore filters if we cannot meet the filter requirements. This will lead to the MAC dropping packets that are expected to pass. A better solution would be to set the NIC to promisc mode when the

[PATCH 5.2 66/66] block: Limit zone array allocation size

2019-07-26 Thread Greg Kroah-Hartman
From: Damien Le Moal commit 26202928fafad8bda8b478edb7e62c885be623d7 upstream. Limit the size of the struct blk_zone array used in blk_revalidate_disk_zones() to avoid memory allocation failures leading to disk revalidation failure. Also further reduce the likelyhood of such failures by using

[PATCH 5.1 06/62] ipv6: rt6_check should return NULL if from is NULL

2019-07-26 Thread Greg Kroah-Hartman
From: David Ahern [ Upstream commit 49d05fe2c9d1b4a27761c9807fec39b8155bef9e ] Paul reported that l2tp sessions were broken after the commit referenced in the Fixes tag. Prior to this commit rt6_check returned NULL if the rt6_info 'from' was NULL - ie., the dst_entry was disconnected from a FIB

[PATCH 5.1 26/62] vrf: make sure skb->data contains ip header to make routing

2019-07-26 Thread Greg Kroah-Hartman
From: Peter Kosyh [ Upstream commit 107e47cc80ec37cb332bd41b22b1c7779e22e018 ] vrf_process_v4_outbound() and vrf_process_v6_outbound() do routing using ip/ipv6 addresses, but don't make sure the header is available in skb->data[] (skb_headlen() is less then header size). Case: 1) igb driver

[PATCH 5.1 09/62] net: dsa: mv88e6xxx: wait after reset deactivation

2019-07-26 Thread Greg Kroah-Hartman
From: Baruch Siach [ Upstream commit 7b75e49de424ceb53d13e60f35d0a73765626fda ] Add a 1ms delay after reset deactivation. Otherwise the chip returns bogus ID value. This is observed with 88E6390 (Peridot) chip. Signed-off-by: Baruch Siach Reviewed-by: Andrew Lunn Signed-off-by: David S.

[PATCH 5.1 03/62] hv_netvsc: Fix extra rcu_read_unlock in netvsc_recv_callback()

2019-07-26 Thread Greg Kroah-Hartman
From: Haiyang Zhang [ Upstream commit be4363bdf0ce9530f15aa0a03d1060304d116b15 ] There is an extra rcu_read_unlock left in netvsc_recv_callback(), after a previous patch that removes RCU from this function. This patch removes the extra RCU unlock. Fixes: 345ac08990b8 ("hv_netvsc: pass

[PATCH 5.1 11/62] net: neigh: fix multiple neigh timer scheduling

2019-07-26 Thread Greg Kroah-Hartman
From: Lorenzo Bianconi [ Upstream commit 071c37983d99da07797294ea78e9da1a6e287144 ] Neigh timer can be scheduled multiple times from userspace adding multiple neigh entries and forcing the neigh timer scheduling passing NTF_USE in the netlink requests. This will result in a refcount leak and in

Re: [RFC PATCH 01/40] soundwire: add debugfs support

2019-07-26 Thread Pierre-Louis Bossart
diff --git a/drivers/soundwire/debugfs.c b/drivers/soundwire/debugfs.c new file mode 100644 index ..8d86e100516e --- /dev/null +++ b/drivers/soundwire/debugfs.c @@ -0,0 +1,156 @@ +// SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause) No, for debugfs-specific code, that dual

[PATCH 5.1 29/62] net: bridge: mcast: fix stale ipv6 hdr pointer when handling v6 query

2019-07-26 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit 3b26a5d03d35d8f732d75951218983c0f7f68dff ] We get a pointer to the ipv6 hdr in br_ip6_multicast_query but we may call pskb_may_pull afterwards and end up using a stale pointer. So use the header directly, it's just 1 place where it's needed. Fixes:

Re: [PATCH v3 06/14] crypto: caam - check assoclen

2019-07-26 Thread Horia Geanta
On 7/25/2019 4:58 PM, Iuliana Prodan wrote: > Check assoclen to solve the extra tests that expect -EINVAL to be > returned when the associated data size is not valid. > > Validated assoclen for RFC4106 and RFC4543 which expects an assoclen > of 16 or 20. > Based on seqiv, IPsec ESP and

[PATCH 5.2 26/66] vrf: make sure skb->data contains ip header to make routing

2019-07-26 Thread Greg Kroah-Hartman
From: Peter Kosyh [ Upstream commit 107e47cc80ec37cb332bd41b22b1c7779e22e018 ] vrf_process_v4_outbound() and vrf_process_v6_outbound() do routing using ip/ipv6 addresses, but don't make sure the header is available in skb->data[] (skb_headlen() is less then header size). Case: 1) igb driver

[PATCH 5.2 49/66] Revert "gpio/spi: Fix spi-gpio regression on active high CS"

2019-07-26 Thread Greg Kroah-Hartman
From: Linus Walleij commit da7f134972f473053ea9d721a1d8397546476dc4 upstream. This reverts commit fbbf145a0e0a0177e089c52275fbfa55763e7d1d. It seems I was misguided in my fixup, which was working at the time but did not work on the final v5.2. The patch tried to avoid a quirk the gpiolib code

[PATCH 5.2 07/66] ipv6: Unlink sibling route in case of failure

2019-07-26 Thread Greg Kroah-Hartman
From: Ido Schimmel [ Upstream commit 54851aa90cf27041d64b12f65ac72e9f97bd90fd ] When a route needs to be appended to an existing multipath route, fib6_add_rt2node() first appends it to the siblings list and increments the number of sibling routes on each sibling. Later, the function notifies

[PATCH 5.2 36/66] selftests: txring_overwrite: fix incorrect test of mmap() return value

2019-07-26 Thread Greg Kroah-Hartman
From: Frank de Brabander [ Upstream commit cecaa76b2919aac2aa584ce476e9fcd5b084add5 ] If mmap() fails it returns MAP_FAILED, which is defined as ((void *) -1). The current if-statement incorrectly tests if *ring is NULL. Fixes: 358be656406d ("selftests/net: add txring_overwrite")

[PATCH 5.2 40/66] net/mlx5e: Rx, Fix checksum calculation for new hardware

2019-07-26 Thread Greg Kroah-Hartman
From: Saeed Mahameed [ Upstream commit db849faa9bef993a1379dc510623f750a72fa7ce ] CQE checksum full mode in new HW, provides a full checksum of rx frame. Covering bytes starting from eth protocol up to last byte in the received frame (frame_size - ETH_HLEN), as expected by the stack. Fixing up

[PATCH 5.2 04/66] igmp: fix memory leak in igmpv3_del_delrec()

2019-07-26 Thread Greg Kroah-Hartman
From: Eric Dumazet [ Upstream commit e5b1c6c6277d5a283290a8c033c72544746f9b5b ] im->tomb and/or im->sources might not be NULL, but we currently overwrite their values blindly. Using swap() will make sure the following call to kfree_pmc(pmc) will properly free the psf structures. Tested with

[PATCH 5.2 10/66] net: make skb_dst_force return true when dst is refcounted

2019-07-26 Thread Greg Kroah-Hartman
From: Florian Westphal [ Upstream commit b60a77386b1d4868f72f6353d35dabe5fbe981f2 ] netfilter did not expect that skb_dst_force() can cause skb to lose its dst entry. I got a bug report with a skb->dst NULL dereference in netfilter output path. The backtrace contains nf_reinject(), so the dst

[PATCH 5.2 28/66] net: bridge: mcast: fix stale nsrcs pointer in igmp3/mld2 report handling

2019-07-26 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit e57f61858b7cf478ed6fa23ed4b3876b1c9625c4 ] We take a pointer to grec prior to calling pskb_may_pull and use it afterwards to get nsrcs so record nsrcs before the pull when handling igmp3 and we get a pointer to nsrcs and call pskb_may_pull when

[PATCH 5.2 50/66] gpiolib: of: fix a memory leak in of_gpio_flags_quirks()

2019-07-26 Thread Greg Kroah-Hartman
From: Nishka Dasgupta commit 89fea04c85e85f21ef4937611055abce82330d48 upstream. Each iteration of for_each_child_of_node puts the previous node, but in the case of a break from the middle of the loop, there is no put, thus causing a memory leak. Hence add an of_node_put before the break. Issue

[PATCH 5.2 56/66] ext4: dont allow any modifications to an immutable file

2019-07-26 Thread Greg Kroah-Hartman
From: Darrick J. Wong commit 2e53840362771c73eb0a5ff71611507e64e8eecd upstream. Don't allow any modifications to a file that's marked immutable, which means that we have to flush all the writable pages to make the readonly and we have to check the setattr/setflags parameters more closely.

[PATCH 5.2 58/66] mm: add filemap_fdatawait_range_keep_errors()

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit aa0bfcd939c30617385ffa28682c062d78050eba upstream. In the spirit of filemap_fdatawait_range() and filemap_fdatawait_keep_errors(), introduce filemap_fdatawait_range_keep_errors() which both takes a range upon which to wait and does not clear errors from the address

[PATCH 4.19 49/50] KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested

2019-07-26 Thread Greg Kroah-Hartman
From: Jan Kiszka commit cf64527bb33f6cec2ed50f89182fc4688d0056b6 upstream. Letting this pend may cause nested_get_vmcs12_pages to run against an invalid state, corrupting the effective vmcs of L1. This was triggerable in QEMU after a guest corruption in L2, followed by a L1 reset.

[PATCH 5.1 47/62] MIPS: lb60: Fix pin mappings

2019-07-26 Thread Greg Kroah-Hartman
From: Paul Cercueil commit 1323c3b72a987de57141cabc44bf9cd83656bc70 upstream. The pin mappings introduced in commit 636f8ba67fb6 ("MIPS: JZ4740: Qi LB60: Add pinctrl configuration for several drivers") are completely wrong. The pinctrl driver name is incorrect, and the function and group fields

[PATCH 5.1 53/62] mm: add filemap_fdatawait_range_keep_errors()

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit aa0bfcd939c30617385ffa28682c062d78050eba upstream. In the spirit of filemap_fdatawait_range() and filemap_fdatawait_keep_errors(), introduce filemap_fdatawait_range_keep_errors() which both takes a range upon which to wait and does not clear errors from the address

[PATCH 4.19 48/50] KVM: nVMX: do not use dangling shadow VMCS after guest reset

2019-07-26 Thread Greg Kroah-Hartman
From: Paolo Bonzini commit 88dddc11a8d6b09201b4db9d255b3394d9bc9e57 upstream. If a KVM guest is reset while running a nested guest, free_nested will disable the shadow VMCS execution control in the vmcs01. However, on the next KVM_RUN vmx_vcpu_run would nevertheless try to sync the VMCS12 to

[PATCH 4.19 44/50] mm: add filemap_fdatawait_range_keep_errors()

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit aa0bfcd939c30617385ffa28682c062d78050eba upstream. In the spirit of filemap_fdatawait_range() and filemap_fdatawait_keep_errors(), introduce filemap_fdatawait_range_keep_errors() which both takes a range upon which to wait and does not clear errors from the address

[PATCH 5.1 48/62] perf script: Assume native_arch for pipe mode

2019-07-26 Thread Greg Kroah-Hartman
From: Song Liu commit 9d49169c5958e429ffa6874fbef734ae7502ad65 upstream. In pipe mode, session->header.env.arch is not populated until the events are processed. Therefore, the following command crashes: perf record -o - | perf script (gdb) bt It fails when we try to compare env.arch

[PATCH 5.1 59/62] Revert "kvm: x86: Use task structs fpu field for user"

2019-07-26 Thread Greg Kroah-Hartman
From: Paolo Bonzini commit ec269475cba7bcdd1eb8fdf8e87f4c6c81a376fe upstream. This reverts commit 240c35a3783ab9b3a0afaba0dde7291295680a6b ("kvm: x86: Use task structs fpu field for user", 2018-11-06). The commit is broken and causes QEMU's FPU state to be destroyed when KVM_RUN is preempted.

[PATCH 4.19 38/50] gpio: davinci: silence error prints in case of EPROBE_DEFER

2019-07-26 Thread Greg Kroah-Hartman
From: Keerthy commit 541e4095f388c196685685633c950cb9b97f8039 upstream. Silence error prints in case of EPROBE_DEFER. This avoids multiple/duplicate defer prints during boot. Cc: Signed-off-by: Keerthy Signed-off-by: Bartosz Golaszewski Signed-off-by: Greg Kroah-Hartman ---

[PATCH 5.1 52/62] ext4: enforce the immutable flag on open files

2019-07-26 Thread Greg Kroah-Hartman
From: Theodore Ts'o commit 02b016ca7f99229ae6227e7b2fc950c4e140d74a upstream. According to the chattr man page, "a file with the 'i' attribute cannot be modified..." Historically, this was only enforced when the file was opened, per the rest of the description, "... and the file can not be

[PATCH 4.19 34/50] net: bridge: dont cache ether dest pointer on input

2019-07-26 Thread Greg Kroah-Hartman
From: Nikolay Aleksandrov [ Upstream commit 3d26eb8ad1e9b906433903ce05f775cf038e747f ] We would cache ether dst pointer on input in br_handle_frame_finish but after the neigh suppress code that could lead to a stale pointer since both ipv4 and ipv6 suppress code do pskb_may_pull. This means we

[PATCH 4.19 07/50] ipv6: Unlink sibling route in case of failure

2019-07-26 Thread Greg Kroah-Hartman
From: Ido Schimmel [ Upstream commit 54851aa90cf27041d64b12f65ac72e9f97bd90fd ] When a route needs to be appended to an existing multipath route, fib6_add_rt2node() first appends it to the siblings list and increments the number of sibling routes on each sibling. Later, the function notifies

[PATCH 4.19 46/50] ext4: use jbd2_inode dirty range scoping

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 73131fbb003b3691cfcf9656f234b00da497fcd6 upstream. Use the newly introduced jbd2_inode dirty range scoping to prevent us from waiting forever when trying to complete a journal transaction. Signed-off-by: Ross Zwisler Signed-off-by: Theodore Ts'o Reviewed-by: Jan

[PATCH 4.19 37/50] dma-buf: Discard old fence_excl on retrying get_fences_rcu for realloc

2019-07-26 Thread Greg Kroah-Hartman
From: Chris Wilson commit f5b07b04e5f090a85d1e96938520f2b2b58e4a8e upstream. If we have to drop the seqcount & rcu lock to perform a krealloc, we have to restart the loop. In doing so, be careful not to lose track of the already acquired exclusive fence. Fixes: fedf54132d24 ("dma-buf: Restart

[PATCH 5.1 18/62] r8169: fix issue with confused RX unit after PHY power-down on RTL8411b

2019-07-26 Thread Greg Kroah-Hartman
From: Heiner Kallweit [ Upstream commit fe4e8db0392a6c2e795eb89ef5fcd86522e66248 ] On RTL8411b the RX unit gets confused if the PHY is powered-down. This was reported in [0] and confirmed by Realtek. Realtek provided a sequence to fix the RX unit after PHY wakeup. The issue itself seems to

[PATCH 4.19 42/50] ext4: dont allow any modifications to an immutable file

2019-07-26 Thread Greg Kroah-Hartman
From: Darrick J. Wong commit 2e53840362771c73eb0a5ff71611507e64e8eecd upstream. Don't allow any modifications to a file that's marked immutable, which means that we have to flush all the writable pages to make the readonly and we have to check the setattr/setflags parameters more closely.

[PATCH 4.19 31/50] sctp: not bind the socket in sctp_connect

2019-07-26 Thread Greg Kroah-Hartman
From: Xin Long [ Upstream commit 9b6c08878e23adb7cc84bdca94d8a944b03f099e ] Now when sctp_connect() is called with a wrong sa_family, it binds to a port but doesn't set bp->port, then sctp_get_af_specific will return NULL and sctp_connect() returns -EINVAL. Then if sctp_bind() is called to

[PATCH 5.1 39/62] net/mlx5e: Fix port tunnel GRE entropy control

2019-07-26 Thread Greg Kroah-Hartman
From: Eli Britstein [ Upstream commit 914adbb1bcf89478ac138318d28b302704564d59 ] GRE entropy calculation is a single bit per card, and not per port. Force disable GRE entropy calculation upon the first GRE encap rule, and release the force at the last GRE encap rule removal. This is done per

[PATCH 4.19 28/50] netrom: hold sock when setting skb->destructor

2019-07-26 Thread Greg Kroah-Hartman
From: Cong Wang [ Upstream commit 4638faac032756f7eab5524be7be56bee77e426b ] sock_efree() releases the sock refcnt, if we don't hold this refcnt when setting skb->destructor to it, the refcnt would not be balanced. This leads to several bug reports from syzbot. I have checked other users of

[PATCH 4.19 36/50] dma-buf: balance refcount inbalance

2019-07-26 Thread Greg Kroah-Hartman
From: Jérôme Glisse commit 5e383a9798990c69fc759a4930de224bb497e62c upstream. The debugfs take reference on fence without dropping them. Signed-off-by: Jérôme Glisse Cc: Christian König Cc: Daniel Vetter Cc: Sumit Semwal Cc: linux-me...@vger.kernel.org Cc: dri-de...@lists.freedesktop.org

[PATCH 5.1 49/62] perf/core: Fix exclusive events grouping

2019-07-26 Thread Greg Kroah-Hartman
From: Alexander Shishkin commit 8a58ddae23796c733c5dfbd717538d89d036c5bd upstream. So far, we tried to disallow grouping exclusive events for the fear of complications they would cause with moving between contexts. Specifically, moving a software group to a hardware context would violate the

[PATCH 4.19 45/50] jbd2: introduce jbd2_inode dirty range scoping

2019-07-26 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 6ba0e7dc64a5adcda2fbe65adc466891795d639e upstream. Currently both journal_submit_inode_data_buffers() and journal_finish_inode_data_buffers() operate on the entire address space of each of the inodes associated with a given journal entry. The consequence of this is

Re: [RFC PATCH 04/40] soundwire: intel: add debugfs register dump

2019-07-26 Thread Pierre-Louis Bossart
+static const struct file_operations intel_reg_fops = { + .open = simple_open, + .read = intel_reg_read, + .llseek = default_llseek, +}; DEFINE_SIMPLE_ATTRIBUTE()? yes + +static void intel_debugfs_init(struct sdw_intel *sdw) +{ + struct dentry *root =

[PATCH 5.1 58/62] KVM: nVMX: Clear pending KVM_REQ_GET_VMCS12_PAGES when leaving nested

2019-07-26 Thread Greg Kroah-Hartman
From: Jan Kiszka commit cf64527bb33f6cec2ed50f89182fc4688d0056b6 upstream. Letting this pend may cause nested_get_vmcs12_pages to run against an invalid state, corrupting the effective vmcs of L1. This was triggerable in QEMU after a guest corruption in L2, followed by a L1 reset.

[PATCH 4.19 50/50] mm: vmscan: scan anonymous pages on file refaults

2019-07-26 Thread Greg Kroah-Hartman
From: Kuo-Hsin Yang commit 2c012a4ad1a2cd3fb5a0f9307b9d219f84eda1fa upstream. When file refaults are detected and there are many inactive file pages, the system never reclaim anonymous pages, the file pages are dropped aggressively when there are still a lot of cold anonymous pages and system

[PATCH 5.1 51/62] ext4: dont allow any modifications to an immutable file

2019-07-26 Thread Greg Kroah-Hartman
From: Darrick J. Wong commit 2e53840362771c73eb0a5ff71611507e64e8eecd upstream. Don't allow any modifications to a file that's marked immutable, which means that we have to flush all the writable pages to make the readonly and we have to check the setattr/setflags parameters more closely.

[PATCH 4.19 43/50] ext4: enforce the immutable flag on open files

2019-07-26 Thread Greg Kroah-Hartman
From: Theodore Ts'o commit 02b016ca7f99229ae6227e7b2fc950c4e140d74a upstream. According to the chattr man page, "a file with the 'i' attribute cannot be modified..." Historically, this was only enforced when the file was opened, per the rest of the description, "... and the file can not be

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