[PATCH 5.10 161/221] selinux: vsock: Set SID for socket returned by accept()

2021-03-29 Thread Greg Kroah-Hartman
From: David Brazdil [ Upstream commit 1f935e8e72ec28dddb2dc0650b3b6626a293d94b ] For AF_VSOCK, accept() currently returns sockets that are unlabelled. Other socket families derive the child's SID from the SID of the parent and the SID of the incoming packet. This is typically done as the connect

[PATCH 5.10 167/221] drm/msm: Fix suspend/resume on i.MX5

2021-03-29 Thread Greg Kroah-Hartman
From: Fabio Estevam [ Upstream commit a9748134ea4aad989e52a6a91479e0acfd306e5b ] When putting iMX5 into suspend, the following flow is observed: [ 70.023427] [] (msm_atomic_commit_tail) from [] (commit_tail+0x9c/0x18c) [ 70.031890] [] (commit_tail) from [] (drm_atomic_helper_commit+0x1a0/0x

[PATCH 5.10 141/221] ionic: linearize tso skb with too many frags

2021-03-29 Thread Greg Kroah-Hartman
From: Shannon Nelson [ Upstream commit d2c21422323b06938b3c070361dc544f047489d7 ] We were linearizing non-TSO skbs that had too many frags, but we weren't checking number of frags on TSO skbs. This could lead to a bad page reference when we received a TSO skb with more frags than the Tx descrip

[PATCH 5.10 165/221] can: isotp: tx-path: zero initialize outgoing CAN frames

2021-03-29 Thread Greg Kroah-Hartman
From: Oliver Hartkopp [ Upstream commit b5f020f82a8e41201c6ede20fa00389d6980b223 ] Commit d4eb538e1f48 ("can: isotp: TX-path: ensure that CAN frame flags are initialized") ensured the TX flags to be properly set for outgoing CAN frames. In fact the root cause of the issue results from a missing

[PATCH 5.10 169/221] PM: runtime: Defer suspending suppliers

2021-03-29 Thread Greg Kroah-Hartman
From: Rafael J. Wysocki [ Upstream commit 5244f5e2d801259af877ee759e8c22364c607072 ] Because the PM-runtime status of the device is not updated in __rpm_callback(), attempts to suspend the suppliers of the given device triggered by the rpm_put_suppliers() call in there may cause a supplier to be

[PATCH 5.10 160/221] net: stmmac: dwmac-sun8i: Provide TX and RX fifo sizes

2021-03-29 Thread Greg Kroah-Hartman
From: Corentin Labbe [ Upstream commit 014dfa26ce1c647af09bf506285ef67e0e3f0a6b ] MTU cannot be changed on dwmac-sun8i. (ip link set eth0 mtu xxx returning EINVAL) This is due to tx_fifo_size being 0, since this value is used to compute valid MTU range. Like dwmac-sunxi (with commit 806fd188ce2

[PATCH 5.10 170/221] net/mlx5: Add back multicast stats for uplink representor

2021-03-29 Thread Greg Kroah-Hartman
From: Huy Nguyen [ Upstream commit a07231084da2207629b42244380ae2f1e10bd9b4 ] The multicast counter got removed from uplink representor due to the cited patch. Fixes: 47c97e6b10a1 ("net/mlx5e: Fix multicast counter not up-to-date in "ip -s"") Signed-off-by: Huy Nguyen Reviewed-by: Daniel Jurg

[PATCH 5.10 171/221] net/mlx5e: Allow to match on MPLS parameters only for MPLS over UDP

2021-03-29 Thread Greg Kroah-Hartman
From: Alaa Hleihel [ Upstream commit 7d6c86e3ccb5ceea767df5c7a9a17cdfccd3df9a ] Currently, we support hardware offload only for MPLS over UDP. However, rules matching on MPLS parameters are now wrongly offloaded for regular MPLS, without actually taking the parameters into consideration when doi

[PATCH 5.10 175/221] net: bridge: dont notify switchdev for local FDB addresses

2021-03-29 Thread Greg Kroah-Hartman
From: Vladimir Oltean [ Upstream commit 6ab4c3117aec4e08007d9e971fa4133e1de1082d ] As explained in this discussion: https://lore.kernel.org/netdev/20210117193009.io3nungdwuzmo5f7@skbuf/ the switchdev notifiers for FDB entries managed to have a zero-day bug. The bridge would not say that this en

[PATCH 5.10 143/221] netfilter: nftables: report EOPNOTSUPP on unsupported flowtable flags

2021-03-29 Thread Greg Kroah-Hartman
From: Pablo Neira Ayuso [ Upstream commit 7e6136f1b7272b2202817cff37ada355eb5e6784 ] Error was not set accordingly. Fixes: 8bb69f3b2918 ("netfilter: nf_tables: add flowtable offload control plane") Signed-off-by: Pablo Neira Ayuso Signed-off-by: Sasha Levin --- net/netfilter/nf_tables_api.c

[PATCH 5.10 173/221] net/mlx5e: Fix error path for ethtool set-priv-flag

2021-03-29 Thread Greg Kroah-Hartman
From: Aya Levin [ Upstream commit 4eacfe72e3e037e3fc019113df32c39a705148c2 ] Expose error value when failing to comply to command: $ ethtool --set-priv-flags eth2 rx_cqe_compress [on/off] Fixes: be7e87f92b58 ("net/mlx5e: Fail safe cqe compressing/moderation mode setting") Signed-off-by: Aya Le

[PATCH 5.10 145/221] netfilter: flowtable: Make sure GC works periodically in idle system

2021-03-29 Thread Greg Kroah-Hartman
From: Yinjun Zhang [ Upstream commit 740b486a8d1f966e68ac0666f1fd57441a7cda94 ] Currently flowtable's GC work is initialized as deferrable, which means GC cannot work on time when system is idle. So the hardware offloaded flow may be deleted for timeout, since its used time is not timely updated

[PATCH 5.10 147/221] libbpf: Use SOCK_CLOEXEC when opening the netlink socket

2021-03-29 Thread Greg Kroah-Hartman
From: Kumar Kartikeya Dwivedi [ Upstream commit 58bfd95b554f1a23d01228672f86bb489bdbf4ba ] Otherwise, there exists a small window between the opening and closing of the socket fd where it may leak into processes launched by some other thread. Fixes: 949abbe88436 ("libbpf: add function to setup

[PATCH 5.10 138/221] nfp: flower: fix pre_tun mask id allocation

2021-03-29 Thread Greg Kroah-Hartman
From: Louis Peens [ Upstream commit d8ce0275e45ec809a33f98fc080fe7921b720dfb ] pre_tun_rule flows does not follow the usual add-flow path, instead they are used to update the pre_tun table on the firmware. This means that if the mask-id gets allocated here the firmware will never see the "NFP_FL

[PATCH 5.10 146/221] libbpf: Fix error path in bpf_object__elf_init()

2021-03-29 Thread Greg Kroah-Hartman
From: Namhyung Kim [ Upstream commit 8f3f5792f2940c16ab63c614b26494c8689c9c1e ] When it failed to get section names, it should call into bpf_object__elf_finish() like others. Fixes: 88a82120282b ("libbpf: Factor out common ELF operations and improve logging") Signed-off-by: Namhyung Kim Signe

[PATCH 5.10 144/221] netfilter: nftables: allow to update flowtable flags

2021-03-29 Thread Greg Kroah-Hartman
From: Pablo Neira Ayuso [ Upstream commit 7b35582cd04ace2fd1807c1b624934e465cc939d ] Honor flowtable flags from the control update path. Disallow disabling to toggle hardware offload support though. Fixes: 8bb69f3b2918 ("netfilter: nf_tables: add flowtable offload control plane") Signed-off-by

[PATCH 5.10 186/221] net: phy: broadcom: Avoid forward for bcm54xx_config_clock_delay()

2021-03-29 Thread Greg Kroah-Hartman
From: Florian Fainelli [ Upstream commit 133bf7b4fbbe58cff5492e37e95e75c88161f1b8 ] Avoid a forward declaration by moving the callers of bcm54xx_config_clock_delay() below its body. Signed-off-by: Florian Fainelli Reviewed-by: Vladimir Oltean Signed-off-by: David S. Miller Signed-off-by: Sas

[PATCH 5.10 187/221] net: phy: broadcom: Set proper 1000BaseX/SGMII interface mode for BCM54616S

2021-03-29 Thread Greg Kroah-Hartman
From: Robert Hancock [ Upstream commit 3afd0218992a8d1398e9791d6c2edd4c948ae7ee ] The default configuration for the BCM54616S PHY may not match the desired mode when using 1000BaseX or SGMII interface modes, such as when it is on an SFP module. Add code to explicitly set the correct mode using p

[PATCH 5.10 177/221] xen/x86: make XEN_BALLOON_MEMORY_HOTPLUG_LIMIT depend on MEMORY_HOTPLUG

2021-03-29 Thread Greg Kroah-Hartman
From: Roger Pau Monne [ Upstream commit 2b514ec72706a31bea0c3b97e622b81535b5323a ] The Xen memory hotplug limit should depend on the memory hotplug generic option, rather than the Xen balloon configuration. It's possible to have a kernel with generic memory hotplug enabled, but without Xen ballo

[PATCH 5.10 190/221] netfilter: x_tables: Use correct memory barriers.

2021-03-29 Thread Greg Kroah-Hartman
From: Mark Tomlinson [ Upstream commit 175e476b8cdf2a4de7432583b49c871345e4f8a1 ] When a new table value was assigned, it was followed by a write memory barrier. This ensured that all writes before this point would complete before any writes after this point. However, to determine whether the ru

[PATCH 5.10 189/221] Revert "netfilter: x_tables: Switch synchronization to RCU"

2021-03-29 Thread Greg Kroah-Hartman
From: Mark Tomlinson [ Upstream commit d3d40f237480abf3268956daf18cdc56edd32834 ] This reverts commit cc00bcaa589914096edef7fb87ca5cee4a166b5c. This (and the preceding) patch basically re-implemented the RCU mechanisms of patch 784544739a25. That patch was replaced because of the performance pr

[PATCH 5.10 188/221] net: phy: broadcom: Fix RGMII delays for BCM50160 and BCM50610M

2021-03-29 Thread Greg Kroah-Hartman
From: Florian Fainelli [ Upstream commit b1dd9bf688b0dcc5a34dca660de46c7570bd9243 ] The PHY driver entry for BCM50160 and BCM50610M calls bcm54xx_config_init() but does not call bcm54xx_config_clock_delay() in order to configuration appropriate clock delays on the PHY, fix that. Fixes: 7626

[PATCH 5.10 192/221] arm64: mm: correct the inside linear map range during hotplug check

2021-03-29 Thread Greg Kroah-Hartman
From: Pavel Tatashin [ Upstream commit ee7febce051945be28ad86d16a15886f878204de ] Memory hotplug may fail on systems with CONFIG_RANDOMIZE_BASE because the linear map range is not checked correctly. The start physical address that linear map covers can be actually at the end of the range becaus

[PATCH 5.10 191/221] arm64/mm: define arch_get_mappable_range()

2021-03-29 Thread Greg Kroah-Hartman
From: Anshuman Khandual [ Upstream commit 03aaf83fba6e5af08b5dd174c72edee9b7d9ed9b ] This overrides arch_get_mappable_range() on arm64 platform which will be used with recently added generic framework. It drops inside_linear_region() and subsequent check in arch_add_memory() which are no longer

[PATCH 5.10 195/221] Revert "netfilter: x_tables: Update remaining dereference to RCU"

2021-03-29 Thread Greg Kroah-Hartman
From: Mark Tomlinson [ Upstream commit abe7034b9a8d57737e80cc16d60ed3666990bdbf ] This reverts commit 443d6e86f821a165fae3fc3fc13086d27ac140b1. This (and the following) patch basically re-implemented the RCU mechanisms of patch 784544739a25. That patch was replaced because of the performance pr

[PATCH 5.10 193/221] dm table: Fix zoned model check and zone sectors check

2021-03-29 Thread Greg Kroah-Hartman
From: Shin'ichiro Kawasaki [ Upstream commit 2d669ceb69c276f7637cf760287ca4187add082e ] Commit 24f6b6036c9e ("dm table: fix zoned iterate_devices based device capability checks") triggered dm table load failure when dm-zoned device is set up for zoned block devices and a regular device for cache

[PATCH 5.10 194/221] mm/mmu_notifiers: ensure range_end() is paired with range_start()

2021-03-29 Thread Greg Kroah-Hartman
From: Sean Christopherson [ Upstream commit c2655835fd8cabdfe7dab737253de3ffb88da126 ] If one or more notifiers fails .invalidate_range_start(), invoke .invalidate_range_end() for "all" notifiers. If there are multiple notifiers, those that did not fail are expecting _start() and _end() to be p

[PATCH 5.10 197/221] ACPI: scan: Use unique number for instance_no

2021-03-29 Thread Greg Kroah-Hartman
From: Andy Shevchenko [ Upstream commit eb50aaf960e3bedfef79063411ffd670da94b84b ] The decrementation of acpi_device_bus_id->instance_no in acpi_device_del() is incorrect, because it may cause a duplicate instance number to be allocated next time a device with the same acpi_device_bus_id is adde

[PATCH 5.10 178/221] RDMA/cxgb4: Fix adapter LE hash errors while destroying ipv6 listening server

2021-03-29 Thread Greg Kroah-Hartman
From: Potnuri Bharat Teja [ Upstream commit 3408be145a5d6418ff955fe5badde652be90e700 ] Not setting the ipv6 bit while destroying ipv6 listening servers may result in potential fatal adapter errors due to lookup engine memory hash errors. Therefore always set ipv6 field while destroying ipv6 list

[PATCH 5.10 196/221] ACPI: scan: Rearrange memory allocation in acpi_device_add()

2021-03-29 Thread Greg Kroah-Hartman
From: Rafael J. Wysocki [ Upstream commit c1013ff7a5472db637c56bb6237f8343398c03a7 ] The upfront allocation of new_bus_id is done to avoid allocating memory under acpi_device_lock, but it doesn't really help, because (1) it leads to many unnecessary memory allocations for _ADR devices, (2) kstrd

[PATCH 5.10 198/221] perf auxtrace: Fix auxtrace queue conflict

2021-03-29 Thread Greg Kroah-Hartman
From: Adrian Hunter [ Upstream commit b410ed2a8572d41c68bd9208555610e4b07d0703 ] The only requirement of an auxtrace queue is that the buffers are in time order. That is achieved by making separate queues for separate perf buffer or AUX area buffer mmaps. That generally means a separate queue

[PATCH 5.10 199/221] perf synthetic events: Avoid write of uninitialized memory when generating PERF_RECORD_MMAP* records

2021-03-29 Thread Greg Kroah-Hartman
From: Ian Rogers [ Upstream commit 2a76f6de07906f0bb5f2a13fb02845db1695cc29 ] Account for alignment bytes in the zero-ing memset. Fixes: 1a853e36871b533c ("perf record: Allow specifying a pid to record") Signed-off-by: Ian Rogers Acked-by: Jiri Olsa Cc: Ingo Molnar Cc: Alexander Shishkin Cc

[PATCH 5.10 200/221] io_uring: fix provide_buffers sign extension

2021-03-29 Thread Greg Kroah-Hartman
From: Pavel Begunkov [ Upstream commit d81269fecb8ce16eb07efafc9ff5520b2a31c486 ] io_provide_buffers_prep()'s "p->len * p->nbufs" to sign extension problems. Not a huge problem as it's only used for access_ok() and increases the checked length, but better to keep typing right. Reported-by: Coli

[PATCH 5.10 201/221] block: recalculate segment count for multi-segment discards correctly

2021-03-29 Thread Greg Kroah-Hartman
From: David Jeffery [ Upstream commit a958937ff166fc60d1c3a721036f6ff41bfa2821 ] When a stacked block device inserts a request into another block device using blk_insert_cloned_request, the request's nr_phys_segments field gets recalculated by a call to blk_recalc_rq_segments in blk_cloned_rq_ch

[PATCH 5.10 204/221] scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 3401ecf7fc1b9458a19d42c0e26a228f18ac7dda ] When kzalloc() returns NULL, no error return code of mpt3sas_base_attach() is assigned. To fix this bug, r is assigned with -ENOMEM in this case. Link: https://lore.kernel.org/r/20210308035241.3288-1-baijiaju1...@gmai

[PATCH 5.10 208/221] x86/mem_encrypt: Correct physical address calculation in __set_clr_pte_enc()

2021-03-29 Thread Greg Kroah-Hartman
From: Isaku Yamahata commit 8249d17d3194eac064a8ca5bc5ca0abc86feecde upstream. The pfn variable contains the page frame number as returned by the pXX_pfn() functions, shifted to the right by PAGE_SHIFT to remove the page bits. After page protection computations are done to it, it gets shifted ba

[PATCH 5.10 207/221] locking/mutex: Fix non debug version of mutex_lock_io_nested()

2021-03-29 Thread Greg Kroah-Hartman
From: Thomas Gleixner commit 291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7 upstream. If CONFIG_DEBUG_LOCK_ALLOC=n then mutex_lock_io_nested() maps to mutex_lock() which is clearly wrong because mutex_lock() lacks the io_schedule_prepare()/finish() invocations. Map it to mutex_lock_io(). Fixes: f218

[PATCH 5.10 209/221] mm/memcg: fix 5.10 backport of splitting page memcg

2021-03-29 Thread Greg Kroah-Hartman
From: Hugh Dickins The straight backport of 5.12's e1baddf8475b ("mm/memcg: set memcg when splitting page") works fine in 5.11, but turned out to be wrong for 5.10: because that relies on a separate flag, which must also be set for the memcg to be recognized and uncharged and cleared when freeing

[PATCH 5.10 206/221] cifs: Adjust key sizes and key generation routines for AES256 encryption

2021-03-29 Thread Greg Kroah-Hartman
From: Shyam Prasad N commit 45a4546c6167a2da348a31ca439d8a8ff773b6ea upstream. For AES256 encryption (GCM and CCM), we need to adjust the size of a few fields to 32 bytes instead of 16 to accommodate the larger keys. Also, the L value supplied to the key generator needs to be changed from to 25

[PATCH 5.10 180/221] net: Consolidate common blackhole dst ops

2021-03-29 Thread Greg Kroah-Hartman
From: Daniel Borkmann [ Upstream commit c4c877b2732466b4c63217baad05c96f775912c7 ] Move generic blackhole dst ops to the core and use them from both ipv4_dst_blackhole_ops and ip6_dst_blackhole_ops where possible. No functional change otherwise. We need these also in other locations and having t

[PATCH 5.10 181/221] net, bpf: Fix ip6ip6 crash with collect_md populated skbs

2021-03-29 Thread Greg Kroah-Hartman
From: Daniel Borkmann [ Upstream commit a188bb5638d41aa99090ebf2f85d3505ab13fba5 ] I ran into a crash where setting up a ip6ip6 tunnel device which was /not/ set to collect_md mode was receiving collect_md populated skbs for xmit. The BPF prog was populating the skb via bpf_skb_set_tunnel_key()

[PATCH 5.10 213/221] r8169: fix DMA being used after buffer free if WoL is enabled

2021-03-29 Thread Greg Kroah-Hartman
From: Heiner Kallweit commit f658b90977d2e79822a558e48116e059a7e75dec upstream. IOMMU errors have been reported if WoL is enabled and interface is brought down. It turned out that the network chip triggers DMA transfers after the DMA buffers have been freed. For WoL to work we need to leave rx e

[PATCH 5.10 182/221] igb: avoid premature Rx buffer reuse

2021-03-29 Thread Greg Kroah-Hartman
From: Li RongQing [ Upstream commit 98dfb02aa22280bd8833836d1b00ab0488fa951f ] Igb needs a similar fix as commit 75aab4e10ae6a ("i40e: avoid premature Rx buffer reuse") The page recycle code, incorrectly, relied on that a page fragment could not be freed inside xdp_do_redirect(). This assumptio

[PATCH 5.10 210/221] fs/cachefiles: Remove wait_bit_key layout dependency

2021-03-29 Thread Greg Kroah-Hartman
From: Matthew Wilcox (Oracle) commit 39f985c8f667c80a3d1eb19d31138032fa36b09e upstream. Cachefiles was relying on wait_page_key and wait_bit_key being the same layout, which is fragile. Now that wait_page_key is exposed in the pagemap.h header, we can remove that fragility A comment on the nee

[PATCH 5.10 184/221] net: axienet: Fix probe error cleanup

2021-03-29 Thread Greg Kroah-Hartman
From: Robert Hancock [ Upstream commit 59cd4f19267a0aab87a8c07e4426eb7187ee548d ] The driver did not always clean up all allocated resources when probe failed. Fix the probe cleanup path to clean up everything that was allocated. Fixes: 57baf8cc70ea ("net: axienet: Handle deferred probe on cloc

[PATCH 5.10 176/221] octeontx2-af: Fix memory leak of object buf

2021-03-29 Thread Greg Kroah-Hartman
From: Colin Ian King [ Upstream commit 9e0a537d06fc36861e4f78d0a7df1fe2b3592714 ] Currently the error return path when lfs fails to allocate is not free'ing the memory allocated to buf. Fix this by adding the missing kfree. Addresses-Coverity: ("Resource leak") Fixes: f7884097141b ("octeontx2-a

[PATCH 5.10 215/221] mac80211: fix double free in ibss_leave

2021-03-29 Thread Greg Kroah-Hartman
From: Markus Theil commit 3bd801b14e0c5d29eeddc7336558beb3344efaa3 upstream. Clear beacon ie pointer and ie length after free in order to prevent double free. == BUG: KASAN: double-free or invalid-free \ in ieee80211_ibss_leave+0x8

[PATCH 5.10 185/221] net: phy: introduce phydev->port

2021-03-29 Thread Greg Kroah-Hartman
From: Michael Walle [ Upstream commit 4217a64e18a1647a0dbc68cb3169a5a06f054ec8 ] At the moment, PORT_MII is reported in the ethtool ops. This is odd because it is an interface between the MAC and the PHY and no external port. Some network card drivers will overwrite the port to twisted pair or f

[PATCH 5.10 217/221] fs/ext4: fix integer overflow in s_log_groups_per_flex

2021-03-29 Thread Greg Kroah-Hartman
From: Sabyrzhan Tasbolatov commit f91436d55a279f045987e8b8c1385585dca54be9 upstream. syzbot found UBSAN: shift-out-of-bounds in ext4_mb_init [1], when 1 << sbi->s_es->s_log_groups_per_flex is bigger than UINT_MAX, where sbi->s_mb_prefetch is unsigned integer type. 32 is the maximum allowed powe

[PATCH 5.10 219/221] Revert "net: bonding: fix error return code of bond_neigh_init()"

2021-03-29 Thread Greg Kroah-Hartman
From: David S. Miller commit 080bfa1e6d928a5d1f185cc44e5f3c251df06df5 upstream. This reverts commit 2055a99da8a253a357bdfd359b3338ef3375a26c. This change rejects legitimate configurations. A slave doesn't need to exist nor implement ndo_slave_setup. Signed-off-by: David S. Miller Signed-off-

[PATCH 5.10 218/221] Revert "xen: fix p2m size in dom0 for disabled memory hotplug case"

2021-03-29 Thread Greg Kroah-Hartman
From: Roger Pau Monne commit af44a387e743ab7aa39d3fb5e29c0a973cf91bdc upstream. This partially reverts commit 882213990d32 ("xen: fix p2m size in dom0 for disabled memory hotplug case") There's no need to special case XEN_UNPOPULATED_ALLOC anymore in order to correctly size the p2m. The generic

[PATCH 5.10 216/221] ext4: add reclaim checks to xattr code

2021-03-29 Thread Greg Kroah-Hartman
From: Jan Kara commit 163f0ec1df33cf468509ff38cbcbb5eb0d7fac60 upstream. Syzbot is reporting that ext4 can enter fs reclaim from kvmalloc() while the transaction is started like: fs_reclaim_acquire+0x117/0x150 mm/page_alloc.c:4340 might_alloc include/linux/sched/mm.h:193 [inline] slab_pre

[PATCH 5.10 214/221] net: dsa: b53: VLAN filtering is global to all users

2021-03-29 Thread Greg Kroah-Hartman
From: Florian Fainelli commit d45c36bafb94e72fdb6dee437279b61b6d97e706 upstream. The bcm_sf2 driver uses the b53 driver as a library but does not make usre of the b53_setup() function, this made it fail to inherit the vlan_filtering_is_global attribute. Fix this by moving the assignment to b53_s

[PATCH 5.10 220/221] nvme: fix the nsid value to print in nvme_validate_or_alloc_ns

2021-03-29 Thread Greg Kroah-Hartman
From: Christoph Hellwig commit f4f9fc29e56b6fa9d7fa65ec51d3c82aff99c99b upstream. ns can be NULL at this point, and my move of the check from the original patch by Chaitanya broke this. Fixes: 0ec84df4953b ("nvme-core: check ctrl css before setting up zns") Signed-off-by: Christoph Hellwig Sig

[PATCH 5.10 221/221] can: peak_usb: Revert "can: peak_usb: add forgotten supported devices"

2021-03-29 Thread Greg Kroah-Hartman
From: Marc Kleine-Budde commit 5d7047ed6b7214fbabc16d8712a822e256b1aa44 upstream. In commit 6417f03132a6 ("module: remove never implemented MODULE_SUPPORTED_DEVICE") the MODULE_SUPPORTED_DEVICE macro was removed from the kerne entirely. Shortly before this patch was applied mainline the commit 5

[PATCH 5.11 001/254] mt76: fix tx skb error handling in mt76_dma_tx_queue_skb

2021-03-29 Thread Greg Kroah-Hartman
From: Felix Fietkau [ Upstream commit ae064fc0e32a4d28389086d9f4b260a0c157cfee ] When running out of room in the tx queue after calling drv->tx_prepare_skb, the buffer list will already have been modified on MT7615 and newer drivers. This can leak a DMA mapping and will show up as swiotlb alloca

[PATCH 5.11 003/254] net: stmmac: fix dma physical address of descriptor when display ring

2021-03-29 Thread Greg Kroah-Hartman
From: Joakim Zhang [ Upstream commit bfaf91ca848e758ed7be99b61fd936d03819fa56 ] Driver uses dma_alloc_coherent to allocate dma memory for descriptors, dma_alloc_coherent will return both the virtual address and physical address. AFAIK, virt_to_phys could not convert virtual address to physical a

[PATCH 5.11 002/254] mt76: mt7915: only modify tx buffer list after allocating tx token id

2021-03-29 Thread Greg Kroah-Hartman
From: Felix Fietkau [ Upstream commit 94f0e6256c2ab6803c935634aa1f653174c94879 ] Modifying the tx buffer list too early can leak DMA mappings Signed-off-by: Felix Fietkau Signed-off-by: Kalle Valo Link: https://lore.kernel.org/r/20210216135119.23809-2-...@nbd.name Signed-off-by: Sasha Levin

[PATCH 5.10 168/221] arm64: kdump: update ppos when reading elfcorehdr

2021-03-29 Thread Greg Kroah-Hartman
From: Pavel Tatashin [ Upstream commit 141f8202cfa4192c3af79b6cbd68e7760bb01b5a ] The ppos points to a position in the old kernel memory (and in case of arm64 in the crash kernel since elfcorehdr is passed as a segment). The function should update the ppos by the amount that was read. This bug i

[PATCH 5.10 142/221] net/sched: cls_flower: fix only mask bit check in the validate_ct_state

2021-03-29 Thread Greg Kroah-Hartman
From: wenxu [ Upstream commit afa536d8405a9ca36e45ba035554afbb8da27b82 ] The ct_state validate should not only check the mask bit and also check mask_bit & key_bit.. For the +new+est case example, The 'new' and 'est' bits should be set in both state_mask and state flags. Or the -new-est case als

[PATCH 5.10 174/221] PM: EM: postpone creating the debugfs dir till fs_initcall

2021-03-29 Thread Greg Kroah-Hartman
From: Lukasz Luba [ Upstream commit fb9d62b27ab1e07d625591549c314b7d406d21df ] The debugfs directory '/sys/kernel/debug/energy_model' is needed before the Energy Model registration can happen. With the recent change in debugfs subsystem it's not allowed to create this directory at early stage (c

[PATCH 5.10 172/221] net/mlx5e: Offload tuple rewrite for non-CT flows

2021-03-29 Thread Greg Kroah-Hartman
From: Dima Chumak [ Upstream commit 96b5b4585843e3c83fb1930e5dfbefd0fb889c55 ] Setting connection tracking OVS flows and then setting non-CT flows that use tuple rewrite action (e.g. mod_tp_dst), causes the latter flows not being offloaded. Fix by using a stricter condition in modify_header_mat

[PATCH 5.11 000/254] 5.11.11-rc1 review

2021-03-29 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.11.11 release. There are 254 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 Wed, 31 Mar 2021 07:55:56 +. Anything re

[PATCH 5.11 015/254] sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count

2021-03-29 Thread Greg Kroah-Hartman
From: Denis Efremov [ Upstream commit 155b23e6e53475ca3b8c2a946299b4d4dd6a5a1e ] RXMAC_BC_FRM_CNT_COUNT added to mp->rx_bcasts twice in a row in niu_xmac_interrupt(). Remove the second addition. Signed-off-by: Denis Efremov Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drive

[PATCH 5.11 005/254] powerpc/4xx: Fix build errors from mfdcr()

2021-03-29 Thread Greg Kroah-Hartman
From: Michael Ellerman [ Upstream commit eead089311f4d935ab5d1d8fbb0c42ad44699ada ] lkp reported a build error in fsp2.o: CC arch/powerpc/platforms/44x/fsp2.o {standard input}:577: Error: unsupported relocation against base Which comes from: pr_err("GESR0: 0x%08x\n", mfdcr(base + P

[PATCH 5.11 019/254] cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev

2021-03-29 Thread Greg Kroah-Hartman
From: Sudeep Holla [ Upstream commit fbb31cb805fd3574d3be7defc06a7fd2fd9af7d2 ] Add "arm,vexpress" to cpufreq-dt-platdev blacklist since the actual scaling is handled by the firmware cpufreq drivers(scpi, scmi and vexpress-spc). Signed-off-by: Sudeep Holla Signed-off-by: Viresh Kumar Signed-o

[PATCH 5.11 017/254] cifs: ask for more credit on async read/write code paths

2021-03-29 Thread Greg Kroah-Hartman
From: Aurelien Aptel [ Upstream commit 88fd98a2306755b965e4f4567f84e73db3b6738c ] When doing a large read or write workload we only very gradually increase the number of credits which can cause problems with parallelizing large i/o (I/O ramps up more slowly than it should for large read/write wo

[PATCH 5.11 018/254] gfs2: fix use-after-free in trans_drain

2021-03-29 Thread Greg Kroah-Hartman
From: Bob Peterson [ Upstream commit 1a5a2cfd34c17db73c53ef127272c8c1ae220485 ] This patch adds code to function trans_drain to remove drained bd elements from the ail lists, if queued, before freeing the bd. If we don't remove the bd from the ail, function ail_drain will try to reference the bd

[PATCH 5.11 022/254] NFS: Correct size calculation for create reply length

2021-03-29 Thread Greg Kroah-Hartman
From: Frank Sorenson [ Upstream commit ad3dbe35c833c2d4d0bbf3f04c785d32f931e7c9 ] CREATE requests return a post_op_fh3, rather than nfs_fh3. The post_op_fh3 includes an extra word to indicate 'handle_follows'. Without that additional word, create fails when full 64-byte filehandles are in use.

[PATCH 5.11 021/254] nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default

2021-03-29 Thread Greg Kroah-Hartman
From: Timo Rothenpieler [ Upstream commit a0590473c5e6c4ef17c3132ad08fbad170f72d55 ] This follows what was done in 8c2fabc6542d9d0f8b16bd1045c2eda59bdcde13. With the default being m, it's impossible to build the module into the kernel. Signed-off-by: Timo Rothenpieler Signed-off-by: Anna Schum

[PATCH 5.11 020/254] gpiolib: acpi: Add missing IRQF_ONESHOT

2021-03-29 Thread Greg Kroah-Hartman
From: Yang Li [ Upstream commit 6e5d5791730b55a1f987e1db84b078b91eb49e99 ] fixed the following coccicheck: ./drivers/gpio/gpiolib-acpi.c:176:7-27: ERROR: Threaded IRQ with no primary handler requested without IRQF_ONESHOT Make sure threaded IRQs without a primary handler are always request with

[PATCH 5.11 026/254] net: enetc: set MAC RX FIFO to recommended value

2021-03-29 Thread Greg Kroah-Hartman
From: Alex Marginean [ Upstream commit 1b2395dfff5bb40228a187f21f577cd90673d344 ] On LS1028A, the MAC RX FIFO defaults to the value 2, which is too high and may lead to RX lock-up under traffic at a rate higher than 6 Gbps. Set it to 1 instead, as recommended by the hardware design team and by l

[PATCH 5.11 025/254] net: davicom: Use platform_get_irq_optional()

2021-03-29 Thread Greg Kroah-Hartman
From: Paul Cercueil [ Upstream commit 2e2696223676d56db1a93acfca722c1b96cd552d ] The second IRQ line really is optional, so use platform_get_irq_optional() to obtain it. Signed-off-by: Paul Cercueil Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/davicom/d

[PATCH 5.11 006/254] atm: eni: dont release is never initialized

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 4deb550bc3b698a1f03d0332cde3df154d1b6c1e ] label err_eni_release is reachable when eni_start() fail. In eni_start() it calls dev->phy->start() in the last step, if start() fail we don't need to call phy->stop(), if start() is never called, we neither need to ca

[PATCH 5.11 024/254] net: wan: fix error return code of uhdlc_init()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 62765d39553cfd1ad340124fe1e280450e8c89e2 ] When priv->rx_skbuff or priv->tx_skbuff is NULL, no error return code of uhdlc_init() is assigned. To fix this bug, ret is assigned with -ENOMEM in these cases. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai Sign

[PATCH 5.11 023/254] net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit 143c253f42bad20357e7e4432087aca747c43384 ] When hns_assemble_skb() returns NULL to skb, no error return code of hns_nic_clear_all_rx_fetch() is assigned. To fix this bug, ret is assigned with -ENOMEM in this case. Reported-by: TOTE Robot Signed-off-by: Jia-Ju

[PATCH 5.11 032/254] kbuild: dummy-tools: fix inverted tests for gcc

2021-03-29 Thread Greg Kroah-Hartman
From: Jiri Slaby [ Upstream commit b3d9fc1436808a4ef9927e558b3415e728e710c5 ] There is a test in Kconfig which takes inverted value of a compiler check: * config CC_HAS_INT128 def_bool !$(cc-option,$(m64-flag) -D__SIZEOF_INT128__=0) This results in CC_HAS_INT128 not being in super-confi

[PATCH 5.11 033/254] umem: fix error return code in mm_pci_probe()

2021-03-29 Thread Greg Kroah-Hartman
From: Wei Yongjun [ Upstream commit eeb05595d22c19c8f814ff893dcf88ec277a2365 ] Fix to return negative error code -ENOMEM from the blk_alloc_queue() and dma_alloc_coherent() error handling cases instead of 0, as done elsewhere in this function. Reported-by: Hulk Robot Signed-off-by: Wei Yongjun

[PATCH 5.11 029/254] cifs: change noisy error message to FYI

2021-03-29 Thread Greg Kroah-Hartman
From: Paulo Alcantara [ Upstream commit e3d100eae44b42f309c1366efb8397368f1cf8ed ] A customer has reported that their dmesg were being flooded by CIFS: VFS: \\server Cancelling wait for mid xxx cmd: a CIFS: VFS: \\server Cancelling wait for mid yyy cmd: b CIFS: VFS: \\server Cancelling wa

[PATCH 5.11 030/254] irqchip/ingenic: Add support for the JZ4760

2021-03-29 Thread Greg Kroah-Hartman
From: Paul Cercueil [ Upstream commit 5fbecd2389f48e1415799c63130d0cdce1cf3f60 ] Add support for the interrupt controller found in the JZ4760 SoC, which works exactly like the one in the JZ4770. Signed-off-by: Paul Cercueil Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/202103071

Re: [PATCH v4 1/2] dt-bindings: imx6q-pcie: add one regulator used to power up pcie phy

2021-03-29 Thread Lucas Stach
Am Montag, dem 29.03.2021 um 16:03 +0800 schrieb Richard Zhu: > Both 1.8v and 3.3v power supplies can be used by i.MX8MQ PCIe PHY. > In default, the PCIE_VPH voltage is suggested to be 1.8v refer to data > sheet. When PCIE_VPH is supplied by 3.3v in the HW schematic design, > the VREG_BYPASS bits o

[PATCH 5.11 034/254] sparc64: Fix opcode filtering in handling of no fault loads

2021-03-29 Thread Greg Kroah-Hartman
From: Rob Gardner [ Upstream commit e5e8b80d352ec999d2bba3ea584f541c83f4ca3f ] is_no_fault_exception() has two bugs which were discovered via random opcode testing with stress-ng. Both are caused by improper filtering of opcodes. The first bug can be triggered by a floating point store with a n

Re: linux-next: manual merge of the net-next tree with the bpf tree

2021-03-29 Thread Jiri Olsa
On Mon, Mar 29, 2021 at 12:29:16PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the net-next tree got a conflict in: > > include/linux/bpf.h > > between commit: > > 861de02e5f3f ("bpf: Take module reference for trampoline in module") > > from the bpf tree and co

[PATCH 5.11 028/254] atm: idt77252: fix null-ptr-dereference

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 4416e98594dc04590ebc498fc4e530009535c511 ] this one is similar to the phy_data allocation fix in uPD98402, the driver allocate the idt77105_priv and store to dev_data but later dereference using dev->dev_data, which will cause null-ptr-dereference. fix this is

[PATCH 5.10 202/221] scsi: Revert "qla2xxx: Make sure that aborted commands are freed"

2021-03-29 Thread Greg Kroah-Hartman
From: Bart Van Assche [ Upstream commit 39c0c8553bfb5a3d108aa47f1256076d507605e3 ] Calling vha->hw->tgt.tgt_ops->free_cmd() from qlt_xmit_response() is wrong since the command for which a response is sent must remain valid until the SCSI target core calls .release_cmd(). It has been observed tha

[PATCH 5.10 205/221] smb3: fix cached file size problems in duplicate extents (reflink)

2021-03-29 Thread Greg Kroah-Hartman
From: Steve French commit cfc63fc8126a93cbf95379bc4cad79a7b15b6ece upstream. There were two problems (one of which could cause data corruption) that were noticed with duplicate extents (ie reflink) when debugging why various xfstests were being incorrectly skipped (e.g. generic/138, generic/140,

[PATCH 5.11 036/254] habanalabs: Disable file operations after device is removed

2021-03-29 Thread Greg Kroah-Hartman
From: Tomer Tayar [ Upstream commit ffd123fe839700366ea79b19ac3683bf56817372 ] A device can be removed from the PCI subsystem while a process holds the file descriptor opened. In such a case, the driver attempts to kill the process, but as it is still possible that the process will be alive afte

[PATCH 5.11 031/254] kbuild: add image_name to no-sync-config-targets

2021-03-29 Thread Greg Kroah-Hartman
From: Masahiro Yamada [ Upstream commit 993bdde94547887faaad4a97f0b0480a6da271c3 ] 'make image_name' needs include/config/auto.conf to show the correct output because KBUILD_IMAGE depends on CONFIG options, but should not attempt to resync the configuration. Signed-off-by: Masahiro Yamada Sign

[PATCH 5.11 007/254] atm: lanai: dont run lanai_dev_close if not open

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit a2bd45834e83d6c5a04d397bde13d744a4812dfc ] lanai_dev_open() can fail. When it fail, lanai->base is unmapped and the pci device is disabled. The caller, lanai_init_one(), then tries to run atm_dev_deregister(). This will subsequently call lanai_dev_close() and u

[PATCH 5.11 039/254] kselftest: arm64: Fix exit code of sve-ptrace

2021-03-29 Thread Greg Kroah-Hartman
From: Mark Brown [ Upstream commit 07e644885bf6727a48db109fad053cb43f3c9859 ] We track if sve-ptrace encountered a failure in a variable but don't actually use that value when we exit the program, do so. Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20210309190304.39169-1-broo...@k

[PATCH 5.11 038/254] u64_stats,lockdep: Fix u64_stats_init() vs lockdep

2021-03-29 Thread Greg Kroah-Hartman
From: Peter Zijlstra [ Upstream commit d5b0e0677bfd5efd17c5bbb00156931f0d41cb85 ] Jakub reported that: static struct net_device *rtl8139_init_board(struct pci_dev *pdev) { ... u64_stats_init(&tp->rx_stats.syncp); u64_stats_init(&tp->tx_stats.syncp);

[PATCH 5.11 040/254] regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck

2021-03-29 Thread Greg Kroah-Hartman
From: satya priya [ Upstream commit e610e072c87a30658479a7b4c51e1801cb3f450c ] Correct the REGULATOR_LINEAR_RANGE and n_voltges for pmic5_hfsmps515 buck. Signed-off-by: satya priya Link: https://lore.kernel.org/r/1614155592-14060-4-git-send-email-ska...@codeaurora.org Signed-off-by: Mark Brow

[PATCH 5.10 212/221] can: dev: Move device back to init netns on owning netns delete

2021-03-29 Thread Greg Kroah-Hartman
From: Martin Willi commit 3a5ca857079ea022e0b1b17fc154f7ad7dbc150f upstream. When a non-initial netns is destroyed, the usual policy is to delete all virtual network interfaces contained, but move physical interfaces back to the initial netns. This keeps the physical interface visible on the sys

[PATCH 5.11 008/254] Revert "r8152: adjust the settings about MAC clock speed down for RTL8153"

2021-03-29 Thread Greg Kroah-Hartman
From: Hayes Wang [ Upstream commit 4b5dc1a94d4f92b5845e98bd9ae344b26d933aad ] This reverts commit 134f98bcf1b898fb9d6f2b91bc85dd2e5478b4b8. The r8153_mac_clk_spd() is used for RTL8153A only, because the register table of RTL8153B is different from RTL8153A. However, this function would be calle

[PATCH 5.11 041/254] regulator: qcom-rpmh: Use correct buck for S1C regulator

2021-03-29 Thread Greg Kroah-Hartman
From: satya priya [ Upstream commit dfe03bca8db4957d4b60614ff7df4d136ba90f37 ] Use correct buck, that is, pmic5_hfsmps515 for S1C regulator of PM8350C PMIC. Signed-off-by: satya priya Link: https://lore.kernel.org/r/1614155592-14060-7-git-send-email-ska...@codeaurora.org Signed-off-by: Mark B

[PATCH 5.10 203/221] scsi: qedi: Fix error return code of qedi_alloc_global_queues()

2021-03-29 Thread Greg Kroah-Hartman
From: Jia-Ju Bai [ Upstream commit f69953837ca5d98aa983a138dc0b90a411e9c763 ] When kzalloc() returns NULL to qedi->global_queues[i], no error return code of qedi_alloc_global_queues() is assigned. To fix this bug, status is assigned with -ENOMEM in this case. Link: https://lore.kernel.org/r/20

[PATCH 5.11 027/254] atm: uPD98402: fix incorrect allocation

2021-03-29 Thread Greg Kroah-Hartman
From: Tong Zhang [ Upstream commit 3153724fc084d8ef640c611f269ddfb576d1dcb1 ] dev->dev_data is set in zatm.c, calling zatm_start() will overwrite this dev->dev_data in uPD98402_start() and a subsequent PRIV(dev)->lock (i.e dev->phy_data->lock) will result in a null-ptr-dereference. I believe th

[PATCH 5.11 016/254] gianfar: fix jumbo packets+napi+rx overrun crash

2021-03-29 Thread Greg Kroah-Hartman
From: Michael Braun [ Upstream commit d8861bab48b6c1fc3cdbcab8ff9d1eaea43afe7f ] When using jumbo packets and overrunning rx queue with napi enabled, the following sequence is observed in gfar_add_rx_frag: | lstatus | | skb | t | lstatus,

[PATCH 5.10 211/221] ch_ktls: fix enum-conversion warning

2021-03-29 Thread Greg Kroah-Hartman
From: Arnd Bergmann commit 6f235a69e59484e382dc31952025b0308efedc17 upstream. gcc points out an incorrect enum assignment: drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c: In function 'chcr_ktls_cpl_set_tcb_rpl': drivers/net/ethernet/chelsio/inline_crypto/ch_ktls/chcr_ktls.c:684

[PATCH 5.10 179/221] bpf: Dont do bpf_cgroup_storage_set() for kuprobe/tp programs

2021-03-29 Thread Greg Kroah-Hartman
[ Upstream commit 05a68ce5fa51a83c360381630f823545c5757aa2 ] For kuprobe and tracepoint bpf programs, kernel calls trace_call_bpf() which calls BPF_PROG_RUN_ARRAY_CHECK() to run the program array. Currently, BPF_PROG_RUN_ARRAY_CHECK() also calls bpf_cgroup_storage_set() to set percpu cgroup local

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