5.10.88-rc1 review
Subsystems (5)
Greg Kroah-Hartman
maintainercover 5.10.88-rc1 review
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.88-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.10.88-rc1
Juergen Gross <[email protected]>
xen/netback: don't queue unlimited number of packages
Juergen Gross <[email protected]>
xen/netback: fix rx queue stall detection
Juergen Gross <[email protected]>
xen/console: harden hvc_xen against event channel storms
Juergen Gross <[email protected]>
xen/netfront: harden netfront against event channel storms
Juergen Gross <[email protected]>
xen/blkfront: harden blkfront against event channel storms
Magnus Karlsson <[email protected]>
Revert "xsk: Do not sleep in poll() when need_wakeup set"
Tony Lindgren <[email protected]>
bus: ti-sysc: Fix variable set but not used warning for reinit_modules
Paul E. McKenney <[email protected]>
rcu: Mark accesses to rcu_state.n_force_qs
George Kennedy <[email protected]>
scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()
George Kennedy <[email protected]>
scsi: scsi_debug: Fix type in min_t to avoid stack OOB
George Kennedy <[email protected]>
scsi: scsi_debug: Don't call kcalloc() if size arg is zero
Miklos Szeredi <[email protected]>
ovl: fix warning in ovl_create_real()
Miklos Szeredi <[email protected]>
fuse: annotate lock in fuse_reverse_inval_entry()
Pavel Skripkin <[email protected]>
media: mxl111sf: change mutex_init() location
Magnus Karlsson <[email protected]>
xsk: Do not sleep in poll() when need_wakeup set
Fabio Estevam <[email protected]>
ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
Nathan Chancellor <[email protected]>
Input: touchscreen - avoid bitwise vs logical OR warning
Le Ma <[email protected]>
drm/amdgpu: correct register access for RLC_JUMP_TABLE_RESTORE
George Kennedy <[email protected]>
libata: if T_LENGTH is zero, dma direction should be DMA_NONE
Yu Liao <[email protected]>
timekeeping: Really make sure wall_to_monotonic isn't positive
Ji-Ze Hong (Peter Hong) <[email protected]>
serial: 8250_fintek: Fix garbled text for console
Tejun Heo <[email protected]>
iocost: Fix divide-by-zero on donation from low hweight cgroup
Naohiro Aota <[email protected]>
zonefs: add MODULE_ALIAS_FS
Filipe Manana <[email protected]>
btrfs: fix double free of anon_dev after failure to create subvolume
Jianglei Nie <[email protected]>
btrfs: fix memory leak in __add_inode_ref()
Daniele Palmas <[email protected]>
USB: serial: option: add Telit FN990 compositions
Johan Hovold <[email protected]>
USB: serial: cp210x: fix CP2105 GPIO registration
Nehal Bakulchandra Shah <[email protected]>
usb: xhci: Extend support for runtime power management for AMD's Yellow carp.
Stefan Roese <[email protected]>
PCI/MSI: Mask MSI-X vectors only on success
Thomas Gleixner <[email protected]>
PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
Amelie Delaunay <[email protected]>
usb: dwc2: fix STM ID/VBUS detection startup delay in dwc2_driver_probe
Jimmy Wang <[email protected]>
USB: NO_LPM quirk Lenovo USB-C to Ethernet Adapher(RTL8153-04)
Tetsuo Handa <[email protected]>
tty: n_hdlc: make n_hdlc_tty_wakeup() asynchronous
Vitaly Kuznetsov <[email protected]>
KVM: x86: Drop guest CPUID check for host initiated writes to MSR_IA32_PERF_CAPABILITIES
Greg Kroah-Hartman <[email protected]>
Revert "usb: early: convert to readl_poll_timeout_atomic()"
Greg Kroah-Hartman <[email protected]>
USB: gadget: bRequestType is a bitfield, not a enum
Xiaoming Ni <[email protected]>
powerpc/85xx: Fix oops when CONFIG_FSL_PMC=n
Martin KaFai Lau <[email protected]>
bpf, selftests: Fix racing issue in btf_skc_cls_ingress test
Eric Dumazet <[email protected]>
sit: do not call ipip6_dev_free() from sit_init_net()
Florian Fainelli <[email protected]>
net: systemport: Add global locking for descriptor lifecycle
D. Wythe <[email protected]>
net/smc: Prevent smc_release() from long blocking
Gal Pressman <[email protected]>
net: Fix double 0x prefix print in SKB dump
Jiasheng Jiang <[email protected]>
sfc_ef100: potential dereference of null pointer
Willem de Bruijn <[email protected]>
net/packet: rx_owner_map depends on pg_vec
Haimin Zhang <[email protected]>
netdevsim: Zero-initialize memory for new map's value in function nsim_bpf_map_alloc
Cyril Novikov <[email protected]>
ixgbe: set X550 MDIO speed before talking to PHY
Robert Schlabbach <[email protected]>
ixgbe: Document how to enable NBASE-T support
Sasha Neftin <[email protected]>
igc: Fix typo in i225 LTR functions
Letu Ren <[email protected]>
igbvf: fix double free in igbvf_probe
Karen Sornek <[email protected]>
igb: Fix removal of unicast MAC filters of VFs
Nathan Chancellor <[email protected]>
soc/tegra: fuse: Fix bitwise vs. logical OR warning
Florian Westphal <[email protected]>
mptcp: clear 'kern' flag from fallback sockets
Lang Yu <[email protected]>
drm/amd/pm: fix a potential gpu_metrics_table memory leak
Hangyu Hua <[email protected]>
rds: memory leak in __rds_conn_create()
Baowen Zheng <[email protected]>
flow_offload: return EOPNOTSUPP for the unsupported mpls action type
Johannes Berg <[email protected]>
mac80211: fix lookup when adding AddBA extension element
Johannes Berg <[email protected]>
mac80211: agg-tx: don't schedule_and_wake_txq() under sta->lock
Jiasheng Jiang <[email protected]>
drm/ast: potential dereference of null pointer
Hangbin Liu <[email protected]>
selftest/net/forwarding: declare NETIFS p9 p10
Davide Caratti <[email protected]>
net/sched: sch_ets: don't remove idle classes from the round-robin list
Alyssa Ross <[email protected]>
dmaengine: st_fdma: fix MODULE_ALIAS
David Ahern <[email protected]>
selftests: Fix IPv6 address bind tests
David Ahern <[email protected]>
selftests: Fix raw socket bind tests with VRF
David Ahern <[email protected]>
selftests: Add duplicate config only for MD5 VRF tests
Jie Wang <[email protected]>
net: hns3: fix use-after-free bug in hclgevf_send_mbx_msg
Eric Dumazet <[email protected]>
inet_diag: fix kernel-infoleak for UDP sockets
Eric Dumazet <[email protected]>
sch_cake: do not call cake_destroy() from cake_init()
Philipp Rudo <[email protected]>
s390/kexec_file: fix error handling when applying relocations
Jie2x Zhou <[email protected]>
selftests: net: Correct ping6 expected rc from 2 to 1
Wei Wang <[email protected]>
virtio/vsock: fix the transport to work with VMADDR_CID_ANY
Stephan Gerhold <[email protected]>
soc: imx: Register SoC device only on i.MX boards
Mike Tipton <[email protected]>
clk: Don't parent clks until the parent is fully registered
Dinh Nguyen <[email protected]>
ARM: socfpga: dts: fix qspi node compatible
Xiubo Li <[email protected]>
ceph: initialize pathlen variable in reconnect_caps_cb
Hu Weiwen <[email protected]>
ceph: fix duplicate increment of opened_inodes metric
Dan Carpenter <[email protected]>
tee: amdtee: fix an IS_ERR() vs NULL bug
Randy Dunlap <[email protected]>
hv: utils: add PTP_1588_CLOCK to Kconfig to fix build
Johannes Berg <[email protected]>
mac80211: track only QoS data frames for admission control
Alex Bee <[email protected]>
arm64: dts: rockchip: fix audio-supply for Rock Pi 4
John Keeping <[email protected]>
arm64: dts: rockchip: fix rk3399-leez-p710 vcc3v3-lan supply
John Keeping <[email protected]>
arm64: dts: rockchip: fix rk3308-roc-cc vcc-sd supply
Artem Lapkin <[email protected]>
arm64: dts: rockchip: remove mmc-hs400-enhanced-strobe from rk3399-khadas-edge
Fabio Estevam <[email protected]>
arm64: dts: imx8mp-evk: Improve the Ethernet PHY description
Joakim Zhang <[email protected]>
arm64: dts: imx8m: correct assigned clocks for FEC
Paul Moore <[email protected]>
audit: improve robustness of the audit queue handling
Joe Thornber <[email protected]>
dm btree remove: fix use after free in rebalance_children()
Jerome Marchand <[email protected]>
recordmcount.pl: look for jgnop instruction as well as bcrl on s390
Dan Carpenter <[email protected]>
vdpa: check that offsets are within bounds
Will Deacon <[email protected]>
virtio_ring: Fix querying of maximum DMA mapping size for virtio device
Daniel Borkmann <[email protected]>
bpf, selftests: Add test case trying to taint map value pointer
Daniel Borkmann <[email protected]>
bpf: Make 32->64 bounds propagation slightly more robust
Daniel Borkmann <[email protected]>
bpf: Fix signed bounds propagation after mov32
Sudeep Holla <[email protected]>
firmware: arm_scpi: Fix string overflow in SCPI genpd driver
Johannes Berg <[email protected]>
mac80211: validate extended element ID is present
Felix Fietkau <[email protected]>
mac80211: send ADDBA requests using the tid/queue of the aggregation session
Johannes Berg <[email protected]>
mac80211: mark TX-during-stop for TX in in_reconfig
Felix Fietkau <[email protected]>
mac80211: fix regression in SSN handling of addba tx
Paolo Bonzini <[email protected]>
KVM: downgrade two BUG_ONs to WARN_ON_ONCE
Vitaly Kuznetsov <[email protected]>
KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE
-------------
Diffstat:
.../device_drivers/ethernet/intel/ixgbe.rst | 16 +++ Makefile | 4 +- arch/arm/boot/dts/imx6ull-pinfunc.h | 2 +- arch/arm/boot/dts/socfpga_arria10_socdk_qspi.dts | 2 +- arch/arm/boot/dts/socfpga_arria5_socdk.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_socdk.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_sockit.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_socrates.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_sodia.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts | 4 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 7 +- arch/arm64/boot/dts/freescale/imx8mn.dtsi | 7 +- arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 2 + arch/arm64/boot/dts/freescale/imx8mp.dtsi | 7 +- arch/arm64/boot/dts/rockchip/rk3308-roc-cc.dts | 2 +- .../boot/dts/rockchip/rk3399-khadas-edge.dtsi | 1 - arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dts | 2 +- arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 2 +- arch/powerpc/platforms/85xx/smp.c | 4 +- arch/s390/kernel/machine_kexec_file.c | 7 +- arch/x86/kvm/x86.c | 2 +- block/blk-iocost.c | 9 +- drivers/ata/libata-scsi.c | 15 ++- drivers/block/xen-blkfront.c | 15 ++- drivers/bus/ti-sysc.c | 3 +- drivers/clk/clk.c | 15 ++- drivers/dma/st_fdma.c | 2 +- drivers/firmware/scpi_pm_domain.c | 10 +- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 4 +- drivers/gpu/drm/amd/pm/swsmu/smu12/smu_v12_0.c | 3 + drivers/gpu/drm/ast/ast_mode.c | 5 +- drivers/hv/Kconfig | 1 + drivers/input/touchscreen/of_touchscreen.c | 42 +++---- drivers/md/persistent-data/dm-btree-remove.c | 2 +- drivers/media/usb/dvb-usb-v2/mxl111sf.c | 16 ++- drivers/net/ethernet/broadcom/bcmsysport.c | 5 +- drivers/net/ethernet/broadcom/bcmsysport.h | 1 + .../ethernet/hisilicon/hns3/hns3vf/hclgevf_mbx.c | 3 +- drivers/net/ethernet/intel/igb/igb_main.c | 28 ++--- drivers/net/ethernet/intel/igbvf/netdev.c | 1 + drivers/net/ethernet/intel/igc/igc_i225.c | 2 +- drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 + drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c | 3 + drivers/net/ethernet/sfc/ef100_nic.c | 3 + drivers/net/netdevsim/bpf.c | 1 + drivers/net/xen-netback/common.h | 1 + drivers/net/xen-netback/rx.c | 77 ++++++++----- drivers/net/xen-netfront.c | 125 ++++++++++++++++----- drivers/pci/msi.c | 15 ++- drivers/scsi/scsi_debug.c | 42 ++++--- drivers/soc/imx/soc-imx.c | 4 + drivers/soc/tegra/fuse/fuse-tegra.c | 2 +- drivers/soc/tegra/fuse/fuse.h | 2 +- drivers/tee/amdtee/core.c | 5 +- drivers/tty/hvc/hvc_xen.c | 30 ++++- drivers/tty/n_hdlc.c | 23 +++- drivers/tty/serial/8250/8250_fintek.c | 20 ---- drivers/usb/core/quirks.c | 3 + drivers/usb/dwc2/platform.c | 3 + drivers/usb/early/xhci-dbc.c | 15 ++- drivers/usb/gadget/composite.c | 6 +- drivers/usb/gadget/legacy/dbgp.c | 6 +- drivers/usb/gadget/legacy/inode.c | 6 +- drivers/usb/host/xhci-pci.c | 6 +- drivers/usb/serial/cp210x.c | 6 +- drivers/usb/serial/option.c | 8 ++ drivers/vhost/vdpa.c | 2 +- drivers/virtio/virtio_ring.c | 2 +- fs/btrfs/disk-io.c | 8 ++ fs/btrfs/tree-log.c | 1 + fs/ceph/caps.c | 16 +-- fs/ceph/mds_client.c | 3 +- fs/fuse/dir.c | 2 +- fs/overlayfs/dir.c | 3 +- fs/overlayfs/overlayfs.h | 1 + fs/overlayfs/super.c | 12 +- fs/zonefs/super.c | 1 + kernel/audit.c | 21 ++-- kernel/bpf/verifier.c | 28 +++-- kernel/rcu/tree.c | 10 +- kernel/time/timekeeping.c | 3 +- net/core/skbuff.c | 2 +- net/ipv4/inet_diag.c | 4 +- net/ipv6/sit.c | 1 - net/mac80211/agg-rx.c | 5 +- net/mac80211/agg-tx.c | 16 ++- net/mac80211/driver-ops.h | 5 +- net/mac80211/mlme.c | 13 ++- net/mac80211/sta_info.h | 1 + net/mac80211/util.c | 7 +- net/mptcp/protocol.c | 4 +- net/packet/af_packet.c | 5 +- net/rds/connection.c | 1 + net/sched/cls_api.c | 1 + net/sched/sch_cake.c | 6 +- net/sched/sch_ets.c | 4 +- net/smc/af_smc.c | 4 +- net/vmw_vsock/virtio_transport_common.c | 3 +- scripts/recordmcount.pl | 2 +- .../selftests/bpf/prog_tests/btf_skc_cls_ingress.c | 16 ++- .../selftests/bpf/verifier/value_ptr_arith.c | 23 ++++ tools/testing/selftests/kvm/kvm_create_max_vcpus.c | 30 +++++ tools/testing/selftests/net/fcnal-test.sh | 49 +++++--- .../net/forwarding/forwarding.config.sample | 2 + virt/kvm/kvm_main.c | 6 +- 105 files changed, 697 insertions(+), 305 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/99 KVM: selftests: Make sure kvm_create_max_vcpus test wont hit RLIMIT_NOFILE
From: Vitaly Kuznetsov <[email protected]>
[ Upstream commit 908fa88e420f30dde6d80f092795a18ec72ca6d3 ]
With the elevated 'KVM_CAP_MAX_VCPUS' value kvm_create_max_vcpus test may hit RLIMIT_NOFILE limits:
# ./kvm_create_max_vcpus KVM_CAP_MAX_VCPU_ID: 4096 KVM_CAP_MAX_VCPUS: 1024 Testing creating 1024 vCPUs, with IDs 0...1023. /dev/kvm not available (errno: 24), skipping test
Adjust RLIMIT_NOFILE limits to make sure KVM_CAP_MAX_VCPUS fds can be opened. Note, raising hard limit ('rlim_max') requires CAP_SYS_RESOURCE capability which is generally not needed to run kvm selftests (but without raising the limit the test is doomed to fail anyway).
Message-Id: <[email protected]>
--- .../selftests/kvm/kvm_create_max_vcpus.c | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+)
tools/testing/selftests/kvm/kvm_create_max_vcpus.c +30 -0
@@ -12,6 +12,7 @@#include <stdio.h> #include <stdlib.h> #include <string.h> +#include <sys/resource.h> #include "test_util.h"
@@ -40,10 +41,39 @@ int main(int argc, char *argv[]) {int kvm_max_vcpu_id =kvm_check_cap (KVM_CAP_MAX_VCPU_ID );int kvm_max_vcpus =kvm_check_cap (KVM_CAP_MAX_VCPUS ); +/* +* Number of file descriptors reqired, KVM_CAP_MAX_VCPUS for vCPU fds + +* an arbitrary number for everything else. +*/ +int nr_fds_wanted = kvm_max_vcpus +100 ; +struct rlimit rl;pr_info ("KVM_CAP_MAX_VCPU_ID: %d\n" , kvm_max_vcpu_id);pr_info ("KVM_CAP_MAX_VCPUS: %d\n" , kvm_max_vcpus); +/* +* Check that we're allowed to open nr_fds_wanted file descriptors and +* try raising the limits if needed. +*/ +TEST_ASSERT (!getrlimit (RLIMIT_NOFILE , &rl),"getrlimit() failed!" ); + +if (rl.rlim_cur < nr_fds_wanted) { + rl.rlim_cur = nr_fds_wanted; +if (rl.rlim_max < nr_fds_wanted) { +int old_rlim_max = rl.rlim_max; + rl.rlim_max = nr_fds_wanted; + +int r =setrlimit (RLIMIT_NOFILE , &rl); +if (r <0 ) { +printf ("RLIMIT_NOFILE hard limit is too low (%d, wanted %d)\n" , + old_rlim_max, nr_fds_wanted); +exit (KSFT_SKIP ); + } + }else { +TEST_ASSERT (!setrlimit (RLIMIT_NOFILE , &rl),"setrlimit() failed!" ); + } + } +/* * Upstream KVM prior to 4.8 does not support KVM_CAP_MAX_VCPU_ID. * Userspace is supposed to use KVM_CAP_MAX_VCPUS as the maximum ID
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 2/99 KVM: downgrade two BUG_ONs to WARN_ON_ONCE
In reply to Greg Kroah-HartmanFrom: Paolo Bonzini <[email protected]>
[ Upstream commit 5f25e71e311478f9bb0a8ef49e7d8b95316491d7 ]
This is not an unrecoverable situation. Users of kvm_read_guest_offset_cached and kvm_write_guest_offset_cached must expect the read/write to fail, and therefore it is possible to just return early with an error value.
--- virt/kvm/kvm_main.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
virt/kvm/kvm_main.c +4 -2
@@ -2590,7 +2590,8 @@ int kvm_write_guest_offset_cached(struct kvm *kvm, struct gfn_to_hva_cache *ghc,int r;gpa_t gpa = ghc->gpa + offset; -BUG_ON (len + offset > ghc->len); +if (WARN_ON_ONCE (len + offset > ghc->len)) +return -EINVAL ;if (slots->generation != ghc->generation) {if (__kvm_gfn_to_hva_cache_init (slots, ghc, ghc->gpa, ghc->len))
@@ -2627,7 +2628,8 @@ int kvm_read_guest_offset_cached(struct kvm *kvm, struct gfn_to_hva_cache *ghc,int r;gpa_t gpa = ghc->gpa + offset; -BUG_ON (len + offset > ghc->len); +if (WARN_ON_ONCE (len + offset > ghc->len)) +return -EINVAL ;if (slots->generation != ghc->generation) {if (__kvm_gfn_to_hva_cache_init (slots, ghc, ghc->gpa, ghc->len))
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 3/99 mac80211: fix regression in SSN handling of addba tx
In reply to Greg Kroah-HartmanFrom: Felix Fietkau <[email protected]>
commit 73111efacd3c6d9e644acca1d132566932be8af0 upstream.
Some drivers that do their own sequence number allocation (e.g. ath9k) rely on being able to modify params->ssn on starting tx ampdu sessions. This was broken by a change that modified it to use sta->tid_seq[tid] instead.
--- net/mac80211/agg-tx.c | 4 ++-- net/mac80211/sta_info.h | 1 + 2 files changed, 3 insertions(+), 2 deletions(-)
net/mac80211/agg-tx.c +2 -2
@@ -480,8 +480,7 @@ static void ieee80211_send_addba_with_ti/* send AddBA request */ ieee80211_send_addba_request (sdata, sta->sta.addr, tid, - tid_tx->dialog_token, - sta->tid_seq[tid] >>4 , + tid_tx->dialog_token, tid_tx->ssn, buf_size, tid_tx->timeout);WARN_ON (test_and_set_bit (HT_AGG_STATE_SENT_ADDBA , &tid_tx->state));
@@ -523,6 +522,7 @@ void ieee80211_tx_ba_session_handle_star params.ssn = sta->tid_seq[tid] >>4 ; ret =drv_ampdu_action (local, sdata, ¶ms); + tid_tx->ssn = params.ssn;if (ret ==IEEE80211_AMPDU_TX_START_DELAY_ADDBA ) {return ; }else if (ret ==IEEE80211_AMPDU_TX_START_IMMEDIATE ) {
net/mac80211/sta_info.h +1 -0
@@ -190,6 +190,7 @@ struct tid_ampdu_tx {u8 stop_initiator;bool tx_stop;u16 buf_size; +u16 ssn;u16 failed_bar_ssn;bool bar_pending;
Greg Kroah-Hartman
maintainerPATCH 4/99 mac80211: mark TX-during-stop for TX in in_reconfig
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
commit db7205af049d230e7e0abf61c1e74c1aab40f390 upstream.
Mark TXQs as having seen transmit while they were stopped if we bail out of drv_wake_tx_queue() due to reconfig, so that the queue wake after this will make them catch up. This is particularly necessary for when TXQs are used for management packets since those TXQs won't see a lot of traffic that'd make them catch up later.
--- net/mac80211/driver-ops.h | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
net/mac80211/driver-ops.h +4 -1
@@ -1201,8 +1201,11 @@ static inline void drv_wake_tx_queue(str {struct ieee80211_sub_if_data *sdata =vif_to_sdata (txq->txq.vif); -if (local->in_reconfig) +/* In reconfig don't transmit now, but mark for waking later */ +if (local->in_reconfig) { +set_bit (IEEE80211_TXQ_STOP_NETIF_TX , &txq->flags);return ; + }if (!check_sdata_in_driver (sdata))return ;
Greg Kroah-Hartman
maintainerPATCH 5/99 mac80211: send ADDBA requests using the tid/queue of the aggregation session
In reply to Greg Kroah-HartmanFrom: Felix Fietkau <[email protected]>
commit 1fe98f5690c4219d419ea9cc190f94b3401cf324 upstream.
Sending them out on a different queue can cause a race condition where a number of packets in the queue may be discarded by the receiver, because the ADDBA request is sent too early.
This affects any driver with software A-MPDU setup which does not allocate packet seqno in hardware on tx, regardless of whether iTXQ is used or not. The only driver I've seen that explicitly deals with this issue internally is mwl8k.
--- net/mac80211/agg-tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/mac80211/agg-tx.c +1 -1
@@ -106,7 +106,7 @@ static void ieee80211_send_addba_request mgmt->u.action.u.addba_req.start_seq_num =cpu_to_le16 (start_seq_num <<4 ); -ieee80211_tx_skb (sdata, skb); +ieee80211_tx_skb_tid (sdata, skb, tid); }void ieee80211_send_bar (struct ieee80211_vif *vif,u8 *ra,u16 tid,u16 ssn)
Greg Kroah-Hartman
maintainerPATCH 6/99 mac80211: validate extended element ID is present
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
commit 768c0b19b50665e337c96858aa2b7928d6dcf756 upstream.
Before attempting to parse an extended element, verify that the extended element ID is present.
--- net/mac80211/util.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
net/mac80211/util.c +6 -1
@@ -950,7 +950,12 @@ static void ieee80211_parse_extension_el struct ieee802_11_elems *elems) {const void *data = elem->data +1 ; -u8 len = elem->datalen -1 ; +u8 len; + +if (!elem->datalen) +return ; + + len = elem->datalen -1 ;switch (elem->data[0 ]) {case WLAN_EID_EXT_HE_MU_EDCA :
Greg Kroah-Hartman
maintainerPATCH 7/99 firmware: arm_scpi: Fix string overflow in SCPI genpd driver
In reply to Greg Kroah-HartmanFrom: Sudeep Holla <[email protected]>
commit 865ed67ab955428b9aa771d8b4f1e4fb7fd08945 upstream.
Without the bound checks for scpi_pd->name, it could result in the buffer overflow when copying the SCPI device name from the corresponding device tree node as the name string is set at maximum size of 30.
Let us fix it by using devm_kasprintf so that the string buffer is allocated dynamically.
--- drivers/firmware/scpi_pm_domain.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
drivers/firmware/scpi_pm_domain.c +7 -3
@@ -16,7 +16,6 @@ struct scpi_pm_domain {struct generic_pm_domain genpd;struct scpi_ops *ops;u32 domain; -char name[30 ]; };/*
@@ -110,8 +109,13 @@ static int scpi_pm_domain_probe(struct p scpi_pd->domain = i; scpi_pd->ops = scpi_ops; -sprintf (scpi_pd->name,"%pOFn.%d" , np, i); - scpi_pd->genpd.name = scpi_pd->name; + scpi_pd->genpd.name =devm_kasprintf (dev,GFP_KERNEL , +"%pOFn.%d" , np, i); +if (!scpi_pd->genpd.name) { +dev_err (dev,"Failed to allocate genpd name:%pOFn.%d\n" , + np, i); +continue ; + } scpi_pd->genpd.power_off = scpi_pd_power_off; scpi_pd->genpd.power_on = scpi_pd_power_on;
Greg Kroah-Hartman
maintainerPATCH 8/99 bpf: Fix signed bounds propagation after mov32
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit 3cf2b61eb06765e27fec6799292d9fb46d0b7e60 upstream.
For the case where both s32_{min,max}_value bounds are positive, the __reg_assign_32_into_64() directly propagates them to their 64 bit counterparts, otherwise it pessimises them into [0,u32_max] universe and tries to refine them later on by learning through the tnum as per comment in mentioned function. However, that does not always happen, for example, in mov32 operation we call zext_32_to_64(dst_reg) which invokes the __reg_assign_32_into_64() as is without subsequent bounds update as elsewhere thus no refinement based on tnum takes place.
Thus, not calling into the __update_reg_bounds() / __reg_deduce_bounds() / __reg_bound_offset() triplet as we do, for example, in case of ALU ops via adjust_scalar_min_max_vals(), will lead to more pessimistic bounds when dumping the full register state:
Before fix:
0: (b4) w0 = -1
1: R0_w=invP4294967295
(id=0,imm=ffffffff,
smin_value=4294967295,smax_value=4294967295,
umin_value=4294967295,umax_value=4294967295,
var_off=(0xffffffff; 0x0),
s32_min_value=-1,s32_max_value=-1,
u32_min_value=-1,u32_max_value=-1) 1: (bc) w0 = w0
2: R0_w=invP4294967295
(id=0,imm=ffffffff,
smin_value=0,smax_value=4294967295,
umin_value=4294967295,umax_value=4294967295,
var_off=(0xffffffff; 0x0),
s32_min_value=-1,s32_max_value=-1,
u32_min_value=-1,u32_max_value=-1)Technically, the smin_value=0 and smax_value=4294967295 bounds are not incorrect, but given the register is still a constant, they break assumptions about const scalars that smin_value == smax_value and umin_value == umax_value.
After fix:
0: (b4) w0 = -1
1: R0_w=invP4294967295
(id=0,imm=ffffffff,
smin_value=4294967295,smax_value=4294967295,
umin_value=4294967295,umax_value=4294967295,
var_off=(0xffffffff; 0x0),
s32_min_value=-1,s32_max_value=-1,
u32_min_value=-1,u32_max_value=-1) 1: (bc) w0 = w0
2: R0_w=invP4294967295
(id=0,imm=ffffffff,
smin_value=4294967295,smax_value=4294967295,
umin_value=4294967295,umax_value=4294967295,
var_off=(0xffffffff; 0x0),
s32_min_value=-1,s32_max_value=-1,
u32_min_value=-1,u32_max_value=-1)Without the smin_value == smax_value and umin_value == umax_value invariant being intact for const scalars, it is possible to leak out kernel pointers from unprivileged user space if the latter is enabled. For example, when such registers are involved in pointer arithmtics, then adjust_ptr_min_max_vals() will taint the destination register into an unknown scalar, and the latter can be exported and stored e.g. into a BPF map value.
--- kernel/bpf/verifier.c | 4 ++++ 1 file changed, 4 insertions(+)
kernel/bpf/verifier.c +4 -0
@@ -7125,6 +7125,10 @@ static int check_alu_op(struct bpf_verif insn->dst_reg); }zext_32_to_64 (dst_reg); + +__update_reg_bounds (dst_reg); +__reg_deduce_bounds (dst_reg); +__reg_bound_offset (dst_reg); } }else {/* case: R = imm
Greg Kroah-Hartman
maintainerPATCH 9/99 bpf: Make 32->64 bounds propagation slightly more robust
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit e572ff80f05c33cd0cb4860f864f5c9c044280b6 upstream.
Make the bounds propagation in __reg_assign_32_into_64() slightly more robust and readable by aligning it similarly as we did back in the __reg_combine_64_into_32() counterpart. Meaning, only propagate or pessimize them as a smin/smax pair.
--- kernel/bpf/verifier.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-)
kernel/bpf/verifier.c +15 -9
@@ -1249,22 +1249,28 @@ static void __reg_bound_offset(struct bp reg->var_off =tnum_or (tnum_clear_subreg (var64_off), var32_off); } +static bool __reg32_bound_s64 (s32 a) +{ +return a >=0 && a <=S32_MAX ; +} +static void __reg_assign_32_into_64 (struct bpf_reg_state *reg) { reg->umin_value = reg->u32_min_value; reg->umax_value = reg->u32_max_value; -/* Attempt to pull 32-bit signed bounds into 64-bit bounds -* but must be positive otherwise set to worse case bounds -* and refine later from tnum. + +/* Attempt to pull 32-bit signed bounds into 64-bit bounds but must +* be positive otherwise set to worse case bounds and refine later +* from tnum. */ -if (reg->s32_min_value >=0 && reg->s32_max_value >=0 ) - reg->smax_value = reg->s32_max_value; -else - reg->smax_value =U32_MAX ; -if (reg->s32_min_value >=0 ) +if (__reg32_bound_s64 (reg->s32_min_value) && +__reg32_bound_s64 (reg->s32_max_value)) { reg->smin_value = reg->s32_min_value; -else + reg->smax_value = reg->s32_max_value; + }else { reg->smin_value =0 ; + reg->smax_value =U32_MAX ; + } }static void __reg_combine_32_into_64 (struct bpf_reg_state *reg)
Greg Kroah-Hartman
maintainerPATCH 10/99 bpf, selftests: Add test case trying to taint map value pointer
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit b1a7288dedc6caf9023f2676b4f5ed34cf0d4029 upstream.
Add a test case which tries to taint map value pointer arithmetic into a unknown scalar with subsequent export through the map.
Before fix:
# ./test_verifier 1186 #1186/u map access: trying to leak tained dst reg FAIL Unexpected success to load! verification time 24 usec stack depth 8 processed 15 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 #1186/p map access: trying to leak tained dst reg FAIL Unexpected success to load! verification time 8 usec stack depth 8 processed 15 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1 Summary: 0 PASSED, 0 SKIPPED, 2 FAILED
After fix:
# ./test_verifier 1186 #1186/u map access: trying to leak tained dst reg OK #1186/p map access: trying to leak tained dst reg OK Summary: 2 PASSED, 0 SKIPPED, 0 FAILED
--- tools/testing/selftests/bpf/verifier/value_ptr_arith.c | 23 +++++++++++++++++ 1 file changed, 23 insertions(+)
tools/testing/selftests/bpf/verifier/value_ptr_arith.c +23 -0
@@ -849,6 +849,29 @@ .errstr_unpriv = "R0 pointer -= pointer prohibited", }, { + "map access: trying to leak tained dst reg", + .insns = { +BPF_MOV64_IMM (BPF_REG_0 ,0 ), +BPF_ST_MEM (BPF_DW ,BPF_REG_10 ,-8 ,0 ), +BPF_MOV64_REG (BPF_REG_2 ,BPF_REG_10 ), +BPF_ALU64_IMM (BPF_ADD ,BPF_REG_2 ,-8 ), +BPF_LD_MAP_FD (BPF_REG_1 ,0 ), +BPF_RAW_INSN (BPF_JMP |BPF_CALL ,0 ,0 ,0 , BPF_FUNC_map_lookup_elem), +BPF_JMP_IMM (BPF_JNE ,BPF_REG_0 ,0 ,1 ), +BPF_EXIT_INSN (), +BPF_MOV64_REG (BPF_REG_2 ,BPF_REG_0 ), +BPF_MOV32_IMM (BPF_REG_1 ,0xFFFFFFFF ), +BPF_MOV32_REG (BPF_REG_1 ,BPF_REG_1 ), +BPF_ALU64_REG (BPF_SUB ,BPF_REG_2 ,BPF_REG_1 ), +BPF_STX_MEM (BPF_DW ,BPF_REG_0 ,BPF_REG_2 ,0 ), +BPF_MOV64_IMM (BPF_REG_0 ,0 ), + BPF_EXIT_INSN(), + }, + .fixup_map_array_48b = { 4 }, + .result = REJECT, + .errstr = "math between map_value pointer and 4294967295 is not allowed", +}, +{"32bit pkt_ptr -= scalar" , .insns = { BPF_LDX_MEM(BPF_W, BPF_REG_8, BPF_REG_1,
Greg Kroah-Hartman
maintainerPATCH 11/99 virtio_ring: Fix querying of maximum DMA mapping size for virtio device
In reply to Greg Kroah-HartmanFrom: Will Deacon <[email protected]>
commit 817fc978b5a29b039db0418a91072b31c9aab152 upstream.
virtio_max_dma_size() returns the maximum DMA mapping size of the virtio device by querying dma_max_mapping_size() for the device when the DMA API is in use for the vring. Unfortunately, the device passed is initialised by register_virtio_device() and does not inherit the DMA configuration from its parent, resulting in SWIOTLB errors when bouncing is enabled and the default 256K mapping limit (IO_TLB_SEGSIZE) is not respected:
| virtio-pci 0000:00:01.0: swiotlb buffer is full (sz: 294912 bytes), total 1024 (slots), used 725 (slots)
Follow the pattern used elsewhere in the virtio_ring code when calling into the DMA layer and pass the parent device to dma_max_mapping_size() instead.
--- drivers/virtio/virtio_ring.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/virtio/virtio_ring.c +1 -1
@@ -263,7 +263,7 @@ size_t virtio_max_dma_size(struct virtiosize_t max_segment_size =SIZE_MAX ;if (vring_use_dma_api (vdev)) - max_segment_size =dma_max_mapping_size (&vdev->dev); + max_segment_size =dma_max_mapping_size (vdev->dev.parent);return max_segment_size; }
Greg Kroah-Hartman
maintainerPATCH 12/99 vdpa: check that offsets are within bounds
In reply to Greg Kroah-HartmanFrom: Dan Carpenter <[email protected]>
commit 3ed21c1451a14d139e1ceb18f2fa70865ce3195a upstream.
In this function "c->off" is a u32 and "size" is a long. On 64bit systems if "c->off" is greater than "size" then "size - c->off" is a negative and we always return -E2BIG. But on 32bit systems the subtraction is type promoted to a high positive u32 value and basically any "c->len" is accepted.
--- drivers/vhost/vdpa.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/vhost/vdpa.c +1 -1
@@ -196,7 +196,7 @@ static int vhost_vdpa_config_validate(stbreak ; } -if (c->len ==0 ) +if (c->len ==0 || c->off > size)return -EINVAL ;if (c->len > size - c->off)
Greg Kroah-Hartman
maintainerPATCH 13/99 recordmcount.pl: look for jgnop instruction as well as bcrl on s390
In reply to Greg Kroah-HartmanFrom: Jerome Marchand <[email protected]>
commit 85bf17b28f97ca2749968d8786dc423db320d9c2 upstream.
On s390, recordmcount.pl is looking for "bcrl 0,<xxx>" instructions in the objdump -d outpout. However since binutils 2.37, objdump -d display "jgnop <xxx>" for the same instruction. Update the mcount_regex so that it accepts both.
--- scripts/recordmcount.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
scripts/recordmcount.pl +1 -1
@@ -252,7 +252,7 @@ if ($arch eq "x86_64") { } elsif ($arch eq "s390" && $bits == 64) { if ($cc =~ /-DCC_USING_HOTPATCH/) { - $mcount_regex = "^\\s*([0-9a-fA-F]+):\\s*c0 04 00 00 00 00\\s*brcl\\s*0,[0-9a-f]+ <([^\+]*)>\$"; + $mcount_regex = "^\\s*([0-9a-fA-F]+):\\s*c0 04 00 00 00 00\\s*(bcrl\\s*0,|jgnop\\s*)[0-9a-f]+ <([^\+]*)>\$"; $mcount_adjust = 0; } else { $mcount_regex = "^\\s*([0-9a-fA-F]+):\\s*R_390_(PC|PLT)32DBL\\s+_mcount\\+0x2\$";
Greg Kroah-Hartman
maintainerPATCH 14/99 dm btree remove: fix use after free in rebalance_children()
In reply to Greg Kroah-HartmanFrom: Joe Thornber <[email protected]>
commit 1b8d2789dad0005fd5e7d35dab26a8e1203fb6da upstream.
Move dm_tm_unlock() after dm_tm_dec().
--- drivers/md/persistent-data/dm-btree-remove.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/md/persistent-data/dm-btree-remove.c +1 -1
@@ -423,9 +423,9 @@ static int rebalance_children(struct shamemcpy (n,dm_block_data (child),dm_bm_block_size (dm_tm_get_bm (info->tm))); -dm_tm_unlock (info->tm, child);dm_tm_dec (info->tm,dm_block_location (child)); +dm_tm_unlock (info->tm, child);return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 15/99 audit: improve robustness of the audit queue handling
In reply to Greg Kroah-HartmanFrom: Paul Moore <[email protected]>
commit f4b3ee3c85551d2d343a3ba159304066523f730f upstream.
If the audit daemon were ever to get stuck in a stopped state the kernel's kauditd_thread() could get blocked attempting to send audit records to the userspace audit daemon. With the kernel thread blocked it is possible that the audit queue could grow unbounded as certain audit record generating events must be exempt from the queue limits else the system enter a deadlock state.
This patch resolves this problem by lowering the kernel thread's socket sending timeout from MAX_SCHEDULE_TIMEOUT to HZ/10 and tweaks the kauditd_send_queue() function to better manage the various audit queues when connection problems occur between the kernel and the audit daemon. With this patch, the backlog may temporarily grow beyond the defined limits when the audit daemon is stopped and the system is under heavy audit pressure, but kauditd_thread() will continue to make progress and drain the queues as it would for other connection problems. For example, with the audit daemon put into a stopped state and the system configured to audit every syscall it was still possible to shutdown the system without a kernel panic, deadlock, etc.; granted, the system was slow to shutdown but that is to be expected given the extreme pressure of recording every syscall.
The timeout value of HZ/10 was chosen primarily through experimentation and this developer's "gut feeling". There is likely no one perfect value, but as this scenario is limited in scope (root privileges would be needed to send SIGSTOP to the audit daemon), it is likely not worth exposing this as a tunable at present. This can always be done at a later date if it proves necessary.
--- kernel/audit.c | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-)
kernel/audit.c +10 -11
@@ -718,7 +718,7 @@ static int kauditd_send_queue(struct soc {int rc =0 ;struct sk_buff *skb; -static unsigned int failed =0 ; +unsigned int failed =0 ;/* NOTE: kauditd_thread takes care of all our locking, we just use * the netlink info passed to us (e.g. sk and portid) */
@@ -735,32 +735,30 @@ static int kauditd_send_queue(struct soccontinue ; } +retry:/* grab an extra skb reference in case of error */ skb_get (skb); rc =netlink_unicast (sk, skb, portid,0 );if (rc <0 ) { -/* fatal failure for our queue flush attempt? */ +/* send failed - try a few times unless fatal error */ if (++failed >= retry_limit || rc == -ECONNREFUSED || rc == -EPERM ) { -/* yes - error processing for the queue */ sk =NULL ;if (err_hook) (*err_hook)(skb); -if (!skb_hook) - goto out; -/* keep processing with the skb_hook */ +if (rc == -EAGAIN ) + rc =0 ; +/* continue to drain the queue */ continue ; }else -/* no - requeue to preserve ordering */ -skb_queue_head (queue, skb); + goto retry; }else { -/* it worked - drop the extra reference and continue */ +/* skb sent - drop the extra reference and continue */ consume_skb (skb); failed =0 ; } } -out:return (rc >=0 ?0 : rc); }
@@ -1609,7 +1607,8 @@ static int __net_init audit_net_init(straudit_panic ("cannot initialize netlink socket in namespace" );return -ENOMEM ; } - aunet->sk->sk_sndtimeo =MAX_SCHEDULE_TIMEOUT ; +/* limit the timeout in case auditd is blocked/stopped */ + aunet->sk->sk_sndtimeo =HZ /10 ;return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 16/99 arm64: dts: imx8m: correct assigned clocks for FEC
In reply to Greg Kroah-HartmanFrom: Joakim Zhang <[email protected]>
commit 70eacf42a93aff6589a8b91279bbfe5f73c4ca3d upstream.
CLK_ENET_TIMER assigned clocks twice, should be a typo, correct to CLK_ENET_PHY_REF clock.
--- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 7 ++++--- arch/arm64/boot/dts/freescale/imx8mn.dtsi | 7 ++++--- arch/arm64/boot/dts/freescale/imx8mp.dtsi | 7 ++++--- 3 files changed, 12 insertions(+), 9 deletions(-)
arch/arm64/boot/dts/freescale/imx8mm.dtsi +4 -3
@@ -866,11 +866,12 @@ assigned-clocks = <&clk IMX8MM_CLK_ENET_AXI>, <&clk IMX8MM_CLK_ENET_TIMER>, <&clk IMX8MM_CLK_ENET_REF>, - <&clk IMX8MM_CLK_ENET_TIMER>; + <&clk IMX8MM_CLK_ENET_PHY_REF>; assigned-clock-parents = <&clk IMX8MM_SYS_PLL1_266M>, <&clk IMX8MM_SYS_PLL2_100M>, - <&clk IMX8MM_SYS_PLL2_125M>; - assigned-clock-rates = <0>, <0>, <125000000>, <100000000>; + <&clk IMX8MM_SYS_PLL2_125M>, + <&clk IMX8MM_SYS_PLL2_50M>; + assigned-clock-rates = <0>, <100000000>, <125000000>, <0>; fsl,num-tx-queues = <3>; fsl,num-rx-queues = <3>; status = "disabled";
arch/arm64/boot/dts/freescale/imx8mn.dtsi +4 -3
@@ -753,11 +753,12 @@ assigned-clocks = <&clk IMX8MN_CLK_ENET_AXI>, <&clk IMX8MN_CLK_ENET_TIMER>, <&clk IMX8MN_CLK_ENET_REF>, - <&clk IMX8MN_CLK_ENET_TIMER>; + <&clk IMX8MN_CLK_ENET_PHY_REF>; assigned-clock-parents = <&clk IMX8MN_SYS_PLL1_266M>, <&clk IMX8MN_SYS_PLL2_100M>, - <&clk IMX8MN_SYS_PLL2_125M>; - assigned-clock-rates = <0>, <0>, <125000000>, <100000000>; + <&clk IMX8MN_SYS_PLL2_125M>, + <&clk IMX8MN_SYS_PLL2_50M>; + assigned-clock-rates = <0>, <100000000>, <125000000>, <0>; fsl,num-tx-queues = <3>; fsl,num-rx-queues = <3>; status = "disabled";
arch/arm64/boot/dts/freescale/imx8mp.dtsi +4 -3
@@ -725,11 +725,12 @@ assigned-clocks = <&clk IMX8MP_CLK_ENET_AXI>, <&clk IMX8MP_CLK_ENET_TIMER>, <&clk IMX8MP_CLK_ENET_REF>, - <&clk IMX8MP_CLK_ENET_TIMER>; + <&clk IMX8MP_CLK_ENET_PHY_REF>; assigned-clock-parents = <&clk IMX8MP_SYS_PLL1_266M>, <&clk IMX8MP_SYS_PLL2_100M>, - <&clk IMX8MP_SYS_PLL2_125M>; - assigned-clock-rates = <0>, <0>, <125000000>, <100000000>; + <&clk IMX8MP_SYS_PLL2_125M>, + <&clk IMX8MP_SYS_PLL2_50M>; + assigned-clock-rates = <0>, <100000000>, <125000000>, <0>; fsl,num-tx-queues = <3>; fsl,num-rx-queues = <3>; status = "disabled";
Greg Kroah-Hartman
maintainerPATCH 17/99 arm64: dts: imx8mp-evk: Improve the Ethernet PHY description
In reply to Greg Kroah-HartmanFrom: Fabio Estevam <[email protected]>
commit 798a1807ab13a38e21c6fecd8d22a513d6786e2d upstream.
According to the datasheet RTL8211, it must be asserted low for at least 10ms and at least 72ms "for internal circuits settling time" before accessing the PHY registers.
Add properties to describe such requirements.
--- arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 2 ++ 1 file changed, 2 insertions(+)
arch/arm64/boot/dts/freescale/imx8mp-evk.dts +2 -0
@@ -62,6 +62,8 @@ reg = <1>; eee-broken-1000t; reset-gpios = <&gpio4 2 GPIO_ACTIVE_LOW>; + reset-assert-us = <10000>; + reset-deassert-us = <80000>; }; }; };
Greg Kroah-Hartman
maintainerPATCH 18/99 arm64: dts: rockchip: remove mmc-hs400-enhanced-strobe from rk3399-khadas-edge
In reply to Greg Kroah-HartmanFrom: Artem Lapkin <[email protected]>
[ Upstream commit 6dd0053683804427529ef3523f7872f473440a19 ]
Remove mmc-hs400-enhanced-strobe from the rk3399-khadas-edge dts to improve compatibility with a wider range of eMMC chips.
Before (BJTD4R 29.1 GiB):
[ 7.001493] mmc2: CQHCI version 5.10 [ 7.027971] mmc2: SDHCI controller on fe330000.mmc [fe330000.mmc] using ADMA ....... [ 7.207086] mmc2: mmc_select_hs400es failed, error -110 [ 7.207129] mmc2: error -110 whilst initialising MMC card [ 7.308893] mmc2: mmc_select_hs400es failed, error -110 [ 7.308921] mmc2: error -110 whilst initialising MMC card [ 7.427524] mmc2: mmc_select_hs400es failed, error -110 [ 7.427546] mmc2: error -110 whilst initialising MMC card [ 7.590993] mmc2: mmc_select_hs400es failed, error -110 [ 7.591012] mmc2: error -110 whilst initialising MMC card
After:
[ 6.960785] mmc2: CQHCI version 5.10 [ 6.984672] mmc2: SDHCI controller on fe330000.mmc [fe330000.mmc] using ADMA [ 7.175021] mmc2: Command Queue Engine enabled [ 7.175053] mmc2: new HS400 MMC card at address 0001 [ 7.175808] mmcblk2: mmc2:0001 BJTD4R 29.1 GiB [ 7.176033] mmcblk2boot0: mmc2:0001 BJTD4R 4.00 MiB [ 7.176245] mmcblk2boot1: mmc2:0001 BJTD4R 4.00 MiB [ 7.176495] mmcblk2rpmb: mmc2:0001 BJTD4R 4.00 MiB, chardev (242:0)
--- arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi | 1 - 1 file changed, 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3399-khadas-edge.dtsi +0 -1
@@ -699,7 +699,6 @@ &sdmmc { &sdhci { bus-width = <8>; mmc-hs400-1_8v; - mmc-hs400-enhanced-strobe; non-removable; status = "okay"; };
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 19/99 arm64: dts: rockchip: fix rk3308-roc-cc vcc-sd supply
In reply to Greg Kroah-HartmanFrom: John Keeping <[email protected]>
[ Upstream commit 772fb46109f635dd75db20c86b7eaf48efa46cef ]
Correct a typo in the vin-supply property. The input supply is always-on, so this mistake doesn't affect whether the supply is actually enabled correctly.
--- arch/arm64/boot/dts/rockchip/rk3308-roc-cc.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3308-roc-cc.dts +1 -1
@@ -91,7 +91,7 @@ vcc_sd: vcc-sd { regulator-max-microvolt = <3300000>; regulator-always-on; regulator-boot-on; - vim-supply = <&vcc_io>; + vin-supply = <&vcc_io>; }; vdd_core: vdd-core {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 20/99 arm64: dts: rockchip: fix rk3399-leez-p710 vcc3v3-lan supply
In reply to Greg Kroah-HartmanFrom: John Keeping <[email protected]>
[ Upstream commit 2b454a90e2ccdd6e03f88f930036da4df577be76 ]
Correct a typo in the vin-supply property. The input supply is always-on, so this mistake doesn't affect whether the supply is actually enabled correctly.
--- arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3399-leez-p710.dts +1 -1
@@ -49,7 +49,7 @@ vcc3v3_lan: vcc3v3-lan { regulator-boot-on; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; - vim-supply = <&vcc3v3_sys>; + vin-supply = <&vcc3v3_sys>; }; vcc3v3_sys: vcc3v3-sys {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 21/99 arm64: dts: rockchip: fix audio-supply for Rock Pi 4
In reply to Greg Kroah-HartmanFrom: Alex Bee <[email protected]>
[ Upstream commit 8240e87f16d17a9592c9d67857a3dcdbcb98f10d ]
As stated in the schematics [1] and [2] P5 the APIO5 domain is supplied by RK808-D Buck4, which in our case vcc1v8_codec - i.e. a 1.8 V regulator.
Currently only white noise comes from the ES8316's output, which - for whatever reason - came up only after the the correct switch from i2s0_8ch_bus to i2s0_2ch_bus for i2s0's pinctrl was done.
Fix this by setting the correct regulator for audio-supply.
[1] https://dl.radxa.com/rockpi4/docs/hw/rockpi4/rockpi4_v13_sch_20181112.pdf
[2] https://dl.radxa.com/rockpi4/docs/hw/rockpi4/rockpi_4c_v12_sch_20200620.pdf
--- arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi +1 -1
@@ -459,7 +459,7 @@ &io_domains { status = "okay"; bt656-supply = <&vcc_3v0>; - audio-supply = <&vcc_3v0>; + audio-supply = <&vcc1v8_codec>; sdmmc-supply = <&vcc_sdio>; gpio1830-supply = <&vcc_3v0>; };
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 22/99 mac80211: track only QoS data frames for admission control
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
[ Upstream commit d5e568c3a4ec2ddd23e7dc5ad5b0c64e4f22981a ]
For admission control, obviously all of that only works for QoS data frames, otherwise we cannot even access the QoS field in the header.
Syzbot reported (see below) an uninitialized value here due to a status of a non-QoS nullfunc packet, which isn't even long enough to contain the QoS header.
Fix this to only do anything for QoS data packets.
--- net/mac80211/mlme.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
net/mac80211/mlme.c +10 -3
@@ -2493,11 +2493,18 @@ static void ieee80211_sta_tx_wmm_ac_notify(struct ieee80211_sub_if_data *sdata, u16 tx_time) {struct ieee80211_if_managed *ifmgd = &sdata->u.mgd; -u16 tid =ieee80211_get_tid (hdr); -int ac =ieee80211_ac_from_tid (tid); -struct ieee80211_sta_tx_tspec *tx_tspec = &ifmgd->tx_tspec[ac]; +u16 tid; +int ac; +struct ieee80211_sta_tx_tspec *tx_tspec;unsigned long now = jiffies; +if (!ieee80211_is_data_qos (hdr->frame_control)) +return ; + + tid =ieee80211_get_tid (hdr); + ac =ieee80211_ac_from_tid (tid); + tx_tspec = &ifmgd->tx_tspec[ac]; +if (likely (!tx_tspec->admitted_time))return ;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 23/99 hv: utils: add PTP_1588_CLOCK to Kconfig to fix build
In reply to Greg Kroah-HartmanFrom: Randy Dunlap <[email protected]>
[ Upstream commit 1dc2f2b81a6a9895da59f3915760f6c0c3074492 ]
The hyperv utilities use PTP clock interfaces and should depend a a kconfig symbol such that they will be built as a loadable module or builtin so that linker errors do not happen.
Prevents these build errors:
ld: drivers/hv/hv_util.o: in function `hv_timesync_deinit':
hv_util.c:(.text+0x37d): undefined reference to `ptp_clock_unregister'
ld: drivers/hv/hv_util.o: in function `hv_timesync_init':
hv_util.c:(.text+0x738): undefined reference to `ptp_clock_register'
--- drivers/hv/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/hv/Kconfig +1 -0
@@ -17,6 +17,7 @@ config HYPERV_TIMER config HYPERV_UTILS tristate "Microsoft Hyper-V Utilities driver" depends on HYPERV && CONNECTOR && NLS + depends on PTP_1588_CLOCK_OPTIONAL help Select this option to enable the Hyper-V Utilities.
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 24/99 tee: amdtee: fix an IS_ERR() vs NULL bug
In reply to Greg Kroah-HartmanFrom: Dan Carpenter <[email protected]>
[ Upstream commit 9d7482771fac8d8e38e763263f2ca0ca12dd22c6 ]
The __get_free_pages() function does not return error pointers it returns NULL so fix this condition to avoid a NULL dereference.
--- drivers/tee/amdtee/core.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/tee/amdtee/core.c +2 -3
@@ -203,9 +203,8 @@ static int copy_ta_binary(struct tee_context *ctx, void *ptr, void **ta, *ta_size =roundup (fw->size,PAGE_SIZE ); *ta = (void *)__get_free_pages (GFP_KERNEL ,get_order (*ta_size)); -if (IS_ERR (*ta)) { -pr_err ("%s: get_free_pages failed 0x%llx\n" , __func__, - (u64)*ta); +if (!*ta) { +pr_err ("%s: get_free_pages failed\n" , __func__); rc = -ENOMEM ; goto rel_fw; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 25/99 ceph: fix duplicate increment of opened_inodes metric
In reply to Greg Kroah-HartmanFrom: Hu Weiwen <[email protected]>
[ Upstream commit 973e5245637accc4002843f6b888495a6a7762bc ]
opened_inodes is incremented twice when the same inode is opened twice with O_RDONLY and O_WRONLY respectively.
To reproduce, run this python script, then check the metrics:
import os
for _ in range(10000):
fd_r = os.open('a', os.O_RDONLY)
fd_w = os.open('a', os.O_WRONLY)
os.close(fd_r)
os.close(fd_w)--- fs/ceph/caps.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
fs/ceph/caps.c +8 -8
@@ -4359,7 +4359,7 @@ void ceph_get_fmode(struct ceph_inode_info *ci, int fmode, int count) {struct ceph_mds_client *mdsc =ceph_sb_to_mdsc (ci->vfs_inode.i_sb);int bits = (fmode <<1 ) |1 ; -bool is_opened = false; +bool already_opened = false;int i;if (count ==1 )
@@ -4367,19 +4367,19 @@ void ceph_get_fmode(struct ceph_inode_info *ci, int fmode, int count)spin_lock (&ci->i_ceph_lock);for (i =0 ; i <CEPH_FILE_MODE_BITS ; i++) { -if (bits & (1 << i)) - ci->i_nr_by_mode[i] += count; -/* -* If any of the mode ref is larger than 1, +* If any of the mode ref is larger than 0, * that means it has been already opened by * others. Just skip checking the PIN ref. */ -if (i && ci->i_nr_by_mode[i] >1 ) - is_opened = true; +if (i && ci->i_nr_by_mode[i]) + already_opened = true; + +if (bits & (1 << i)) + ci->i_nr_by_mode[i] += count; } -if (!is_opened) +if (!already_opened)percpu_counter_inc (&mdsc->metric.opened_inodes);spin_unlock (&ci->i_ceph_lock); }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 26/99 ceph: initialize pathlen variable in reconnect_caps_cb
In reply to Greg Kroah-HartmanFrom: Xiubo Li <[email protected]>
[ Upstream commit ee2a095d3b24f300a5e11944d208801e928f108c ]
The smatch static checker warned about an uninitialized symbol usage in this function, in the case where ceph_mdsc_build_path returns an error.
It turns out that that case is harmless, but it just looks sketchy. Initialize the variable at declaration time, and remove the unneeded setting of it later.
--- fs/ceph/mds_client.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
fs/ceph/mds_client.c +1 -2
@@ -3696,7 +3696,7 @@ static int reconnect_caps_cb(struct inode *inode, struct ceph_cap *cap,struct ceph_pagelist *pagelist = recon_state->pagelist;struct dentry *dentry;char *path; -int pathlen, err; +int pathlen =0 , err;u64 pathbase;u64 snap_follows;
@@ -3716,7 +3716,6 @@ static int reconnect_caps_cb(struct inode *inode, struct ceph_cap *cap, } }else { path =NULL ; - pathlen =0 ; pathbase =0 ; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 27/99 ARM: socfpga: dts: fix qspi node compatible
In reply to Greg Kroah-HartmanFrom: Dinh Nguyen <[email protected]>
[ Upstream commit cb25b11943cbcc5a34531129952870420f8be858 ]
The QSPI flash node needs to have the required "jedec,spi-nor" in the compatible string.
--- arch/arm/boot/dts/socfpga_arria10_socdk_qspi.dts | 2 +- arch/arm/boot/dts/socfpga_arria5_socdk.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_socdk.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_sockit.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_socrates.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_sodia.dts | 2 +- arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts | 4 ++-- 7 files changed, 8 insertions(+), 8 deletions(-)
arch/arm/boot/dts/socfpga_arria10_socdk_qspi.dts +1 -1
@@ -12,7 +12,7 @@ &qspi { flash0: n25q00@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q00aa"; + compatible = "micron,mt25qu02g", "jedec,spi-nor"; reg = <0>; spi-max-frequency = <100000000>;
arch/arm/boot/dts/socfpga_arria5_socdk.dts +1 -1
@@ -119,7 +119,7 @@ &qspi { flash: flash@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q256a"; + compatible = "micron,n25q256a", "jedec,spi-nor"; reg = <0>; spi-max-frequency = <100000000>;
arch/arm/boot/dts/socfpga_cyclone5_socdk.dts +1 -1
@@ -124,7 +124,7 @@ &qspi { flash0: n25q00@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q00"; + compatible = "micron,mt25qu02g", "jedec,spi-nor"; reg = <0>; /* chip select */ spi-max-frequency = <100000000>;
arch/arm/boot/dts/socfpga_cyclone5_sockit.dts +1 -1
@@ -169,7 +169,7 @@ &qspi { flash: flash@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q00"; + compatible = "micron,mt25qu02g", "jedec,spi-nor"; reg = <0>; spi-max-frequency = <100000000>;
arch/arm/boot/dts/socfpga_cyclone5_socrates.dts +1 -1
@@ -80,7 +80,7 @@ &qspi { flash: flash@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q256a"; + compatible = "micron,n25q256a", "jedec,spi-nor"; reg = <0>; spi-max-frequency = <100000000>; m25p,fast-read;
arch/arm/boot/dts/socfpga_cyclone5_sodia.dts +1 -1
@@ -116,7 +116,7 @@ &qspi { flash0: n25q512a@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q512a"; + compatible = "micron,n25q512a", "jedec,spi-nor"; reg = <0>; spi-max-frequency = <100000000>;
arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts +2 -2
@@ -224,7 +224,7 @@ &qspi { n25q128@0 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q128"; + compatible = "micron,n25q128", "jedec,spi-nor"; reg = <0>; /* chip select */ spi-max-frequency = <100000000>; m25p,fast-read;
@@ -241,7 +241,7 @@ n25q128@0 { n25q00@1 { #address-cells = <1>; #size-cells = <1>; - compatible = "n25q00"; + compatible = "micron,mt25qu02g", "jedec,spi-nor"; reg = <1>; /* chip select */ spi-max-frequency = <100000000>; m25p,fast-read;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 28/99 clk: Dont parent clks until the parent is fully registered
In reply to Greg Kroah-HartmanFrom: Mike Tipton <[email protected]>
[ Upstream commit 54baf56eaa40aa5cdcd02b3c20d593e4e1211220 ]
Before commit fc0c209c147f ("clk: Allow parents to be specified without string names") child clks couldn't find their parent until the parent clk was added to a list in __clk_core_init(). After that commit, child clks can reference their parent clks directly via a clk_hw pointer, or they can lookup that clk_hw pointer via DT if the parent clk is registered with an OF clk provider.
The common clk framework treats hw->core being non-NULL as "the clk is registered" per the logic within clk_core_fill_parent_index():
parent = entry->hw->core; /* * We have a direct reference but it isn't registered yet? * Orphan it and let clk_reparent() update the orphan status * when the parent is registered. */ if (!parent)
Therefore we need to be extra careful to not set hw->core until the clk is fully registered with the clk framework. Otherwise we can get into a situation where a child finds a parent clk and we move the child clk off the orphan list when the parent isn't actually registered, wrecking our enable accounting and breaking critical clks.
Consider the following scenario:
CPU0 CPU1
---- ----
struct clk_hw clkBad;
struct clk_hw clkA;
clkA.init.parent_hws = { &clkBad }; clk_hw_register(&clkA) clk_hw_register(&clkBad)
... __clk_register()
hw->core = core
...
__clk_register()
__clk_core_init()
clk_prepare_lock()
__clk_init_parent()
clk_core_get_parent_by_index()
clk_core_fill_parent_index()
if (entry->hw) {
parent = entry->hw->core;At this point, 'parent' points to clkBad even though clkBad hasn't been fully registered yet. Ouch! A similar problem can happen if a clk controller registers orphan clks that are referenced in the DT node of another clk controller.
Let's fix all this by only setting the hw->core pointer underneath the clk prepare lock in __clk_core_init(). This way we know that clk_core_fill_parent_index() can't see hw->core be non-NULL until the clk is fully registered.
--- drivers/clk/clk.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
drivers/clk/clk.c +12 -3
@@ -3389,6 +3389,14 @@ static int __clk_core_init(struct clk_core *core)clk_prepare_lock (); +/* +* Set hw->core after grabbing the prepare_lock to synchronize with +* callers of clk_core_fill_parent_index() where we treat hw->core +* being NULL as the clk not being registered yet. This is crucial so +* that clks aren't parented until their parent is fully registered. +*/ + core->hw->core = core; + ret =clk_pm_runtime_get (core);if (ret) goto unlock;
@@ -3557,8 +3565,10 @@ static int __clk_core_init(struct clk_core *core) out:clk_pm_runtime_put (core); unlock: -if (ret) +if (ret) {hlist_del_init (&core->child_node); + core->hw->core =NULL ; + }clk_prepare_unlock ();
@@ -3804,7 +3814,6 @@ __clk_register(struct device *dev, struct device_node *np, struct clk_hw *hw) core->num_parents = init->num_parents; core->min_rate =0 ; core->max_rate =ULONG_MAX ; - hw->core = core; ret =clk_core_populate_parent_map (core, init);if (ret)
@@ -3822,7 +3831,7 @@ __clk_register(struct device *dev, struct device_node *np, struct clk_hw *hw) goto fail_create_clk; } -clk_core_link_consumer (hw->core, hw->clk); +clk_core_link_consumer (core, hw->clk); ret =__clk_core_init (core);if (!ret)
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 29/99 soc: imx: Register SoC device only on i.MX boards
In reply to Greg Kroah-HartmanFrom: Stephan Gerhold <[email protected]>
[ Upstream commit 4ebd29f91629e69da7d57390cdc953772eee03ab ]
At the moment, using the ARM32 multi_v7_defconfig always results in two SoCs being exposed in sysfs. This is wrong, as far as I'm aware the Qualcomm DragonBoard 410c does not actually make use of a i.MX SoC. :)
qcom-db410c:/sys/devices/soc0$ grep . * family:Freescale i.MX machine:Qualcomm Technologies, Inc. APQ 8016 SBC revision:0.0 serial_number:0000000000000000 soc_id:Unknown
qcom-db410c:/sys/devices/soc1$ grep . * family:Snapdragon machine:APQ8016 ...
This happens because imx_soc_device_init() registers the soc device unconditionally, even when running on devices that do not make use of i.MX. Arnd already reported this more than a year ago and even suggested a fix similar to this commit, but for some reason it was never submitted.
Fix it by checking if the "__mxc_cpu_type" variable was actually initialized by earlier platform code. On devices without i.MX it will simply stay 0.
--- drivers/soc/imx/soc-imx.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/soc/imx/soc-imx.c +4 -0
@@ -33,6 +33,10 @@ static int __init imx_soc_device_init(void)u32 val;int ret; +/* Return early if this is running on devices with different SoCs */ +if (!__mxc_cpu_type) +return 0 ; +if (of_machine_is_compatible ("fsl,ls1021a" ))return 0 ;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 30/99 virtio/vsock: fix the transport to work with VMADDR_CID_ANY
In reply to Greg Kroah-HartmanFrom: Wei Wang <[email protected]>
[ Upstream commit 1db8f5fc2e5c66a5c51e1f6488e0ba7d45c29ae4 ]
The VMADDR_CID_ANY flag used by a socket means that the socket isn't bound to any specific CID. For example, a host vsock server may want to be bound with VMADDR_CID_ANY, so that a guest vsock client can connect to the host server with CID=VMADDR_CID_HOST (i.e. 2), and meanwhile, a host vsock client can connect to the same local server with CID=VMADDR_CID_LOCAL (i.e. 1).
The current implementation sets the destination socket's svm_cid to a fixed CID value after the first client's connection, which isn't an expected operation. For example, if the guest client first connects to the host server, the server's svm_cid gets set to VMADDR_CID_HOST, then other host clients won't be able to connect to the server anymore.
Reproduce steps:
1. Run the host server:
socat VSOCK-LISTEN:1234,fork -
2. Run a guest client to connect to the host server:
socat - VSOCK-CONNECT:2:1234
3. Run a host client to connect to the host server:
socat - VSOCK-CONNECT:1:1234
Without this patch, step 3. above fails to connect, and socat complains "socat[1720] E connect(5, AF=40 cid:1 port:1234, 16): Connection reset by peer".
With this patch, the above works well.
--- net/vmw_vsock/virtio_transport_common.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/vmw_vsock/virtio_transport_common.c +2 -1
@@ -1153,7 +1153,8 @@ void virtio_transport_recv_pkt(struct virtio_transport *t, space_available =virtio_transport_space_update (sk, pkt);/* Update CID in case it has changed after a transport reset event */ - vsk->local_addr.svm_cid = dst.svm_cid; +if (vsk->local_addr.svm_cid !=VMADDR_CID_ANY ) + vsk->local_addr.svm_cid = dst.svm_cid;if (space_available) sk->sk_write_space (sk);
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 31/99 selftests: net: Correct ping6 expected rc from 2 to 1
In reply to Greg Kroah-HartmanFrom: Jie2x Zhou <[email protected]>
[ Upstream commit 92816e2629808726af015c7f5b14adc8e4f8b147 ]
./fcnal-test.sh -v -t ipv6_ping
TEST: ping out, VRF bind - ns-B IPv6 LLA [FAIL]
TEST: ping out, VRF bind - multicast IP [FAIL]
ping6 is failing as it should.
COMMAND: ip netns exec ns-A /bin/ping6 -c1 -w1 fe80::7c4c:bcff:fe66:a63a%red strace of ping6 shows it is failing with '1',
so change the expected rc from 2 to 1.
--- tools/testing/selftests/net/fcnal-test.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/net/fcnal-test.sh +1 -1
@@ -2128,7 +2128,7 @@ ipv6_ping_vrf() log_start show_hint "Fails since VRF device does not support linklocal or multicast" run_cmd ${ping6} -c1 -w1 ${a} - log_test_addr ${a} $? 2 "ping out, VRF bind" + log_test_addr ${a} $? 1 "ping out, VRF bind" done for a in ${NSB_IP6} ${NSB_LO_IP6} ${NSB_LINKIP6}%${NSA_DEV} ${MCAST}%${NSA_DEV}
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 32/99 s390/kexec_file: fix error handling when applying relocations
In reply to Greg Kroah-HartmanFrom: Philipp Rudo <[email protected]>
[ Upstream commit 41967a37b8eedfee15b81406a9f3015be90d3980 ]
arch_kexec_apply_relocations_add currently ignores all errors returned by arch_kexec_do_relocs. This means that every unknown relocation is silently skipped causing unpredictable behavior while the relocated code runs. Fix this by checking for errors and fail kexec_file_load if an unknown relocation type is encountered.
The problem was found after gcc changed its behavior and used R_390_PLT32DBL relocations for brasl instruction and relied on ld to resolve the relocations in the final link in case direct calls are possible. As the purgatory code is only linked partially (option -r) ld didn't resolve the relocations leaving them for arch_kexec_do_relocs. But arch_kexec_do_relocs doesn't know how to handle R_390_PLT32DBL relocations so they were silently skipped. This ultimately caused an endless loop in the purgatory as the brasl instructions kept branching to itself.
--- arch/s390/kernel/machine_kexec_file.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
arch/s390/kernel/machine_kexec_file.c +6 -1
@@ -277,6 +277,7 @@ int arch_kexec_apply_relocations_add(struct purgatory_info *pi, {Elf_Rela *relas;int i, r_type; +int ret; relas = (void *)pi->ehdr + relsec->sh_offset;
@@ -311,7 +312,11 @@ int arch_kexec_apply_relocations_add(struct purgatory_info *pi, addr = section->sh_addr + relas[i].r_offset; r_type =ELF64_R_TYPE (relas[i].r_info); -arch_kexec_do_relocs (r_type, loc, val, addr); + ret =arch_kexec_do_relocs (r_type, loc, val, addr); +if (ret) { +pr_err ("Unknown rela relocation: %d\n" , r_type); +return -ENOEXEC ; + } }return 0 ; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 33/99 sch_cake: do not call cake_destroy() from cake_init()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit ab443c53916730862cec202078d36fd4008bea79 ]
qdiscs are not supposed to call their own destroy() method from init(), because core stack already does that.
syzbot was able to trigger use after free:
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock_common kernel/locking/mutex.c:586 [inline] WARNING: CPU: 0 PID: 21902 at kernel/locking/mutex.c:586 __mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740 Modules linked in: CPU: 0 PID: 21902 Comm: syz-executor189 Not tainted 5.16.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:586 [inline] RIP: 0010:__mutex_lock+0x9ec/0x12f0 kernel/locking/mutex.c:740 Code: 08 84 d2 0f 85 19 08 00 00 8b 05 97 38 4b 04 85 c0 0f 85 27 f7 ff ff 48 c7 c6 20 00 ac 89 48 c7 c7 a0 fe ab 89 e8 bf 76 ba ff <0f> 0b e9 0d f7 ff ff 48 8b 44 24 40 48 8d b8 c8 08 00 00 48 89 f8 RSP: 0018:ffffc9000627f290 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88802315d700 RSI: ffffffff815f1db8 RDI: fffff52000c4fe44 RBP: ffff88818f28e000 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815ebb5e R11: 0000000000000000 R12: 0000000000000000 R13: dffffc0000000000 R14: ffffc9000627f458 R15: 0000000093c30000 FS: 0000555556abc400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fda689c3303 CR3: 000000001cfbb000 CR4: 0000000000350ef0 Call Trace: <TASK> tcf_chain0_head_change_cb_del+0x2e/0x3d0 net/sched/cls_api.c:810 tcf_block_put_ext net/sched/cls_api.c:1381 [inline] tcf_block_put_ext net/sched/cls_api.c:1376 [inline] tcf_block_put+0xbc/0x130 net/sched/cls_api.c:1394 cake_destroy+0x3f/0x80 net/sched/sch_cake.c:2695 qdisc_create.constprop.0+0x9da/0x10f0 net/sched/sch_api.c:1293 tc_modify_qdisc+0x4c5/0x1980 net/sched/sch_api.c:1660 rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5571 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2496 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x904/0xdf0 net/netlink/af_netlink.c:1921 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:724 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2409 ___sys_sendmsg+0xf3/0x170 net/socket.c:2463 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2492 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f1bb06badb9 Code: Unable to access opcode bytes at RIP 0x7f1bb06bad8f. RSP: 002b:00007fff3012a658 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f1bb06badb9 RDX: 0000000000000000 RSI: 00000000200007c0 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000003 R10: 0000000000000003 R11: 0000000000000246 R12: 00007fff3012a688 R13: 00007fff3012a6a0 R14: 00007fff3012a6e0 R15: 00000000000013c2 </TASK>
--- net/sched/sch_cake.c | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)
net/sched/sch_cake.c +1 -5
@@ -2736,7 +2736,7 @@ static int cake_init(struct Qdisc *sch, struct nlattr *opt, q->tins =kvcalloc (CAKE_MAX_TINS ,sizeof (struct cake_tin_data ),GFP_KERNEL );if (!q->tins) - goto nomem; +return -ENOMEM ;for (i =0 ; i <CAKE_MAX_TINS ; i++) {struct cake_tin_data *b = q->tins + i;
@@ -2766,10 +2766,6 @@ static int cake_init(struct Qdisc *sch, struct nlattr *opt, q->min_netlen = ~0 ; q->min_adjlen = ~0 ;return 0 ; - -nomem: -cake_destroy (sch); -return -ENOMEM ; }static int cake_dump (struct Qdisc *sch,struct sk_buff *skb)
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 34/99 inet_diag: fix kernel-infoleak for UDP sockets
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit 71ddeac8cd1d217744a0e060ff520e147c9328d1 ]
KMSAN reported a kernel-infoleak [1], that can exploited by unpriv users.
After analysis it turned out UDP was not initializing r->idiag_expires. Other users of inet_sk_diag_fill() might make the same mistake in the future, so fix this in inet_sk_diag_fill().
[1]
BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:121 [inline] BUG: KMSAN: kernel-infoleak in copyout lib/iov_iter.c:156 [inline] BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x69d/0x25c0 lib/iov_iter.c:670 instrument_copy_to_user include/linux/instrumented.h:121 [inline] copyout lib/iov_iter.c:156 [inline] _copy_to_iter+0x69d/0x25c0 lib/iov_iter.c:670 copy_to_iter include/linux/uio.h:155 [inline] simple_copy_to_iter+0xf3/0x140 net/core/datagram.c:519 __skb_datagram_iter+0x2cb/0x1280 net/core/datagram.c:425 skb_copy_datagram_iter+0xdc/0x270 net/core/datagram.c:533 skb_copy_datagram_msg include/linux/skbuff.h:3657 [inline] netlink_recvmsg+0x660/0x1c60 net/netlink/af_netlink.c:1974 sock_recvmsg_nosec net/socket.c:944 [inline] sock_recvmsg net/socket.c:962 [inline] sock_read_iter+0x5a9/0x630 net/socket.c:1035 call_read_iter include/linux/fs.h:2156 [inline] new_sync_read fs/read_write.c:400 [inline] vfs_read+0x1631/0x1980 fs/read_write.c:481 ksys_read+0x28c/0x520 fs/read_write.c:619 __do_sys_read fs/read_write.c:629 [inline] __se_sys_read fs/read_write.c:627 [inline] __x64_sys_read+0xdb/0x120 fs/read_write.c:627 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x44/0xae
Uninit was created at:
slab_post_alloc_hook mm/slab.h:524 [inline] slab_alloc_node mm/slub.c:3251 [inline] __kmalloc_node_track_caller+0xe0c/0x1510 mm/slub.c:4974 kmalloc_reserve net/core/skbuff.c:354 [inline] __alloc_skb+0x545/0xf90 net/core/skbuff.c:426 alloc_skb include/linux/skbuff.h:1126 [inline] netlink_dump+0x3d5/0x16a0 net/netlink/af_netlink.c:2245 __netlink_dump_start+0xd1c/0xee0 net/netlink/af_netlink.c:2370 netlink_dump_start include/linux/netlink.h:254 [inline] inet_diag_handler_cmd+0x2e7/0x400 net/ipv4/inet_diag.c:1343 sock_diag_rcv_msg+0x24a/0x620 netlink_rcv_skb+0x447/0x800 net/netlink/af_netlink.c:2491 sock_diag_rcv+0x63/0x80 net/core/sock_diag.c:276 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x1095/0x1360 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x16f3/0x1870 net/netlink/af_netlink.c:1916 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg net/socket.c:724 [inline] sock_write_iter+0x594/0x690 net/socket.c:1057 do_iter_readv_writev+0xa7f/0xc70 do_iter_write+0x52c/0x1500 fs/read_write.c:851 vfs_writev fs/read_write.c:924 [inline] do_writev+0x63f/0xe30 fs/read_write.c:967 __do_sys_writev fs/read_write.c:1040 [inline] __se_sys_writev fs/read_write.c:1037 [inline] __x64_sys_writev+0xe5/0x120 fs/read_write.c:1037 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x54/0xd0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x44/0xae
Bytes 68-71 of 312 are uninitialized
Memory access of size 312 starts at ffff88812ab54000 Data copied to user address 0000000020001440
CPU: 1 PID: 6365 Comm: syz-executor801 Not tainted 5.16.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
--- net/ipv4/inet_diag.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
net/ipv4/inet_diag.c +1 -3
@@ -261,6 +261,7 @@ int inet_sk_diag_fill(struct sock *sk, struct inet_connection_sock *icsk, r->idiag_state = sk->sk_state; r->idiag_timer =0 ; r->idiag_retrans =0 ; + r->idiag_expires =0 ; if (inet_diag_msg_attrs_fill(sk, skb, r, ext, sk_user_ns(NETLINK_CB(cb->skb).sk),
@@ -314,9 +315,6 @@ int inet_sk_diag_fill(struct sock *sk, struct inet_connection_sock *icsk, r->idiag_retrans = icsk->icsk_probes_out; r->idiag_expires =jiffies_delta_to_msecs (sk->sk_timer.expires - jiffies); - }else { - r->idiag_timer =0 ; - r->idiag_expires =0 ; }if ((ext & (1 << (INET_DIAG_INFO -1 ))) && handler->idiag_info_size) {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 35/99 net: hns3: fix use-after-free bug in hclgevf_send_mbx_msg
In reply to Greg Kroah-HartmanFrom: Jie Wang <[email protected]>
[ Upstream commit 27cbf64a766e86f068ce6214f04c00ceb4db1af4 ]
Currently, the hns3_remove function firstly uninstall client instance, and then uninstall acceletion engine device. The netdevice is freed in client instance uninstall process, but acceletion engine device uninstall process still use it to trace runtime information. This causes a use after free problem.
So fixes it by check the instance register state to avoid use after free.
--- drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_mbx.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/hisilicon/hns3/hns3vf/hclgevf_mbx.c +2 -1
@@ -109,7 +109,8 @@ int hclgevf_send_mbx_msg(struct hclgevf_dev *hdev,memcpy (&req->msg, send_msg,sizeof (struct hclge_vf_to_pf_msg )); -trace_hclge_vf_mbx_send (hdev, req); +if (test_bit (HCLGEVF_STATE_NIC_REGISTERED , &hdev->state)) +trace_hclge_vf_mbx_send (hdev, req);/* synchronous send */ if (need_resp) {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 36/99 selftests: Add duplicate config only for MD5 VRF tests
In reply to Greg Kroah-HartmanFrom: David Ahern <[email protected]>
[ Upstream commit 7e0147592b5c4f9e2eb8c54a7857a56d4863f74e ]
Commit referenced below added configuration in the default VRF that duplicates a VRF to check MD5 passwords are properly used and fail when expected. That config should not be added all the time as it can cause tests to pass that should not (by matching on default VRF setup when it should not). Move the duplicate setup to a function that is only called for the MD5 tests and add a cleanup function to remove it after the MD5 tests.
--- tools/testing/selftests/net/fcnal-test.sh | 26 +++++++++++++++++------ 1 file changed, 20 insertions(+), 6 deletions(-)
tools/testing/selftests/net/fcnal-test.sh +20 -6
@@ -446,6 +446,22 @@ cleanup() ip netns del ${NSC} >/dev/null 2>&1 } +cleanup_vrf_dup() +{ + ip link del ${NSA_DEV2} >/dev/null 2>&1 + ip netns pids ${NSC} | xargs kill 2>/dev/null + ip netns del ${NSC} >/dev/null 2>&1 +} + +setup_vrf_dup() +{ + # some VRF tests use ns-C which has the same config as + # ns-B but for a device NOT in the VRF + create_ns ${NSC} "-" "-" + connect_ns ${NSA} ${NSA_DEV2} ${NSA_IP}/24 ${NSA_IP6}/64 \ + ${NSC} ${NSC_DEV} ${NSB_IP}/24 ${NSB_IP6}/64 +} + setup() { local with_vrf=${1}
@@ -475,12 +491,6 @@ setup() ip -netns ${NSB} ro add ${VRF_IP}/32 via ${NSA_IP} dev ${NSB_DEV} ip -netns ${NSB} -6 ro add ${VRF_IP6}/128 via ${NSA_IP6} dev ${NSB_DEV} - - # some VRF tests use ns-C which has the same config as - # ns-B but for a device NOT in the VRF - create_ns ${NSC} "-" "-" - connect_ns ${NSA} ${NSA_DEV2} ${NSA_IP}/24 ${NSA_IP6}/64 \ - ${NSC} ${NSC_DEV} ${NSB_IP}/24 ${NSB_IP6}/64 else ip -netns ${NSA} ro add ${NSB_LO_IP}/32 via ${NSB_IP} dev ${NSA_DEV} ip -netns ${NSA} ro add ${NSB_LO_IP6}/128 via ${NSB_IP6} dev ${NSA_DEV}
@@ -1177,7 +1187,9 @@ ipv4_tcp_vrf() log_test_addr ${a} $? 1 "Global server, local connection" # run MD5 tests + setup_vrf_dup ipv4_tcp_md5 + cleanup_vrf_dup # # enable VRF global server
@@ -2656,7 +2668,9 @@ ipv6_tcp_vrf() log_test_addr ${a} $? 1 "Global server, local connection" # run MD5 tests + setup_vrf_dup ipv6_tcp_md5 + cleanup_vrf_dup # # enable VRF global server
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 37/99 selftests: Fix raw socket bind tests with VRF
In reply to Greg Kroah-HartmanFrom: David Ahern <[email protected]>
[ Upstream commit 0f108ae4452025fef529671998f6c7f1c4526790 ]
Commit referenced below added negative socket bind tests for VRF. The socket binds should fail since the address to bind to is in a VRF yet the socket is not bound to the VRF or a device within it. Update the expected return code to check for 1 (bind failure) so the test passes when the bind fails as expected. Add a 'show_hint' comment to explain why the bind is expected to fail.
--- tools/testing/selftests/net/fcnal-test.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
tools/testing/selftests/net/fcnal-test.sh +2 -1
@@ -1747,8 +1747,9 @@ ipv4_addr_bind_vrf() for a in ${NSA_IP} ${VRF_IP} do log_start + show_hint "Socket not bound to VRF, but address is in VRF" run_cmd nettest -s -R -P icmp -l ${a} -b - log_test_addr ${a} $? 0 "Raw socket bind to local address" + log_test_addr ${a} $? 1 "Raw socket bind to local address" log_start run_cmd nettest -s -R -P icmp -l ${a} -d ${NSA_DEV} -b
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 38/99 selftests: Fix IPv6 address bind tests
In reply to Greg Kroah-HartmanFrom: David Ahern <[email protected]>
[ Upstream commit 28a2686c185e84b6aa6a4d9c9a972360eb7ca266 ]
IPv6 allows binding a socket to a device then binding to an address not on the device (__inet6_bind -> ipv6_chk_addr with strict flag not set). Update the bind tests to reflect legacy behavior.
--- tools/testing/selftests/net/fcnal-test.sh | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-)
tools/testing/selftests/net/fcnal-test.sh +13 -5
@@ -3366,11 +3366,14 @@ ipv6_addr_bind_novrf() run_cmd nettest -6 -s -l ${a} -d ${NSA_DEV} -t1 -b log_test_addr ${a} $? 0 "TCP socket bind to local address after device bind" + # Sadly, the kernel allows binding a socket to a device and then + # binding to an address not on the device. So this test passes + # when it really should not a=${NSA_LO_IP6} log_start - show_hint "Should fail with 'Cannot assign requested address'" - run_cmd nettest -6 -s -l ${a} -d ${NSA_DEV} -t1 -b - log_test_addr ${a} $? 1 "TCP socket bind to out of scope local address" + show_hint "Tecnically should fail since address is not on device but kernel allows" + run_cmd nettest -6 -s -l ${a} -I ${NSA_DEV} -t1 -b + log_test_addr ${a} $? 0 "TCP socket bind to out of scope local address" } ipv6_addr_bind_vrf()
@@ -3411,10 +3414,15 @@ ipv6_addr_bind_vrf() run_cmd nettest -6 -s -l ${a} -d ${NSA_DEV} -t1 -b log_test_addr ${a} $? 0 "TCP socket bind to local address with device bind" + # Sadly, the kernel allows binding a socket to a device and then + # binding to an address not on the device. The only restriction + # is that the address is valid in the L3 domain. So this test + # passes when it really should not a=${VRF_IP6} log_start - run_cmd nettest -6 -s -l ${a} -d ${NSA_DEV} -t1 -b - log_test_addr ${a} $? 1 "TCP socket bind to VRF address with device bind" + show_hint "Tecnically should fail since address is not on device but kernel allows" + run_cmd nettest -6 -s -l ${a} -I ${NSA_DEV} -t1 -b + log_test_addr ${a} $? 0 "TCP socket bind to VRF address with device bind" a=${NSA_LO_IP6} log_start
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 39/99 dmaengine: st_fdma: fix MODULE_ALIAS
In reply to Greg Kroah-HartmanFrom: Alyssa Ross <[email protected]>
[ Upstream commit 822c9f2b833c53fc67e8adf6f63ecc3ea24d502c ]
modprobe can't handle spaces in aliases.
--- drivers/dma/st_fdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/dma/st_fdma.c +1 -1
@@ -874,4 +874,4 @@ MODULE_LICENSE("GPL v2");MODULE_DESCRIPTION ("STMicroelectronics FDMA engine driver" );MODULE_AUTHOR ("Ludovic.barre <[email protected]>" );MODULE_AUTHOR ("Peter Griffin <[email protected]>" ); -MODULE_ALIAS ("platform: " DRIVER_NAME ); +MODULE_ALIAS ("platform:" DRIVER_NAME );
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 40/99 net/sched: sch_ets: dont remove idle classes from the round-robin list
In reply to Greg Kroah-HartmanFrom: Davide Caratti <[email protected]>
[ Upstream commit c062f2a0b04d86c5b8c9d973bea43493eaca3d32 ]
Shuang reported that the following script:
1) tc qdisc add dev ddd0 handle 10: parent 1: ets bands 8 strict 4 priomap 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
2) mausezahn ddd0 -A 10.10.10.1 -B 10.10.10.2 -c 0 -a own -b 00:c1:a0:c1:a0:00 -t udp &
3) tc qdisc change dev ddd0 handle 10: ets bands 4 strict 2 quanta 2500 2500 priomap 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
crashes systematically when line 2) is commented:
list_del corruption, ffff8e028404bd30->next is LIST_POISON1 (dead000000000100)
------------[ cut here ]------------ kernel BUG at lib/list_debug.c:47! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 954 Comm: tc Not tainted 5.16.0-rc4+ #478 Hardware name: Red Hat KVM, BIOS 1.11.1-4.module+el8.1.0+4066+0f1aadab 04/01/2014 RIP: 0010:__list_del_entry_valid.cold.1+0x12/0x47 Code: fe ff 0f 0b 48 89 c1 4c 89 c6 48 c7 c7 08 42 1b 87 e8 1d c5 fe ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 98 42 1b 87 e8 09 c5 fe ff <0f> 0b 48 c7 c7 48 43 1b 87 e8 fb c4 fe ff 0f 0b 48 89 f2 48 89 fe RSP: 0018:ffffae46807a3888 EFLAGS: 00010246 RAX: 000000000000004e RBX: 0000000000000007 RCX: 0000000000000202 RDX: 0000000000000000 RSI: ffffffff871ac536 RDI: 00000000ffffffff RBP: ffffae46807a3a10 R08: 0000000000000000 R09: c0000000ffff7fff R10: 0000000000000001 R11: ffffae46807a36a8 R12: ffff8e028404b800 R13: ffff8e028404bd30 R14: dead000000000100 R15: ffff8e02fafa2400 FS: 00007efdc92e4480(0000) GS:ffff8e02fb600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000682f48 CR3: 00000001058be000 CR4: 0000000000350ef0 Call Trace: <TASK> ets_qdisc_change+0x58b/0xa70 [sch_ets] tc_modify_qdisc+0x323/0x880 rtnetlink_rcv_msg+0x169/0x4a0 netlink_rcv_skb+0x50/0x100 netlink_unicast+0x1a5/0x280 netlink_sendmsg+0x257/0x4d0 sock_sendmsg+0x5b/0x60 ____sys_sendmsg+0x1f2/0x260 ___sys_sendmsg+0x7c/0xc0 __sys_sendmsg+0x57/0xa0 do_syscall_64+0x3a/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7efdc8031338 Code: 89 02 48 c7 c0 ff ff ff ff eb b5 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 8d 05 25 43 2c 00 8b 00 85 c0 75 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 41 54 41 89 d4 55 RSP: 002b:00007ffdf1ce9828 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000061b37a97 RCX: 00007efdc8031338 RDX: 0000000000000000 RSI: 00007ffdf1ce9890 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000000000001 R09: 000000000078a940 R10: 000000000000000c R11: 0000000000000246 R12: 0000000000000001 R13: 0000000000688880 R14: 0000000000000000 R15: 0000000000000000 </TASK> Modules linked in: sch_ets sch_tbf dummy rfkill iTCO_wdt iTCO_vendor_support intel_rapl_msr intel_rapl_common joydev pcspkr i2c_i801 virtio_balloon i2c_smbus lpc_ich ip_tables xfs libcrc32c crct10dif_pclmul crc32_pclmul crc32c_intel serio_raw ghash_clmulni_intel ahci libahci libata virtio_blk virtio_console virtio_net net_failover failover sunrpc dm_mirror dm_region_hash dm_log dm_mod [last unloaded: sch_ets] ---[ end trace f35878d1912655c2 ]--- RIP: 0010:__list_del_entry_valid.cold.1+0x12/0x47 Code: fe ff 0f 0b 48 89 c1 4c 89 c6 48 c7 c7 08 42 1b 87 e8 1d c5 fe ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 98 42 1b 87 e8 09 c5 fe ff <0f> 0b 48 c7 c7 48 43 1b 87 e8 fb c4 fe ff 0f 0b 48 89 f2 48 89 fe RSP: 0018:ffffae46807a3888 EFLAGS: 00010246 RAX: 000000000000004e RBX: 0000000000000007 RCX: 0000000000000202 RDX: 0000000000000000 RSI: ffffffff871ac536 RDI: 00000000ffffffff RBP: ffffae46807a3a10 R08: 0000000000000000 R09: c0000000ffff7fff R10: 0000000000000001 R11: ffffae46807a36a8 R12: ffff8e028404b800 R13: ffff8e028404bd30 R14: dead000000000100 R15: ffff8e02fafa2400 FS: 00007efdc92e4480(0000) GS:ffff8e02fb600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000682f48 CR3: 00000001058be000 CR4: 0000000000350ef0 Kernel panic - not syncing: Fatal exception in interrupt Kernel Offset: 0x4e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---
we can remove 'q->classes[i].alist' only if DRR class 'i' was part of the active list. In the ETS scheduler DRR classes belong to that list only if the queue length is greater than zero: we need to test for non-zero value of 'q->classes[i].qdisc->q.qlen' before removing from the list, similarly to what has been done elsewhere in the ETS code.
--- net/sched/sch_ets.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/sched/sch_ets.c +2 -2
@@ -668,9 +668,9 @@ static int ets_qdisc_change(struct Qdisc *sch, struct nlattr *opt, } }for (i = q->nbands; i < oldbands; i++) { -qdisc_tree_flush_backlog (q->classes[i].qdisc); -if (i >= q->nstrict) +if (i >= q->nstrict && q->classes[i].qdisc->q.qlen)list_del (&q->classes[i].alist); +qdisc_tree_flush_backlog (q->classes[i].qdisc); } q->nstrict = nstrict;memcpy (q->prio2band, priomap,sizeof (priomap));
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 41/99 selftest/net/forwarding: declare NETIFS p9 p10
In reply to Greg Kroah-HartmanFrom: Hangbin Liu <[email protected]>
[ Upstream commit 71da1aec215290e249d09c44c768df859f3a3bba ]
The recent GRE selftests defined NUM_NETIFS=10. If the users copy forwarding.config.sample to forwarding.config directly, they will get error "Command line is not complete" when run the GRE tests, because create_netif_veth() failed with no interface name defined.
Fix it by extending the NETIFS with p9 and p10.
--- tools/testing/selftests/net/forwarding/forwarding.config.sample | 2 ++ 1 file changed, 2 insertions(+)
tools/testing/selftests/net/forwarding/forwarding.config.sample +2 -0
@@ -13,6 +13,8 @@ NETIFS[p5]=veth4 NETIFS[p6]=veth5 NETIFS[p7]=veth6 NETIFS[p8]=veth7 +NETIFS[p9]=veth8 +NETIFS[p10]=veth9 # Port that does not have a cable connected. NETIF_NO_CABLE=eth8
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 42/99 drm/ast: potential dereference of null pointer
In reply to Greg Kroah-HartmanFrom: Jiasheng Jiang <[email protected]>
[ Upstream commit fea3fdf975dd9f3e5248afaab8fe023db313f005 ]
The return value of kzalloc() needs to be checked. To avoid use of null pointer '&ast_state->base' in case of the failure of alloc.
--- drivers/gpu/drm/ast/ast_mode.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/gpu/drm/ast/ast_mode.c +4 -1
@@ -857,7 +857,10 @@ static void ast_crtc_reset(struct drm_crtc *crtc)if (crtc->state) crtc->funcs->atomic_destroy_state (crtc, crtc->state); -__drm_atomic_helper_crtc_reset (crtc, &ast_state->base); +if (ast_state) +__drm_atomic_helper_crtc_reset (crtc, &ast_state->base); +else +__drm_atomic_helper_crtc_reset (crtc,NULL ); } static struct drm_crtc_state *
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 43/99 mac80211: agg-tx: dont schedule_and_wake_txq() under sta->lock
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
[ Upstream commit 06c41bda0ea14aa7fba932a9613c4ee239682cf0 ]
When we call ieee80211_agg_start_txq(), that will in turn call schedule_and_wake_txq(). Called from ieee80211_stop_tx_ba_cb() this is done under sta->lock, which leads to certain circular lock dependencies, as reported by Chris Murphy:
https://lore.kernel.org/r/CAJCQCtSXJ5qA4bqSPY=oLRMbv-irihVvP7A2uGutEbXQVkoNaw@mail.gmail.com
In general, ieee80211_agg_start_txq() is usually not called with sta->lock held, only in this one place. But it's always called with sta->ampdu_mlme.mtx held, and that's therefore clearly sufficient.
Change ieee80211_stop_tx_ba_cb() to also call it without the sta->lock held, by factoring it out of ieee80211_remove_tid_tx() (which is only called in this one place).
This breaks the locking chain and makes it less likely that we'll have similar locking chain problems in the future.
--- net/mac80211/agg-tx.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
net/mac80211/agg-tx.c +8 -2
@@ -9,7 +9,7 @@* Copyright 2007, Michael Wu <[email protected]> * Copyright 2007-2010, Intel Corporation * Copyright(c) 2015-2017 Intel Deutschland GmbH -* Copyright (C) 2018 - 2020 Intel Corporation +* Copyright (C) 2018 - 2021 Intel Corporation */ #include <linux/ieee80211.h>
@@ -213,6 +213,8 @@ ieee80211_agg_start_txq(struct sta_info *sta, int tid, bool enable)struct ieee80211_txq *txq = sta->sta.txq[tid];struct txq_info *txqi; +lockdep_assert_held (&sta->ampdu_mlme.mtx); +if (!txq)return ;
@@ -290,7 +292,6 @@ static void ieee80211_remove_tid_tx(struct sta_info *sta, int tid)ieee80211_assign_tid_tx (sta, tid,NULL );ieee80211_agg_splice_finish (sta->sdata, tid); -ieee80211_agg_start_txq (sta, tid, false);kfree_rcu (tid_tx, rcu_head); }
@@ -889,6 +890,7 @@ void ieee80211_stop_tx_ba_cb(struct sta_info *sta, int tid, {struct ieee80211_sub_if_data *sdata = sta->sdata;bool send_delba = false; +bool start_txq = false;ht_dbg (sdata,"Stopping Tx BA session for %pM tid %d\n" , sta->sta.addr, tid);
@@ -906,10 +908,14 @@ void ieee80211_stop_tx_ba_cb(struct sta_info *sta, int tid, send_delba = true;ieee80211_remove_tid_tx (sta, tid); + start_txq = true; unlock_sta:spin_unlock_bh (&sta->lock); +if (start_txq) +ieee80211_agg_start_txq (sta, tid, false); +if (send_delba)ieee80211_send_delba (sdata, sta->sta.addr, tid,WLAN_BACK_INITIATOR ,WLAN_REASON_QSTA_NOT_USE );
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 44/99 mac80211: fix lookup when adding AddBA extension element
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
[ Upstream commit 511ab0c1dfb260a6b17b8771109e8d63474473a7 ]
We should be doing the HE capabilities lookup based on the full interface type so if P2P doesn't have HE but client has it doesn't get confused. Fix that.
--- net/mac80211/agg-rx.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
net/mac80211/agg-rx.c +3 -2
@@ -9,7 +9,7 @@* Copyright 2007, Michael Wu <[email protected]> * Copyright 2007-2010, Intel Corporation * Copyright(c) 2015-2017 Intel Deutschland GmbH -* Copyright (C) 2018-2020 Intel Corporation +* Copyright (C) 2018-2021 Intel Corporation */ /**
@@ -191,7 +191,8 @@ static void ieee80211_add_addbaext(struct ieee80211_sub_if_data *sdata, sband =ieee80211_get_sband (sdata);if (!sband)return ; - he_cap =ieee80211_get_he_iftype_cap (sband, sdata->vif.type); + he_cap =ieee80211_get_he_iftype_cap (sband, +ieee80211_vif_type_p2p (&sdata->vif));if (!he_cap)return ;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 45/99 flow_offload: return EOPNOTSUPP for the unsupported mpls action type
In reply to Greg Kroah-HartmanFrom: Baowen Zheng <[email protected]>
[ Upstream commit 166b6a46b78bf8b9559a6620c3032f9fe492e082 ]
We need to return EOPNOTSUPP for the unsupported mpls action type when setup the flow action.
In the original implement, we will return 0 for the unsupported mpls action type, actually we do not setup it and the following actions to the flow action entry.
--- net/sched/cls_api.c | 1 + 1 file changed, 1 insertion(+)
net/sched/cls_api.c +1 -0
@@ -3703,6 +3703,7 @@ int tc_setup_flow_action(struct flow_action *flow_action, entry->mpls_mangle.ttl =tcf_mpls_ttl (act);break ;default : + err = -EOPNOTSUPP ; goto err_out_locked; } }else if (is_tcf_skbedit_ptype (act)) {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 46/99 rds: memory leak in __rds_conn_create()
In reply to Greg Kroah-HartmanFrom: Hangyu Hua <[email protected]>
[ Upstream commit 5f9562ebe710c307adc5f666bf1a2162ee7977c0 ]
__rds_conn_create() did not release conn->c_path when loop_trans != 0 and trans->t_prefer_loopback != 0 and is_outgoing == 0.
--- net/rds/connection.c | 1 + 1 file changed, 1 insertion(+)
net/rds/connection.c +1 -0
@@ -253,6 +253,7 @@ static struct rds_connection *__rds_conn_create(struct net *net,* should end up here, but if it * does, reset/destroy the connection. */ +kfree (conn->c_path);kmem_cache_free (rds_conn_slab, conn); conn =ERR_PTR (-EOPNOTSUPP ); goto out;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 47/99 drm/amd/pm: fix a potential gpu_metrics_table memory leak
In reply to Greg Kroah-HartmanFrom: Lang Yu <[email protected]>
[ Upstream commit aa464957f7e660abd554f2546a588f6533720e21 ]
Memory is allocated for gpu_metrics_table in renoir_init_smc_tables(), but not freed in int smu_v12_0_fini_smc_tables(). Free it!
--- drivers/gpu/drm/amd/pm/swsmu/smu12/smu_v12_0.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/amd/pm/swsmu/smu12/smu_v12_0.c +3 -0
@@ -187,6 +187,9 @@ int smu_v12_0_fini_smc_tables(struct smu_context *smu)kfree (smu_table->watermarks_table); smu_table->watermarks_table =NULL ; +kfree (smu_table->gpu_metrics_table); + smu_table->gpu_metrics_table =NULL ; +return 0 ; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 48/99 mptcp: clear kern flag from fallback sockets
In reply to Greg Kroah-HartmanFrom: Florian Westphal <[email protected]>
[ Upstream commit d6692b3b97bdc165d150f4c1505751a323a80717 ]
The mptcp ULP extension relies on sk->sk_sock_kern being set correctly:
It prevents setsockopt(fd, IPPROTO_TCP, TCP_ULP, "mptcp", 6); from working for plain tcp sockets (any userspace-exposed socket).
But in case of fallback, accept() can return a plain tcp sk. In such case, sk is still tagged as 'kernel' and setsockopt will work.
This will crash the kernel, The subflow extension has a NULL ctx->conn mptcp socket:
BUG: KASAN: null-ptr-deref in subflow_data_ready+0x181/0x2b0 Call Trace: tcp_data_ready+0xf8/0x370 [..]
--- net/mptcp/protocol.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/mptcp/protocol.c +3 -1
@@ -2149,7 +2149,7 @@ static struct sock *mptcp_accept(struct sock *sk, int flags, int *err,*/ if (WARN_ON_ONCE (!new_mptcp_sock)) {tcp_sk (newsk)->is_mptcp =0 ; -return newsk; + goto out; }/* acquire the 2nd reference for the owning socket */
@@ -2174,6 +2174,8 @@ static struct sock *mptcp_accept(struct sock *sk, int flags, int *err, MPTCP_MIB_MPCAPABLEPASSIVEFALLBACK); } +out: + newsk->sk_kern_sock = kern;return newsk; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 49/99 soc/tegra: fuse: Fix bitwise vs. logical OR warning
In reply to Greg Kroah-HartmanFrom: Nathan Chancellor <[email protected]>
[ Upstream commit a7083763619f7485ccdade160deb81737cf2732f ]
A new warning in clang points out two instances where boolean expressions are being used with a bitwise OR instead of logical OR:
drivers/soc/tegra/fuse/speedo-tegra20.c:72:9: warning: use of bitwise '|' with boolean operands [-Wbitwise-instead-of-logical]
reg = tegra_fuse_read_spare(i) |
^~~~~~~~~~~~~~~~~~~~~~~~~~
||
drivers/soc/tegra/fuse/speedo-tegra20.c:72:9: note: cast one or both operands to int to silence this warning
drivers/soc/tegra/fuse/speedo-tegra20.c:87:9: warning: use of bitwise '|' with boolean operands [-Wbitwise-instead-of-logical]
reg = tegra_fuse_read_spare(i) |
^~~~~~~~~~~~~~~~~~~~~~~~~~
||drivers/soc/tegra/fuse/speedo-tegra20.c:87:9: note: cast one or both operands to int to silence this warning 2 warnings generated.
The motivation for the warning is that logical operations short circuit while bitwise operations do not.
In this instance, tegra_fuse_read_spare() is not semantically returning a boolean, it is returning a bit value. Use u32 for its return type so that it can be used with either bitwise or boolean operators without any warnings.
--- drivers/soc/tegra/fuse/fuse-tegra.c | 2 +- drivers/soc/tegra/fuse/fuse.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
drivers/soc/tegra/fuse/fuse-tegra.c +1 -1
@@ -260,7 +260,7 @@ static struct platform_driver tegra_fuse_driver = { };builtin_platform_driver (tegra_fuse_driver); -bool __init tegra_fuse_read_spare (unsigned int spare) +u32 __init tegra_fuse_read_spare (unsigned int spare) {unsigned int offset = fuse->soc->info->spare + spare *4 ;
drivers/soc/tegra/fuse/fuse.h +1 -1
@@ -63,7 +63,7 @@ struct tegra_fuse {void tegra_init_revision (void );void tegra_init_apbmisc (void ); -bool __init tegra_fuse_read_spare (unsigned int spare); +u32 __init tegra_fuse_read_spare (unsigned int spare);u32 __init tegra_fuse_read_early (unsigned int offset);u8 tegra_get_major_rev (void );
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 50/99 igb: Fix removal of unicast MAC filters of VFs
In reply to Greg Kroah-HartmanFrom: Karen Sornek <[email protected]>
[ Upstream commit 584af82154f56e6b2740160fcc84a2966d969e15 ]
Move checking condition of VF MAC filter before clearing or adding MAC filter to VF to prevent potential blackout caused by removal of necessary and working VF's MAC filter.
--- drivers/net/ethernet/intel/igb/igb_main.c | 28 +++++++++++------------ 1 file changed, 14 insertions(+), 14 deletions(-)
drivers/net/ethernet/intel/igb/igb_main.c +14 -14
@@ -7654,6 +7654,20 @@ static int igb_set_vf_mac_filter(struct igb_adapter *adapter, const int vf,struct vf_mac_filter *entry =NULL ;int ret =0 ; +if ((vf_data->flags &IGB_VF_FLAG_PF_SET_MAC ) && + !vf_data->trusted) { +dev_warn (&pdev->dev, +"VF %d requested MAC filter but is administratively denied\n" , + vf); +return -EINVAL ; + } +if (!is_valid_ether_addr (addr)) { +dev_warn (&pdev->dev, +"VF %d attempted to set invalid MAC filter\n" , + vf); +return -EINVAL ; + } +switch (info) {case E1000_VF_MAC_FILTER_CLR :/* remove all unicast MAC filters related to the current VF */
@@ -7667,20 +7681,6 @@ static int igb_set_vf_mac_filter(struct igb_adapter *adapter, const int vf, }break ;case E1000_VF_MAC_FILTER_ADD : -if ((vf_data->flags &IGB_VF_FLAG_PF_SET_MAC ) && - !vf_data->trusted) { -dev_warn (&pdev->dev, -"VF %d requested MAC filter but is administratively denied\n" , - vf); -return -EINVAL ; - } -if (!is_valid_ether_addr (addr)) { -dev_warn (&pdev->dev, -"VF %d attempted to set invalid MAC filter\n" , - vf); -return -EINVAL ; - } -/* try to find empty slot in the list */ list_for_each (pos, &adapter->vf_macs.l) { entry = list_entry(pos, struct vf_mac_filter, l);
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 51/99 igbvf: fix double free in `igbvf_probe`
In reply to Greg Kroah-HartmanFrom: Letu Ren <[email protected]>
[ Upstream commit b6d335a60dc624c0d279333b22c737faa765b028 ]
In igbvf_probe, if register_netdev() fails, the program will go to label err_hw_init, and then to label err_ioremap. In free_netdev() which is just below label err_ioremap, there is list_for_each_entry_safe and netif_napi_del which aims to delete all entries in dev->napi_list. The program has added an entry adapter->rx_ring->napi which is added by netif_napi_add in igbvf_alloc_queues(). However, adapter->rx_ring has been freed below label err_hw_init. So this a UAF.
In terms of how to patch the problem, we can refer to igbvf_remove() and delete the entry before adapter->rx_ring.
The KASAN logs are as follows:
[ 35.126075] BUG: KASAN: use-after-free in free_netdev+0x1fd/0x450 [ 35.127170] Read of size 8 at addr ffff88810126d990 by task modprobe/366 [ 35.128360] [ 35.128643] CPU: 1 PID: 366 Comm: modprobe Not tainted 5.15.0-rc2+ #14 [ 35.129789] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014 [ 35.131749] Call Trace: [ 35.132199] dump_stack_lvl+0x59/0x7b [ 35.132865] print_address_description+0x7c/0x3b0 [ 35.133707] ? free_netdev+0x1fd/0x450 [ 35.134378] __kasan_report+0x160/0x1c0 [ 35.135063] ? free_netdev+0x1fd/0x450 [ 35.135738] kasan_report+0x4b/0x70 [ 35.136367] free_netdev+0x1fd/0x450 [ 35.137006] igbvf_probe+0x121d/0x1a10 [igbvf] [ 35.137808] ? igbvf_vlan_rx_add_vid+0x100/0x100 [igbvf] [ 35.138751] local_pci_probe+0x13c/0x1f0 [ 35.139461] pci_device_probe+0x37e/0x6c0 [ 35.165526] [ 35.165806] Allocated by task 366: [ 35.166414] ____kasan_kmalloc+0xc4/0xf0 [ 35.167117] foo_kmem_cache_alloc_trace+0x3c/0x50 [igbvf] [ 35.168078] igbvf_probe+0x9c5/0x1a10 [igbvf] [ 35.168866] local_pci_probe+0x13c/0x1f0 [ 35.169565] pci_device_probe+0x37e/0x6c0 [ 35.179713] [ 35.179993] Freed by task 366: [ 35.180539] kasan_set_track+0x4c/0x80 [ 35.181211] kasan_set_free_info+0x1f/0x40 [ 35.181942] ____kasan_slab_free+0x103/0x140 [ 35.182703] kfree+0xe3/0x250 [ 35.183239] igbvf_probe+0x1173/0x1a10 [igbvf] [ 35.184040] local_pci_probe+0x13c/0x1f0
--- drivers/net/ethernet/intel/igbvf/netdev.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/ethernet/intel/igbvf/netdev.c +1 -0
@@ -2873,6 +2873,7 @@ static int igbvf_probe(struct pci_dev *pdev, const struct pci_device_id *ent)return 0 ; err_hw_init: +netif_napi_del (&adapter->rx_ring->napi);kfree (adapter->tx_ring);kfree (adapter->rx_ring); err_sw_init:
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 52/99 igc: Fix typo in i225 LTR functions
In reply to Greg Kroah-HartmanFrom: Sasha Neftin <[email protected]>
[ Upstream commit 0182d1f3fa640888a2ed7e3f6df2fdb10adee7c8 ]
The LTR maximum value was incorrectly written using the scale from the LTR minimum value. This would cause incorrect values to be sent, in cases where the initial calculation lead to different min/max scales.
--- drivers/net/ethernet/intel/igc/igc_i225.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/intel/igc/igc_i225.c +1 -1
@@ -636,7 +636,7 @@ s32 igc_set_ltr_i225(struct igc_hw *hw, bool link) ltrv =rd32 (IGC_LTRMAXV );if (ltr_max != (ltrv &IGC_LTRMAXV_LTRV_MASK )) { ltrv =IGC_LTRMAXV_LSNP_REQ | ltr_max | - (scale_min <<IGC_LTRMAXV_SCALE_SHIFT ); + (scale_max <<IGC_LTRMAXV_SCALE_SHIFT );wr32 (IGC_LTRMAXV , ltrv); } }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 53/99 ixgbe: Document how to enable NBASE-T support
In reply to Greg Kroah-HartmanFrom: Robert Schlabbach <[email protected]>
[ Upstream commit 271225fd57c2f1e0b3f8826df51be6c634affefe ]
Commit a296d665eae1 ("ixgbe: Add ethtool support to enable 2.5 and 5.0 Gbps support") introduced suppression of the advertisement of NBASE-T speeds by default, according to Todd Fujinaka to accommodate customers with network switches which could not cope with advertised NBASE-T speeds, as posted in the E1000-devel mailing list:
https://sourceforge.net/p/e1000/mailman/message/37106269/
However, the suppression was not documented at all, nor was how to enable NBASE-T support.
Properly document the NBASE-T suppression and how to enable NBASE-T support.
--- .../device_drivers/ethernet/intel/ixgbe.rst | 16 ++++++++++++++++ drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 4 ++++ 2 files changed, 20 insertions(+)
Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst +16 -0
@@ -440,6 +440,22 @@ NOTE: For 82599-based network connections, if you are enabling jumbo frames in a virtual function (VF), jumbo frames must first be enabled in the physical function (PF). The VF MTU setting cannot be larger than the PF MTU. +NBASE-T Support +--------------- +The ixgbe driver supports NBASE-T on some devices. However, the advertisement +of NBASE-T speeds is suppressed by default, to accommodate broken network +switches which cannot cope with advertised NBASE-T speeds. Use the ethtool +command to enable advertising NBASE-T speeds on devices which support it:: + + ethtool -s eth? advertise 0x1800000001028 + +On Linux systems with INTERFACES(5), this can be specified as a pre-up command +in /etc/network/interfaces so that the interface is always brought up with +NBASE-T support, e.g.:: + + iface eth? inet dhcp + pre-up ethtool -s eth? advertise 0x1800000001028 || true + Generic Receive Offload, aka GRO -------------------------------- The driver supports the in-kernel software implementation of GRO. GRO has
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c +4 -0
@@ -5532,6 +5532,10 @@ static int ixgbe_non_sfp_link_config(struct ixgbe_hw *hw)if (!speed && hw->mac.ops.get_link_capabilities) { ret = hw->mac.ops.get_link_capabilities (hw, &speed, &autoneg); +/* remove NBASE-T speeds from default autonegotiation +* to accommodate broken network switches in the field +* which cannot cope with advertised NBASE-T speeds +*/ speed &= ~(IXGBE_LINK_SPEED_5GB_FULL |IXGBE_LINK_SPEED_2_5GB_FULL ); }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 54/99 ixgbe: set X550 MDIO speed before talking to PHY
In reply to Greg Kroah-HartmanFrom: Cyril Novikov <[email protected]>
[ Upstream commit bf0a375055bd1afbbf02a0ef45f7655da7b71317 ]
The MDIO bus speed must be initialized before talking to the PHY the first time in order to avoid talking to it using a speed that the PHY doesn't support.
This fixes HW initialization error -17 (IXGBE_ERR_PHY_ADDR_INVALID) on Denverton CPUs (a.k.a. the Atom C3000 family) on ports with a 10Gb network plugged in. On those devices, HLREG0[MDCSPD] resets to 1, which combined with the 10Gb network results in a 24MHz MDIO speed, which is apparently too fast for the connected PHY. PHY register reads over MDIO bus return garbage, leading to initialization failure.
Reproduced with Linux kernel 4.19 and 5.15-rc7. Can be reproduced using the following setup:
* Use an Atom C3000 family system with at least one X552 LAN on the SoC
* Disable PXE or other BIOS network initialization if possible (the interface must not be initialized before Linux boots)
* Connect a live 10Gb Ethernet cable to an X550 port
* Power cycle (not reset, doesn't always work) the system and boot Linux
* Observe: ixgbe interfaces w/ 10GbE cables plugged in fail with error -17
--- drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c +3 -0
@@ -3405,6 +3405,9 @@ static s32 ixgbe_reset_hw_X550em(struct ixgbe_hw *hw)/* flush pending Tx transactions */ ixgbe_clear_tx_pending (hw); +/* set MDIO speed before talking to the PHY in case it's the 1st time */ +ixgbe_set_mdio_speed (hw); +/* PHY ops must be identified and initialized prior to reset */ status = hw->phy.ops.init (hw); if (status == IXGBE_ERR_SFP_NOT_SUPPORTED ||
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 55/99 netdevsim: Zero-initialize memory for new maps value in function nsim_bpf_map_alloc
In reply to Greg Kroah-HartmanFrom: Haimin Zhang <[email protected]>
[ Upstream commit 481221775d53d6215a6e5e9ce1cce6d2b4ab9a46 ]
Zero-initialize memory for new map's value in function nsim_bpf_map_alloc since it may cause a potential kernel information leak issue, as follows:
1. nsim_bpf_map_alloc calls nsim_map_alloc_elem to allocate elements for a new map.
2. nsim_map_alloc_elem uses kmalloc to allocate map's value, but doesn't zero it.
3. A user application can use IOCTL BPF_MAP_LOOKUP_ELEM to get specific element's information in the map.
4. The kernel function map_lookup_elem will call bpf_map_copy_value to get the information allocated at step-2, then use copy_to_user to copy to the user buffer.
This can only leak information for an array map.
--- drivers/net/netdevsim/bpf.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/netdevsim/bpf.c +1 -0
@@ -514,6 +514,7 @@ nsim_bpf_map_alloc(struct netdevsim *ns, struct bpf_offloaded_map *offmap) goto err_free; key = nmap->entry[i].key; *key = i; +memset (nmap->entry[i].value,0 , offmap->map.value_size); } }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 56/99 net/packet: rx_owner_map depends on pg_vec
In reply to Greg Kroah-HartmanFrom: Willem de Bruijn <[email protected]>
[ Upstream commit ec6af094ea28f0f2dda1a6a33b14cd57e36a9755 ]
Packet sockets may switch ring versions. Avoid misinterpreting state between versions, whose fields share a union. rx_owner_map is only allocated with a packet ring (pg_vec) and both are swapped together. If pg_vec is NULL, meaning no packet ring was allocated, then neither was rx_owner_map. And the field may be old state from a tpacket_v3.
--- net/packet/af_packet.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
net/packet/af_packet.c +3 -2
@@ -4461,9 +4461,10 @@ static int packet_set_ring(struct sock *sk, union tpacket_req_u *req_u, } out_free_pg_vec: -bitmap_free (rx_owner_map); -if (pg_vec) +if (pg_vec) { +bitmap_free (rx_owner_map);free_pg_vec (pg_vec, order, req->tp_block_nr); + } out:return err; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 57/99 sfc_ef100: potential dereference of null pointer
In reply to Greg Kroah-HartmanFrom: Jiasheng Jiang <[email protected]>
[ Upstream commit 407ecd1bd726f240123f704620d46e285ff30dd9 ]
The return value of kmalloc() needs to be checked.
To avoid use in efx_nic_update_stats() in case of the failure of alloc.
--- drivers/net/ethernet/sfc/ef100_nic.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/net/ethernet/sfc/ef100_nic.c +3 -0
@@ -597,6 +597,9 @@ static size_t ef100_update_stats(struct efx_nic *efx,ef100_common_stat_mask (mask);ef100_ethtool_stat_mask (mask); +if (!mc_stats) +return 0 ; +efx_nic_copy_stats (efx, mc_stats);efx_nic_update_stats (ef100_stat_desc,EF100_STAT_COUNT , mask, stats, mc_stats, false);
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 58/99 net: Fix double 0x prefix print in SKB dump
In reply to Greg Kroah-HartmanFrom: Gal Pressman <[email protected]>
[ Upstream commit 8a03ef676ade55182f9b05115763aeda6dc08159 ]
When printing netdev features %pNF already takes care of the 0x prefix, remove the explicit one.
--- net/core/skbuff.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/core/skbuff.c +1 -1
@@ -769,7 +769,7 @@ void skb_dump(const char *level, const struct sk_buff *skb, bool full_pkt) ntohs(skb->protocol), skb->pkt_type, skb->skb_iif);if (dev) -printk ("%sdev name=%s feat=0x%pNF\n" , +printk ("%sdev name=%s feat=%pNF\n" , level, dev->name, &dev->features);if (sk) printk("%ssk family=%hu type=%u proto=%u\n",
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 59/99 net/smc: Prevent smc_release() from long blocking
In reply to Greg Kroah-HartmanFrom: D. Wythe <[email protected]>
[ Upstream commit 5c15b3123f65f8fbb1b445d9a7e8812e0e435df2 ]
In nginx/wrk benchmark, there's a hung problem with high probability on case likes that: (client will last several minutes to exit)
server: smc_run nginx
client: smc_run wrk -c 10000 -t 1 http://server
Client hangs with the following backtrace:
0 [ffffa7ce8Of3bbf8] __schedule at ffffffff9f9eOd5f
1 [ffffa7ce8Of3bc88] schedule at ffffffff9f9eløe6
2 [ffffa7ce8Of3bcaO] schedule_timeout at ffffffff9f9e3f3c
3 [ffffa7ce8Of3bd2O] wait_for_common at ffffffff9f9el9de
4 [ffffa7ce8Of3bd8O] __flush_work at ffffffff9fOfeOl3
5 [ffffa7ce8øf3bdfO] smc_release at ffffffffcO697d24 [smc]
6 [ffffa7ce8Of3be2O] __sock_release at ffffffff9f8O2e2d
7 [ffffa7ce8Of3be4ø] sock_close at ffffffff9f8ø2ebl
8 [ffffa7ce8øf3be48] __fput at ffffffff9f334f93
9 [ffffa7ce8Of3be78] task_work_run at ffffffff9flOlff5
10 [ffffa7ce8Of3beaO] do_exit at ffffffff9fOe5Ol2
11 [ffffa7ce8Of3bflO] do_group_exit at ffffffff9fOe592a
12 [ffffa7ce8Of3bf38] __x64_sys_exit_group at ffffffff9fOe5994 13 [ffffa7ce8Of3bf4O] do_syscall_64 at ffffffff9f9d4373
14 [ffffa7ce8Of3bfsO] entry_SYSCALL_64_after_hwframe at ffffffff9fa0007c
This issue dues to flush_work(), which is used to wait for smc_connect_work() to finish in smc_release(). Once lots of smc_connect_work() was pending or all executing work dangling, smc_release() has to block until one worker comes to free, which is equivalent to wait another smc_connnect_work() to finish.
In order to fix this, There are two changes:
1. For those idle smc_connect_work(), cancel it from the workqueue; for executing smc_connect_work(), waiting for it to finish. For that purpose, replace flush_work() with cancel_work_sync().
2. Since smc_connect() hold a reference for passive closing, if smc_connect_work() has been cancelled, release the reference.
--- net/smc/af_smc.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/smc/af_smc.c +3 -1
@@ -191,7 +191,9 @@ static int smc_release(struct socket *sock)/* cleanup for a dangling non-blocking connect */ if (smc->connect_nonblock && sk->sk_state ==SMC_INIT )tcp_abort (smc->clcsock->sk,ECONNABORTED ); -flush_work (&smc->connect_work); + +if (cancel_work_sync (&smc->connect_work)) +sock_put (&smc->sk);/* sock_hold in smc_connect for passive closing */ if (sk->sk_state ==SMC_LISTEN )/* smc_close_non_accepted() is called and acquires
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 60/99 net: systemport: Add global locking for descriptor lifecycle
In reply to Greg Kroah-HartmanFrom: Florian Fainelli <[email protected]>
[ Upstream commit 8b8e6e782456f1ce02a7ae914bbd5b1053f0b034 ]
The descriptor list is a shared resource across all of the transmit queues, and the locking mechanism used today only protects concurrency across a given transmit queue between the transmit and reclaiming. This creates an opportunity for the SYSTEMPORT hardware to work on corrupted descriptors if we have multiple producers at once which is the case when using multiple transmit queues.
This was particularly noticeable when using multiple flows/transmit queues and it showed up in interesting ways in that UDP packets would get a correct UDP header checksum being calculated over an incorrect packet length. Similarly TCP packets would get an equally correct checksum computed by the hardware over an incorrect packet length.
The SYSTEMPORT hardware maintains an internal descriptor list that it re-arranges when the driver produces a new descriptor anytime it writes to the WRITE_PORT_{HI,LO} registers, there is however some delay in the hardware to re-organize its descriptors and it is possible that concurrent TX queues eventually break this internal allocation scheme to the point where the length/status part of the descriptor gets used for an incorrect data buffer.
The fix is to impose a global serialization for all TX queues in the short section where we are writing to the WRITE_PORT_{HI,LO} registers which solves the corruption even with multiple concurrent TX queues being used.
--- drivers/net/ethernet/broadcom/bcmsysport.c | 5 ++++- drivers/net/ethernet/broadcom/bcmsysport.h | 1 + 2 files changed, 5 insertions(+), 1 deletion(-)
drivers/net/ethernet/broadcom/bcmsysport.c +4 -1
@@ -1304,11 +1304,11 @@ static netdev_tx_t bcm_sysport_xmit(struct sk_buff *skb,struct bcm_sysport_priv *priv =netdev_priv (dev);struct device *kdev = &priv->pdev->dev;struct bcm_sysport_tx_ring *ring; +unsigned long flags, desc_flags;struct bcm_sysport_cb *cb;struct netdev_queue *txq;u32 len_status, addr_lo;unsigned int skb_len; -unsigned long flags;dma_addr_t mapping;u16 queue;int ret;
@@ -1368,8 +1368,10 @@ static netdev_tx_t bcm_sysport_xmit(struct sk_buff *skb, ring->desc_count--;/* Ports are latched, so write upper address first */ +spin_lock_irqsave (&priv->desc_lock, desc_flags);tdma_writel (priv, len_status,TDMA_WRITE_PORT_HI (ring->index));tdma_writel (priv, addr_lo,TDMA_WRITE_PORT_LO (ring->index)); +spin_unlock_irqrestore (&priv->desc_lock, desc_flags);/* Check ring space and update SW control flow */ if (ring->desc_count ==0 )
@@ -2008,6 +2010,7 @@ static int bcm_sysport_open(struct net_device *dev) }/* Initialize both hardware and software ring */ +spin_lock_init (&priv->desc_lock);for (i =0 ; i < dev->num_tx_queues; i++) { ret =bcm_sysport_init_tx_ring (priv, i);if (ret) {
drivers/net/ethernet/broadcom/bcmsysport.h +1 -0
@@ -742,6 +742,7 @@ struct bcm_sysport_priv {int wol_irq;/* Transmit rings */ +spinlock_t desc_lock;struct bcm_sysport_tx_ring *tx_rings;/* Receive queue */
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 61/99 sit: do not call ipip6_dev_free() from sit_init_net()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit e28587cc491ef0f3c51258fdc87fbc386b1d4c59 ]
ipip6_dev_free is sit dev->priv_destructor, already called by register_netdevice() if something goes wrong.
Alternative would be to make ipip6_dev_free() robust against multiple invocations, but other drivers do not implement this strategy.
syzbot reported:
dst_release underflow
WARNING: CPU: 0 PID: 5059 at net/core/dst.c:173 dst_release+0xd8/0xe0 net/core/dst.c:173 Modules linked in: CPU: 1 PID: 5059 Comm: syz-executor.4 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:dst_release+0xd8/0xe0 net/core/dst.c:173 Code: 4c 89 f2 89 d9 31 c0 5b 41 5e 5d e9 da d5 44 f9 e8 1d 90 5f f9 c6 05 87 48 c6 05 01 48 c7 c7 80 44 99 8b 31 c0 e8 e8 67 29 f9 <0f> 0b eb 85 0f 1f 40 00 53 48 89 fb e8 f7 8f 5f f9 48 83 c3 a8 48 RSP: 0018:ffffc9000aa5faa0 EFLAGS: 00010246 RAX: d6894a925dd15a00 RBX: 00000000ffffffff RCX: 0000000000040000 RDX: ffffc90005e19000 RSI: 000000000003ffff RDI: 0000000000040000 RBP: 0000000000000000 R08: ffffffff816a1f42 R09: ffffed1017344f2c R10: ffffed1017344f2c R11: 0000000000000000 R12: 0000607f462b1358 R13: 1ffffffff1bfd305 R14: ffffe8ffffcb1358 R15: dffffc0000000000 FS: 00007f66c71a2700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f88aaed5058 CR3: 0000000023e0f000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> dst_cache_destroy+0x107/0x1e0 net/core/dst_cache.c:160 ipip6_dev_free net/ipv6/sit.c:1414 [inline] sit_init_net+0x229/0x550 net/ipv6/sit.c:1936 ops_init+0x313/0x430 net/core/net_namespace.c:140 setup_net+0x35b/0x9d0 net/core/net_namespace.c:326 copy_net_ns+0x359/0x5c0 net/core/net_namespace.c:470 create_new_namespaces+0x4ce/0xa00 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0x11e/0x180 kernel/nsproxy.c:226 ksys_unshare+0x57d/0xb50 kernel/fork.c:3075 __do_sys_unshare kernel/fork.c:3146 [inline] __se_sys_unshare kernel/fork.c:3144 [inline] __x64_sys_unshare+0x34/0x40 kernel/fork.c:3144 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f66c882ce99 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f66c71a2168 EFLAGS: 00000246 ORIG_RAX: 0000000000000110 RAX: ffffffffffffffda RBX: 00007f66c893ff60 RCX: 00007f66c882ce99 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000048040200 RBP: 00007f66c8886ff1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff6634832f R14: 00007f66c71a2300 R15: 0000000000022000 </TASK>
--- net/ipv6/sit.c | 1 - 1 file changed, 1 deletion(-)
net/ipv6/sit.c +0 -1
@@ -1924,7 +1924,6 @@ static int __net_init sit_init_net(struct net *net)return 0 ; err_reg_dev: -ipip6_dev_free (sitn->fb_tunnel_dev);free_netdev (sitn->fb_tunnel_dev); err_alloc_dev:return err;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 62/99 bpf, selftests: Fix racing issue in btf_skc_cls_ingress test
In reply to Greg Kroah-HartmanFrom: Martin KaFai Lau <[email protected]>
[ Upstream commit c2fcbf81c332b42382a0c439bfe2414a241e4f5b ]
The libbpf CI reported occasional failure in btf_skc_cls_ingress:
test_syncookie:FAIL:Unexpected syncookie states gen_cookie:80326634 recv_cookie:0 bpf prog error at line 97
"error at line 97" means the bpf prog cannot find the listening socket when the final ack is received. It then skipped processing the syncookie in the final ack which then led to "recv_cookie:0".
The problem is the userspace program did not do accept() and went ahead to close(listen_fd) before the kernel (and the bpf prog) had a chance to process the final ack.
The fix is to add accept() call so that the userspace will wait for the kernel to finish processing the final ack first before close()-ing everything.
--- .../bpf/prog_tests/btf_skc_cls_ingress.c | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-)
tools/testing/selftests/bpf/prog_tests/btf_skc_cls_ingress.c +14 -2
@@ -90,7 +90,7 @@ static void print_err_line(void)static void test_conn (void ) { -int listen_fd =-1 , cli_fd =-1 , err; +int listen_fd =-1 , cli_fd =-1 , srv_fd =-1 , err;socklen_t addrlen =sizeof (srv_sa6);int srv_port;
@@ -112,6 +112,10 @@ static void test_conn(void)if (CHECK_FAIL (cli_fd ==-1 )) goto done; + srv_fd =accept (listen_fd,NULL ,NULL ); +if (CHECK_FAIL (srv_fd ==-1 )) + goto done; + if (CHECK(skel->bss->listen_tp_sport != srv_port || skel->bss->req_sk_sport != srv_port, "Unexpected sk src port",
@@ -134,11 +138,13 @@ static void test_conn(void)close (listen_fd);if (cli_fd !=-1 )close (cli_fd); +if (srv_fd !=-1 ) +close (srv_fd); }static void test_syncookie (void ) { -int listen_fd =-1 , cli_fd =-1 , err; +int listen_fd =-1 , cli_fd =-1 , srv_fd =-1 , err;socklen_t addrlen =sizeof (srv_sa6);int srv_port;
@@ -161,6 +167,10 @@ static void test_syncookie(void)if (CHECK_FAIL (cli_fd ==-1 )) goto done; + srv_fd =accept (listen_fd,NULL ,NULL ); +if (CHECK_FAIL (srv_fd ==-1 )) + goto done; + if (CHECK(skel->bss->listen_tp_sport != srv_port, "Unexpected tp src port", "listen_tp_sport:%u expected:%u\n",
@@ -188,6 +198,8 @@ static void test_syncookie(void)close (listen_fd);if (cli_fd !=-1 )close (cli_fd); +if (srv_fd !=-1 ) +close (srv_fd); }struct test {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 63/99 powerpc/85xx: Fix oops when CONFIG_FSL_PMC=n
In reply to Greg Kroah-HartmanFrom: Xiaoming Ni <[email protected]>
[ Upstream commit 3dc709e518b47386e6af937eaec37bb36539edfd ]
When CONFIG_FSL_PMC is set to n, no value is assigned to cpu_up_prepare in the mpc85xx_pm_ops structure. As a result, oops is triggered in smp_85xx_start_cpu().
smp: Bringing up secondary CPUs ...
kernel tried to execute user page (0) - exploit attempt? (uid: 0)
BUG: Unable to handle kernel instruction fetch (NULL pointer?) Faulting instruction address: 0x00000000 Oops: Kernel access of bad area, sig: 11 [#1] ... NIP [00000000] 0x0 LR [c0021d2c] smp_85xx_kick_cpu+0xe8/0x568 Call Trace: [c1051da8] [c0021cb8] smp_85xx_kick_cpu+0x74/0x568 (unreliable) [c1051de8] [c0011460] __cpu_up+0xc0/0x228 [c1051e18] [c0031bbc] bringup_cpu+0x30/0x224 [c1051e48] [c0031f3c] cpu_up.constprop.0+0x180/0x33c [c1051e88] [c00322e8] bringup_nonboot_cpus+0x88/0xc8 [c1051eb8] [c07e67bc] smp_init+0x30/0x78 [c1051ed8] [c07d9e28] kernel_init_freeable+0x118/0x2a8 [c1051f18] [c00032d8] kernel_init+0x14/0x124 [c1051f38] [c0010278] ret_from_kernel_thread+0x14/0x1c
--- arch/powerpc/platforms/85xx/smp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/powerpc/platforms/85xx/smp.c +2 -2
@@ -220,7 +220,7 @@ static int smp_85xx_start_cpu(int cpu)local_irq_save (flags);hard_irq_disable (); -if (qoriq_pm_ops) +if (qoriq_pm_ops && qoriq_pm_ops->cpu_up_prepare) qoriq_pm_ops->cpu_up_prepare (cpu);/* if cpu is not spinning, reset it */
@@ -292,7 +292,7 @@ static int smp_85xx_kick_cpu(int nr) booting_thread_hwid =cpu_thread_in_core (nr); primary =cpu_first_thread_sibling (nr); -if (qoriq_pm_ops) +if (qoriq_pm_ops && qoriq_pm_ops->cpu_up_prepare) qoriq_pm_ops->cpu_up_prepare (nr);/*
Signature · 1 line
2.34.1
Greg Kroah-Hartman
maintainerPATCH 64/99 USB: gadget: bRequestType is a bitfield, not a enum
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
[ Upstream commit f08adf5add9a071160c68bb2a61d697f39ab0758 ]
Szymon rightly pointed out that the previous check for the endpoint direction in bRequestType was not looking at only the bit involved, but rather the whole value. Normally this is ok, but for some request types, bits other than bit 8 could be set and the check for the endpoint length could not stall correctly.
Fix that up by only checking the single bit.
--- drivers/usb/gadget/composite.c | 6 +++--- drivers/usb/gadget/legacy/dbgp.c | 6 +++--- drivers/usb/gadget/legacy/inode.c | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-)
drivers/usb/gadget/composite.c +3 -3
@@ -1649,14 +1649,14 @@ composite_setup(struct usb_gadget *gadget, const struct usb_ctrlrequest *ctrl)u8 endp;if (w_length >USB_COMP_EP0_BUFSIZ ) { -if (ctrl->bRequestType ==USB_DIR_OUT ) { - goto done; - }else { +if (ctrl->bRequestType &USB_DIR_IN ) {/* Cast away the const, we are going to overwrite on purpose. */ __le16 *temp = (__le16 *)&ctrl->wLength; *temp =cpu_to_le16 (USB_COMP_EP0_BUFSIZ ); w_length =USB_COMP_EP0_BUFSIZ ; + }else { + goto done; } }
drivers/usb/gadget/legacy/dbgp.c +3 -3
@@ -346,14 +346,14 @@ static int dbgp_setup(struct usb_gadget *gadget,u16 len =0 ;if (length >DBGP_REQ_LEN ) { -if (ctrl->bRequestType ==USB_DIR_OUT ) { -return err; - }else { +if (ctrl->bRequestType &USB_DIR_IN ) {/* Cast away the const, we are going to overwrite on purpose. */ __le16 *temp = (__le16 *)&ctrl->wLength; *temp =cpu_to_le16 (DBGP_REQ_LEN ); length =DBGP_REQ_LEN ; + }else { +return err; } }
drivers/usb/gadget/legacy/inode.c +3 -3
@@ -1336,14 +1336,14 @@ gadgetfs_setup (struct usb_gadget *gadget, const struct usb_ctrlrequest *ctrl)u16 w_length =le16_to_cpu (ctrl->wLength);if (w_length >RBUF_SIZE ) { -if (ctrl->bRequestType ==USB_DIR_OUT ) { -return value; - }else { +if (ctrl->bRequestType &USB_DIR_IN ) {/* Cast away the const, we are going to overwrite on purpose. */ __le16 *temp = (__le16 *)&ctrl->wLength; *temp =cpu_to_le16 (RBUF_SIZE ); w_length =RBUF_SIZE ; + }else { +return value; } }
Signature · 1 line
2.34.1
Greg Kroah-Hartman
maintainerPATCH 65/99 Revert "usb: early: convert to readl_poll_timeout_atomic()"
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
[ Upstream commit c4d936efa46d8ea183df16c0f3fa4423327da51d ]
This reverts commit 796eed4b2342c9d6b26c958e92af91253a2390e1.
This change causes boot lockups when using "arlyprintk=xdbc" because ktime can not be used at this point in time in the boot process. Also, it is not needed for very small delays like this.
--- drivers/usb/early/xhci-dbc.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
drivers/usb/early/xhci-dbc.c +11 -4
@@ -14,7 +14,6 @@#include <linux/pci_ids.h> #include <linux/memblock.h> #include <linux/io.h> -#include <linux/iopoll.h> #include <asm/pci-direct.h> #include <asm/fixmap.h> #include <linux/bcd.h>
@@ -136,9 +135,17 @@ static int handshake(void __iomem *ptr, u32 mask, u32 done, int wait, int delay) {u32 result; -return readl_poll_timeout_atomic (ptr, result, - ((result & mask) == done), - delay, wait); +/* Can not use readl_poll_timeout_atomic() for early boot things */ +do { + result =readl (ptr); + result &= mask; +if (result == done) +return 0 ; +udelay (delay); + wait -= delay; + }while (wait >0 ); + +return -ETIMEDOUT ; }static void __init xdbc_bios_handoff (void )
Signature · 1 line
2.34.1
Greg Kroah-Hartman
maintainerPATCH 66/99 KVM: x86: Drop guest CPUID check for host initiated writes to MSR_IA32_PERF_CAPABILITIES
In reply to Greg Kroah-HartmanFrom: Vitaly Kuznetsov <[email protected]>
[ Upstream commit 1aa2abb33a419090c7c87d4ae842a6347078ee12 ]
The ability to write to MSR_IA32_PERF_CAPABILITIES from the host should not depend on guest visible CPUID entries, even if just to allow creating/restoring guest MSRs and CPUIDs in any sequence.
Message-Id: <[email protected]>
--- arch/x86/kvm/x86.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/x86.c +1 -1
@@ -3065,7 +3065,7 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, struct msr_data *msr_info)if (!msr_info->host_initiated)return 1 ; -if (guest_cpuid_has (vcpu,X86_FEATURE_PDCM ) &&kvm_get_msr_feature (&msr_ent)) +if (kvm_get_msr_feature (&msr_ent))return 1 ;if (data & ~msr_ent.data)return 1 ;
Signature · 1 line
2.34.1
Greg Kroah-Hartman
maintainerPATCH 67/99 tty: n_hdlc: make n_hdlc_tty_wakeup() asynchronous
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
commit 1ee33b1ca2b8dabfcc17198ffd049a6b55674a86 upstream.
syzbot is reporting that an unprivileged user who logged in from tty console can crash the system using a reproducer shown below [1], for n_hdlc_tty_wakeup() is synchronously calling n_hdlc_send_frames().
----------
#include <sys/ioctl.h>
#include <unistd.h>
int main(int argc, char *argv[])
{
const int disc = 0xd; ioctl(1, TIOCSETD, &disc);
while (1) {
ioctl(1, TCXONC, 0);
write(1, "", 1);
ioctl(1, TCXONC, 1); /* Kernel panic - not syncing: scheduling while atomic */
} }
----------
Linus suspected that "struct tty_ldisc"->ops->write_wakeup() must not sleep, and Jiri confirmed it from include/linux/tty_ldisc.h. Thus, defer n_hdlc_send_frames() from n_hdlc_tty_wakeup() to a WQ context like net/nfc/nci/uart.c does.
--- drivers/tty/n_hdlc.c | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-)
drivers/tty/n_hdlc.c +22 -1
@@ -139,6 +139,8 @@ struct n_hdlc {struct n_hdlc_buf_list rx_buf_list;struct n_hdlc_buf_list tx_free_buf_list;struct n_hdlc_buf_list rx_free_buf_list; +struct work_struct write_work; +struct tty_struct *tty_for_write_work; };/*
@@ -153,6 +155,7 @@ static struct n_hdlc_buf *n_hdlc_buf_get/* Local functions */ static struct n_hdlc *n_hdlc_alloc (void ); +static void n_hdlc_tty_write_work (struct work_struct *work);/* max frame size for memory allocations */ static int maxframe =4096 ;
@@ -209,6 +212,8 @@ static void n_hdlc_tty_close(struct tty_wake_up_interruptible (&tty->read_wait);wake_up_interruptible (&tty->write_wait); +cancel_work_sync (&n_hdlc->write_work); +n_hdlc_free_buf_list (&n_hdlc->rx_free_buf_list);n_hdlc_free_buf_list (&n_hdlc->tx_free_buf_list);n_hdlc_free_buf_list (&n_hdlc->rx_buf_list);
@@ -240,6 +245,8 @@ static int n_hdlc_tty_open(struct tty_streturn -ENFILE ; } +INIT_WORK (&n_hdlc->write_work, n_hdlc_tty_write_work); + n_hdlc->tty_for_write_work = tty; tty->disc_data = n_hdlc; tty->receive_room =65536 ;
@@ -334,6 +341,20 @@ check_again: }/* end of n_hdlc_send_frames() */ /** +* n_hdlc_tty_write_work - Asynchronous callback for transmit wakeup +* @work: pointer to work_struct +* +* Called when low level device driver can accept more send data. +*/ +static void n_hdlc_tty_write_work (struct work_struct *work) +{ + struct n_hdlc *n_hdlc = container_of(work, struct n_hdlc, write_work); +struct tty_struct *tty = n_hdlc->tty_for_write_work; + +n_hdlc_send_frames (n_hdlc, tty); +}/* end of n_hdlc_tty_write_work() */ + +/** * n_hdlc_tty_wakeup - Callback for transmit wakeup * @tty: pointer to associated tty instance data *
@@ -343,7 +364,7 @@ static void n_hdlc_tty_wakeup(struct tty {struct n_hdlc *n_hdlc = tty->disc_data; -n_hdlc_send_frames (n_hdlc, tty); +schedule_work (&n_hdlc->write_work); }/* end of n_hdlc_tty_wakeup() */ /**
Greg Kroah-Hartman
maintainerPATCH 68/99 USB: NO_LPM quirk Lenovo USB-C to Ethernet Adapher(RTL8153-04)
In reply to Greg Kroah-HartmanFrom: Jimmy Wang <[email protected]>
commit 0ad3bd562bb91853b9f42bda145b5db6255aee90 upstream.
This device doesn't work well with LPM, losing connectivity intermittently. Disable LPM to resolve the issue.
--- drivers/usb/core/quirks.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/usb/core/quirks.c +3 -0
@@ -435,6 +435,9 @@ static const struct usb_device_id usb_qu { USB_DEVICE(0x1532, 0x0116), .driver_info = USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL }, + /* Lenovo USB-C to Ethernet Adapter RTL8153-04 */ + { USB_DEVICE(0x17ef, 0x720c), .driver_info = USB_QUIRK_NO_LPM }, + /* Lenovo Powered USB-C Travel Hub (4X90S92381, RTL8153 GigE) */ { USB_DEVICE(0x17ef, 0x721e), .driver_info = USB_QUIRK_NO_LPM },
Greg Kroah-Hartman
maintainerPATCH 69/99 usb: dwc2: fix STM ID/VBUS detection startup delay in dwc2_driver_probe
In reply to Greg Kroah-HartmanFrom: Amelie Delaunay <[email protected]>
commit fac6bf87c55f7f0733efb0375565fb6a50cf2caf upstream.
When activate_stm_id_vb_detection is enabled, ID and Vbus detection relies on sensing comparators. This detection needs time to stabilize. A delay was already applied in dwc2_resume() when reactivating the detection, but it wasn't done in dwc2_probe().
This patch adds delay after enabling STM ID/VBUS detection. Then, ID state is good when initializing gadget and host, and avoid to get a wrong Connector ID Status Change interrupt.
--- drivers/usb/dwc2/platform.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/usb/dwc2/platform.c +3 -0
@@ -542,6 +542,9 @@ static int dwc2_driver_probe(struct plat ggpio |=GGPIO_STM32_OTG_GCCFG_IDEN ; ggpio |=GGPIO_STM32_OTG_GCCFG_VBDEN ;dwc2_writel (hsotg, ggpio,GGPIO ); + +/* ID/VBUS detection startup time */ +usleep_range (5000 ,7000 ); } retval =dwc2_drd_init (hsotg);
Greg Kroah-Hartman
maintainerPATCH 70/99 PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
In reply to Greg Kroah-HartmanFrom: Thomas Gleixner <[email protected]>
commit 94185adbfad56815c2c8401e16d81bdb74a79201 upstream.
PCI_MSIX_FLAGS_MASKALL is set in the MSI-X control register at MSI-X interrupt setup time. It's cleared on success, but the error handling path only clears the PCI_MSIX_FLAGS_ENABLE bit.
That's incorrect as the reset state of the PCI_MSIX_FLAGS_MASKALL bit is zero. That can be observed via lspci:
Capabilities: [b0] MSI-X: Enable- Count=67 Masked+
Clear the bit in the error path to restore the reset state.
--- drivers/pci/msi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pci/msi.c +1 -1
@@ -879,7 +879,7 @@ out_free:free_msi_irqs (dev); out_disable: -pci_msix_clear_and_set_ctrl (dev,PCI_MSIX_FLAGS_ENABLE ,0 ); +pci_msix_clear_and_set_ctrl (dev,PCI_MSIX_FLAGS_MASKALL |PCI_MSIX_FLAGS_ENABLE ,0 );return ret; }
Greg Kroah-Hartman
maintainerPATCH 71/99 PCI/MSI: Mask MSI-X vectors only on success
In reply to Greg Kroah-HartmanFrom: Stefan Roese <[email protected]>
commit 83dbf898a2d45289be875deb580e93050ba67529 upstream.
Masking all unused MSI-X entries is done to ensure that a crash kernel starts from a clean slate, which correponds to the reset state of the device as defined in the PCI-E specificion 3.0 and later:
Vector Control for MSI-X Table Entries
--------------------------------------
"00: Mask bit: When this bit is set, the function is prohibited from
sending a message using this MSI-X Table entry.
...
This bit’s state after reset is 1 (entry is masked)."
A Marvell NVME device fails to deliver MSI interrupts after trying to enable MSI-X interrupts due to that masking. It seems to take the MSI-X mask bits into account even when MSI-X is disabled.
While not specification compliant, this can be cured by moving the masking into the success path, so that the MSI-X table entries stay in device reset state when the MSI-X setup fails.
[ tglx: Move it into the success path, add comment and amend changelog ]
--- drivers/pci/msi.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
drivers/pci/msi.c +10 -3
@@ -828,9 +828,6 @@ static int msix_capability_init(struct p goto out_disable; } -/* Ensure that all table entries are masked. */ -msix_mask_all (base, tsize); - ret =msix_setup_entries (dev, base, entries, nvec, affd);if (ret) goto out_disable;
@@ -853,6 +850,16 @@ static int msix_capability_init(struct p/* Set MSI-X enabled bits and unmask the function */ pci_intx_for_msi (dev,0 ); dev->msix_enabled =1 ; + +/* +* Ensure that all table entries are masked to prevent +* stale entries from firing in a crash kernel. +* +* Done late to deal with a broken Marvell NVME device +* which takes the MSI-X mask bits into account even +* when MSI-X is disabled, which prevents MSI delivery. +*/ +msix_mask_all (base, tsize);pci_msix_clear_and_set_ctrl (dev,PCI_MSIX_FLAGS_MASKALL ,0 );pcibios_free_irq (dev);
Greg Kroah-Hartman
maintainerPATCH 72/99 usb: xhci: Extend support for runtime power management for AMDs Yellow carp.
In reply to Greg Kroah-HartmanFrom: Nehal Bakulchandra Shah <[email protected]>
commit f886d4fbb7c97b8f5f447c92d2dab99c841803c0 upstream.
AMD's Yellow Carp platform has few more XHCI controllers, enable the runtime power management support for the same.
--- drivers/usb/host/xhci-pci.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/usb/host/xhci-pci.c +5 -1
@@ -70,6 +70,8 @@#define PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_4 0x161e#define PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_5 0x15d6#define PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_6 0x15d7 +#define PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_7 0x161c +#define PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_8 0x161f#define PCI_DEVICE_ID_ASMEDIA_1042_XHCI 0x1042#define PCI_DEVICE_ID_ASMEDIA_1042A_XHCI 0x1142
@@ -325,7 +327,9 @@ static void xhci_pci_quirks(struct devic pdev->device ==PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_3 || pdev->device ==PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_4 || pdev->device ==PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_5 || - pdev->device == PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_6)) + pdev->device ==PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_6 || + pdev->device ==PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_7 || + pdev->device == PCI_DEVICE_ID_AMD_YELLOW_CARP_XHCI_8)) xhci->quirks |= XHCI_DEFAULT_PM_RUNTIME_ALLOW;if (xhci->quirks &XHCI_RESET_ON_RESUME )
Greg Kroah-Hartman
maintainerPATCH 73/99 USB: serial: cp210x: fix CP2105 GPIO registration
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 83b67041f3eaf33f98a075249aa7f4c7617c2f85 upstream.
When generalising GPIO support and adding support for CP2102N, the GPIO registration for some CP2105 devices accidentally broke. Specifically, when all the pins of a port are in "modem" mode, and thus unavailable for GPIO use, the GPIO chip would now be registered without having initialised the number of GPIO lines. This would in turn be rejected by gpiolib and some errors messages would be printed (but importantly probe would still succeed).
Fix this by initialising the number of GPIO lines before registering the GPIO chip.
Note that as for the other device types, and as when all CP2105 pins are muxed for LED function, the GPIO chip is registered also when no pins are available for GPIO use.
--- drivers/usb/serial/cp210x.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/usb/serial/cp210x.c +4 -2
@@ -1750,6 +1750,8 @@ static int cp2105_gpioconf_init(struct u/* 2 banks of GPIO - One for the pins taken from each serial port */ if (intf_num ==0 ) { + priv->gc.ngpio =2 ; +if (mode.eci ==CP210X_PIN_MODE_MODEM ) {/* mark all GPIOs of this interface as reserved */ priv->gpio_altfunc =0xff ;
@@ -1760,8 +1762,9 @@ static int cp2105_gpioconf_init(struct u priv->gpio_pushpull = (u8)((le16_to_cpu (config.gpio_mode) &CP210X_ECI_GPIO_MODE_MASK ) >>CP210X_ECI_GPIO_MODE_OFFSET ); - priv->gc.ngpio =2 ; }else if (intf_num ==1 ) { + priv->gc.ngpio =3 ; +if (mode.sci ==CP210X_PIN_MODE_MODEM ) {/* mark all GPIOs of this interface as reserved */ priv->gpio_altfunc =0xff ;
@@ -1772,7 +1775,6 @@ static int cp2105_gpioconf_init(struct u priv->gpio_pushpull = (u8)((le16_to_cpu (config.gpio_mode) &CP210X_SCI_GPIO_MODE_MASK ) >>CP210X_SCI_GPIO_MODE_OFFSET ); - priv->gc.ngpio =3 ; }else {return -ENODEV ; }
Greg Kroah-Hartman
maintainerPATCH 74/99 USB: serial: option: add Telit FN990 compositions
In reply to Greg Kroah-HartmanFrom: Daniele Palmas <[email protected]>
commit 2b503c8598d1b232e7fc7526bce9326d92331541 upstream.
Add the following Telit FN990 compositions:
0x1070: tty, adb, rmnet, tty, tty, tty, tty 0x1071: tty, adb, mbim, tty, tty, tty, tty 0x1072: rndis, tty, adb, tty, tty, tty, tty 0x1073: tty, adb, ecm, tty, tty, tty, tty
--- drivers/usb/serial/option.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/usb/serial/option.c +8 -0
@@ -1219,6 +1219,14 @@ static const struct usb_device_id option .driver_info = NCTRL(2) | RSVD(3) }, { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1063, 0xff), /* Telit LN920 (ECM) */ .driver_info = NCTRL(0) | RSVD(1) }, + { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1070, 0xff), /* Telit FN990 (rmnet) */ + .driver_info = NCTRL(0) | RSVD(1) | RSVD(2) }, + { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1071, 0xff), /* Telit FN990 (MBIM) */ + .driver_info = NCTRL(0) | RSVD(1) }, + { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1072, 0xff), /* Telit FN990 (RNDIS) */ + .driver_info = NCTRL(2) | RSVD(3) }, + { USB_DEVICE_INTERFACE_CLASS(TELIT_VENDOR_ID, 0x1073, 0xff), /* Telit FN990 (ECM) */ + .driver_info = NCTRL(0) | RSVD(1) }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_ME910), .driver_info = NCTRL(0) | RSVD(1) | RSVD(3) }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_ME910_DUAL_MODEM),
Greg Kroah-Hartman
maintainerPATCH 75/99 btrfs: fix memory leak in __add_inode_ref()
In reply to Greg Kroah-HartmanFrom: Jianglei Nie <[email protected]>
commit f35838a6930296fc1988764cfa54cb3f705c0665 upstream.
Line 1169 (#3) allocates a memory chunk for victim_name by kmalloc(), but when the function returns in line 1184 (#4) victim_name allocated by line 1169 (#3) is not freed, which will lead to a memory leak. There is a similar snippet of code in this function as allocating a memory chunk for victim_name in line 1104 (#1) as well as releasing the memory in line 1116 (#2).
We should kfree() victim_name when the return value of backref_in_log() is less than zero and before the function returns in line 1184 (#4).
1057 static inline int __add_inode_ref(struct btrfs_trans_handle *trans,
1058 struct btrfs_root *root, 1059 struct btrfs_path *path, 1060 struct btrfs_root *log_root, 1061 struct btrfs_inode *dir, 1062 struct btrfs_inode *inode, 1063 u64 inode_objectid, u64 parent_objectid, 1064 u64 ref_index, char *name, int namelen, 1065 int *search_done)
1066 {
1104 victim_name = kmalloc(victim_name_len, GFP_NOFS); // #1: kmalloc (victim_name-1)
1105 if (!victim_name)
1106 return -ENOMEM;
1112 ret = backref_in_log(log_root, &search_key,
1113 parent_objectid, victim_name,
1114 victim_name_len);
1115 if (ret < 0) {
1116 kfree(victim_name); // #2: kfree (victim_name-1)
1117 return ret;
1118 } else if (!ret) {
1169 victim_name = kmalloc(victim_name_len, GFP_NOFS); // #3: kmalloc (victim_name-2)
1170 if (!victim_name)
1171 return -ENOMEM;
1180 ret = backref_in_log(log_root, &search_key,
1181 parent_objectid, victim_name,
1182 victim_name_len);
1183 if (ret < 0) {
1184 return ret; // #4: missing kfree (victim_name-2)
1185 } else if (!ret) {
1241 return 0;
1242 }
--- fs/btrfs/tree-log.c | 1 + 1 file changed, 1 insertion(+)
fs/btrfs/tree-log.c +1 -0
@@ -1109,6 +1109,7 @@ again: parent_objectid, victim_name, victim_name_len);if (ret <0 ) { +kfree (victim_name);return ret; }else if (!ret) { ret = -ENOENT ;
Greg Kroah-Hartman
maintainerPATCH 76/99 btrfs: fix double free of anon_dev after failure to create subvolume
In reply to Greg Kroah-HartmanFrom: Filipe Manana <[email protected]>
commit 33fab972497ae66822c0b6846d4f9382938575b6 upstream.
When creating a subvolume, at create_subvol(), we allocate an anonymous device and later call btrfs_get_new_fs_root(), which in turn just calls btrfs_get_root_ref(). There we call btrfs_init_fs_root() which assigns the anonymous device to the root, but if after that call there's an error, when we jump to 'fail' label, we call btrfs_put_root(), which frees the anonymous device and then returns an error that is propagated back to create_subvol(). Than create_subvol() frees the anonymous device again.
When this happens, if the anonymous device was not reallocated after the first time it was freed with btrfs_put_root(), we get a kernel message like the following:
(...)
[13950.282466] BTRFS: error (device dm-0) in create_subvol:663: errno=-5 IO failure [13950.283027] ida_free called for id=65 which is not allocated. [13950.285974] BTRFS info (device dm-0): forced readonly (...)
If the anonymous device gets reallocated by another btrfs filesystem or any other kernel subsystem, then bad things can happen.
So fix this by setting the root's anonymous device to 0 at btrfs_get_root_ref(), before we call btrfs_put_root(), if an error happened.
--- fs/btrfs/disk-io.c | 8 ++++++++ 1 file changed, 8 insertions(+)
fs/btrfs/disk-io.c +8 -0
@@ -1603,6 +1603,14 @@ again: }return root; fail: +/* +* If our caller provided us an anonymous device, then it's his +* responsability to free it in case we fail. So we have to set our +* root's anon_dev to 0 to avoid a double free, once by btrfs_put_root() +* and once again by our caller. +*/ +if (anon_dev) + root->anon_dev =0 ;btrfs_put_root (root);return ERR_PTR (ret); }
Greg Kroah-Hartman
maintainerPATCH 77/99 zonefs: add MODULE_ALIAS_FS
In reply to Greg Kroah-HartmanFrom: Naohiro Aota <[email protected]>
commit 8ffea2599f63fdbee968b894eab78170abf3ec2c upstream.
Add MODULE_ALIAS_FS() to load the module automatically when you do "mount -t zonefs".
--- fs/zonefs/super.c | 1 + 1 file changed, 1 insertion(+)
fs/zonefs/super.c +1 -0
@@ -1799,5 +1799,6 @@ static void __exit zonefs_exit(void)MODULE_AUTHOR ("Damien Le Moal" );MODULE_DESCRIPTION ("Zone file system for zoned block devices" );MODULE_LICENSE ("GPL" ); +MODULE_ALIAS_FS ("zonefs" );module_init (zonefs_init);module_exit (zonefs_exit);
Greg Kroah-Hartman
maintainerPATCH 78/99 iocost: Fix divide-by-zero on donation from low hweight cgroup
In reply to Greg Kroah-HartmanFrom: Tejun Heo <[email protected]>
commit edaa26334c117a584add6053f48d63a988d25a6e upstream.
The donation calculation logic assumes that the donor has non-zero after-donation hweight, so the lowest active hweight a donating cgroup can have is 2 so that it can donate 1 while keeping the other 1 for itself. Earlier, we only donated from cgroups with sizable surpluses so this condition was always true. However, with the precise donation algorithm implemented, f1de2439ec43 ("blk-iocost: revamp donation amount determination") made the donation amount calculation exact enabling even low hweight cgroups to donate.
This means that in rare occasions, a cgroup with active hweight of 1 can enter donation calculation triggering the following warning and then a divide-by-zero oops.
WARNING: CPU: 4 PID: 0 at block/blk-iocost.c:1928 transfer_surpluses.cold+0x0/0x53 [884/94867] ... RIP: 0010:transfer_surpluses.cold+0x0/0x53 Code: 92 ff 48 c7 c7 28 d1 ab b5 65 48 8b 34 25 00 ae 01 00 48 81 c6 90 06 00 00 e8 8b 3f fe ff 48 c7 c0 ea ff ff ff e9 95 ff 92 ff <0f> 0b 48 c7 c7 30 da ab b5 e8 71 3f fe ff 4c 89 e8 4d 85 ed 74 0 4 ... Call Trace: <IRQ> ioc_timer_fn+0x1043/0x1390 call_timer_fn+0xa1/0x2c0 __run_timers.part.0+0x1ec/0x2e0 run_timer_softirq+0x35/0x70 ... iocg: invalid donation weights in /a/b: active=1 donating=1 after=0
Fix it by excluding cgroups w/ active hweight < 2 from donating. Excluding these extreme low hweight donations shouldn't affect work conservation in any meaningful way.
--- block/blk-iocost.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
block/blk-iocost.c +8 -1
@@ -2246,7 +2246,14 @@ static void ioc_timer_fn(struct timer_li hwm =current_hweight_max (iocg); new_hwi =hweight_after_donation (iocg, old_hwi, hwm, usage, &now); -if (new_hwi < hwm) { +/* +* Donation calculation assumes hweight_after_donation +* to be positive, a condition that a donor w/ hwa < 2 +* can't meet. Don't bother with donation if hwa is +* below 2. It's not gonna make a meaningful difference +* anyway. +*/ +if (new_hwi < hwm && hwa >=2 ) { iocg->hweight_donating = hwa; iocg->hweight_after_donation = new_hwi;list_add (&iocg->surplus_list, &surpluses);
Greg Kroah-Hartman
maintainerPATCH 79/99 serial: 8250_fintek: Fix garbled text for console
In reply to Greg Kroah-HartmanFrom: Ji-Ze Hong (Peter Hong) <[email protected]>
commit 6c33ff728812aa18792afffaf2c9873b898e7512 upstream.
Commit fab8a02b73eb ("serial: 8250_fintek: Enable high speed mode on Fintek F81866") introduced support to use high baudrate with Fintek SuperIO UARTs. It'll change clocksources when the UART probed.
But when user add kernel parameter "console=ttyS0,115200 console=tty0" to make the UART as console output, the console will output garbled text after the following kernel message.
[ 3.681188] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
The issue is occurs in following step:
probe_setup_port() -> fintek_8250_goto_highspeed()
It change clocksource from 115200 to 921600 with wrong time, it should change clocksource in set_termios() not in probed. The following 3 patches are implemented change clocksource in fintek_8250_set_termios().
Commit 58178914ae5b ("serial: 8250_fintek: UART dynamic clocksource on Fintek F81216H") Commit 195638b6d44f ("serial: 8250_fintek: UART dynamic clocksource on Fintek F81866") Commit 423d9118c624 ("serial: 8250_fintek: Add F81966 Support")
Due to the high baud rate had implemented above 3 patches and the patch Commit fab8a02b73eb ("serial: 8250_fintek: Enable high speed mode on Fintek F81866") is bugged, So this patch will remove it.
--- drivers/tty/serial/8250/8250_fintek.c | 20 -------------------- 1 file changed, 20 deletions(-)
drivers/tty/serial/8250/8250_fintek.c +0 -20
@@ -290,25 +290,6 @@ static void fintek_8250_set_max_fifo(str } } -static void fintek_8250_goto_highspeed (struct uart_8250_port *uart, -struct fintek_8250 *pdata) -{ -sio_write_reg (pdata,LDN , pdata->index); - -switch (pdata->pid) { -case CHIP_ID_F81966 : -case CHIP_ID_F81866 :/* set uart clock for high speed serial mode */ -sio_write_mask_reg (pdata,F81866_UART_CLK , -F81866_UART_CLK_MASK , -F81866_UART_CLK_14_769MHZ ); - - uart->port.uartclk =921600 *16 ; -break ; -default :/* leave clock speed untouched */ -break ; - } -} -static void fintek_8250_set_termios (struct uart_port *port,struct ktermios *termios,struct ktermios *old)
@@ -430,7 +411,6 @@ static int probe_setup_port(struct fintefintek_8250_set_irq_mode (pdata, level_mode);fintek_8250_set_max_fifo (pdata); -fintek_8250_goto_highspeed (uart, pdata);fintek_8250_exit_key (addr[i]);
Greg Kroah-Hartman
maintainerPATCH 80/99 timekeeping: Really make sure wall_to_monotonic isnt positive
In reply to Greg Kroah-HartmanFrom: Yu Liao <[email protected]>
commit 4e8c11b6b3f0b6a283e898344f154641eda94266 upstream.
Even after commit e1d7ba873555 ("time: Always make sure wall_to_monotonic isn't positive") it is still possible to make wall_to_monotonic positive by running the following code:
int main(void)
{
struct timespec time;
clock_gettime(CLOCK_MONOTONIC, &time);
time.tv_nsec = 0;
clock_settime(CLOCK_REALTIME, &time);
return 0;
}The reason is that the second parameter of timespec64_compare(), ts_delta, may be unnormalized because the delta is calculated with an open coded substraction which causes the comparison of tv_sec to yield the wrong result:
wall_to_monotonic = { .tv_sec = -10, .tv_nsec = 900000000 }
ts_delta = { .tv_sec = -9, .tv_nsec = -900000000 }
That makes timespec64_compare() claim that wall_to_monotonic < ts_delta, but actually the result should be wall_to_monotonic > ts_delta.
After normalization, the result of timespec64_compare() is correct because the tv_sec comparison is not longer misleading:
wall_to_monotonic = { .tv_sec = -10, .tv_nsec = 900000000 }
ts_delta = { .tv_sec = -10, .tv_nsec = 100000000 }
Use timespec64_sub() to ensure that ts_delta is normalized, which fixes the issue.
--- kernel/time/timekeeping.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
kernel/time/timekeeping.c +1 -2
@@ -1310,8 +1310,7 @@ int do_settimeofday64(const struct timestimekeeping_forward_now (tk); xt =tk_xtime (tk); - ts_delta.tv_sec = ts->tv_sec - xt.tv_sec; - ts_delta.tv_nsec = ts->tv_nsec - xt.tv_nsec; + ts_delta =timespec64_sub (*ts, xt);if (timespec64_compare (&tk->wall_to_monotonic, &ts_delta) >0 ) { ret = -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 81/99 libata: if T_LENGTH is zero, dma direction should be DMA_NONE
In reply to Greg Kroah-HartmanFrom: George Kennedy <[email protected]>
commit 5da5231bb47864e5dd6c6731151e98b6ee498827 upstream.
Avoid data corruption by rejecting pass-through commands where T_LENGTH is zero (No data is transferred) and the dma direction is not DMA_NONE.
--- drivers/ata/libata-scsi.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
drivers/ata/libata-scsi.c +13 -2
@@ -2870,8 +2870,19 @@ static unsigned int ata_scsi_pass_thru(s goto invalid_fld; } -if (ata_is_ncq (tf->protocol) && (cdb[2 + cdb_offset] &0x3 ) ==0 ) - tf->protocol =ATA_PROT_NCQ_NODATA ; +if ((cdb[2 + cdb_offset] &0x3 ) ==0 ) { +/* +* When T_LENGTH is zero (No data is transferred), dir should +* be DMA_NONE. +*/ +if (scmd->sc_data_direction !=DMA_NONE ) { + fp =2 + cdb_offset; + goto invalid_fld; + } + +if (ata_is_ncq (tf->protocol)) + tf->protocol =ATA_PROT_NCQ_NODATA ; + }/* enable LBA */ tf->flags |=ATA_TFLAG_LBA ;
Greg Kroah-Hartman
maintainerPATCH 82/99 drm/amdgpu: correct register access for RLC_JUMP_TABLE_RESTORE
In reply to Greg Kroah-HartmanFrom: Le Ma <[email protected]>
commit f3a8076eb28cae1553958c629aecec479394bbe2 upstream.
should count on GC IP base address
--- drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c +2 -2
@@ -3002,8 +3002,8 @@ static void gfx_v9_0_init_pg(struct amdg AMD_PG_SUPPORT_CP | AMD_PG_SUPPORT_GDS | AMD_PG_SUPPORT_RLC_SMU_HS)) { -WREG32 (mmRLC_JUMP_TABLE_RESTORE, - adev->gfx.rlc.cp_table_gpu_addr >>8 ); +WREG32_SOC15 (GC ,0 , mmRLC_JUMP_TABLE_RESTORE, + adev->gfx.rlc.cp_table_gpu_addr >>8 );gfx_v9_0_init_gfx_power_gating (adev); } }
Greg Kroah-Hartman
maintainerPATCH 83/99 Input: touchscreen - avoid bitwise vs logical OR warning
In reply to Greg Kroah-HartmanFrom: Nathan Chancellor <[email protected]>
commit a02dcde595f7cbd240ccd64de96034ad91cffc40 upstream.
A new warning in clang points out a few places in this driver where a bitwise OR is being used with boolean types:
drivers/input/touchscreen.c:81:17: warning: use of bitwise '|' with boolean operands [-Wbitwise-instead-of-logical]
data_present = touchscreen_get_prop_u32(dev, "touchscreen-min-x",
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This use of a bitwise OR is intentional, as bitwise operations do not short circuit, which allows all the calls to touchscreen_get_prop_u32() to happen so that the last parameter is initialized while coalescing the results of the calls to make a decision after they are all evaluated.
To make this clearer to the compiler, use the '|=' operator to assign the result of each touchscreen_get_prop_u32() call to data_present, which keeps the meaning of the code the same but makes it obvious that every one of these calls is expected to happen.
--- drivers/input/touchscreen/of_touchscreen.c | 42 ++++++++++++++--------------- 1 file changed, 21 insertions(+), 21 deletions(-)
drivers/input/touchscreen/of_touchscreen.c +21 -21
@@ -79,27 +79,27 @@ void touchscreen_parse_properties(struct data_present =touchscreen_get_prop_u32 (dev,"touchscreen-min-x" ,input_abs_get_min (input, axis_x), - &minimum) | -touchscreen_get_prop_u32 (dev,"touchscreen-size-x" , -input_abs_get_max (input, - axis_x) +1 , - &maximum) | -touchscreen_get_prop_u32 (dev,"touchscreen-fuzz-x" , -input_abs_get_fuzz (input, axis_x), - &fuzz); + &minimum); + data_present |=touchscreen_get_prop_u32 (dev,"touchscreen-size-x" , +input_abs_get_max (input, + axis_x) +1 , + &maximum); + data_present |=touchscreen_get_prop_u32 (dev,"touchscreen-fuzz-x" , +input_abs_get_fuzz (input, axis_x), + &fuzz);if (data_present)touchscreen_set_params (input, axis_x, minimum, maximum -1 , fuzz); data_present =touchscreen_get_prop_u32 (dev,"touchscreen-min-y" ,input_abs_get_min (input, axis_y), - &minimum) | -touchscreen_get_prop_u32 (dev,"touchscreen-size-y" , -input_abs_get_max (input, - axis_y) +1 , - &maximum) | -touchscreen_get_prop_u32 (dev,"touchscreen-fuzz-y" , -input_abs_get_fuzz (input, axis_y), - &fuzz); + &minimum); + data_present |=touchscreen_get_prop_u32 (dev,"touchscreen-size-y" , +input_abs_get_max (input, + axis_y) +1 , + &maximum); + data_present |=touchscreen_get_prop_u32 (dev,"touchscreen-fuzz-y" , +input_abs_get_fuzz (input, axis_y), + &fuzz);if (data_present)touchscreen_set_params (input, axis_y, minimum, maximum -1 , fuzz);
@@ -107,11 +107,11 @@ void touchscreen_parse_properties(struct data_present =touchscreen_get_prop_u32 (dev,"touchscreen-max-pressure" ,input_abs_get_max (input, axis), - &maximum) | -touchscreen_get_prop_u32 (dev, -"touchscreen-fuzz-pressure" , -input_abs_get_fuzz (input, axis), - &fuzz); + &maximum); + data_present |=touchscreen_get_prop_u32 (dev, +"touchscreen-fuzz-pressure" , +input_abs_get_fuzz (input, axis), + &fuzz);if (data_present)touchscreen_set_params (input, axis,0 , maximum, fuzz);
Greg Kroah-Hartman
maintainerPATCH 84/99 ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
In reply to Greg Kroah-HartmanFrom: Fabio Estevam <[email protected]>
commit 737e65c7956795b3553781fb7bc82fce1c39503f upstream.
According to the i.MX6ULL Reference Manual, pad CSI_DATA07 may have the ESAI_TX0 functionality, not ESAI_T0.
Also, NXP's i.MX Config Tools 10.0 generates dtsi with the MX6ULL_PAD_CSI_DATA07__ESAI_TX0 naming, so fix it accordingly.
There are no devicetree users in mainline that use the old name, so just remove the old entry.
--- arch/arm/boot/dts/imx6ull-pinfunc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/imx6ull-pinfunc.h +1 -1
@@ -82,6 +82,6 @@#define MX6ULL_PAD_CSI_DATA04__ESAI_TX_FS 0x01F4 0x0480 0x0000 0x9 0x0#define MX6ULL_PAD_CSI_DATA05__ESAI_TX_CLK 0x01F8 0x0484 0x0000 0x9 0x0#define MX6ULL_PAD_CSI_DATA06__ESAI_TX5_RX0 0x01FC 0x0488 0x0000 0x9 0x0 -#define MX6ULL_PAD_CSI_DATA07__ESAI_T0 0x0200 0x048C 0x0000 0x9 0x0 +#define MX6ULL_PAD_CSI_DATA07__ESAI_TX0 0x0200 0x048C 0x0000 0x9 0x0#endif /* __DTS_IMX6ULL_PINFUNC_H */
Greg Kroah-Hartman
maintainerPATCH 85/99 xsk: Do not sleep in poll() when need_wakeup set
In reply to Greg Kroah-HartmanFrom: Magnus Karlsson <[email protected]>
commit bd0687c18e635b63233dc87f38058cd728802ab4 upstream.
Do not sleep in poll() when the need_wakeup flag is set. When this flag is set, the application needs to explicitly wake up the driver with a syscall (poll, recvmsg, sendmsg, etc.) to guarantee that Rx and/or Tx processing will be processed promptly. But the current code in poll(), sleeps first then wakes up the driver. This means that no driver processing will occur (baring any interrupts) until the timeout has expired.
Fix this by checking the need_wakeup flag first and if set, wake the driver and return to the application. Only if need_wakeup is not set should the process sleep if there is a timeout set in the poll() call.
--- net/xdp/xsk.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/xdp/xsk.c +2 -2
@@ -499,8 +499,6 @@ static __poll_t xsk_poll(struct file *fistruct xdp_sock *xs =xdp_sk (sk);struct xsk_buff_pool *pool; -sock_poll_wait (file, sock, wait); -if (unlikely (!xsk_is_bound (xs)))return mask;
@@ -512,6 +510,8 @@ static __poll_t xsk_poll(struct file *fielse /* Poll needs to drive Tx also in copy mode */ __xsk_sendmsg (sk); + }else { +sock_poll_wait (file, sock, wait); }if (xs->rx && !xskq_prod_is_empty (xs->rx))
Greg Kroah-Hartman
maintainerPATCH 86/99 media: mxl111sf: change mutex_init() location
In reply to Greg Kroah-HartmanFrom: Pavel Skripkin <[email protected]>
commit 44870a9e7a3c24acbb3f888b2a7cc22c9bdf7e7f upstream.
Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location.
Previous mutex_init(&state->msg_lock) call was in ->init() function, but dvb_usbv2_init() has this order of calls:
dvb_usbv2_init() dvb_usbv2_adapter_init() dvb_usbv2_adapter_frontend_init() props->frontend_attach() props->init()
Since mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach() internally we need to initialize state->msg_lock before frontend_attach(). To achieve it, ->probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.
--- drivers/media/usb/dvb-usb-v2/mxl111sf.c | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-)
drivers/media/usb/dvb-usb-v2/mxl111sf.c +14 -2
@@ -931,8 +931,6 @@ static int mxl111sf_init(struct dvb_usb_ .len = sizeof(eeprom), .buf = eeprom }, }; -mutex_init (&state->msg_lock); - ret =get_chip_info (state);if (mxl_fail (ret))pr_err ("failed to get chip info during probe" );
@@ -1074,6 +1072,14 @@ static int mxl111sf_get_stream_config_dvreturn 0 ; } +static int mxl111sf_probe (struct dvb_usb_device *dev) +{ +struct mxl111sf_state *state =d_to_priv (dev); + +mutex_init (&state->msg_lock); +return 0 ; +} +static struct dvb_usb_device_properties mxl111sf_props_dvbt = { .driver_name =KBUILD_MODNAME , .owner =THIS_MODULE ,
@@ -1083,6 +1089,7 @@ static struct dvb_usb_device_properties .generic_bulk_ctrl_endpoint = 0x02, .generic_bulk_ctrl_endpoint_response = 0x81, + .probe = mxl111sf_probe, .i2c_algo = &mxl111sf_i2c_algo, .frontend_attach = mxl111sf_frontend_attach_dvbt, .tuner_attach = mxl111sf_attach_tuner,
@@ -1124,6 +1131,7 @@ static struct dvb_usb_device_properties .generic_bulk_ctrl_endpoint = 0x02, .generic_bulk_ctrl_endpoint_response = 0x81, + .probe = mxl111sf_probe, .i2c_algo = &mxl111sf_i2c_algo, .frontend_attach = mxl111sf_frontend_attach_atsc, .tuner_attach = mxl111sf_attach_tuner,
@@ -1165,6 +1173,7 @@ static struct dvb_usb_device_properties .generic_bulk_ctrl_endpoint = 0x02, .generic_bulk_ctrl_endpoint_response = 0x81, + .probe = mxl111sf_probe, .i2c_algo = &mxl111sf_i2c_algo, .frontend_attach = mxl111sf_frontend_attach_mh, .tuner_attach = mxl111sf_attach_tuner,
@@ -1233,6 +1242,7 @@ static struct dvb_usb_device_properties .generic_bulk_ctrl_endpoint = 0x02, .generic_bulk_ctrl_endpoint_response = 0x81, + .probe = mxl111sf_probe, .i2c_algo = &mxl111sf_i2c_algo, .frontend_attach = mxl111sf_frontend_attach_atsc_mh, .tuner_attach = mxl111sf_attach_tuner,
@@ -1311,6 +1321,7 @@ static struct dvb_usb_device_properties .generic_bulk_ctrl_endpoint = 0x02, .generic_bulk_ctrl_endpoint_response = 0x81, + .probe = mxl111sf_probe, .i2c_algo = &mxl111sf_i2c_algo, .frontend_attach = mxl111sf_frontend_attach_mercury, .tuner_attach = mxl111sf_attach_tuner,
@@ -1381,6 +1392,7 @@ static struct dvb_usb_device_properties .generic_bulk_ctrl_endpoint = 0x02, .generic_bulk_ctrl_endpoint_response = 0x81, + .probe = mxl111sf_probe, .i2c_algo = &mxl111sf_i2c_algo, .frontend_attach = mxl111sf_frontend_attach_mercury_mh, .tuner_attach = mxl111sf_attach_tuner,
Greg Kroah-Hartman
maintainerPATCH 87/99 fuse: annotate lock in fuse_reverse_inval_entry()
In reply to Greg Kroah-HartmanFrom: Miklos Szeredi <[email protected]>
commit bda9a71980e083699a0360963c0135657b73f47a upstream.
Add missing inode lock annotatation; found by syzbot.
--- fs/fuse/dir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/fuse/dir.c +1 -1
@@ -1132,7 +1132,7 @@ int fuse_reverse_inval_entry(struct fuseif (!parent)return -ENOENT ; -inode_lock (parent); +inode_lock_nested (parent,I_MUTEX_PARENT );if (!S_ISDIR (parent->i_mode)) goto unlock;
Greg Kroah-Hartman
maintainerPATCH 88/99 ovl: fix warning in ovl_create_real()
In reply to Greg Kroah-HartmanFrom: Miklos Szeredi <[email protected]>
commit 1f5573cfe7a7056e80a92c7a037a3e69f3a13d1c upstream.
Syzbot triggered the following warning in ovl_workdir_create() -> ovl_create_real():
if (!err && WARN_ON(!newdentry->d_inode)) {The reason is that the cgroup2 filesystem returns from mkdir without instantiating the new dentry.
Weird filesystems such as this will be rejected by overlayfs at a later stage during setup, but to prevent such a warning, call ovl_mkdir_real() directly from ovl_workdir_create() and reject this case early.
--- fs/overlayfs/dir.c | 3 +-- fs/overlayfs/overlayfs.h | 1 + fs/overlayfs/super.c | 12 ++++++++---- 3 files changed, 10 insertions(+), 6 deletions(-)
fs/overlayfs/dir.c +1 -2
@@ -137,8 +137,7 @@ kill_whiteout: goto out; } -static int ovl_mkdir_real (struct inode *dir,struct dentry **newdentry, -umode_t mode) +int ovl_mkdir_real (struct inode *dir,struct dentry **newdentry,umode_t mode) {int err;struct dentry *d, *dentry = *newdentry;
fs/overlayfs/overlayfs.h +1 -0
@@ -519,6 +519,7 @@ struct ovl_cattr {#define OVL_CATTR (m) (&(struct ovl_cattr) { .mode = (m) }) +int ovl_mkdir_real (struct inode *dir,struct dentry **newdentry,umode_t mode);struct dentry *ovl_create_real (struct inode *dir,struct dentry *newdentry,struct ovl_cattr *attr);int ovl_cleanup (struct inode *dir,struct dentry *dentry);
fs/overlayfs/super.c +8 -4
@@ -743,10 +743,14 @@ retry: goto retry; } - work =ovl_create_real (dir, work,OVL_CATTR (attr.ia_mode)); - err =PTR_ERR (work); -if (IS_ERR (work)) - goto out_err; + err =ovl_mkdir_real (dir, &work, attr.ia_mode); +if (err) + goto out_dput; + +/* Weird filesystem returning with hashed negative (kernfs)? */ + err = -EINVAL ; +if (d_really_is_negative (work)) + goto out_dput;/* * Try to remove POSIX ACL xattrs from workdir. We are good if:
Greg Kroah-Hartman
maintainerPATCH 89/99 scsi: scsi_debug: Dont call kcalloc() if size arg is zero
In reply to Greg Kroah-HartmanFrom: George Kennedy <[email protected]>
commit 3344b58b53a76199dae48faa396e9fc37bf86992 upstream.
If the size arg to kcalloc() is zero, it returns ZERO_SIZE_PTR. Because of that, for a following NULL pointer check to work on the returned pointer, kcalloc() must not be called with the size arg equal to zero. Return early without error before the kcalloc() call if size arg is zero.
BUG: KASAN: null-ptr-deref in memcpy include/linux/fortify-string.h:191 [inline] BUG: KASAN: null-ptr-deref in sg_copy_buffer+0x138/0x240 lib/scatterlist.c:974 Write of size 4 at addr 0000000000000010 by task syz-executor.1/22789 CPU: 1 PID: 22789 Comm: syz-executor.1 Not tainted 5.15.0-syzk #1 Hardware name: Red Hat KVM, BIOS 1.13.0-2 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106 __kasan_report mm/kasan/report.c:446 [inline] kasan_report.cold.14+0x112/0x117 mm/kasan/report.c:459 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x1a3/0x210 mm/kasan/generic.c:189 memcpy+0x3b/0x60 mm/kasan/shadow.c:66 memcpy include/linux/fortify-string.h:191 [inline] sg_copy_buffer+0x138/0x240 lib/scatterlist.c:974 do_dout_fetch drivers/scsi/scsi_debug.c:2954 [inline] do_dout_fetch drivers/scsi/scsi_debug.c:2946 [inline] resp_verify+0x49e/0x930 drivers/scsi/scsi_debug.c:4276 schedule_resp+0x4d8/0x1a70 drivers/scsi/scsi_debug.c:5478 scsi_debug_queuecommand+0x8c9/0x1ec0 drivers/scsi/scsi_debug.c:7533 scsi_dispatch_cmd drivers/scsi/scsi_lib.c:1520 [inline] scsi_queue_rq+0x16b0/0x2d40 drivers/scsi/scsi_lib.c:1699 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1639 __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325 blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1761 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1838 blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:62 blk_execute_rq+0xdb/0x360 block/blk-exec.c:102 sg_scsi_ioctl drivers/scsi/scsi_ioctl.c:621 [inline] scsi_ioctl+0x8bb/0x15c0 drivers/scsi/scsi_ioctl.c:930 sg_ioctl_common+0x172d/0x2710 drivers/scsi/sg.c:1112 sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1165 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae
--- drivers/scsi/scsi_debug.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/scsi/scsi_debug.c +4 -0
@@ -4238,6 +4238,8 @@ static int resp_verify(struct scsi_cmndmk_sense_invalid_opcode (scp);return check_condition_result; } +if (vnum ==0 ) +return 0 ;/* not an error */ a_num = is_bytchk3 ?1 : vnum;/* Treat following check like one for read (i.e. no write) access */ ret =check_device_access_params (scp, lba, a_num, false);
@@ -4301,6 +4303,8 @@ static int resp_report_zones(struct scsi } zs_lba =get_unaligned_be64 (cmd +2 ); alloc_len =get_unaligned_be32 (cmd +10 ); +if (alloc_len ==0 ) +return 0 ;/* not an error */ rep_opts = cmd[14 ] &0x3f ; partial = cmd[14 ] &0x80 ;
Greg Kroah-Hartman
maintainerPATCH 90/99 scsi: scsi_debug: Fix type in min_t to avoid stack OOB
In reply to Greg Kroah-HartmanFrom: George Kennedy <[email protected]>
commit 36e07d7ede88a1f1ef8f0f209af5b7612324ac2c upstream.
Change min_t() to use type "u32" instead of type "int" to avoid stack out of bounds. With min_t() type "int" the values get sign extended and the larger value gets used causing stack out of bounds.
BUG: KASAN: stack-out-of-bounds in memcpy include/linux/fortify-string.h:191 [inline] BUG: KASAN: stack-out-of-bounds in sg_copy_buffer+0x1de/0x240 lib/scatterlist.c:976 Read of size 127 at addr ffff888072607128 by task syz-executor.7/18707 CPU: 1 PID: 18707 Comm: syz-executor.7 Not tainted 5.15.0-syzk #1 Hardware name: Red Hat KVM, BIOS 1.13.0-2 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:106 print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:256 __kasan_report mm/kasan/report.c:442 [inline] kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:459 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0x1a3/0x210 mm/kasan/generic.c:189 memcpy+0x23/0x60 mm/kasan/shadow.c:65 memcpy include/linux/fortify-string.h:191 [inline] sg_copy_buffer+0x1de/0x240 lib/scatterlist.c:976 sg_copy_from_buffer+0x33/0x40 lib/scatterlist.c:1000 fill_from_dev_buffer.part.34+0x82/0x130 drivers/scsi/scsi_debug.c:1162 fill_from_dev_buffer drivers/scsi/scsi_debug.c:1888 [inline] resp_readcap16+0x365/0x3b0 drivers/scsi/scsi_debug.c:1887 schedule_resp+0x4d8/0x1a70 drivers/scsi/scsi_debug.c:5478 scsi_debug_queuecommand+0x8c9/0x1ec0 drivers/scsi/scsi_debug.c:7533 scsi_dispatch_cmd drivers/scsi/scsi_lib.c:1520 [inline] scsi_queue_rq+0x16b0/0x2d40 drivers/scsi/scsi_lib.c:1699 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1639 __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325 blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1761 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1838 blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:62 sg_common_write.isra.18+0xeb3/0x2000 drivers/scsi/sg.c:836 sg_new_write.isra.19+0x570/0x8c0 drivers/scsi/sg.c:774 sg_ioctl_common+0x14d6/0x2710 drivers/scsi/sg.c:939 sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1165 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae
--- drivers/scsi/scsi_debug.c | 34 +++++++++++++++++++--------------- 1 file changed, 19 insertions(+), 15 deletions(-)
drivers/scsi/scsi_debug.c +19 -15
@@ -1188,7 +1188,7 @@ static int p_fill_from_dev_buffer(struct __func__, off_dst,scsi_bufflen (scp), act_len, scsi_get_resid(scp)); n =scsi_bufflen (scp) - (off_dst + act_len); -scsi_set_resid (scp,min_t (int,scsi_get_resid (scp), n)); +scsi_set_resid (scp,min_t (u32,scsi_get_resid (scp), n));return 0 ; }
@@ -1561,7 +1561,8 @@ static int resp_inquiry(struct scsi_cmndunsigned char pq_pdt;unsigned char *arr;unsigned char *cmd = scp->cmnd; -int alloc_len, n, ret; +u32 alloc_len, n; +int ret;bool have_wlun, is_disk, is_zbc, is_disk_zbc; alloc_len =get_unaligned_be16 (cmd +3 );
@@ -1584,7 +1585,8 @@ static int resp_inquiry(struct scsi_cmndkfree (arr);return check_condition_result; }else if (0x1 & cmd[1 ]) {/* EVPD bit set */ -int lu_id_num, port_group_id, target_dev_id, len; +int lu_id_num, port_group_id, target_dev_id; +u32 len;char lu_id_str[6 ];int host_no = devip->sdbg_host->shost->host_no;
@@ -1675,9 +1677,9 @@ static int resp_inquiry(struct scsi_cmndkfree (arr);return check_condition_result; } - len =min (get_unaligned_be16 (arr +2 ) +4 , alloc_len); + len =min_t (u32,get_unaligned_be16 (arr +2 ) +4 , alloc_len); ret =fill_from_dev_buffer (scp, arr, -min (len,SDEBUG_MAX_INQ_ARR_SZ )); +min_t (u32, len,SDEBUG_MAX_INQ_ARR_SZ ));kfree (arr);return ret; }
@@ -1713,7 +1715,7 @@ static int resp_inquiry(struct scsi_cmnd }put_unaligned_be16 (0x2100 , arr + n);/* SPL-4 no version claimed */ ret =fill_from_dev_buffer (scp, arr, -min_t (int, alloc_len,SDEBUG_LONG_INQ_SZ )); +min_t (u32, alloc_len,SDEBUG_LONG_INQ_SZ ));kfree (arr);return ret; }
@@ -1728,8 +1730,8 @@ static int resp_requests(struct scsi_cmnunsigned char *cmd = scp->cmnd;unsigned char arr[SCSI_SENSE_BUFFERSIZE ];/* assume >= 18 bytes */ bool dsense = !!(cmd[1 ] &1 ); -int alloc_len = cmd[4 ]; -int len =18 ; +u32 alloc_len = cmd[4 ]; +u32 len =18 ;int stopped_state =atomic_read (&devip->stopped);memset (arr,0 ,sizeof (arr));
@@ -1773,7 +1775,7 @@ static int resp_requests(struct scsi_cmn arr[7 ] =0xa ; } } -return fill_from_dev_buffer (scp, arr,min_t (int, len, alloc_len)); +return fill_from_dev_buffer (scp, arr,min_t (u32, len, alloc_len)); }static int resp_start_stop (struct scsi_cmnd *scp,struct sdebug_dev_info *devip)
@@ -2311,7 +2313,8 @@ static int resp_mode_sense(struct scsi_c {int pcontrol, pcode, subpcode, bd_len;unsigned char dev_spec; -int alloc_len, offset, len, target_dev_id; +u32 alloc_len, offset, len; +int target_dev_id;int target = scp->device->id;unsigned char *ap;unsigned char arr[SDEBUG_MAX_MSENSE_SZ ];
@@ -2467,7 +2470,7 @@ static int resp_mode_sense(struct scsi_c arr[0 ] = offset -1 ; else put_unaligned_be16((offset - 2), arr + 0); -return fill_from_dev_buffer (scp, arr,min_t (int, alloc_len, offset)); +return fill_from_dev_buffer (scp, arr,min_t (u32, alloc_len, offset)); }#define SDEBUG_MAX_MSELECT_SZ 512
@@ -2582,7 +2585,8 @@ static int resp_ie_l_pg(unsigned char *astatic int resp_log_sense (struct scsi_cmnd *scp,struct sdebug_dev_info *devip) { -int ppc, sp, pcode, subpcode, alloc_len, len, n; +int ppc, sp, pcode, subpcode; +u32 alloc_len, len, n;unsigned char arr[SDEBUG_MAX_LSENSE_SZ ];unsigned char *cmd = scp->cmnd;
@@ -2652,9 +2656,9 @@ static int resp_log_sense(struct scsi_cmmk_sense_invalid_fld (scp,SDEB_IN_CDB ,3 ,-1 );return check_condition_result; } - len =min_t (int,get_unaligned_be16 (arr +2 ) +4 , alloc_len); + len =min_t (u32,get_unaligned_be16 (arr +2 ) +4 , alloc_len);return fill_from_dev_buffer (scp, arr, -min_t (int, len,SDEBUG_MAX_INQ_ARR_SZ )); +min_t (u32, len,SDEBUG_MAX_INQ_ARR_SZ )); }static inline bool sdebug_dev_is_zoned (struct sdebug_dev_info *devip)
@@ -4409,7 +4413,7 @@ static int resp_report_zones(struct scsiput_unaligned_be64 (sdebug_capacity -1 , arr +8 ); rep_len = (unsigned long )desc - (unsigned long )arr; - ret =fill_from_dev_buffer (scp, arr,min_t (int, alloc_len, rep_len)); + ret =fill_from_dev_buffer (scp, arr,min_t (u32, alloc_len, rep_len)); fini:read_unlock (macc_lckp);
Greg Kroah-Hartman
maintainerPATCH 91/99 scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()
In reply to Greg Kroah-HartmanFrom: George Kennedy <[email protected]>
commit e0a2c28da11e2c2b963fc01d50acbf03045ac732 upstream.
In resp_mode_select() sanity check the block descriptor len to avoid UAF.
BUG: KASAN: use-after-free in resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509 Read of size 1 at addr ffff888026670f50 by task scsicmd/15032 CPU: 1 PID: 15032 Comm: scsicmd Not tainted 5.15.0-01d0625 #15 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Call Trace: <TASK> dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:107 print_address_description.constprop.9+0x28/0x160 mm/kasan/report.c:257 kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:443 __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:306 resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509 schedule_resp+0x4af/0x1a10 drivers/scsi/scsi_debug.c:5483 scsi_debug_queuecommand+0x8c9/0x1e70 drivers/scsi/scsi_debug.c:7537 scsi_queue_rq+0x16b4/0x2d10 drivers/scsi/scsi_lib.c:1521 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1640 __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325 blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/0x150 block/blk-mq.c:1762 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1839 blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:63 sg_common_write.isra.18+0xeb3/0x2000 drivers/scsi/sg.c:837 sg_new_write.isra.19+0x570/0x8c0 drivers/scsi/sg.c:775 sg_ioctl_common+0x14d6/0x2710 drivers/scsi/sg.c:941 sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1166 __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:52 do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:50 entry_SYSCALL_64_after_hwframe+0x44/0xae arch/x86/entry/entry_64.S:113
--- drivers/scsi/scsi_debug.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/scsi/scsi_debug.c +2 -2
@@ -2501,11 +2501,11 @@ static int resp_mode_select(struct scsi_ __func__, param_len, res); md_len = mselect6 ? (arr[0 ] +1 ) : (get_unaligned_be16 (arr +0 ) +2 ); bd_len = mselect6 ? arr[3 ] :get_unaligned_be16 (arr +6 ); -if (md_len >2 ) { + off = bd_len + (mselect6 ?4 :8 ); +if (md_len >2 || off >= res) {mk_sense_invalid_fld (scp,SDEB_IN_DATA ,0 ,-1 );return check_condition_result; } - off = bd_len + (mselect6 ?4 :8 ); mpage = arr[off] &0x3f ; ps = !!(arr[off] &0x80 );if (ps) {
Greg Kroah-Hartman
maintainerPATCH 92/99 rcu: Mark accesses to rcu_state.n_force_qs
In reply to Greg Kroah-HartmanFrom: Paul E. McKenney <[email protected]>
commit 2431774f04d1050292054c763070021bade7b151 upstream.
This commit marks accesses to the rcu_state.n_force_qs. These data races are hard to make happen, but syzkaller was equal to the task.
--- kernel/rcu/tree.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
kernel/rcu/tree.c +5 -5
@@ -1888,7 +1888,7 @@ static void rcu_gp_fqs(bool first_time)struct rcu_node *rnp =rcu_get_root ();WRITE_ONCE (rcu_state.gp_activity, jiffies); - rcu_state.n_force_qs++; +WRITE_ONCE (rcu_state.n_force_qs, rcu_state.n_force_qs +1 );if (first_time) {/* Collect dyntick-idle snapshots. */ force_qs_rnp (dyntick_save_progress_counter);
@@ -2530,7 +2530,7 @@ static void rcu_do_batch(struct rcu_data/* Reset ->qlen_last_fqs_check trigger if enough CBs have drained. */ if (count ==0 && rdp->qlen_last_fqs_check !=0 ) { rdp->qlen_last_fqs_check =0 ; - rdp->n_force_qs_snap = rcu_state.n_force_qs; + rdp->n_force_qs_snap =READ_ONCE (rcu_state.n_force_qs); }else if (count < rdp->qlen_last_fqs_check - qhimark) rdp->qlen_last_fqs_check = count;
@@ -2876,10 +2876,10 @@ static void __call_rcu_core(struct rcu_d }else {/* Give the grace period a kick. */ rdp->blimit =DEFAULT_MAX_RCU_BLIMIT ; -if (rcu_state.n_force_qs == rdp->n_force_qs_snap && +if (READ_ONCE (rcu_state.n_force_qs) == rdp->n_force_qs_snap &&rcu_segcblist_first_pend_cb (&rdp->cblist) != head)rcu_force_quiescent_state (); - rdp->n_force_qs_snap = rcu_state.n_force_qs; + rdp->n_force_qs_snap =READ_ONCE (rcu_state.n_force_qs); rdp->qlen_last_fqs_check =rcu_segcblist_n_cbs (&rdp->cblist); } }
@@ -3986,7 +3986,7 @@ int rcutree_prepare_cpu(unsigned int cpu/* Set up local state, ensuring consistent view of global state. */ raw_spin_lock_irqsave_rcu_node (rnp, flags); rdp->qlen_last_fqs_check =0 ; - rdp->n_force_qs_snap = rcu_state.n_force_qs; + rdp->n_force_qs_snap =READ_ONCE (rcu_state.n_force_qs); rdp->blimit = blimit;if (rcu_segcblist_empty (&rdp->cblist) &&/* No early-boot CBs? */ !rcu_segcblist_is_offloaded (&rdp->cblist))
Greg Kroah-Hartman
maintainerPATCH 93/99 bus: ti-sysc: Fix variable set but not used warning for reinit_modules
In reply to Greg Kroah-HartmanFrom: Tony Lindgren <[email protected]>
commit 1b1da99b845337362a3dafe0f7b49927ab4ae041 upstream.
Fix drivers/bus/ti-sysc.c:2494:13: error: variable 'error' set but not used introduced by commit 9d881361206e ("bus: ti-sysc: Add quirk handling for reinit on context lost").
--- drivers/bus/ti-sysc.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/bus/ti-sysc.c +1 -2
@@ -2443,12 +2443,11 @@ static void sysc_reinit_modules(struct sstruct sysc_module *module;struct list_head *pos;struct sysc *ddata; -int error =0 ;list_for_each (pos, &sysc_soc->restored_modules) { module = list_entry(pos, struct sysc_module, node); ddata = module->ddata; - error =sysc_reinit_module (ddata, ddata->enabled); +sysc_reinit_module (ddata, ddata->enabled); } }
Greg Kroah-Hartman
maintainerPATCH 94/99 Revert "xsk: Do not sleep in poll() when need_wakeup set"
In reply to Greg Kroah-HartmanFrom: Magnus Karlsson <[email protected]>
commit 0706a78f31c4217ca144f630063ec9561a21548d upstream.
This reverts commit bd0687c18e635b63233dc87f38058cd728802ab4.
This patch causes a Tx only workload to go to sleep even when it does not have to, leading to misserable performance in skb mode. It fixed one rare problem but created a much worse one, so this need to be reverted while I try to craft a proper solution to the original problem.
--- net/xdp/xsk.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/xdp/xsk.c +2 -2
@@ -499,6 +499,8 @@ static __poll_t xsk_poll(struct file *fistruct xdp_sock *xs =xdp_sk (sk);struct xsk_buff_pool *pool; +sock_poll_wait (file, sock, wait); +if (unlikely (!xsk_is_bound (xs)))return mask;
@@ -510,8 +512,6 @@ static __poll_t xsk_poll(struct file *fielse /* Poll needs to drive Tx also in copy mode */ __xsk_sendmsg (sk); - }else { -sock_poll_wait (file, sock, wait); }if (xs->rx && !xskq_prod_is_empty (xs->rx))
Greg Kroah-Hartman
maintainerPATCH 95/99 xen/blkfront: harden blkfront against event channel storms
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit 0fd08a34e8e3b67ec9bd8287ac0facf8374b844a upstream.
The Xen blkfront driver is still vulnerable for an attack via excessive number of events sent by the backend. Fix that by using lateeoi event channels.
This is part of XSA-391
--- drivers/block/xen-blkfront.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
drivers/block/xen-blkfront.c +12 -3
@@ -1573,9 +1573,12 @@ static irqreturn_t blkif_interrupt(int iunsigned long flags;struct blkfront_ring_info *rinfo = (struct blkfront_ring_info *)dev_id;struct blkfront_info *info = rinfo->dev_info; +unsigned int eoiflag =XEN_EOI_FLAG_SPURIOUS ; -if (unlikely (info->connected !=BLKIF_STATE_CONNECTED )) +if (unlikely (info->connected !=BLKIF_STATE_CONNECTED )) { +xen_irq_lateeoi (irq,XEN_EOI_FLAG_SPURIOUS );return IRQ_HANDLED ; + }spin_lock_irqsave (&rinfo->ring_lock, flags); again:
@@ -1591,6 +1594,8 @@ static irqreturn_t blkif_interrupt(int iunsigned long id;unsigned int op; + eoiflag =0 ; +RING_COPY_RESPONSE (&rinfo->ring, i, &bret); id = bret.id;
@@ -1707,6 +1712,8 @@ static irqreturn_t blkif_interrupt(int ispin_unlock_irqrestore (&rinfo->ring_lock, flags); +xen_irq_lateeoi (irq, eoiflag); +return IRQ_HANDLED ; err:
@@ -1714,6 +1721,8 @@ static irqreturn_t blkif_interrupt(int ispin_unlock_irqrestore (&rinfo->ring_lock, flags); +/* No EOI in order to avoid further interrupts. */ +pr_alert ("%s disabled for further use\n" , info->gd->disk_name);return IRQ_HANDLED ; }
@@ -1753,8 +1762,8 @@ static int setup_blkring(struct xenbus_dif (err) goto fail; - err =bind_evtchn_to_irqhandler (rinfo->evtchn, blkif_interrupt,0 , -"blkif" , rinfo); + err =bind_evtchn_to_irqhandler_lateeoi (rinfo->evtchn, blkif_interrupt, +0 ,"blkif" , rinfo);if (err <=0 ) {xenbus_dev_fatal (dev, err,"bind_evtchn_to_irqhandler failed" );
Greg Kroah-Hartman
maintainerPATCH 96/99 xen/netfront: harden netfront against event channel storms
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit b27d47950e481f292c0a5ad57357edb9d95d03ba upstream.
The Xen netfront driver is still vulnerable for an attack via excessive number of events sent by the backend. Fix that by using lateeoi event channels.
For being able to detect the case of no rx responses being added while the carrier is down a new lock is needed in order to update and test rsp_cons and the number of seen unconsumed responses atomically.
This is part of XSA-391
--- drivers/net/xen-netfront.c | 125 +++++++++++++++++++++++++++++++++------------ 1 file changed, 94 insertions(+), 31 deletions(-)
drivers/net/xen-netfront.c +94 -31
@@ -148,6 +148,9 @@ struct netfront_queue {grant_ref_t gref_rx_head;grant_ref_t grant_rx_ref[NET_RX_RING_SIZE ]; +unsigned int rx_rsp_unconsumed; +spinlock_t rx_cons_lock; +struct page_pool *page_pool;struct xdp_rxq_info xdp_rxq; };
@@ -376,12 +379,13 @@ static int xennet_open(struct net_devicereturn 0 ; } -static void xennet_tx_buf_gc (struct netfront_queue *queue) +static bool xennet_tx_buf_gc (struct netfront_queue *queue) {RING_IDX cons, prod;unsigned short id;struct sk_buff *skb;bool more_to_do; +bool work_done = false;const struct device *dev = &queue->info->netdev->dev;BUG_ON (!netif_carrier_ok (queue->info->netdev));
@@ -398,6 +402,8 @@ static void xennet_tx_buf_gc(struct netffor (cons = queue->tx.rsp_cons; cons != prod; cons++) {struct xen_netif_tx_response txrsp; + work_done = true; +RING_COPY_RESPONSE (&queue->tx, cons, &txrsp);if (txrsp.status ==XEN_NETIF_RSP_NULL )continue ;
@@ -441,11 +447,13 @@ static void xennet_tx_buf_gc(struct netfxennet_maybe_wake_tx (queue); -return ; +return work_done; err: queue->info->broken = true;dev_alert (dev,"Disabled for further use\n" ); + +return work_done; }struct xennet_gnttab_make_txreq {
@@ -836,6 +844,16 @@ static int xennet_close(struct net_devicreturn 0 ; } +static void xennet_set_rx_rsp_cons (struct netfront_queue *queue,RING_IDX val) +{ +unsigned long flags; + +spin_lock_irqsave (&queue->rx_cons_lock, flags); + queue->rx.rsp_cons = val; + queue->rx_rsp_unconsumed =RING_HAS_UNCONSUMED_RESPONSES (&queue->rx); +spin_unlock_irqrestore (&queue->rx_cons_lock, flags); +} +static void xennet_move_rx_slot (struct netfront_queue *queue,struct sk_buff *skb,grant_ref_t ref) {
@@ -887,7 +905,7 @@ static int xennet_get_extras(struct netfxennet_move_rx_slot (queue, skb, ref); }while (extra.flags &XEN_NETIF_EXTRA_FLAG_MORE ); - queue->rx.rsp_cons = cons; +xennet_set_rx_rsp_cons (queue, cons);return err; }
@@ -1041,7 +1059,7 @@ next: }if (unlikely (err)) - queue->rx.rsp_cons = cons + slots; +xennet_set_rx_rsp_cons (queue, cons + slots);return err; }
@@ -1095,7 +1113,8 @@ static int xennet_fill_frags(struct netf__pskb_pull_tail (skb, pull_to -skb_headlen (skb)); }if (unlikely (skb_shinfo (skb)->nr_frags >=MAX_SKB_FRAGS )) { - queue->rx.rsp_cons = ++cons +skb_queue_len (list); +xennet_set_rx_rsp_cons (queue, + ++cons +skb_queue_len (list));kfree_skb (nskb);return -ENOENT ; }
@@ -1108,7 +1127,7 @@ static int xennet_fill_frags(struct netfkfree_skb (nskb); } - queue->rx.rsp_cons = cons; +xennet_set_rx_rsp_cons (queue, cons);return 0 ; }
@@ -1231,7 +1250,9 @@ err:if (unlikely (xennet_set_skb_gso (skb, gso))) {__skb_queue_head (&tmpq, skb); - queue->rx.rsp_cons +=skb_queue_len (&tmpq); +xennet_set_rx_rsp_cons (queue, + queue->rx.rsp_cons + +skb_queue_len (&tmpq)); goto err; } }
@@ -1255,7 +1276,8 @@ err:__skb_queue_tail (&rxq, skb); - i = ++queue->rx.rsp_cons; + i = queue->rx.rsp_cons +1 ; +xennet_set_rx_rsp_cons (queue, i); work_done++; }if (need_xdp_flush)
@@ -1419,40 +1441,79 @@ static int xennet_set_features(struct nereturn 0 ; } -static irqreturn_t xennet_tx_interrupt (int irq,void *dev_id) +static bool xennet_handle_tx (struct netfront_queue *queue,unsigned int *eoi) { -struct netfront_queue *queue = dev_id;unsigned long flags; -if (queue->info->broken) -return IRQ_HANDLED ; +if (unlikely (queue->info->broken)) +return false;spin_lock_irqsave (&queue->tx_lock, flags); -xennet_tx_buf_gc (queue); +if (xennet_tx_buf_gc (queue)) + *eoi =0 ;spin_unlock_irqrestore (&queue->tx_lock, flags); +return true; +} + +static irqreturn_t xennet_tx_interrupt (int irq,void *dev_id) +{ +unsigned int eoiflag =XEN_EOI_FLAG_SPURIOUS ; + +if (likely (xennet_handle_tx (dev_id, &eoiflag))) +xen_irq_lateeoi (irq, eoiflag); +return IRQ_HANDLED ; } -static irqreturn_t xennet_rx_interrupt (int irq,void *dev_id) +static bool xennet_handle_rx (struct netfront_queue *queue,unsigned int *eoi) { -struct netfront_queue *queue = dev_id; -struct net_device *dev = queue->info->netdev; +unsigned int work_queued; +unsigned long flags; + +if (unlikely (queue->info->broken)) +return false; -if (queue->info->broken) -return IRQ_HANDLED ; +spin_lock_irqsave (&queue->rx_cons_lock, flags); + work_queued =RING_HAS_UNCONSUMED_RESPONSES (&queue->rx); +if (work_queued > queue->rx_rsp_unconsumed) { + queue->rx_rsp_unconsumed = work_queued; + *eoi =0 ; + }else if (unlikely (work_queued < queue->rx_rsp_unconsumed)) { +const struct device *dev = &queue->info->netdev->dev; + +spin_unlock_irqrestore (&queue->rx_cons_lock, flags); +dev_alert (dev,"RX producer index going backwards\n" ); +dev_alert (dev,"Disabled for further use\n" ); + queue->info->broken = true; +return false; + } +spin_unlock_irqrestore (&queue->rx_cons_lock, flags); -if (likely (netif_carrier_ok (dev) && -RING_HAS_UNCONSUMED_RESPONSES (&queue->rx))) +if (likely (netif_carrier_ok (queue->info->netdev) && work_queued))napi_schedule (&queue->napi); +return true; +} + +static irqreturn_t xennet_rx_interrupt (int irq,void *dev_id) +{ +unsigned int eoiflag =XEN_EOI_FLAG_SPURIOUS ; + +if (likely (xennet_handle_rx (dev_id, &eoiflag))) +xen_irq_lateeoi (irq, eoiflag); +return IRQ_HANDLED ; }static irqreturn_t xennet_interrupt (int irq,void *dev_id) { -xennet_tx_interrupt (irq, dev_id); -xennet_rx_interrupt (irq, dev_id); +unsigned int eoiflag =XEN_EOI_FLAG_SPURIOUS ; + +if (xennet_handle_tx (dev_id, &eoiflag) && +xennet_handle_rx (dev_id, &eoiflag)) +xen_irq_lateeoi (irq, eoiflag); +return IRQ_HANDLED ; }
@@ -1770,9 +1831,10 @@ static int setup_netfront_single(structif (err <0 ) goto fail; - err =bind_evtchn_to_irqhandler (queue->tx_evtchn, - xennet_interrupt, -0 , queue->info->netdev->name, queue); + err =bind_evtchn_to_irqhandler_lateeoi (queue->tx_evtchn, + xennet_interrupt,0 , + queue->info->netdev->name, + queue);if (err <0 ) goto bind_fail; queue->rx_evtchn = queue->tx_evtchn;
@@ -1800,18 +1862,18 @@ static int setup_netfront_split(struct nsnprintf (queue->tx_irq_name,sizeof (queue->tx_irq_name),"%s-tx" , queue->name); - err =bind_evtchn_to_irqhandler (queue->tx_evtchn, - xennet_tx_interrupt, -0 , queue->tx_irq_name, queue); + err =bind_evtchn_to_irqhandler_lateeoi (queue->tx_evtchn, + xennet_tx_interrupt,0 , + queue->tx_irq_name, queue);if (err <0 ) goto bind_tx_fail; queue->tx_irq = err;snprintf (queue->rx_irq_name,sizeof (queue->rx_irq_name),"%s-rx" , queue->name); - err =bind_evtchn_to_irqhandler (queue->rx_evtchn, - xennet_rx_interrupt, -0 , queue->rx_irq_name, queue); + err =bind_evtchn_to_irqhandler_lateeoi (queue->rx_evtchn, + xennet_rx_interrupt,0 , + queue->rx_irq_name, queue);if (err <0 ) goto bind_rx_fail; queue->rx_irq = err;
@@ -1913,6 +1975,7 @@ static int xennet_init_queue(struct netfspin_lock_init (&queue->tx_lock);spin_lock_init (&queue->rx_lock); +spin_lock_init (&queue->rx_cons_lock);timer_setup (&queue->rx_refill_timer, rx_refill_timeout,0 );
Greg Kroah-Hartman
maintainerPATCH 97/99 xen/console: harden hvc_xen against event channel storms
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit fe415186b43df0db1f17fa3a46275fd92107fe71 upstream.
The Xen console driver is still vulnerable for an attack via excessive number of events sent by the backend. Fix that by using a lateeoi event channel.
For the normal domU initial console this requires the introduction of bind_evtchn_to_irq_lateeoi() as there is no xenbus device available at the time the event channel is bound to the irq.
As the decision whether an interrupt was spurious or not requires to test for bytes having been read from the backend, move sending the event into the if statement, as sending an event without having found any bytes to be read is making no sense at all.
This is part of XSA-391
--- drivers/tty/hvc/hvc_xen.c | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-)
drivers/tty/hvc/hvc_xen.c +27 -3
@@ -37,6 +37,8 @@ struct xencons_info {struct xenbus_device *xbdev;struct xencons_interface *intf;unsigned int evtchn; +XENCONS_RING_IDX out_cons; +unsigned int out_cons_same;struct hvc_struct *hvc;int irq;int vtermno;
@@ -138,6 +140,8 @@ static int domU_read_console(uint32_t vtXENCONS_RING_IDX cons, prod;int recv =0 ;struct xencons_info *xencons =vtermno_to_xencons (vtermno); +unsigned int eoiflag =0 ; +if (xencons ==NULL )return -EINVAL ; intf = xencons->intf;
@@ -157,7 +161,27 @@ static int domU_read_console(uint32_t vtmb ();/* read ring before consuming */ intf->in_cons = cons; -notify_daemon (xencons); +/* +* When to mark interrupt having been spurious: +* - there was no new data to be read, and +* - the backend did not consume some output bytes, and +* - the previous round with no read data didn't see consumed bytes +* (we might have a race with an interrupt being in flight while +* updating xencons->out_cons, so account for that by allowing one +* round without any visible reason) +*/ +if (intf->out_cons != xencons->out_cons) { + xencons->out_cons = intf->out_cons; + xencons->out_cons_same =0 ; + } +if (recv) { +notify_daemon (xencons); + }else if (xencons->out_cons_same++ >1 ) { + eoiflag =XEN_EOI_FLAG_SPURIOUS ; + } + +xen_irq_lateeoi (xencons->irq, eoiflag); +return recv; }
@@ -386,7 +410,7 @@ static int xencons_connect_backend(strucif (ret)return ret; info->evtchn = evtchn; - irq =bind_evtchn_to_irq (evtchn); + irq =bind_interdomain_evtchn_to_irq_lateeoi (dev->otherend_id, evtchn);if (irq <0 )return irq; info->irq = irq;
@@ -550,7 +574,7 @@ static int __init xen_hvc_init(void)return r; info =vtermno_to_xencons (HVC_COOKIE ); - info->irq =bind_evtchn_to_irq (info->evtchn); + info->irq =bind_evtchn_to_irq_lateeoi (info->evtchn); }if (info->irq <0 ) info->irq =0 ;/* NO_IRQ */
Greg Kroah-Hartman
maintainerPATCH 98/99 xen/netback: fix rx queue stall detection
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit 6032046ec4b70176d247a71836186d47b25d1684 upstream.
Commit 1d5d48523900a4b ("xen-netback: require fewer guest Rx slots when not using GSO") introduced a security problem in netback, as an interface would only be regarded to be stalled if no slot is available in the rx queue ring page. In case the SKB at the head of the queued requests will need more than one rx slot and only one slot is free the stall detection logic will never trigger, as the test for that is only looking for at least one slot to be free.
Fix that by testing for the needed number of slots instead of only one slot being available.
In order to not have to take the rx queue lock that often, store the number of needed slots in the queue data. As all SKB dequeue operations happen in the rx queue kernel thread this is safe, as long as the number of needed slots is accessed via READ/WRITE_ONCE() only and updates are always done with the rx queue lock held.
Add a small helper for obtaining the number of free slots.
This is part of XSA-392
--- drivers/net/xen-netback/common.h | 1 drivers/net/xen-netback/rx.c | 65 ++++++++++++++++++++++++--------------- 2 files changed, 42 insertions(+), 24 deletions(-)
drivers/net/xen-netback/common.h +1 -0
@@ -203,6 +203,7 @@ struct xenvif_queue { /* Per-queue dataunsigned int rx_queue_max;unsigned int rx_queue_len;unsigned long last_rx_time; +unsigned int rx_slots_needed;bool stalled;struct xenvif_copy_state rx_copy;
drivers/net/xen-netback/rx.c +41 -24
108 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 99/99 xen/netback: dont queue unlimited number of packages
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit be81992f9086b230623ae3ebbc85ecee4d00a3d3 upstream.
In case a guest isn't consuming incoming network traffic as fast as it is coming in, xen-netback is buffering network packages in unlimited numbers today. This can result in host OOM situations.
Commit f48da8b14d04ca8 ("xen-netback: fix unlimited guest Rx internal queue and carrier flapping") meant to introduce a mechanism to limit the amount of buffered data by stopping the Tx queue when reaching the data limit, but this doesn't work for cases like UDP.
When hitting the limit don't queue further SKBs, but drop them instead. In order to be able to tell Rx packages have been dropped increment the rx_dropped statistics counter in this case.
It should be noted that the old solution to continue queueing SKBs had the additional problem of an overflow of the 32-bit rx_queue_len value would result in intermittent Tx queue enabling.
This is part of XSA-392
--- drivers/net/xen-netback/rx.c | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-)
drivers/net/xen-netback/rx.c +11 -7
@@ -88,16 +88,19 @@ void xenvif_rx_queue_tail(struct xenvif_spin_lock_irqsave (&queue->rx_queue.lock, flags); -if (skb_queue_empty (&queue->rx_queue)) -xenvif_update_needed_slots (queue, skb); - -__skb_queue_tail (&queue->rx_queue, skb); - - queue->rx_queue_len += skb->len; -if (queue->rx_queue_len > queue->rx_queue_max) { +if (queue->rx_queue_len >= queue->rx_queue_max) {struct net_device *dev = queue->vif->dev;netif_tx_stop_queue (netdev_get_tx_queue (dev, queue->id)); +kfree_skb (skb); + queue->vif->dev->stats.rx_dropped++; + }else { +if (skb_queue_empty (&queue->rx_queue)) +xenvif_update_needed_slots (queue, skb); + +__skb_queue_tail (&queue->rx_queue, skb); + + queue->rx_queue_len += skb->len; }spin_unlock_irqrestore (&queue->rx_queue.lock, flags);
@@ -147,6 +150,7 @@ static void xenvif_rx_queue_drop_expiredbreak ;xenvif_rx_dequeue (queue);kfree_skb (skb); + queue->vif->dev->stats.rx_dropped++; } }
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.88-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.10:
10 builds: 10 pass, 0 fail
28 boots: 28 pass, 0 fail
75 tests: 75 pass, 0 failLinux version: 5.10.88-rc1-g22ecdc9ddc3f
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04Jon
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.88-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels:
Signature · 1 line
Florian
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.88-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.88-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
Tested on arm64 and x86 for 5.10.88-rc1,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-5.10.y
Version: 5.10.88-rc1
Commit: e7135fc66e2cabd6ef5205d7cf866ad19f9d7d24
Compiler: gcc version 7.3.0 (GCC)
arm64:
--------------------------------------------------------------------
Testcase Result Summary:
total: 9018
passed: 9018
failed: 0
timeout: 0
--------------------------------------------------------------------
x86:
--------------------------------------------------------------------
Testcase Result Summary:
total: 9018
passed: 9018
failed: 0
timeout: 0
--------------------------------------------------------------------
Hi Greg,
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
Build test:
mips (gcc version 11.2.1 20211214): 63 configs -> no new failure arm (gcc version 11.2.1 20211214): 105 configs -> no new failure arm64 (gcc version 11.2.1 20211214): 3 configs -> no failure x86_64 (gcc version 11.2.1 20211214): 4 configs -> no failure
Boot test:x86_64: Booted on my test laptop. No regression.x86_64: Booted on qemu. No regression. [1]
arm64: Booted on rpi4b (4GB model). No regression. [2]
[1]. https://openqa.qa.codethink.co.uk/tests/535
[2]. https://openqa.qa.codethink.co.uk/tests/532
--
Regards
Sudip
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.88-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.10.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
## Build
* kernel: 5.10.88-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.10.y
* git commit: 22ecdc9ddc3f790d7897c1c8bc1813fba064ec9c
* git describe: v5.10.87-100-g22ecdc9ddc3f
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.87-100-g22ecdc9ddc3f
## No Test Regressions (compared to v5.10.84-128-g24961377099e)
## No Test Fixes (compared to v5.10.84-128-g24961377099e)
## Test result summary
total: 92504, pass: 79026, fail: 519, skip: 12006, xfail: 953
## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 259 total, 255 passed, 4 failed
* arm64: 37 total, 37 passed, 0 failed
* dragonboard-410c: 1 total, 1 passed, 0 failed
* hi6220-hikey: 1 total, 1 passed, 0 failed
* i386: 36 total, 36 passed, 0 failed
* juno-r2: 1 total, 1 passed, 0 failed
* mips: 34 total, 30 passed, 4 failed
* parisc: 12 total, 12 passed, 0 failed
* powerpc: 52 total, 46 passed, 6 failed
* riscv: 24 total, 16 passed, 8 failed
* s390: 18 total, 18 passed, 0 failed
* sh: 24 total, 24 passed, 0 failed
* sparc: 12 total, 12 passed, 0 failed
* x15: 1 total, 1 passed, 0 failed
* x86: 1 total, 1 passed, 0 failed
* x86_64: 37 total, 37 passed, 0 failed
## Test suites summary
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-bpf
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-firmware
* kselftest-fpu
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-controllers-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* network-basic-tests
* packetdrill
* perf
* rcutorture
* ssuite
* v4l2-compliance
--
Linaro LKFT
https://lkft.linaro.org
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.88 release. There are 99 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, 22 Dec 2021 14:30:09 +0000. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 472 pass: 472 fail: 0
Guenter