5.10.146-rc1 review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 5.10.146-rc1 review
This is the start of the stable review cycle for the 5.10.146 release. There are 141 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, 28 Sep 2022 10:07:26 +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.146-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.146-rc1
Jan Kara <[email protected]>
ext4: make directory inode spreading reflect flexbg size
Theodore Ts'o <[email protected]>
ext4: limit the number of retries after discarding preallocations blocks
Luís Henriques <[email protected]>
ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0
Dan Williams <[email protected]>
devdax: Fix soft-reservation memory description
Asmaa Mnebhi <[email protected]>
i2c: mlxbf: Fix frequency calculation
Asmaa Mnebhi <[email protected]>
i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
Asmaa Mnebhi <[email protected]>
i2c: mlxbf: incorrect base address passed during io write
Uwe Kleine-König <[email protected]>
i2c: imx: If pm_runtime_get_sync() returned 1 device access is possible
Tetsuo Handa <[email protected]>
workqueue: don't skip lockdep work dependency in cancel_work_sync()
Nathan Huckleberry <[email protected]>
drm/rockchip: Fix return type of cdn_dp_connector_mode_valid
Nathan Chancellor <[email protected]>
drm/amd/display: Mark dml30's UseMinimumDCFCLK() as noinline for stack usage
Yao Wang1 <[email protected]>
drm/amd/display: Limit user regamma to a valid value
Hamza Mahfooz <[email protected]>
drm/amdgpu: use dirty framebuffer helper
Linus Walleij <[email protected]>
gpio: ixp4xx: Make irqchip immutable
Hans de Goede <[email protected]>
drm/gma500: Fix BUG: sleeping function called from invalid context errors
Vitaly Kuznetsov <[email protected]>
Drivers: hv: Never allocate anything besides framebuffer from framebuffer memory region
Stefan Metzmacher <[email protected]>
cifs: always initialize struct msghdr smb_msg completely
David Howells <[email protected]>
cifs: use discard iterator to discard unneeded network data more efficiently
Luben Tuikov <[email protected]>
drm/amdgpu: Fix check for RAS support
Daniel Jordan <[email protected]>
vfio/type1: fix vaddr_get_pfns() return in vfio_pin_page_external()
Chunfeng Yun <[email protected]>
usb: xhci-mtk: fix issue of out-of-bounds array access
Stefan Haberland <[email protected]>
s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup
Ilpo Järvinen <[email protected]>
serial: tegra-tcu: Use uart_xmit_advance(), fixes icount.tx accounting
Ilpo Järvinen <[email protected]>
serial: tegra: Use uart_xmit_advance(), fixes icount.tx accounting
Ilpo Järvinen <[email protected]>
serial: Create uart_xmit_advance()
Jingwen Chen <[email protected]>
drm/amd/amdgpu: fixing read wrong pf2vf data in SRIOV
Hangbin Liu <[email protected]>
selftests: forwarding: add shebang for sch_red.sh
Hangyu Hua <[email protected]>
net: sched: fix possible refcount leak in tc_new_tfilter()
Sean Anderson <[email protected]>
net: sunhme: Fix packet reception for len < RX_COPY_THRESHOLD
Wen Gu <[email protected]>
net/smc: Stop the CLC flow if no link to map buffers on
Nícolas F. R. A. Prado <[email protected]>
drm/mediatek: dsi: Move mtk_dsi_stop() call back to mtk_dsi_poweroff()
Adrian Hunter <[email protected]>
perf kcore_copy: Do not check /proc/modules is unchanged
Lieven Hey <[email protected]>
perf jit: Include program header in ELF files
Marc Kleine-Budde <[email protected]>
can: gs_usb: gs_can_open(): fix race dev->can.state condition
Florian Westphal <[email protected]>
netfilter: ebtables: fix memory leak when blob is malformed
Tetsuo Handa <[email protected]>
netfilter: nf_tables: fix percpu memory leak at nf_tables_addchain()
Tetsuo Handa <[email protected]>
netfilter: nf_tables: fix nft_counters_enabled underflow at nf_tables_addchain()
Vladimir Oltean <[email protected]>
net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs
Vladimir Oltean <[email protected]>
net/sched: taprio: avoid disabling offload when it was never enabled
Arnd Bergmann <[email protected]>
net: socket: remove register_gifconf
Vladimir Oltean <[email protected]>
net: enetc: move enetc_set_psfp() out of the common enetc_set_features()
Jason A. Donenfeld <[email protected]>
wireguard: netlink: avoid variable-sized memcpy on sockaddr
Jason A. Donenfeld <[email protected]>
wireguard: ratelimiter: disable timings test by default
Alex Elder <[email protected]>
net: ipa: properly limit modem routing table use
Alex Elder <[email protected]>
net: ipa: kill IPA_TABLE_ENTRY_SIZE
Alex Elder <[email protected]>
net: ipa: DMA addresses are nicely aligned
Alex Elder <[email protected]>
net: ipa: avoid 64-bit modulus
Alex Elder <[email protected]>
net: ipa: fix table alignment requirement
Alex Elder <[email protected]>
net: ipa: fix assumptions about DMA address size
Liang He <[email protected]>
of: mdio: Add of_node_put() when breaking out of for_each_xx
Randy Dunlap <[email protected]>
drm/hisilicon: Add depends on MMU
Javier Martinez Canillas <[email protected]>
drm/hisilicon/hibmc: Allow to be built if COMPILE_TEST is enabled
Íñigo Huguet <[email protected]>
sfc: fix null pointer dereference in efx_hard_start_xmit
Íñigo Huguet <[email protected]>
sfc: fix TX channel offset when using legacy interrupts
Michal Jaron <[email protected]>
i40e: Fix set max_tx_rate when it is lower than 1 Mbps
Michal Jaron <[email protected]>
i40e: Fix VF set max MTU size
Michal Jaron <[email protected]>
iavf: Fix set max MTU size with port VLAN and jumbo frames
Norbert Zulinski <[email protected]>
iavf: Fix bad page state
Serge Semin <[email protected]>
MIPS: Loongson32: Fix PHY-mode being left unspecified
Randy Dunlap <[email protected]>
MIPS: lantiq: export clk_get_io() for lantiq_wdt.ko
Heiko Schocher <[email protected]>
drm/panel: simple: Fix innolux_g121i1_l01 bus_format
Benjamin Poirier <[email protected]>
net: team: Unsync device addresses on ndo_stop
Benjamin Poirier <[email protected]>
net: bonding: Unsync device addresses on ndo_stop
Benjamin Poirier <[email protected]>
net: bonding: Share lacpdu_mcast_addr definition
Sreekanth Reddy <[email protected]>
scsi: mpt3sas: Fix return value check of dma_get_required_mask()
Suganath Prabu S <[email protected]>
scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region
Ioana Ciornei <[email protected]>
net: phy: aquantia: wait for the suspend/resume operations to finish
Ludovic Cintrat <[email protected]>
net: core: fix flow symmetric hash
zhang kai <[email protected]>
net: let flow have same hash in two directions
Lu Wei <[email protected]>
ipvlan: Fix out-of-bound bugs caused by unset skb->mac_header
Brett Creeley <[email protected]>
iavf: Fix cached head and tail value for iavf_get_tx_pending
Pablo Neira Ayuso <[email protected]>
netfilter: nfnetlink_osf: fix possible bogus match in nf_osf_find()
David Leadbeater <[email protected]>
netfilter: nf_conntrack_irc: Tighten matching on DCC message
Igor Ryzhov <[email protected]>
netfilter: nf_conntrack_sip: fix ct_sip_walk_headers
Fabio Estevam <[email protected]>
arm64: dts: rockchip: Remove 'enable-active-low' from rk3399-puma
Liang He <[email protected]>
dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
zain wang <[email protected]>
arm64: dts: rockchip: Set RK3399-Gru PCLK_EDP to 24 MHz
AngeloGioacchino Del Regno <[email protected]>
drm/mediatek: dsi: Add atomic {destroy,duplicate}_state, reset callbacks
Brian Norris <[email protected]>
arm64: dts: rockchip: Pull up wlan wake# on Gru-Bob
Dave Chinner <[email protected]>
xfs: validate inode fork size against fork format
Dave Chinner <[email protected]>
xfs: reorder iunlink remove operation in xfs_ifree
Christoph Hellwig <[email protected]>
xfs: fix up non-directory creation in SGID directories
Mike Tipton <[email protected]>
interconnect: qcom: icc-rpmh: Add BCMs to commit list in pre_aggregate
Mingwei Zhang <[email protected]>
KVM: SEV: add cache flush to solve SEV cache incoherency issues
Chao Yu <[email protected]>
mm/slub: fix to return errno if kmalloc() fails
Marc Kleine-Budde <[email protected]>
can: flexcan: flexcan_mailbox_read() fix return value for drop = true
Al Viro <[email protected]>
riscv: fix a nasty sigreturn bug...
Meng Li <[email protected]>
gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
Bartosz Golaszewski <[email protected]>
gpio: mockup: fix NULL pointer dereference when removing debugfs
Felix Fietkau <[email protected]>
wifi: mt76: fix reading current per-tid starting sequence number for aggregation
Ard Biesheuvel <[email protected]>
efi: libstub: check Shim mode using MokSBStateRT
Ard Biesheuvel <[email protected]>
efi: x86: Wipe setup_data on pure EFI boot
Johan Hovold <[email protected]>
media: flexcop-usb: fix endpoint type check
Yi Liu <[email protected]>
iommu/vt-d: Check correct capability for sagaw determination
Callum Osmotherly <[email protected]>
ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
Luke D. Jones <[email protected]>
ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
Luke D. Jones <[email protected]>
ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
Luke D. Jones <[email protected]>
ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
Takashi Iwai <[email protected]>
ALSA: hda/realtek: Re-arrange quirk table entries
Callum Osmotherly <[email protected]>
ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5570 laptop
huangwenhui <[email protected]>
ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
Kai Vehmanen <[email protected]>
ALSA: hda: add Intel 5 Series / 3400 PCI DID
Mohan Kumar <[email protected]>
ALSA: hda/tegra: set depop delay for tegra
jerry meng <[email protected]>
USB: serial: option: add Quectel RM520N
Carl Yin(殷张成) <[email protected]>
USB: serial: option: add Quectel BG95 0x0203 composition
Alan Stern <[email protected]>
USB: core: Fix RST error in hub.c
Mark Brown <[email protected]>
arm64/bti: Disable in kernel BTI when cross section thunks are broken
Nathan Chancellor <[email protected]>
arm64: Restrict ARM64_BTI_KERNEL to clang 12.0.0 and newer
Greg Kroah-Hartman <[email protected]>
Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
Alex Williamson <[email protected]>
vfio/type1: Unpin zero pages
Daniel Jordan <[email protected]>
vfio/type1: Prepare for batched pinning with struct vfio_batch
Daniel Jordan <[email protected]>
vfio/type1: Change success value of vaddr_get_pfn()
Greg Kroah-Hartman <[email protected]>
Revert "usb: add quirks for Lenovo OneLink+ Dock"
Pawel Laszczak <[email protected]>
usb: cdns3: fix issue with rearming ISO OUT endpoint
Pawel Laszczak <[email protected]>
usb: cdns3: fix incorrect handling TRB_SMM flag for ISOC transfer
Piyush Mehta <[email protected]>
usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
Jean-Francois Le Fillatre <[email protected]>
usb: add quirks for Lenovo OneLink+ Dock
Sergiu Moga <[email protected]>
tty: serial: atmel: Preserve previous USART mode if RS485 disabled
Lino Sanfilippo <[email protected]>
serial: atmel: remove redundant assignment in rs485_config
Adrian Hunter <[email protected]>
mmc: core: Fix inconsistent sd3_bus_mode at UHS-I SD voltage switch failure
Marcus Folkesson <[email protected]>
iio: adc: mcp3911: correct "microchip,device-addr" property
Jonathan Cameron <[email protected]>
iio:adc:mcp3911: Switch to generic firmware properties.
Ikjoon Jang <[email protected]>
usb: xhci-mtk: relax TT periodic bandwidth allocation
Chunfeng Yun <[email protected]>
usb: xhci-mtk: allow multiple Start-Split in a microframe
Chunfeng Yun <[email protected]>
usb: xhci-mtk: add some schedule error number
Chunfeng Yun <[email protected]>
usb: xhci-mtk: add a function to (un)load bandwidth info
Chunfeng Yun <[email protected]>
usb: xhci-mtk: use @sch_tt to check whether need do TT schedule
Chunfeng Yun <[email protected]>
usb: xhci-mtk: add only one extra CS for FS/LS INTR
Chunfeng Yun <[email protected]>
usb: xhci-mtk: get the microframe boundary for ESIT
Wesley Cheng <[email protected]>
usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop
Thinh Nguyen <[email protected]>
usb: dwc3: gadget: Don't modify GEVNTCOUNT in pullup()
Thinh Nguyen <[email protected]>
usb: dwc3: gadget: Refactor pullup()
Thinh Nguyen <[email protected]>
usb: dwc3: gadget: Prevent repeat pullup()
Wesley Cheng <[email protected]>
usb: dwc3: Issue core soft reset before enabling run/stop
Wesley Cheng <[email protected]>
usb: dwc3: gadget: Avoid starting DWC3 gadget during UDC unbind
Utkarsh Patel <[email protected]>
usb: typec: intel_pmc_mux: Add new ACPI ID for Meteor Lake IOM device
Azhar Shaikh <[email protected]>
usb: typec: intel_pmc_mux: Update IOM port status offset for AlderLake
Alex Deucher <[email protected]>
drm/amdgpu: make sure to init common IP before gmc
Victor Skvortsov <[email protected]>
drm/amdgpu: Separate vf2pf work item init from virt data exchange
Peng Ju Zhou <[email protected]>
drm/amdgpu: indirect register access for nv12 sriov
Alex Deucher <[email protected]>
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
-------------
Diffstat:
Makefile | 4 +- arch/arm64/Kconfig | 5 +- arch/arm64/boot/dts/rockchip/rk3399-gru-bob.dts | 5 + .../boot/dts/rockchip/rk3399-gru-chromebook.dtsi | 9 ++ arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 1 - arch/mips/lantiq/clk.c | 1 + arch/mips/loongson32/common/platform.c | 16 +- arch/riscv/kernel/signal.c | 2 + arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/svm/sev.c | 8 + arch/x86/kvm/svm/svm.c | 1 + arch/x86/kvm/svm/svm.h | 2 + arch/x86/kvm/x86.c | 6 + drivers/dax/hmem/device.c | 1 + drivers/dma/ti/k3-udma-private.c | 6 +- drivers/firmware/efi/libstub/secureboot.c | 8 +- drivers/firmware/efi/libstub/x86-stub.c | 7 + drivers/gpio/gpio-ixp4xx.c | 17 ++- drivers/gpio/gpio-mockup.c | 2 +- drivers/gpio/gpiolib-cdev.c | 5 +- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 23 ++- drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c | 15 +- drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 34 +++-- drivers/gpu/drm/amd/amdgpu/amdgpu_virt.h | 1 + drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 5 + drivers/gpu/drm/amd/amdgpu/soc15.c | 25 ---- .../amd/display/dc/dml/dcn30/display_mode_vba_30.c | 3 +- .../drm/amd/display/modules/color/color_gamma.c | 4 + drivers/gpu/drm/gma500/gma_display.c | 11 +- drivers/gpu/drm/hisilicon/hibmc/Kconfig | 3 +- drivers/gpu/drm/mediatek/mtk_dsi.c | 24 +-- drivers/gpu/drm/panel/panel-simple.c | 2 +- drivers/gpu/drm/rockchip/cdn-dp-core.c | 5 +- drivers/hv/vmbus_drv.c | 10 +- drivers/i2c/busses/i2c-imx.c | 2 +- drivers/i2c/busses/i2c-mlxbf.c | 68 ++++----- drivers/iio/adc/mcp3911.c | 16 +- drivers/interconnect/qcom/icc-rpmh.c | 10 +- drivers/interconnect/qcom/sm8150.c | 1 - drivers/interconnect/qcom/sm8250.c | 1 - drivers/iommu/intel/iommu.c | 2 +- drivers/media/usb/b2c2/flexcop-usb.c | 2 +- drivers/mmc/core/sd.c | 42 ++---- drivers/net/bonding/bond_3ad.c | 5 +- drivers/net/bonding/bond_main.c | 57 +++++--- drivers/net/can/flexcan.c | 10 +- drivers/net/can/usb/gs_usb.c | 4 +- drivers/net/ethernet/freescale/enetc/enetc.c | 32 +--- drivers/net/ethernet/freescale/enetc/enetc.h | 9 +- drivers/net/ethernet/freescale/enetc/enetc_pf.c | 11 +- drivers/net/ethernet/freescale/enetc/enetc_qos.c | 23 +++ drivers/net/ethernet/freescale/enetc/enetc_vf.c | 4 +- drivers/net/ethernet/intel/i40e/i40e_main.c | 32 +++- drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c | 20 +++ drivers/net/ethernet/intel/iavf/iavf_txrx.c | 9 +- drivers/net/ethernet/intel/iavf/iavf_virtchnl.c | 7 +- drivers/net/ethernet/sfc/efx_channels.c | 2 +- drivers/net/ethernet/sfc/tx.c | 2 +- drivers/net/ethernet/sun/sunhme.c | 4 +- drivers/net/ipa/gsi.c | 16 +- drivers/net/ipa/gsi_private.h | 2 +- drivers/net/ipa/gsi_trans.c | 9 +- drivers/net/ipa/ipa_cmd.c | 2 +- drivers/net/ipa/ipa_data.h | 4 +- drivers/net/ipa/ipa_qmi.c | 10 +- drivers/net/ipa/ipa_qmi_msg.c | 8 +- drivers/net/ipa/ipa_qmi_msg.h | 37 +++-- drivers/net/ipa/ipa_table.c | 88 +++++------ drivers/net/ipa/ipa_table.h | 6 +- drivers/net/ipvlan/ipvlan_core.c | 6 +- drivers/net/mdio/of_mdio.c | 1 + drivers/net/phy/aquantia_main.c | 53 ++++++- drivers/net/team/team.c | 24 ++- drivers/net/wireguard/netlink.c | 13 +- drivers/net/wireguard/selftest/ratelimiter.c | 25 ++-- drivers/net/wireless/mediatek/mt76/mt7615/mac.c | 2 +- drivers/s390/block/dasd_alias.c | 9 +- drivers/scsi/mpt3sas/mpt3sas_base.c | 161 +++++++++++++++------ drivers/scsi/mpt3sas/mpt3sas_base.h | 1 + drivers/tty/serial/atmel_serial.c | 8 +- drivers/tty/serial/serial-tegra.c | 5 +- drivers/tty/serial/tegra-tcu.c | 2 +- drivers/usb/cdns3/gadget.c | 4 +- drivers/usb/core/hub.c | 2 +- drivers/usb/dwc3/core.c | 4 +- drivers/usb/dwc3/core.h | 4 + drivers/usb/dwc3/gadget.c | 81 ++++++----- drivers/usb/host/xhci-mtk-sch.c | 149 +++++++++++-------- drivers/usb/host/xhci-mtk.h | 2 - drivers/usb/serial/option.c | 6 + drivers/usb/typec/mux/intel_pmc_mux.c | 37 ++++- drivers/vfio/vfio_iommu_type1.c | 110 +++++++++++--- fs/cifs/cifsproto.h | 2 + fs/cifs/cifssmb.c | 6 +- fs/cifs/connect.c | 22 ++- fs/cifs/transport.c | 6 +- fs/ext4/extents.c | 4 + fs/ext4/ialloc.c | 2 +- fs/ext4/mballoc.c | 4 +- fs/xfs/libxfs/xfs_inode_buf.c | 35 +++-- fs/xfs/xfs_inode.c | 36 ++--- include/linux/inetdevice.h | 9 ++ include/linux/kvm_host.h | 2 + include/linux/netdevice.h | 8 - include/linux/serial_core.h | 17 +++ include/net/bond_3ad.h | 2 - include/net/bonding.h | 3 + kernel/workqueue.c | 6 +- mm/slub.c | 5 +- net/bridge/netfilter/ebtables.c | 4 +- net/core/dev_ioctl.c | 43 ++---- net/core/flow_dissector.c | 21 ++- net/ipv4/devinet.c | 4 +- net/netfilter/nf_conntrack_irc.c | 34 ++++- net/netfilter/nf_conntrack_sip.c | 4 +- net/netfilter/nf_tables_api.c | 8 +- net/netfilter/nfnetlink_osf.c | 4 +- net/sched/cls_api.c | 1 + net/sched/sch_taprio.c | 18 ++- net/smc/smc_core.c | 5 +- sound/pci/hda/hda_intel.c | 2 + sound/pci/hda/patch_hdmi.c | 1 + sound/pci/hda/patch_realtek.c | 32 +++- tools/perf/util/genelf.c | 14 ++ tools/perf/util/genelf.h | 4 + tools/perf/util/symbol-elf.c | 7 +- tools/testing/selftests/net/forwarding/sch_red.sh | 1 + virt/kvm/kvm_main.c | 16 +- 129 files changed, 1223 insertions(+), 709 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/141 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
From: Alex Deucher <[email protected]>
[ Upstream commit e3163bc8ffdfdb405e10530b140135b2ee487f89 ]
This mirrors what we do for other asics and this way we are sure the sdma doorbell range is properly initialized.
There is a comment about the way doorbells on gfx9 work that requires that they are initialized for other IPs before GFX is initialized. However, the statement says that it applies to multimedia as well, but the VCN code currently initializes doorbells after GFX and there are no known issues there. In my testing at least I don't see any problems on SDMA.
This is a prerequisite for fixing the Unsupported Request error reported through AER during driver load.
The error was unnoticed before and got visible because of the commit referenced below. This doesn't fix anything in the commit below, rather fixes the issue in amdgpu exposed by the commit. The reference is only to associate this commit with below one so that both go together.
--- drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 5 +++++ drivers/gpu/drm/amd/amdgpu/soc15.c | 25 ------------------------- 2 files changed, 5 insertions(+), 25 deletions(-)
drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c +5 -0
@@ -1475,6 +1475,11 @@ static int sdma_v4_0_start(struct amdgpu_device *adev)WREG32_SDMA (i, mmSDMA0_CNTL, temp);if (!amdgpu_sriov_vf (adev)) { + ring = &adev->sdma.instance[i].ring; + adev->nbio.funcs->sdma_doorbell_range (adev, i, + ring->use_doorbell, ring->doorbell_index, + adev->doorbell_index.sdma_doorbell_range); +/* unhalt engine */ temp =RREG32_SDMA (i, mmSDMA0_F32_CNTL); temp =REG_SET_FIELD (temp,SDMA0_F32_CNTL ,HALT ,0 );
drivers/gpu/drm/amd/amdgpu/soc15.c +0 -25
@@ -1332,25 +1332,6 @@ static int soc15_common_sw_fini(void *handle)return 0 ; } -static void soc15_doorbell_range_init (struct amdgpu_device *adev) -{ -int i; -struct amdgpu_ring *ring; - -/* sdma/ih doorbell range are programed by hypervisor */ -if (!amdgpu_sriov_vf (adev)) { -for (i =0 ; i < adev->sdma.num_instances; i++) { - ring = &adev->sdma.instance[i].ring; - adev->nbio.funcs->sdma_doorbell_range (adev, i, - ring->use_doorbell, ring->doorbell_index, - adev->doorbell_index.sdma_doorbell_range); - } - - adev->nbio.funcs->ih_doorbell_range (adev, adev->irq.ih.use_doorbell, - adev->irq.ih.doorbell_index); - } -} -static int soc15_common_hw_init (void *handle) {struct amdgpu_device *adev = (struct amdgpu_device *)handle;
@@ -1370,12 +1351,6 @@ static int soc15_common_hw_init(void *handle)/* enable the doorbell aperture */ soc15_enable_doorbell_aperture (adev, true); -/* HW doorbell routing policy: doorbell writing not -* in SDMA/IH/MM/ACV range will be routed to CP. So -* we need to init SDMA/IH/MM/ACV doorbell range prior -* to CP ip block init and ring test. -*/ -soc15_doorbell_range_init (adev);return 0 ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 2/141 drm/amdgpu: indirect register access for nv12 sriov
In reply to Greg Kroah-HartmanFrom: Peng Ju Zhou <[email protected]>
[ Upstream commit 8b8a162da820d48bb94261ae4684f2c839ce148c ]
unify host driver and guest driver indirect access control bits names
--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 5 +++++ drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 8 ++++++++ 2 files changed, 13 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +5 -0
@@ -2047,6 +2047,11 @@ static int amdgpu_device_ip_early_init(struct amdgpu_device *adev)amdgpu_vf_error_put (adev,AMDGIM_ERROR_VF_ATOMBIOS_INIT_FAIL ,0 ,0 );return r; } + +/*get pf2vf msg info at it's earliest time*/ +if (amdgpu_sriov_vf (adev)) +amdgpu_virt_init_data_exchange (adev); + } }
drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c +8 -0
@@ -615,6 +615,14 @@ void amdgpu_virt_init_data_exchange(struct amdgpu_device *adev)if (adev->virt.ras_init_done)amdgpu_virt_add_bad_page (adev, bp_block_offset, bp_block_size); } + }else if (adev->bios !=NULL ) { + adev->virt.fw_reserve.p_pf2vf = + (struct amd_sriov_msg_pf2vf_info_header *) + (adev->bios + (AMD_SRIOV_MSG_PF2VF_OFFSET_KB <<10 )); + +amdgpu_virt_read_pf2vf_data (adev); + +return ; }if (adev->virt.vf2pf_update_interval_ms !=0 ) {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 3/141 drm/amdgpu: Separate vf2pf work item init from virt data exchange
In reply to Greg Kroah-HartmanFrom: Victor Skvortsov <[email protected]>
[ Upstream commit 892deb48269c65376f3eeb5b4c032ff2c2979bd7 ]
We want to be able to call virt data exchange conditionally after gmc sw init to reserve bad pages as early as possible. Since this is a conditional call, we will need
to call it again unconditionally later in the init sequence.
Refactor the data exchange function so it can be called multiple times without re-initializing the work item.
v2: Cleaned up the code. Kept the original call to init_exchange_data() inside early init to initialize the work item, afterwards call exchange_data() when needed.
Reviewed By: Shaoyun.liu <[email protected]>
--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 6 +++- drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 36 ++++++++++++++-------- drivers/gpu/drm/amd/amdgpu/amdgpu_virt.h | 1 + 3 files changed, 30 insertions(+), 13 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +5 -1
@@ -2181,6 +2181,10 @@ static int amdgpu_device_ip_init(struct amdgpu_device *adev)/* need to do gmc hw init early so we can allocate gpu mem */ if (adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_GMC ) { +/* Try to reserve bad pages early */ +if (amdgpu_sriov_vf (adev)) +amdgpu_virt_exchange_data (adev); + r =amdgpu_device_vram_scratch_init (adev);if (r) {DRM_ERROR ("amdgpu_vram_scratch_init failed %d\n" , r);
@@ -2212,7 +2216,7 @@ static int amdgpu_device_ip_init(struct amdgpu_device *adev) }if (amdgpu_sriov_vf (adev)) -amdgpu_virt_init_data_exchange (adev); +amdgpu_virt_exchange_data (adev); r =amdgpu_ib_pool_init (adev);if (r) {
drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c +24 -12
@@ -580,17 +580,35 @@ void amdgpu_virt_fini_data_exchange(struct amdgpu_device *adev)void amdgpu_virt_init_data_exchange (struct amdgpu_device *adev) { -uint64_t bp_block_offset =0 ; -uint32_t bp_block_size =0 ; -struct amd_sriov_msg_pf2vf_info *pf2vf_v2 =NULL ; - adev->virt.fw_reserve.p_pf2vf =NULL ; adev->virt.fw_reserve.p_vf2pf =NULL ; adev->virt.vf2pf_update_interval_ms =0 ; -if (adev->mman.fw_vram_usage_va !=NULL ) { +if (adev->bios !=NULL ) { adev->virt.vf2pf_update_interval_ms =2000 ; + adev->virt.fw_reserve.p_pf2vf = + (struct amd_sriov_msg_pf2vf_info_header *) + (adev->bios + (AMD_SRIOV_MSG_PF2VF_OFFSET_KB <<10 )); + +amdgpu_virt_read_pf2vf_data (adev); + } + +if (adev->virt.vf2pf_update_interval_ms !=0 ) { +INIT_DELAYED_WORK (&adev->virt.vf2pf_work, amdgpu_virt_update_vf2pf_work_item); +schedule_delayed_work (&(adev->virt.vf2pf_work),msecs_to_jiffies (adev->virt.vf2pf_update_interval_ms)); + } +} + + +void amdgpu_virt_exchange_data (struct amdgpu_device *adev) +{ +uint64_t bp_block_offset =0 ; +uint32_t bp_block_size =0 ; +struct amd_sriov_msg_pf2vf_info *pf2vf_v2 =NULL ; + +if (adev->mman.fw_vram_usage_va !=NULL ) { + adev->virt.fw_reserve.p_pf2vf = (struct amd_sriov_msg_pf2vf_info_header *) (adev->mman.fw_vram_usage_va + (AMD_SRIOV_MSG_PF2VF_OFFSET_KB <<10 ));
@@ -621,16 +639,10 @@ void amdgpu_virt_init_data_exchange(struct amdgpu_device *adev) (adev->bios + (AMD_SRIOV_MSG_PF2VF_OFFSET_KB <<10 ));amdgpu_virt_read_pf2vf_data (adev); - -return ; - } - -if (adev->virt.vf2pf_update_interval_ms !=0 ) { -INIT_DELAYED_WORK (&adev->virt.vf2pf_work, amdgpu_virt_update_vf2pf_work_item); -schedule_delayed_work (&(adev->virt.vf2pf_work), adev->virt.vf2pf_update_interval_ms); } } +void amdgpu_detect_virtualization (struct amdgpu_device *adev) {uint32_t reg;
drivers/gpu/drm/amd/amdgpu/amdgpu_virt.h +1 -0
@@ -271,6 +271,7 @@ int amdgpu_virt_alloc_mm_table(struct amdgpu_device *adev);void amdgpu_virt_free_mm_table (struct amdgpu_device *adev);void amdgpu_virt_release_ras_err_handler_data (struct amdgpu_device *adev);void amdgpu_virt_init_data_exchange (struct amdgpu_device *adev); +void amdgpu_virt_exchange_data (struct amdgpu_device *adev);void amdgpu_virt_fini_data_exchange (struct amdgpu_device *adev);void amdgpu_detect_virtualization (struct amdgpu_device *adev);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 4/141 drm/amdgpu: make sure to init common IP before gmc
In reply to Greg Kroah-HartmanFrom: Alex Deucher <[email protected]>
[ Upstream commit a8671493d2074950553da3cf07d1be43185ef6c6 ]
Move common IP init before GMC init so that HDP gets remapped before GMC init which uses it.
This fixes the Unsupported Request error reported through AER during driver load. The error happens as a write happens to the remap offset before real remapping is done.
The error was unnoticed before and got visible because of the commit referenced below. This doesn't fix anything in the commit below, rather fixes the issue in amdgpu exposed by the commit. The reference is only to associate this commit with below one so that both go together.
--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +11 -3
@@ -2179,8 +2179,16 @@ static int amdgpu_device_ip_init(struct amdgpu_device *adev) } adev->ip_blocks[i].status.sw = true; -/* need to do gmc hw init early so we can allocate gpu mem */ -if (adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_GMC ) { +if (adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_COMMON ) { +/* need to do common hw init early so everything is set up for gmc */ + r = adev->ip_blocks[i].version->funcs->hw_init ((void *)adev); +if (r) { +DRM_ERROR ("hw_init %d failed %d\n" , i, r); + goto init_failed; + } + adev->ip_blocks[i].status.hw = true; + }else if (adev->ip_blocks[i].version->type ==AMD_IP_BLOCK_TYPE_GMC ) { +/* need to do gmc hw init early so we can allocate gpu mem */ /* Try to reserve bad pages early */ if (amdgpu_sriov_vf (adev))amdgpu_virt_exchange_data (adev);
@@ -2762,8 +2770,8 @@ static int amdgpu_device_ip_reinit_early_sriov(struct amdgpu_device *adev)int i, r;static enum amd_ip_block_type ip_order[] = { -AMD_IP_BLOCK_TYPE_GMC ,AMD_IP_BLOCK_TYPE_COMMON , +AMD_IP_BLOCK_TYPE_GMC ,AMD_IP_BLOCK_TYPE_PSP ,AMD_IP_BLOCK_TYPE_IH , };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 5/141 usb: typec: intel_pmc_mux: Update IOM port status offset for AlderLake
In reply to Greg Kroah-HartmanFrom: Azhar Shaikh <[email protected]>
[ Upstream commit ca5ce82529104e96ccc5e1888979258e233e1644 ]
Intel AlderLake(ADL) IOM has a different IOM port status offset than Intel TigerLake.
Add a new ACPI ID for ADL and use the IOM port status offset as per the platform.
Stable-dep-of: 1b1b672cc1d4 ("usb: typec: intel_pmc_mux: Add new ACPI ID for Meteor Lake IOM device")
--- drivers/usb/typec/mux/intel_pmc_mux.c | 28 ++++++++++++++++++++++----- 1 file changed, 23 insertions(+), 5 deletions(-)
drivers/usb/typec/mux/intel_pmc_mux.c +23 -5
@@ -83,8 +83,6 @@ enum {/* * Input Output Manager (IOM) PORT STATUS */ -#define IOM_PORT_STATUS_OFFSET 0x560 -#define IOM_PORT_STATUS_ACTIVITY_TYPE_MASK GENMASK(9, 6)#define IOM_PORT_STATUS_ACTIVITY_TYPE_SHIFT 6#define IOM_PORT_STATUS_ACTIVITY_TYPE_USB 0x03
@@ -144,6 +142,7 @@ struct pmc_usb {struct pmc_usb_port *port;struct acpi_device *iom_adev;void __iomem *iom_base; +u32 iom_port_status_offset; };static void update_port_status (struct pmc_usb_port *port)
@@ -153,7 +152,8 @@ static void update_port_status(struct pmc_usb_port *port)/* SoC expects the USB Type-C port numbers to start with 0 */ port_num = port->usb3_port -1 ; - port->iom_status =readl (port->pmc->iom_base +IOM_PORT_STATUS_OFFSET + + port->iom_status =readl (port->pmc->iom_base + + port->pmc->iom_port_status_offset + port_num *sizeof (u32)); }
@@ -546,14 +546,32 @@ static int is_memory(struct acpi_resource *res, void *data)return !acpi_dev_resource_memory (res, &r); } +/* IOM ACPI IDs and IOM_PORT_STATUS_OFFSET */ +static const struct acpi_device_id iom_acpi_ids[] = { +/* TigerLake */ + {"INTC1072" ,0x560 , }, + +/* AlderLake */ + {"INTC1079" ,0x160 , }, + {} +}; +static int pmc_usb_probe_iom (struct pmc_usb *pmc) {struct list_head resource_list;struct resource_entry *rentry; -struct acpi_device *adev; +static const struct acpi_device_id *dev_id; +struct acpi_device *adev =NULL ;int ret; - adev =acpi_dev_get_first_match_dev ("INTC1072" ,NULL ,-1 ); +for (dev_id = &iom_acpi_ids[0 ]; dev_id->id[0 ]; dev_id++) { +if (acpi_dev_present (dev_id->id,NULL ,-1 )) { + pmc->iom_port_status_offset = (u32 )dev_id->driver_data; + adev =acpi_dev_get_first_match_dev (dev_id->id,NULL ,-1 ); +break ; + } + } +if (!adev)return -ENODEV ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 6/141 usb: typec: intel_pmc_mux: Add new ACPI ID for Meteor Lake IOM device
In reply to Greg Kroah-HartmanFrom: Utkarsh Patel <[email protected]>
[ Upstream commit 1b1b672cc1d4fb3065dac79efb8901bd6244ef69 ]
This adds the necessary ACPI ID for Intel Meteor Lake IOM devices.
The callback function is_memory() is modified so that it also checks if the resource descriptor passed to it is a memory type "Address Space Resource Descriptor".
On Intel Meteor Lake the ACPI memory resource is not described using the "32-bit Memory Range Descriptor" because the memory is outside of the 32-bit address space. The memory resource is described using the "Address Space Resource Descriptor" instead.
Intel Meteor Lake is the first platform to describe the memory resource for this device with Address Space Resource Descriptor, but it most likely will not be the last. Therefore the change to the is_memory() callback function is made generic.
--- drivers/usb/typec/mux/intel_pmc_mux.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
drivers/usb/typec/mux/intel_pmc_mux.c +7 -2
@@ -541,9 +541,11 @@ static int pmc_usb_register_port(struct pmc_usb *pmc, int index,static int is_memory (struct acpi_resource *res,void *data) { -struct resource r; +struct resource_win win = {}; +struct resource *r = &win.res; -return !acpi_dev_resource_memory (res, &r); +return !(acpi_dev_resource_memory (res, r) || +acpi_dev_resource_address_space (res, &win)); }/* IOM ACPI IDs and IOM_PORT_STATUS_OFFSET */
@@ -553,6 +555,9 @@ static const struct acpi_device_id iom_acpi_ids[] = {/* AlderLake */ { "INTC1079", 0x160, }, + + /* Meteor Lake */ + { "INTC107A", 0x160, }, {} };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 7/141 usb: dwc3: gadget: Avoid starting DWC3 gadget during UDC unbind
In reply to Greg Kroah-HartmanFrom: Wesley Cheng <[email protected]>
[ Upstream commit 8217f07a50236779880f13e87f99224cd9117f83 ]
There is a race present where the DWC3 runtime resume runs in parallel to the UDC unbind sequence. This will eventually lead to a possible scenario where we are enabling the run/stop bit, without a valid composition defined.
Thread#1 (handling UDC unbind):usb_gadget_remove_driver()
-->usb_gadget_disconnect()
-->dwc3_gadget_pullup(0)
--> continue UDC unbind sequence
-->Thread#2 is running in parallel here
Thread#2 (handing next cable connect)__dwc3_set_mode()
-->pm_runtime_get_sync()
-->dwc3_gadget_resume()
-->dwc->gadget_driver is NOT NULL yet
-->dwc3_gadget_run_stop(1)
--> _dwc3gadget_start()...
Fix this by tracking the pullup disable routine, and avoiding resuming of the DWC3 gadget. Once the UDC is re-binded, that will trigger the pullup enable routine, which would handle enabling the DWC3 gadget.
Stable-dep-of: 040f2dbd2010 ("usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop")
--- drivers/usb/dwc3/core.h | 2 ++ drivers/usb/dwc3/gadget.c | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-)
drivers/usb/dwc3/core.h +2 -0
@@ -1010,6 +1010,7 @@ struct dwc3_scratchpad_array {* @tx_max_burst_prd: max periodic ESS transmit burst size * @hsphy_interface: "utmi" or "ulpi" * @connected: true when we're connected to a host, false otherwise +* @softconnect: true when gadget connect is called, false when disconnect runs * @delayed_status: true when gadget driver asks for delayed status * @ep0_bounced: true when we used bounce buffer * @ep0_expect_in: true when we expect a DATA IN transfer
@@ -1218,6 +1219,7 @@ struct dwc3 {const char *hsphy_interface; unsigned connected:1; + unsigned softconnect:1; unsigned delayed_status:1; unsigned ep0_bounced:1; unsigned ep0_expect_in:1;
drivers/usb/dwc3/gadget.c +2 -2
@@ -2127,7 +2127,7 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)int ret; is_on = !!is_on; - + dwc->softconnect = is_on;/* * Per databook, when we want to stop the gadget, if a control transfer * is still in process, complete it and get the core into setup phase.
@@ -4048,7 +4048,7 @@ int dwc3_gadget_resume(struct dwc3 *dwc) {int ret; -if (!dwc->gadget_driver) +if (!dwc->gadget_driver || !dwc->softconnect)return 0 ; ret =__dwc3_gadget_start (dwc);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 8/141 usb: dwc3: Issue core soft reset before enabling run/stop
In reply to Greg Kroah-HartmanFrom: Wesley Cheng <[email protected]>
[ Upstream commit 0066472de157439d58454f4a55786f1045ea5681 ]
It is recommended by the Synopsis databook to issue a DCTL.CSftReset when reconnecting from a device-initiated disconnect routine. This resolves issues with enumeration during fast composition switching cases, which result in an unknown device on the host.
Stable-dep-of: 040f2dbd2010 ("usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop")
--- drivers/usb/dwc3/core.c | 4 +--- drivers/usb/dwc3/core.h | 2 ++ drivers/usb/dwc3/gadget.c | 11 +++++++++++ 3 files changed, 14 insertions(+), 3 deletions(-)
drivers/usb/dwc3/core.c +1 -3
@@ -114,8 +114,6 @@ void dwc3_set_prtcap(struct dwc3 *dwc, u32 mode) dwc->current_dr_role = mode; } -static int dwc3_core_soft_reset (struct dwc3 *dwc); -static void __dwc3_set_mode (struct work_struct *work) {struct dwc3 *dwc =work_to_dwc (work);
@@ -265,7 +263,7 @@ u32 dwc3_core_fifo_space(struct dwc3_ep *dep, u8 type)* dwc3_core_soft_reset - Issues core soft reset and PHY reset * @dwc: pointer to our context structure */ -static int dwc3_core_soft_reset (struct dwc3 *dwc) +int dwc3_core_soft_reset (struct dwc3 *dwc) {u32 reg;int retries =1000 ;
drivers/usb/dwc3/core.h +2 -0
@@ -1458,6 +1458,8 @@ bool dwc3_has_imod(struct dwc3 *dwc);int dwc3_event_buffers_setup (struct dwc3 *dwc);void dwc3_event_buffers_cleanup (struct dwc3 *dwc); +int dwc3_core_soft_reset (struct dwc3 *dwc); +#if IS_ENABLED (CONFIG_USB_DWC3_HOST ) ||IS_ENABLED (CONFIG_USB_DWC3_DUAL_ROLE )int dwc3_host_init (struct dwc3 *dwc);void dwc3_host_exit (struct dwc3 *dwc);
drivers/usb/dwc3/gadget.c +11 -0
@@ -2200,6 +2200,17 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on) dwc->ev_buf->length; } }else { +/* +* In the Synopsys DWC_usb31 1.90a programming guide section +* 4.1.9, it specifies that for a reconnect after a +* device-initiated disconnect requires a core soft reset +* (DCTL.CSftRst) before enabling the run/stop bit. +*/ +spin_unlock_irqrestore (&dwc->lock, flags); +dwc3_core_soft_reset (dwc); +spin_lock_irqsave (&dwc->lock, flags); + +dwc3_event_buffers_setup (dwc);__dwc3_gadget_start (dwc); }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 9/141 usb: dwc3: gadget: Prevent repeat pullup()
In reply to Greg Kroah-HartmanFrom: Thinh Nguyen <[email protected]>
[ Upstream commit 69e131d1ac4e52a59ec181ab4f8aa8c48cd8fb64 ]
Don't do soft-disconnect if it's previously done. Likewise, don't do soft-connect if the device is currently connected and running. It would break normal operation.
Currently the caller of pullup() (udc's sysfs soft_connect) only checks if it had initiated disconnect to prevent repeating soft-disconnect. It doesn't check for soft-connect. To be safe, let's keep the check here regardless whether the udc core is fixed.
Stable-dep-of: 040f2dbd2010 ("usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop")
--- drivers/usb/dwc3/gadget.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/dwc3/gadget.c +4 -0
@@ -2127,6 +2127,10 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)int ret; is_on = !!is_on; + +if (dwc->pullups_connected == is_on) +return 0 ; + dwc->softconnect = is_on;/* * Per databook, when we want to stop the gadget, if a control transfer
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 10/141 usb: dwc3: gadget: Refactor pullup()
In reply to Greg Kroah-HartmanFrom: Thinh Nguyen <[email protected]>
[ Upstream commit 861c010a2ee1bc4a66d23f0da4aa22e75d8eaa24 ]
Move soft-disconnect sequence out of dwc3_gadget_pullup(). No functional change here.
Stable-dep-of: 040f2dbd2010 ("usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop")
--- drivers/usb/dwc3/gadget.c | 65 ++++++++++++++++++++++----------------- 1 file changed, 36 insertions(+), 29 deletions(-)
drivers/usb/dwc3/gadget.c +36 -29
@@ -2120,6 +2120,40 @@ static void dwc3_gadget_disable_irq(struct dwc3 *dwc);static void __dwc3_gadget_stop (struct dwc3 *dwc);static int __dwc3_gadget_start (struct dwc3 *dwc); +static int dwc3_gadget_soft_disconnect (struct dwc3 *dwc) +{ +u32 count; + + dwc->connected = false; + +/* +* In the Synopsys DesignWare Cores USB3 Databook Rev. 3.30a +* Section 4.1.8 Table 4-7, it states that for a device-initiated +* disconnect, the SW needs to ensure that it sends "a DEPENDXFER +* command for any active transfers" before clearing the RunStop +* bit. +*/ +dwc3_stop_active_transfers (dwc); +__dwc3_gadget_stop (dwc); + +/* +* In the Synopsys DesignWare Cores USB3 Databook Rev. 3.30a +* Section 1.3.4, it mentions that for the DEVCTRLHLT bit, the +* "software needs to acknowledge the events that are generated +* (by writing to GEVNTCOUNTn) while it is waiting for this bit +* to be set to '1'." +*/ + count =dwc3_readl (dwc->regs,DWC3_GEVNTCOUNT (0 )); + count &=DWC3_GEVNTCOUNT_MASK ; +if (count >0 ) { +dwc3_writel (dwc->regs,DWC3_GEVNTCOUNT (0 ), count); + dwc->ev_buf->lpos = (dwc->ev_buf->lpos + count) % + dwc->ev_buf->length; + } + +return dwc3_gadget_run_stop (dwc, false, false); +} +static int dwc3_gadget_pullup (struct usb_gadget *g,int is_on) {struct dwc3 *dwc =gadget_to_dwc (g);
@@ -2176,33 +2210,7 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)spin_lock_irqsave (&dwc->lock, flags);if (!is_on) { -u32 count; - - dwc->connected = false; -/* -* In the Synopsis DesignWare Cores USB3 Databook Rev. 3.30a -* Section 4.1.8 Table 4-7, it states that for a device-initiated -* disconnect, the SW needs to ensure that it sends "a DEPENDXFER -* command for any active transfers" before clearing the RunStop -* bit. -*/ -dwc3_stop_active_transfers (dwc); -__dwc3_gadget_stop (dwc); - -/* -* In the Synopsis DesignWare Cores USB3 Databook Rev. 3.30a -* Section 1.3.4, it mentions that for the DEVCTRLHLT bit, the -* "software needs to acknowledge the events that are generated -* (by writing to GEVNTCOUNTn) while it is waiting for this bit -* to be set to '1'." -*/ - count =dwc3_readl (dwc->regs,DWC3_GEVNTCOUNT (0 )); - count &=DWC3_GEVNTCOUNT_MASK ; -if (count >0 ) { -dwc3_writel (dwc->regs,DWC3_GEVNTCOUNT (0 ), count); - dwc->ev_buf->lpos = (dwc->ev_buf->lpos + count) % - dwc->ev_buf->length; - } + ret =dwc3_gadget_soft_disconnect (dwc); }else {/* * In the Synopsys DWC_usb31 1.90a programming guide section
@@ -2216,9 +2224,8 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)dwc3_event_buffers_setup (dwc);__dwc3_gadget_start (dwc); + ret =dwc3_gadget_run_stop (dwc, true, false); } - - ret =dwc3_gadget_run_stop (dwc, is_on, false);spin_unlock_irqrestore (&dwc->lock, flags);enable_irq (dwc->irq_gadget);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 11/141 usb: dwc3: gadget: Dont modify GEVNTCOUNT in pullup()
In reply to Greg Kroah-HartmanFrom: Thinh Nguyen <[email protected]>
[ Upstream commit 8f8034f493b5eb1ad21ff392fd30c0cf9e71f73f ]
If the GEVNTCOUNT indicates events in the event buffer, the driver needs to acknowledge them before the controller can halt. Simply let the interrupt handler acknowledges the remaining event generated by the controller while polling for DSTS.DEVCTLHLT. This avoids disabling irq and taking care of race condition between the interrupt handlers and pullup().
Stable-dep-of: 040f2dbd2010 ("usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop")
--- drivers/usb/dwc3/gadget.c | 35 ++++++++--------------------------- 1 file changed, 8 insertions(+), 27 deletions(-)
drivers/usb/dwc3/gadget.c +8 -27
@@ -2122,8 +2122,9 @@ static int __dwc3_gadget_start(struct dwc3 *dwc);static int dwc3_gadget_soft_disconnect (struct dwc3 *dwc) { -u32 count; +unsigned long flags; +spin_lock_irqsave (&dwc->lock, flags); dwc->connected = false;/*
@@ -2135,29 +2136,21 @@ static int dwc3_gadget_soft_disconnect(struct dwc3 *dwc)*/ dwc3_stop_active_transfers (dwc);__dwc3_gadget_stop (dwc); +spin_unlock_irqrestore (&dwc->lock, flags);/* -* In the Synopsys DesignWare Cores USB3 Databook Rev. 3.30a -* Section 1.3.4, it mentions that for the DEVCTRLHLT bit, the -* "software needs to acknowledge the events that are generated -* (by writing to GEVNTCOUNTn) while it is waiting for this bit -* to be set to '1'." +* Note: if the GEVNTCOUNT indicates events in the event buffer, the +* driver needs to acknowledge them before the controller can halt. +* Simply let the interrupt handler acknowledges and handle the +* remaining event generated by the controller while polling for +* DSTS.DEVCTLHLT. */ - count =dwc3_readl (dwc->regs,DWC3_GEVNTCOUNT (0 )); - count &=DWC3_GEVNTCOUNT_MASK ; -if (count >0 ) { -dwc3_writel (dwc->regs,DWC3_GEVNTCOUNT (0 ), count); - dwc->ev_buf->lpos = (dwc->ev_buf->lpos + count) % - dwc->ev_buf->length; - } -return dwc3_gadget_run_stop (dwc, false, false); }static int dwc3_gadget_pullup (struct usb_gadget *g,int is_on) {struct dwc3 *dwc =gadget_to_dwc (g); -unsigned long flags;int ret; is_on = !!is_on;
@@ -2201,14 +2194,6 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)return 0 ; } -/* -* Synchronize and disable any further event handling while controller -* is being enabled/disabled. -*/ -disable_irq (dwc->irq_gadget); - -spin_lock_irqsave (&dwc->lock, flags); -if (!is_on) { ret =dwc3_gadget_soft_disconnect (dwc); }else {
@@ -2218,16 +2203,12 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)* device-initiated disconnect requires a core soft reset * (DCTL.CSftRst) before enabling the run/stop bit. */ -spin_unlock_irqrestore (&dwc->lock, flags);dwc3_core_soft_reset (dwc); -spin_lock_irqsave (&dwc->lock, flags);dwc3_event_buffers_setup (dwc);__dwc3_gadget_start (dwc); ret =dwc3_gadget_run_stop (dwc, true, false); } -spin_unlock_irqrestore (&dwc->lock, flags); -enable_irq (dwc->irq_gadget);pm_runtime_put (dwc->dev);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 12/141 usb: dwc3: gadget: Avoid duplicate requests to enable Run/Stop
In reply to Greg Kroah-HartmanFrom: Wesley Cheng <[email protected]>
[ Upstream commit 040f2dbd2010c43f33ad27249e6dac48456f4d99 ]
Relocate the pullups_connected check until after it is ensured that there are no runtime PM transitions. If another context triggered the DWC3 core's runtime resume, it may have already enabled the Run/Stop. Do not re-run the entire pullup sequence again, as it may issue a core soft reset while Run/Stop is already set.
This patch depends on
commit 69e131d1ac4e ("usb: dwc3: gadget: Prevent repeat pullup()")
--- drivers/usb/dwc3/gadget.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/usb/dwc3/gadget.c +5 -3
@@ -2155,9 +2155,6 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on) is_on = !!is_on; -if (dwc->pullups_connected == is_on) -return 0 ; - dwc->softconnect = is_on;/* * Per databook, when we want to stop the gadget, if a control transfer
@@ -2194,6 +2191,11 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)return 0 ; } +if (dwc->pullups_connected == is_on) { +pm_runtime_put (dwc->dev); +return 0 ; + } +if (!is_on) { ret =dwc3_gadget_soft_disconnect (dwc); }else {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 13/141 usb: xhci-mtk: get the microframe boundary for ESIT
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
[ Upstream commit 7c986fbc16ae6b2f914a3ebf06a3a4a8d9bb0b7c ]
Tune the boundary for FS/LS ESIT due to CS:
For ISOC out-ep, the controller starts transfer data after the first SS; for others, the data is already transferred before the last CS.
Stable-dep-of: 548011957d1d ("usb: xhci-mtk: relax TT periodic bandwidth allocation")
--- drivers/usb/host/xhci-mtk-sch.c | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +19 -5
@@ -513,22 +513,35 @@ static void update_sch_tt(struct usb_device *udev,list_del (&sch_ep->tt_endpoint); } +static u32 get_esit_boundary (struct mu3h_sch_ep_info *sch_ep) +{ +u32 boundary = sch_ep->esit; + +if (sch_ep->sch_tt) {/* LS/FS with TT */ +/* tune for CS */ +if (sch_ep->ep_type !=ISOC_OUT_EP ) + boundary++; +else if (boundary >1 )/* normally esit >= 8 for FS/LS */ + boundary--; + } + +return boundary; +} +static int check_sch_bw (struct usb_device *udev,struct mu3h_sch_bw_info *sch_bw,struct mu3h_sch_ep_info *sch_ep) {u32 offset; -u32 esit;u32 min_bw;u32 min_index;u32 worst_bw;u32 bw_boundary; +u32 esit_boundary;u32 min_num_budget;u32 min_cs_count;bool tt_offset_ok = false;int ret; - esit = sch_ep->esit; -/* * Search through all possible schedule microframes. * and find a microframe where its worst bandwidth is minimum.
@@ -537,7 +550,8 @@ static int check_sch_bw(struct usb_device *udev, min_index =0 ; min_cs_count = sch_ep->cs_count; min_num_budget = sch_ep->num_budget_microframes; -for (offset =0 ; offset < esit; offset++) { + esit_boundary =get_esit_boundary (sch_ep); +for (offset =0 ; offset < sch_ep->esit; offset++) {if (is_fs_or_ls (udev->speed)) { ret =check_sch_tt (udev, sch_ep, offset);if (ret)
@@ -546,7 +560,7 @@ static int check_sch_bw(struct usb_device *udev, tt_offset_ok = true; } -if ((offset + sch_ep->num_budget_microframes) > sch_ep->esit) +if ((offset + sch_ep->num_budget_microframes) > esit_boundary)break ; worst_bw =get_max_bw (sch_bw, sch_ep, offset);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 14/141 usb: xhci-mtk: add only one extra CS for FS/LS INTR
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
[ Upstream commit 1bf661daf6b084bc4d753f55b54f35dc98709685 ]
In USB2 Spec:
"11.18.5 TT Response Generation
In general, there will be two (or more) complete-split transactions scheduled for a periodic endpoint. However, for interrupt endpoints, the maximum size of the full-/low-speed transaction guarantees that it can never require more than two complete-split transactions. Two complete-split transactions are only required when the transaction spans a microframe boundary."
Due to the maxp is 64, and less then 188 (at most in one microframe), seems never span boundary, so use only one CS for FS/LS interrupt transfer, this will save some bandwidth.
Stable-dep-of: 548011957d1d ("usb: xhci-mtk: relax TT periodic bandwidth allocation")
--- drivers/usb/host/xhci-mtk-sch.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +3 -7
@@ -408,13 +408,11 @@ static int check_sch_tt(struct usb_device *udev, {struct mu3h_sch_tt *tt = sch_ep->sch_tt;u32 extra_cs_count; -u32 fs_budget_start;u32 start_ss, last_ss;u32 start_cs, last_cs;int i; start_ss = offset %8 ; - fs_budget_start = (start_ss +1 ) %8 ;if (sch_ep->ep_type ==ISOC_OUT_EP ) { last_ss = start_ss + sch_ep->cs_count -1 ;
@@ -450,16 +448,14 @@ static int check_sch_tt(struct usb_device *udev,if (sch_ep->ep_type ==ISOC_IN_EP ) extra_cs_count = (last_cs ==7 ) ?1 :2 ;else /* ep_type : INTR IN / INTR OUT */ - extra_cs_count = (fs_budget_start ==6 ) ?1 :2 ; + extra_cs_count =1 ; cs_count += extra_cs_count;if (cs_count >7 ) cs_count =7 ;/* HW limit */ -for (i =0 ; i < cs_count +2 ; i++) { -if (test_bit (offset + i, tt->ss_bit_map)) -return -ERANGE ; - } +if (test_bit (offset, tt->ss_bit_map)) +return -ERANGE ; sch_ep->cs_count = cs_count;/* one for ss, the other for idle */
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 15/141 usb: xhci-mtk: use @sch_tt to check whether need do TT schedule
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
[ Upstream commit 4a56adf4fafbc41ceffce0c3f385f59d4fc3c16a ]
It's clearer to use @sch_tt to check whether need do TT schedule, no function is changed.
Stable-dep-of: 548011957d1d ("usb: xhci-mtk: relax TT periodic bandwidth allocation")
--- drivers/usb/host/xhci-mtk-sch.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +2 -2
@@ -548,7 +548,7 @@ static int check_sch_bw(struct usb_device *udev, min_num_budget = sch_ep->num_budget_microframes; esit_boundary =get_esit_boundary (sch_ep);for (offset =0 ; offset < sch_ep->esit; offset++) { -if (is_fs_or_ls (udev->speed)) { +if (sch_ep->sch_tt) { ret =check_sch_tt (udev, sch_ep, offset);if (ret)continue ;
@@ -585,7 +585,7 @@ static int check_sch_bw(struct usb_device *udev, sch_ep->cs_count = min_cs_count; sch_ep->num_budget_microframes = min_num_budget; -if (is_fs_or_ls (udev->speed)) { +if (sch_ep->sch_tt) {/* all offset for tt is not ok*/ if (!tt_offset_ok)return -ERANGE ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 16/141 usb: xhci-mtk: add a function to (un)load bandwidth info
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
[ Upstream commit 338af695fffb12a9407c376ce0cebce896c15050 ]
Extract a function to load/unload bandwidth info, and remove a dummy check of TT offset.
Stable-dep-of: 548011957d1d ("usb: xhci-mtk: relax TT periodic bandwidth allocation")
--- drivers/usb/host/xhci-mtk-sch.c | 37 ++++++++++++++------------------- 1 file changed, 16 insertions(+), 21 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +16 -21
@@ -375,7 +375,6 @@ static void update_bus_bw(struct mu3h_sch_bw_info *sch_bw, sch_ep->bw_budget_table[j]; } } - sch_ep->allocated = used; }static int check_fs_bus_bw (struct mu3h_sch_ep_info *sch_ep,int offset)
@@ -509,6 +508,19 @@ static void update_sch_tt(struct usb_device *udev,list_del (&sch_ep->tt_endpoint); } +static int load_ep_bw (struct usb_device *udev,struct mu3h_sch_bw_info *sch_bw, +struct mu3h_sch_ep_info *sch_ep,bool loaded) +{ +if (sch_ep->sch_tt) +update_sch_tt (udev, sch_ep, loaded); + +/* update bus bandwidth info */ +update_bus_bw (sch_bw, sch_ep, loaded); + sch_ep->allocated = loaded; + +return 0 ; +} +static u32 get_esit_boundary (struct mu3h_sch_ep_info *sch_ep) {u32 boundary = sch_ep->esit;
@@ -535,7 +547,6 @@ static int check_sch_bw(struct usb_device *udev,u32 esit_boundary;u32 min_num_budget;u32 min_cs_count; -bool tt_offset_ok = false;int ret;/*
@@ -552,8 +563,6 @@ static int check_sch_bw(struct usb_device *udev, ret =check_sch_tt (udev, sch_ep, offset);if (ret)continue ; -else - tt_offset_ok = true; }if ((offset + sch_ep->num_budget_microframes) > esit_boundary)
@@ -585,29 +594,15 @@ static int check_sch_bw(struct usb_device *udev, sch_ep->cs_count = min_cs_count; sch_ep->num_budget_microframes = min_num_budget; -if (sch_ep->sch_tt) { -/* all offset for tt is not ok*/ -if (!tt_offset_ok) -return -ERANGE ; - -update_sch_tt (udev, sch_ep,1 ); - } - -/* update bus bandwidth info */ -update_bus_bw (sch_bw, sch_ep,1 ); - -return 0 ; +return load_ep_bw (udev, sch_bw, sch_ep, true); }static void destroy_sch_ep (struct usb_device *udev,struct mu3h_sch_bw_info *sch_bw,struct mu3h_sch_ep_info *sch_ep) {/* only release ep bw check passed by check_sch_bw() */ -if (sch_ep->allocated) { -update_bus_bw (sch_bw, sch_ep,0 ); -if (sch_ep->sch_tt) -update_sch_tt (udev, sch_ep,0 ); - } +if (sch_ep->allocated) +load_ep_bw (udev, sch_bw, sch_ep, false);if (sch_ep->sch_tt)drop_tt (udev);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 17/141 usb: xhci-mtk: add some schedule error number
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
[ Upstream commit ccda8c224c0701caac007311d06a2de9543a7590 ]
This is used to provide more information about which case causes bandwidth schedule failure.
Stable-dep-of: 548011957d1d ("usb: xhci-mtk: relax TT periodic bandwidth allocation")
--- drivers/usb/host/xhci-mtk-sch.c | 44 ++++++++++++++++++++++++++------- 1 file changed, 35 insertions(+), 9 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +35 -9
@@ -25,6 +25,13 @@*/ #define TT_MICROFRAMES_MAX 9 +/* schedule error type */ +#define ESCH_SS_Y6 1001 +#define ESCH_SS_OVERLAP 1002 +#define ESCH_CS_OVERFLOW 1003 +#define ESCH_BW_OVERFLOW 1004 +#define ESCH_FIXME 1005 +/* mtk scheduler bitmasks */ #define EP_BPKTS (p) ((p) & 0x7f)#define EP_BCSCOUNT (p) (((p) & 0x7) << 8)
@@ -32,6 +39,24 @@#define EP_BOFFSET (p) ((p) & 0x3fff)#define EP_BREPEAT (p) (((p) & 0x7fff) << 16) +static char *sch_error_string (int err_num) +{ +switch (err_num) { +case ESCH_SS_Y6 : +return "Can't schedule Start-Split in Y6" ; +case ESCH_SS_OVERLAP : +return "Can't find a suitable Start-Split location" ; +case ESCH_CS_OVERFLOW : +return "The last Complete-Split is greater than 7" ; +case ESCH_BW_OVERFLOW : +return "Bandwidth exceeds the maximum limit" ; +case ESCH_FIXME : +return "FIXME, to be resolved" ; +default : +return "Unknown" ; + } +} +static int is_fs_or_ls (enum usb_device_speed speed) {return speed ==USB_SPEED_FULL || speed ==USB_SPEED_LOW ;
@@ -395,7 +420,7 @@ static int check_fs_bus_bw(struct mu3h_sch_ep_info *sch_ep, int offset)for (j =0 ; j < sch_ep->cs_count; j++) { tmp = tt->fs_bus_bw[base + j] + sch_ep->bw_cost_per_microframe;if (tmp >FS_PAYLOAD_MAX ) -return -ERANGE ; +return -ESCH_BW_OVERFLOW ; } }
@@ -421,11 +446,11 @@ static int check_sch_tt(struct usb_device *udev,* must never schedule Start-Split in Y6 */ if (!(start_ss ==7 || last_ss <6 )) -return -ERANGE ; +return -ESCH_SS_Y6 ;for (i =0 ; i < sch_ep->cs_count; i++)if (test_bit (offset + i, tt->ss_bit_map)) -return -ERANGE ; +return -ESCH_SS_OVERLAP ; }else {u32 cs_count =DIV_ROUND_UP (sch_ep->maxpkt,FS_PAYLOAD_MAX );
@@ -435,14 +460,14 @@ static int check_sch_tt(struct usb_device *udev,* must never schedule Start-Split in Y6 */ if (start_ss ==6 ) -return -ERANGE ; +return -ESCH_SS_Y6 ;/* one uframe for ss + one uframe for idle */ start_cs = (start_ss +2 ) %8 ; last_cs = start_cs + cs_count -1 ;if (last_cs >7 ) -return -ERANGE ; +return -ESCH_CS_OVERFLOW ;if (sch_ep->ep_type ==ISOC_IN_EP ) extra_cs_count = (last_cs ==7 ) ?1 :2 ;
@@ -454,7 +479,7 @@ static int check_sch_tt(struct usb_device *udev, cs_count =7 ;/* HW limit */ if (test_bit (offset, tt->ss_bit_map)) -return -ERANGE ; +return -ESCH_SS_OVERLAP ; sch_ep->cs_count = cs_count;/* one for ss, the other for idle */
@@ -547,7 +572,7 @@ static int check_sch_bw(struct usb_device *udev,u32 esit_boundary;u32 min_num_budget;u32 min_cs_count; -int ret; +int ret =0 ;/* * Search through all possible schedule microframes.
@@ -588,7 +613,7 @@ static int check_sch_bw(struct usb_device *udev,/* check bandwidth */ if (min_bw > bw_boundary) -return -ERANGE ; +return ret ? ret : -ESCH_BW_OVERFLOW ; sch_ep->offset = min_index; sch_ep->cs_count = min_cs_count;
@@ -765,7 +790,8 @@ int xhci_mtk_check_bandwidth(struct usb_hcd *hcd, struct usb_device *udev) ret =check_sch_bw (udev, sch_bw, sch_ep);if (ret) { -xhci_err (xhci,"Not enough bandwidth!\n" ); +xhci_err (xhci,"Not enough bandwidth! (%s)\n" , +sch_error_string (-ret));return -ENOSPC ; } }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 18/141 usb: xhci-mtk: allow multiple Start-Split in a microframe
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
[ Upstream commit d3997fce189fc4423169c51a81ba5ca01144d886 ]
This patch is used to relax bandwidth schedule by allowing multiple Start-Split in the same microframe.
Stable-dep-of: 548011957d1d ("usb: xhci-mtk: relax TT periodic bandwidth allocation")
--- drivers/usb/host/xhci-mtk-sch.c | 18 ------------------ drivers/usb/host/xhci-mtk.h | 2 -- 2 files changed, 20 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +0 -18
@@ -430,11 +430,9 @@ static int check_fs_bus_bw(struct mu3h_sch_ep_info *sch_ep, int offset)static int check_sch_tt (struct usb_device *udev,struct mu3h_sch_ep_info *sch_ep,u32 offset) { -struct mu3h_sch_tt *tt = sch_ep->sch_tt;u32 extra_cs_count;u32 start_ss, last_ss;u32 start_cs, last_cs; -int i; start_ss = offset %8 ;
@@ -448,10 +446,6 @@ static int check_sch_tt(struct usb_device *udev,if (!(start_ss ==7 || last_ss <6 ))return -ESCH_SS_Y6 ; -for (i =0 ; i < sch_ep->cs_count; i++) -if (test_bit (offset + i, tt->ss_bit_map)) -return -ESCH_SS_OVERLAP ; - }else {u32 cs_count =DIV_ROUND_UP (sch_ep->maxpkt,FS_PAYLOAD_MAX );
@@ -478,9 +472,6 @@ static int check_sch_tt(struct usb_device *udev,if (cs_count >7 ) cs_count =7 ;/* HW limit */ -if (test_bit (offset, tt->ss_bit_map)) -return -ESCH_SS_OVERLAP ; - sch_ep->cs_count = cs_count;/* one for ss, the other for idle */ sch_ep->num_budget_microframes = cs_count +2 ;
@@ -502,11 +493,9 @@ static void update_sch_tt(struct usb_device *udev,struct mu3h_sch_tt *tt = sch_ep->sch_tt;u32 base, num_esit;int bw_updated; -int bits;int i, j; num_esit =XHCI_MTK_MAX_ESIT / sch_ep->esit; - bits = (sch_ep->ep_type ==ISOC_OUT_EP ) ? sch_ep->cs_count :1 ;if (used) bw_updated = sch_ep->bw_cost_per_microframe;
@@ -516,13 +505,6 @@ static void update_sch_tt(struct usb_device *udev,for (i =0 ; i < num_esit; i++) { base = sch_ep->offset + i * sch_ep->esit; -for (j =0 ; j < bits; j++) { -if (used) -set_bit (base + j, tt->ss_bit_map); -else -clear_bit (base + j, tt->ss_bit_map); - } -for (j =0 ; j < sch_ep->cs_count; j++) tt->fs_bus_bw[base + j] += bw_updated; }
drivers/usb/host/xhci-mtk.h +0 -2
@@ -20,14 +20,12 @@#define XHCI_MTK_MAX_ESIT 64/** -* @ss_bit_map: used to avoid start split microframes overlay * @fs_bus_bw: array to keep track of bandwidth already used for FS * @ep_list: Endpoints using this TT * @usb_tt: usb TT related * @tt_port: TT port number */ struct mu3h_sch_tt { - DECLARE_BITMAP(ss_bit_map, XHCI_MTK_MAX_ESIT);u32 fs_bus_bw[XHCI_MTK_MAX_ESIT ];struct list_head ep_list;struct usb_tt *usb_tt;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 19/141 usb: xhci-mtk: relax TT periodic bandwidth allocation
In reply to Greg Kroah-HartmanFrom: Ikjoon Jang <[email protected]>
[ Upstream commit 548011957d1d72e0b662300c8b32b81d593b796e ]
Currently xhci-mtk needs software-managed bandwidth allocation for periodic endpoints, it allocates the microframe index for the first start-split packet for each endpoint. As this index allocation logic should avoid the conflicts with other full/low-speed periodic endpoints, it uses the worst case byte budgets on high-speed bus bandwidth For example, for an isochronos IN endpoint with 192 bytes budget, it will consume the whole 4 u-frames(188 * 4) while the actual full-speed bus budget should be just 192bytes.
This patch changes the low/full-speed bandwidth allocation logic to use "approximate" best case budget for lower speed bandwidth management. For the same endpoint from the above example, the approximate best case budget is now reduced to (188 * 2) bytes.
Without this patch, many usb audio headsets with 3 interfaces (audio input, audio output, and HID) cannot be configured on xhci-mtk.
--- drivers/usb/host/xhci-mtk-sch.c | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +13 -7
@@ -408,16 +408,17 @@ static int check_fs_bus_bw(struct mu3h_sch_ep_info *sch_ep, int offset)u32 num_esit, tmp;int base;int i, j; +u8 uframes =DIV_ROUND_UP (sch_ep->maxpkt,FS_PAYLOAD_MAX ); num_esit =XHCI_MTK_MAX_ESIT / sch_ep->esit; + +if (sch_ep->ep_type ==INT_IN_EP || sch_ep->ep_type ==ISOC_IN_EP ) + offset++; +for (i =0 ; i < num_esit; i++) { base = offset + i * sch_ep->esit; -/* -* Compared with hs bus, no matter what ep type, -* the hub will always delay one uframe to send data -*/ -for (j =0 ; j < sch_ep->cs_count; j++) { +for (j =0 ; j < uframes; j++) { tmp = tt->fs_bus_bw[base + j] + sch_ep->bw_cost_per_microframe;if (tmp >FS_PAYLOAD_MAX )return -ESCH_BW_OVERFLOW ;
@@ -494,6 +495,8 @@ static void update_sch_tt(struct usb_device *udev,u32 base, num_esit;int bw_updated;int i, j; +int offset = sch_ep->offset; +u8 uframes =DIV_ROUND_UP (sch_ep->maxpkt,FS_PAYLOAD_MAX ); num_esit =XHCI_MTK_MAX_ESIT / sch_ep->esit;
@@ -502,10 +505,13 @@ static void update_sch_tt(struct usb_device *udev,else bw_updated = -sch_ep->bw_cost_per_microframe; +if (sch_ep->ep_type ==INT_IN_EP || sch_ep->ep_type ==ISOC_IN_EP ) + offset++; +for (i =0 ; i < num_esit; i++) { - base = sch_ep->offset + i * sch_ep->esit; + base = offset + i * sch_ep->esit; -for (j =0 ; j < sch_ep->cs_count; j++) +for (j =0 ; j < uframes; j++) tt->fs_bus_bw[base + j] += bw_updated; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 20/141 iio:adc:mcp3911: Switch to generic firmware properties.
In reply to Greg Kroah-HartmanFrom: Jonathan Cameron <[email protected]>
[ Upstream commit 4efc1c614d334883cce09c38aa3fe74d3fb0bbf0 ]
This allows use of the driver with other types of firmware such as ACPI PRP0001 based probing.
Also part of a general attempt to remove direct use of of_ specific accessors from IIO.
Added an include for mod_devicetable.h whilst here to cover the struct of_device_id definition.
Stable-dep-of: cfbd76d5c9c4 ("iio: adc: mcp3911: correct "microchip,device-addr" property")
--- drivers/iio/adc/mcp3911.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
drivers/iio/adc/mcp3911.c +6 -3
@@ -10,6 +10,8 @@#include <linux/err.h> #include <linux/iio/iio.h> #include <linux/module.h> +#include <linux/mod_devicetable.h> +#include <linux/property.h> #include <linux/regulator/consumer.h> #include <linux/spi/spi.h>
@@ -209,12 +211,13 @@ static const struct iio_info mcp3911_info = { .write_raw = mcp3911_write_raw, }; -static int mcp3911_config (struct mcp3911 *adc,struct device_node *of_node) +static int mcp3911_config (struct mcp3911 *adc) { +struct device *dev = &adc->spi->dev;u32 configreg;int ret; -of_property_read_u32 (of_node,"device-addr" , &adc->dev_addr); +device_property_read_u32 (dev,"device-addr" , &adc->dev_addr);if (adc->dev_addr >3 ) { dev_err(&adc->spi->dev, "invalid device address (%i). Must be in range 0-3.\n",
@@ -298,7 +301,7 @@ static int mcp3911_probe(struct spi_device *spi) } } - ret =mcp3911_config (adc, spi->dev.of_node); + ret =mcp3911_config (adc);if (ret) goto clk_disable;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 21/141 iio: adc: mcp3911: correct "microchip,device-addr" property
In reply to Greg Kroah-HartmanFrom: Marcus Folkesson <[email protected]>
[ Upstream commit cfbd76d5c9c449739bb74288d982bccf9ff822f4 ]
Go for the right property name that is documented in the bindings.
--- drivers/iio/adc/mcp3911.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/iio/adc/mcp3911.c +8 -1
@@ -217,7 +217,14 @@ static int mcp3911_config(struct mcp3911 *adc)u32 configreg;int ret; -device_property_read_u32 (dev,"device-addr" , &adc->dev_addr); + ret =device_property_read_u32 (dev,"microchip,device-addr" , &adc->dev_addr); + +/* +* Fallback to "device-addr" due to historical mismatch between +* dt-bindings and implementation +*/ +if (ret) +device_property_read_u32 (dev,"device-addr" , &adc->dev_addr);if (adc->dev_addr >3 ) { dev_err(&adc->spi->dev, "invalid device address (%i). Must be in range 0-3.\n",
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 22/141 mmc: core: Fix inconsistent sd3_bus_mode at UHS-I SD voltage switch failure
In reply to Greg Kroah-HartmanFrom: Adrian Hunter <[email protected]>
[ Upstream commit 63f1560930e4e1c4f6279b8ae715c9841fe1a6d3 ]
If re-initialization results is a different signal voltage, because the voltage switch failed previously, but not this time (or vice versa), then sd3_bus_mode will be inconsistent with the card because the SD_SWITCH command is done only upon first initialization.
Fix by always reading SD_SWITCH information during re-initialization, which also means it does not need to be re-read later for the 1.8V fixup workaround.
Note, brief testing showed SD_SWITCH took about 1.8ms to 2ms which added about 1% to 1.5% to the re-initialization time, so it's not particularly significant.
--- drivers/mmc/core/sd.c | 42 ++++++++++++++++-------------------------- 1 file changed, 16 insertions(+), 26 deletions(-)
drivers/mmc/core/sd.c +16 -26
@@ -932,15 +932,16 @@ int mmc_sd_setup_card(struct mmc_host *host, struct mmc_card *card,/* Erase init depends on CSD and SSR */ mmc_init_erase (card); - -/* -* Fetch switch information from card. -*/ - err =mmc_read_switch (card); -if (err) -return err; } +/* +* Fetch switch information from card. Note, sd3_bus_mode can change if +* voltage switch outcome changes, so do this always. +*/ + err =mmc_read_switch (card); +if (err) +return err; +/* * For SPI, enable CRC as appropriate. * This CRC enable is located AFTER the reading of the
@@ -1089,26 +1090,15 @@ static int mmc_sd_init_card(struct mmc_host *host, u32 ocr,if (!v18_fixup_failed && !mmc_host_is_spi (host) &&mmc_host_uhs (host) &&mmc_sd_card_using_v18 (card) && host->ios.signal_voltage !=MMC_SIGNAL_VOLTAGE_180 ) { -/* -* Re-read switch information in case it has changed since -* oldcard was initialized. -*/ -if (oldcard) { - err =mmc_read_switch (card); -if (err) - goto free_card; - } -if (mmc_sd_card_using_v18 (card)) { -if (mmc_host_set_uhs_voltage (host) || -mmc_sd_init_uhs_card (card)) { - v18_fixup_failed = true; -mmc_power_cycle (host, ocr); -if (!oldcard) -mmc_remove_card (card); - goto retry; - } - goto cont; +if (mmc_host_set_uhs_voltage (host) || +mmc_sd_init_uhs_card (card)) { + v18_fixup_failed = true; +mmc_power_cycle (host, ocr); +if (!oldcard) +mmc_remove_card (card); + goto retry; } + goto cont; }/* Initialization sequence for UHS-I cards */
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 23/141 serial: atmel: remove redundant assignment in rs485_config
In reply to Greg Kroah-HartmanFrom: Lino Sanfilippo <[email protected]>
[ Upstream commit 60efd0513916f195dd85bfbf21653f74f9ab019c ]
In uart_set_rs485_config() the serial core already assigns the passed serial_rs485 struct to the uart port.
So remove the assignment from the drivers rs485_config() function to avoid redundancy.
Stable-dep-of: 692a8ebcfc24 ("tty: serial: atmel: Preserve previous USART mode if RS485 disabled")
--- drivers/tty/serial/atmel_serial.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/tty/serial/atmel_serial.c +1 -3
@@ -298,11 +298,9 @@ static int atmel_config_rs485(struct uart_port *port,/* Resetting serial mode to RS232 (0x0) */ mode &= ~ATMEL_US_USMODE ; - port->rs485 = *rs485conf; -if (rs485conf->flags &SER_RS485_ENABLED ) {dev_dbg (port->dev,"Setting UART to RS485\n" ); -if (port->rs485.flags &SER_RS485_RX_DURING_TX ) +if (rs485conf->flags &SER_RS485_RX_DURING_TX ) atmel_port->tx_done_mask =ATMEL_US_TXRDY ;else atmel_port->tx_done_mask =ATMEL_US_TXEMPTY ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 24/141 tty: serial: atmel: Preserve previous USART mode if RS485 disabled
In reply to Greg Kroah-HartmanFrom: Sergiu Moga <[email protected]>
[ Upstream commit 692a8ebcfc24f4a5bea0eb2967e450f584193da6 ]
Whenever the atmel_rs485_config() driver method would be called, the USART mode is reset to normal mode before even checking if RS485 flag is set, thus resulting in losing the previous USART mode in the case where the checking fails.
Some tools, such as linux-serial-test, lead to the driver calling this method when doing the setup of the serial port: after setting the port mode (Hardware Flow Control, Normal Mode, RS485 Mode, etc.), linux-serial-test tries to enable/disable RS485 depending on the commandline arguments that were passed.
Example of how this issue could reveal itself:
When doing a serial communication with Hardware Flow Control through linux-serial-test, the tool would lead to the driver roughly doing the following:
- set the corresponding bit to 1 (ATMEL_US_USMODE_HWHS bit in the ATMEL_US_MR register) through the atmel_set_termios() to enable Hardware Flow Control
- disable RS485 through the atmel_config_rs485() method Thus, when the latter is called, the mode will be reset and the previously set bit is unset, leaving USART in normal mode instead of the expected Hardware Flow Control mode.
This fix ensures that this reset is only done if the checking for RS485 succeeds and that the previous mode is preserved otherwise.
--- drivers/tty/serial/atmel_serial.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/tty/serial/atmel_serial.c +1 -3
@@ -295,9 +295,6 @@ static int atmel_config_rs485(struct uart_port *port, mode =atmel_uart_readl (port,ATMEL_US_MR ); -/* Resetting serial mode to RS232 (0x0) */ - mode &= ~ATMEL_US_USMODE ; -if (rs485conf->flags &SER_RS485_ENABLED ) {dev_dbg (port->dev,"Setting UART to RS485\n" );if (rs485conf->flags &SER_RS485_RX_DURING_TX )
@@ -307,6 +304,7 @@ static int atmel_config_rs485(struct uart_port *port,atmel_uart_writel (port,ATMEL_US_TTGR , rs485conf->delay_rts_after_send); + mode &= ~ATMEL_US_USMODE ; mode |=ATMEL_US_USMODE_RS485 ; }else {dev_dbg (port->dev,"Setting UART to RS232\n" );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 25/141 usb: add quirks for Lenovo OneLink+ Dock
In reply to Greg Kroah-HartmanFrom: Jean-Francois Le Fillatre <[email protected]>
[ Upstream commit 3d5f70949f1b1168fbb17d06eb5c57e984c56c58 ]
The Lenovo OneLink+ Dock contains two VL812 USB3.0 controllers:
17ef:1018 upstream
17ef:1019 downstream
Those two controllers both have problems with some USB3.0 devices, particularly self-powered ones. Typical error messages include:
Timeout while waiting for setup device command
device not accepting address X, error -62
unable to enumerate USB device
By process of elimination the controllers themselves were identified as the cause of the problem. Through trial and error the issue was solved by using USB_QUIRK_RESET_RESUME for both chips.
--- drivers/usb/core/quirks.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/core/quirks.c +4 -0
@@ -438,6 +438,10 @@ static const struct usb_device_id usb_quirk_list[] = { { USB_DEVICE(0x1532, 0x0116), .driver_info = USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL }, + /* Lenovo ThinkPad OneLink+ Dock twin hub controllers (VIA Labs VL812) */ + { USB_DEVICE(0x17ef, 0x1018), .driver_info = USB_QUIRK_RESET_RESUME }, + { USB_DEVICE(0x17ef, 0x1019), .driver_info = USB_QUIRK_RESET_RESUME }, + /* Lenovo USB-C to Ethernet Adapter RTL8153-04 */ { USB_DEVICE(0x17ef, 0x720c), .driver_info = USB_QUIRK_NO_LPM },
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 26/141 usb: gadget: udc-xilinx: replace memcpy with memcpy_toio
In reply to Greg Kroah-HartmanFrom: Piyush Mehta <[email protected]>
[ Upstream commit 8cb339f1c1f04baede9d54c1e40ac96247a6393b ]
For ARM processor, unaligned access to device memory is not allowed. Method memcpy does not take care of alignment.
USB detection failure with the unaligned address of memory access, with below kernel crash. To fix the unaligned address the kernel panic issue, replace memcpy with memcpy_toio method.
Kernel crash:
Unable to handle kernel paging request at virtual address ffff80000c05008a
Mem abort info:
ESR = 0x96000061
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x21: alignment fault
Data abort info:
ISV = 0, ISS = 0x00000061
CM = 0, WnR = 1
swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000000143b000 [ffff80000c05008a] pgd=100000087ffff003, p4d=100000087ffff003, pud=100000087fffe003, pmd=1000000800bcc003, pte=00680000a0010713
Internal error: Oops: 96000061 [#1] SMP Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.19-xilinx-v2022.1 #1 Hardware name: ZynqMP ZCU102 Rev1.0 (DT) pstate: 200000c5 (nzCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __memcpy+0x30/0x260 lr : __xudc_ep0_queue+0xf0/0x110
sp : ffff800008003d00
x29: ffff800008003d00 x28: ffff800009474e80 x27: 00000000000000a0
x26: 0000000000000100 x25: 0000000000000012 x24: ffff000800bc8080
x23: 0000000000000001 x22: 0000000000000012 x21: ffff000800bc8080
x20: 0000000000000012 x19: ffff000800bc8080 x18: 0000000000000000
x17: ffff800876482000 x16: ffff800008004000 x15: 0000000000004000
x14: 00001f09785d0400 x13: 0103020101005567 x12: 0781400000000200
x11: 00000000c5672a10 x10: 00000000000008d0 x9 : ffff800009463cf0 x8 : ffff8000094757b0 x7 : 0201010055670781 x6 : 4000000002000112 x5 : ffff80000c05009a x4 : ffff000800a15012 x3 : ffff00080362ad80 x2 : 0000000000000012 x1 : ffff000800a15000 x0 : ffff80000c050088
Call trace: __memcpy+0x30/0x260 xudc_ep0_queue+0x3c/0x60 usb_ep_queue+0x38/0x44 composite_ep0_queue.constprop.0+0x2c/0xc0 composite_setup+0x8d0/0x185c configfs_composite_setup+0x74/0xb0 xudc_irq+0x570/0xa40 __handle_irq_event_percpu+0x58/0x170 handle_irq_event+0x60/0x120 handle_fasteoi_irq+0xc0/0x220 handle_domain_irq+0x60/0x90 gic_handle_irq+0x74/0xa0 call_on_irq_stack+0x2c/0x60 do_interrupt_handler+0x54/0x60 el1_interrupt+0x30/0x50 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x78/0x7c arch_cpu_idle+0x18/0x2c do_idle+0xdc/0x15c cpu_startup_entry+0x28/0x60 rest_init+0xc8/0xe0 arch_call_rest_init+0x10/0x1c start_kernel+0x694/0x6d4 __primary_switched+0xa4/0xac
--- drivers/usb/gadget/udc/udc-xilinx.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/usb/gadget/udc/udc-xilinx.c +8 -8
@@ -496,11 +496,11 @@ static int xudc_eptxrx(struct xusb_ep *ep, struct xusb_req *req,/* Get the Buffer address and copy the transmit data.*/ eprambase = (u32 __force *)(udc->addr + ep->rambase);if (ep->is_in) { -memcpy (eprambase, bufferptr, bytestosend); +memcpy_toio (eprambase, bufferptr, bytestosend); udc->write_fn (udc->addr, ep->offset +XUSB_EP_BUF0COUNT_OFFSET , bufferlen); }else { -memcpy (bufferptr, eprambase, bytestosend); +memcpy_toio (bufferptr, eprambase, bytestosend); }/* * Enable the buffer for transmission.
@@ -514,11 +514,11 @@ static int xudc_eptxrx(struct xusb_ep *ep, struct xusb_req *req, eprambase = (u32 __force *)(udc->addr + ep->rambase + ep->ep_usb.maxpacket);if (ep->is_in) { -memcpy (eprambase, bufferptr, bytestosend); +memcpy_toio (eprambase, bufferptr, bytestosend); udc->write_fn (udc->addr, ep->offset +XUSB_EP_BUF1COUNT_OFFSET , bufferlen); }else { -memcpy (bufferptr, eprambase, bytestosend); +memcpy_toio (bufferptr, eprambase, bytestosend); }/* * Enable the buffer for transmission.
@@ -1020,7 +1020,7 @@ static int __xudc_ep0_queue(struct xusb_ep *ep0, struct xusb_req *req) udc->addr); length = req->usb_req.actual =min_t (u32, length,EP0_MAX_PACKET ); -memcpy (corebuf, req->usb_req.buf, length); +memcpy_toio (corebuf, req->usb_req.buf, length); udc->write_fn (udc->addr,XUSB_EP_BUF0COUNT_OFFSET , length); udc->write_fn (udc->addr,XUSB_BUFFREADY_OFFSET ,1 ); }else {
@@ -1746,7 +1746,7 @@ static void xudc_handle_setup(struct xusb_udc *udc)/* Load up the chapter 9 command buffer.*/ ep0rambase = (u32 __force *) (udc->addr +XUSB_SETUP_PKT_ADDR_OFFSET ); -memcpy (&setup, ep0rambase,8 ); +memcpy_toio (&setup, ep0rambase,8 ); udc->setup = setup; udc->setup.wValue =cpu_to_le16 (setup.wValue);
@@ -1833,7 +1833,7 @@ static void xudc_ep0_out(struct xusb_udc *udc) (ep0->rambase << 2)); buffer = req->usb_req.buf + req->usb_req.actual; req->usb_req.actual = req->usb_req.actual + bytes_to_rx; -memcpy (buffer, ep0rambase, bytes_to_rx); +memcpy_toio (buffer, ep0rambase, bytes_to_rx);if (req->usb_req.length == req->usb_req.actual) {/* Data transfer completed get ready for Status stage */
@@ -1909,7 +1909,7 @@ static void xudc_ep0_in(struct xusb_udc *udc) (ep0->rambase << 2)); buffer = req->usb_req.buf + req->usb_req.actual; req->usb_req.actual = req->usb_req.actual + length; -memcpy (ep0rambase, buffer, length); +memcpy_toio (ep0rambase, buffer, length); } udc->write_fn (udc->addr,XUSB_EP_BUF0COUNT_OFFSET , count); udc->write_fn (udc->addr,XUSB_BUFFREADY_OFFSET ,1 );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 27/141 usb: cdns3: fix incorrect handling TRB_SMM flag for ISOC transfer
In reply to Greg Kroah-HartmanFrom: Pawel Laszczak <[email protected]>
[ Upstream commit d5dcc33677d7415c5f23b3c052f9e80cbab9ea4e ]
The TRB_SMM flag indicates that DMA has completed the TD service with this TRB. Usually it’s a last TRB in TD. In case of ISOC transfer for bInterval > 1 each ISOC transfer contains more than one TD associated with usb request (one TD per ITP). In such case the TRB_SMM flag will be set in every TD and driver will recognize the end of transfer after processing the first TD with TRB_SMM. In result driver stops updating request->actual and returns incorrect actual length.
To fix this issue driver additionally must check TRB_CHAIN which is not used for isochronous transfers.
--- drivers/usb/cdns3/gadget.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/usb/cdns3/gadget.c +2 -1
@@ -1531,7 +1531,8 @@ static void cdns3_transfer_completed(struct cdns3_device *priv_dev,TRB_LEN (le32_to_cpu (trb->length));if (priv_req->num_of_trb >1 && -le32_to_cpu (trb->control) &TRB_SMM ) +le32_to_cpu (trb->control) &TRB_SMM && +le32_to_cpu (trb->control) &TRB_CHAIN ) transfer_end = true;cdns3_ep_inc_deq (priv_ep);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 28/141 usb: cdns3: fix issue with rearming ISO OUT endpoint
In reply to Greg Kroah-HartmanFrom: Pawel Laszczak <[email protected]>
[ Upstream commit b46a6b09fa056042a302b181a1941f0056944603 ]
ISO OUT endpoint is enabled during queuing first usb request in transfer ring and disabled when TRBERR is reported by controller. After TRBERR and before next transfer added to TR driver must again reenable endpoint but does not.
To solve this issue during processing TRBERR event driver must set the flag EP_UPDATE_EP_TRBADDR in priv_ep->flags field.
--- drivers/usb/cdns3/gadget.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/cdns3/gadget.c +1 -0
@@ -1692,6 +1692,7 @@ static int cdns3_check_ep_interrupt_proceed(struct cdns3_endpoint *priv_ep) ep_cfg &= ~EP_CFG_ENABLE ;writel (ep_cfg, &priv_dev->regs->ep_cfg); priv_ep->flags &= ~EP_QUIRK_ISO_OUT_EN ; + priv_ep->flags |=EP_UPDATE_EP_TRBADDR ; }cdns3_transfer_completed (priv_dev, priv_ep); } else if (!(priv_ep->flags & EP_STALLED) &&
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 29/141 Revert "usb: add quirks for Lenovo OneLink+ Dock"
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
[ Upstream commit 58bfe7d8e31014d7ce246788df99c56e3cfe6c68 ]
This reverts commit 3d5f70949f1b1168fbb17d06eb5c57e984c56c58.
The quirk does not work properly, more work is needed to determine what should be done here.
--- drivers/usb/core/quirks.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/usb/core/quirks.c +0 -4
@@ -438,10 +438,6 @@ static const struct usb_device_id usb_quirk_list[] = { { USB_DEVICE(0x1532, 0x0116), .driver_info = USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL }, - /* Lenovo ThinkPad OneLink+ Dock twin hub controllers (VIA Labs VL812) */ - { USB_DEVICE(0x17ef, 0x1018), .driver_info = USB_QUIRK_RESET_RESUME }, - { USB_DEVICE(0x17ef, 0x1019), .driver_info = USB_QUIRK_RESET_RESUME }, - /* Lenovo USB-C to Ethernet Adapter RTL8153-04 */ { USB_DEVICE(0x17ef, 0x720c), .driver_info = USB_QUIRK_NO_LPM },
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 30/141 vfio/type1: Change success value of vaddr_get_pfn()
In reply to Greg Kroah-HartmanFrom: Daniel Jordan <[email protected]>
[ Upstream commit be16c1fd99f41abebc0bf965d5d29cd18c9d271e ]
vaddr_get_pfn() simply returns 0 on success. Have it report the number of pfns successfully gotten instead, whether from page pinning or follow_fault_pfn(), which will be used later when batching pinning.
Change the last check in vfio_pin_pages_remote() for consistency with the other two.
Stable-dep-of: 873aefb376bb ("vfio/type1: Unpin zero pages")
--- drivers/vfio/vfio_iommu_type1.c | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-)
drivers/vfio/vfio_iommu_type1.c +14 -7
@@ -464,6 +464,10 @@ static int follow_fault_pfn(struct vm_area_struct *vma, struct mm_struct *mm,return ret; } +/* +* Returns the positive number of pfns successfully obtained or a negative +* error code. +*/ static int vaddr_get_pfn (struct mm_struct *mm,unsigned long vaddr,int prot,unsigned long *pfn) {
@@ -480,7 +484,6 @@ static int vaddr_get_pfn(struct mm_struct *mm, unsigned long vaddr, page, NULL, NULL);if (ret ==1 ) { *pfn =page_to_pfn (page[0 ]); - ret =0 ; goto done; }
@@ -494,8 +497,12 @@ static int vaddr_get_pfn(struct mm_struct *mm, unsigned long vaddr,if (ret == -EAGAIN ) goto retry; -if (!ret && !is_invalid_reserved_pfn (*pfn)) - ret = -EFAULT ; +if (!ret) { +if (is_invalid_reserved_pfn (*pfn)) + ret =1 ; +else + ret = -EFAULT ; + } } done:mmap_read_unlock (mm);
@@ -521,7 +528,7 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr,return -ENODEV ; ret =vaddr_get_pfn (current->mm, vaddr, dma->prot, pfn_base); -if (ret) +if (ret <0 )return ret; pinned++;
@@ -548,7 +555,7 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr,for (vaddr +=PAGE_SIZE , iova +=PAGE_SIZE ; pinned < npage; pinned++, vaddr +=PAGE_SIZE , iova +=PAGE_SIZE ) { ret =vaddr_get_pfn (current->mm, vaddr, dma->prot, &pfn); -if (ret) +if (ret <0 )break ; if (pfn != *pfn_base + pinned ||
@@ -574,7 +581,7 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr, ret =vfio_lock_acct (dma, lock_acct, false); unpin_out: -if (ret) { +if (ret <0 ) {if (!rsvd) {for (pfn = *pfn_base ; pinned ; pfn++, pinned--)put_pfn (pfn, dma->prot);
@@ -618,7 +625,7 @@ static int vfio_pin_page_external(struct vfio_dma *dma, unsigned long vaddr,return -ENODEV ; ret =vaddr_get_pfn (mm, vaddr, dma->prot, pfn_base); -if (!ret && do_accounting && !is_invalid_reserved_pfn (*pfn_base)) { +if (ret ==1 && do_accounting && !is_invalid_reserved_pfn (*pfn_base)) { ret =vfio_lock_acct (dma,1 , true);if (ret) {put_pfn (*pfn_base, dma->prot);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 31/141 vfio/type1: Prepare for batched pinning with struct vfio_batch
In reply to Greg Kroah-HartmanFrom: Daniel Jordan <[email protected]>
[ Upstream commit 4b6c33b3229678e38a6b0bbd4367d4b91366b523 ]
Get ready to pin more pages at once with struct vfio_batch, which represents a batch of pinned pages.
The struct has a fallback page pointer to avoid two unlikely scenarios:
pointlessly allocating a page if disable_hugepages is enabled or failing the whole pinning operation if the kernel can't allocate memory.
vaddr_get_pfn() becomes vaddr_get_pfns() to prepare for handling multiple pages, though for now only one page is stored in the pages array.
Stable-dep-of: 873aefb376bb ("vfio/type1: Unpin zero pages")
--- drivers/vfio/vfio_iommu_type1.c | 71 +++++++++++++++++++++++++++------ 1 file changed, 58 insertions(+), 13 deletions(-)
drivers/vfio/vfio_iommu_type1.c +58 -13
@@ -98,6 +98,12 @@ struct vfio_dma {unsigned long *bitmap; }; +struct vfio_batch { +struct page **pages;/* for pin_user_pages_remote */ +struct page *fallback_page;/* if pages alloc fails */ +int capacity;/* length of pages array */ +}; +struct vfio_group {struct iommu_group *iommu_group;struct list_head next;
@@ -428,6 +434,31 @@ static int put_pfn(unsigned long pfn, int prot)return 0 ; } +#define VFIO_BATCH_MAX_CAPACITY (PAGE_SIZE / sizeof(struct page *)) + +static void vfio_batch_init (struct vfio_batch *batch) +{ +if (unlikely (disable_hugepages)) + goto fallback; + + batch->pages = (struct page **)__get_free_page (GFP_KERNEL ); +if (!batch->pages) + goto fallback; + + batch->capacity =VFIO_BATCH_MAX_CAPACITY ; +return ; + +fallback: + batch->pages = &batch->fallback_page; + batch->capacity =1 ; +} + +static void vfio_batch_fini (struct vfio_batch *batch) +{ +if (batch->capacity ==VFIO_BATCH_MAX_CAPACITY ) +free_page ((unsigned long )batch->pages); +} +static int follow_fault_pfn (struct vm_area_struct *vma,struct mm_struct *mm,unsigned long vaddr,unsigned long *pfn,bool write_fault)
@@ -468,10 +499,10 @@ static int follow_fault_pfn(struct vm_area_struct *vma, struct mm_struct *mm,* Returns the positive number of pfns successfully obtained or a negative * error code. */ -static int vaddr_get_pfn (struct mm_struct *mm,unsigned long vaddr, -int prot,unsigned long *pfn) +static int vaddr_get_pfns (struct mm_struct *mm,unsigned long vaddr, +long npages,int prot,unsigned long *pfn, +struct page **pages) { -struct page *page[1 ];struct vm_area_struct *vma;unsigned int flags =0 ;int ret;
@@ -480,10 +511,10 @@ static int vaddr_get_pfn(struct mm_struct *mm, unsigned long vaddr, flags |=FOLL_WRITE ;mmap_read_lock (mm); - ret =pin_user_pages_remote (mm, vaddr,1 , flags |FOLL_LONGTERM , - page,NULL ,NULL ); -if (ret ==1 ) { - *pfn =page_to_pfn (page[0 ]); + ret =pin_user_pages_remote (mm, vaddr, npages, flags |FOLL_LONGTERM , + pages,NULL ,NULL ); +if (ret >0 ) { + *pfn =page_to_pfn (pages[0 ]); goto done; }
@@ -516,7 +547,7 @@ static int vaddr_get_pfn(struct mm_struct *mm, unsigned long vaddr,*/ static long vfio_pin_pages_remote (struct vfio_dma *dma,unsigned long vaddr,long npage,unsigned long *pfn_base, -unsigned long limit) +unsigned long limit,struct vfio_batch *batch) {unsigned long pfn =0 ;long ret, pinned =0 , lock_acct =0 ;
@@ -527,7 +558,8 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr,if (!current->mm)return -ENODEV ; - ret =vaddr_get_pfn (current->mm, vaddr, dma->prot, pfn_base); + ret =vaddr_get_pfns (current->mm, vaddr,1 , dma->prot, pfn_base, + batch->pages);if (ret <0 )return ret;
@@ -554,7 +586,8 @@ static long vfio_pin_pages_remote(struct vfio_dma *dma, unsigned long vaddr,/* Lock all the consecutive pages from pfn_base */ for (vaddr +=PAGE_SIZE , iova +=PAGE_SIZE ; pinned < npage; pinned++, vaddr +=PAGE_SIZE , iova +=PAGE_SIZE ) { - ret =vaddr_get_pfn (current->mm, vaddr, dma->prot, &pfn); + ret =vaddr_get_pfns (current->mm, vaddr,1 , dma->prot, &pfn, + batch->pages);if (ret <0 )break ;
@@ -617,6 +650,7 @@ static long vfio_unpin_pages_remote(struct vfio_dma *dma, dma_addr_t iova,static int vfio_pin_page_external (struct vfio_dma *dma,unsigned long vaddr,unsigned long *pfn_base,bool do_accounting) { +struct page *pages[1 ];struct mm_struct *mm;int ret;
@@ -624,7 +658,7 @@ static int vfio_pin_page_external(struct vfio_dma *dma, unsigned long vaddr,if (!mm)return -ENODEV ; - ret =vaddr_get_pfn (mm, vaddr, dma->prot, pfn_base); + ret =vaddr_get_pfns (mm, vaddr,1 , dma->prot, pfn_base, pages);if (ret ==1 && do_accounting && !is_invalid_reserved_pfn (*pfn_base)) { ret =vfio_lock_acct (dma,1 , true);if (ret) {
@@ -1270,15 +1304,19 @@ static int vfio_pin_map_dma(struct vfio_iommu *iommu, struct vfio_dma *dma, {dma_addr_t iova = dma->iova;unsigned long vaddr = dma->vaddr; +struct vfio_batch batch;size_t size = map_size;long npage;unsigned long pfn, limit =rlimit (RLIMIT_MEMLOCK ) >>PAGE_SHIFT ;int ret =0 ; +vfio_batch_init (&batch); +while (size) {/* Pin a contiguous chunk of memory */ npage =vfio_pin_pages_remote (dma, vaddr + dma->size, - size >>PAGE_SHIFT , &pfn, limit); + size >>PAGE_SHIFT , &pfn, limit, + &batch);if (npage <=0 ) {WARN_ON (!npage); ret = (int )npage;
@@ -1298,6 +1336,7 @@ static int vfio_pin_map_dma(struct vfio_iommu *iommu, struct vfio_dma *dma, dma->size += npage <<PAGE_SHIFT ; } +vfio_batch_fini (&batch); dma->iommu_mapped = true;if (ret)
@@ -1456,6 +1495,7 @@ static int vfio_bus_type(struct device *dev, void *data)static int vfio_iommu_replay (struct vfio_iommu *iommu,struct vfio_domain *domain) { +struct vfio_batch batch;struct vfio_domain *d =NULL ;struct rb_node *n;unsigned long limit =rlimit (RLIMIT_MEMLOCK ) >>PAGE_SHIFT ;
@@ -1466,6 +1506,8 @@ static int vfio_iommu_replay(struct vfio_iommu *iommu, d =list_first_entry (&iommu->domain_list, struct vfio_domain, next); +vfio_batch_init (&batch); + n =rb_first (&iommu->dma_list);for (; n; n =rb_next (n)) {
@@ -1513,7 +1555,8 @@ static int vfio_iommu_replay(struct vfio_iommu *iommu, npage =vfio_pin_pages_remote (dma, vaddr, n >>PAGE_SHIFT , - &pfn, limit); + &pfn, limit, + &batch);if (npage <=0 ) {WARN_ON (!npage); ret = (int )npage;
@@ -1546,6 +1589,7 @@ static int vfio_iommu_replay(struct vfio_iommu *iommu, dma->iommu_mapped = true; } +vfio_batch_fini (&batch);return 0 ; unwind:
@@ -1586,6 +1630,7 @@ static int vfio_iommu_replay(struct vfio_iommu *iommu, } } +vfio_batch_fini (&batch);return ret; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 32/141 vfio/type1: Unpin zero pages
In reply to Greg Kroah-HartmanFrom: Alex Williamson <[email protected]>
[ Upstream commit 873aefb376bbc0ed1dd2381ea1d6ec88106fdbd4 ]
There's currently a reference count leak on the zero page. We increment the reference via pin_user_pages_remote(), but the page is later handled as an invalid/reserved page, therefore it's not accounted against the user and not unpinned by our put_pfn().
Introducing special zero page handling in put_pfn() would resolve the leak, but without accounting of the zero page, a single user could still create enough mappings to generate a reference count overflow.
The zero page is always resident, so for our purposes there's no reason to keep it pinned. Therefore, add a loop to walk pages returned from pin_user_pages_remote() and unpin any zero pages.
--- drivers/vfio/vfio_iommu_type1.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/vfio/vfio_iommu_type1.c +12 -0
@@ -514,6 +514,18 @@ static int vaddr_get_pfns(struct mm_struct *mm, unsigned long vaddr, ret =pin_user_pages_remote (mm, vaddr, npages, flags |FOLL_LONGTERM , pages,NULL ,NULL );if (ret >0 ) { +int i; + +/* +* The zero page is always resident, we don't need to pin it +* and it falls into our invalid/reserved test so we don't +* unpin in put_pfn(). Unpin all zero pages in the batch here. +*/ +for (i =0 ; i < ret; i++) { +if (unlikely (is_zero_pfn (page_to_pfn (pages[i])))) +unpin_user_page (pages[i]); + } + *pfn =page_to_pfn (pages[0 ]); goto done; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 33/141 Revert "usb: gadget: udc-xilinx: replace memcpy with memcpy_toio"
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
[ Upstream commit fe0a2ac7c627b064c479ad0c3b25e531d342e048 ]
This reverts commit 8cb339f1c1f04baede9d54c1e40ac96247a6393b as it throws up a bunch of sparse warnings as reported by the kernel test robot.
--- drivers/usb/gadget/udc/udc-xilinx.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
drivers/usb/gadget/udc/udc-xilinx.c +8 -8
@@ -496,11 +496,11 @@ static int xudc_eptxrx(struct xusb_ep *ep, struct xusb_req *req,/* Get the Buffer address and copy the transmit data.*/ eprambase = (u32 __force *)(udc->addr + ep->rambase);if (ep->is_in) { -memcpy_toio (eprambase, bufferptr, bytestosend); +memcpy (eprambase, bufferptr, bytestosend); udc->write_fn (udc->addr, ep->offset +XUSB_EP_BUF0COUNT_OFFSET , bufferlen); }else { -memcpy_toio (bufferptr, eprambase, bytestosend); +memcpy (bufferptr, eprambase, bytestosend); }/* * Enable the buffer for transmission.
@@ -514,11 +514,11 @@ static int xudc_eptxrx(struct xusb_ep *ep, struct xusb_req *req, eprambase = (u32 __force *)(udc->addr + ep->rambase + ep->ep_usb.maxpacket);if (ep->is_in) { -memcpy_toio (eprambase, bufferptr, bytestosend); +memcpy (eprambase, bufferptr, bytestosend); udc->write_fn (udc->addr, ep->offset +XUSB_EP_BUF1COUNT_OFFSET , bufferlen); }else { -memcpy_toio (bufferptr, eprambase, bytestosend); +memcpy (bufferptr, eprambase, bytestosend); }/* * Enable the buffer for transmission.
@@ -1020,7 +1020,7 @@ static int __xudc_ep0_queue(struct xusb_ep *ep0, struct xusb_req *req) udc->addr); length = req->usb_req.actual =min_t (u32, length,EP0_MAX_PACKET ); -memcpy_toio (corebuf, req->usb_req.buf, length); +memcpy (corebuf, req->usb_req.buf, length); udc->write_fn (udc->addr,XUSB_EP_BUF0COUNT_OFFSET , length); udc->write_fn (udc->addr,XUSB_BUFFREADY_OFFSET ,1 ); }else {
@@ -1746,7 +1746,7 @@ static void xudc_handle_setup(struct xusb_udc *udc)/* Load up the chapter 9 command buffer.*/ ep0rambase = (u32 __force *) (udc->addr +XUSB_SETUP_PKT_ADDR_OFFSET ); -memcpy_toio (&setup, ep0rambase,8 ); +memcpy (&setup, ep0rambase,8 ); udc->setup = setup; udc->setup.wValue =cpu_to_le16 (setup.wValue);
@@ -1833,7 +1833,7 @@ static void xudc_ep0_out(struct xusb_udc *udc) (ep0->rambase << 2)); buffer = req->usb_req.buf + req->usb_req.actual; req->usb_req.actual = req->usb_req.actual + bytes_to_rx; -memcpy_toio (buffer, ep0rambase, bytes_to_rx); +memcpy (buffer, ep0rambase, bytes_to_rx);if (req->usb_req.length == req->usb_req.actual) {/* Data transfer completed get ready for Status stage */
@@ -1909,7 +1909,7 @@ static void xudc_ep0_in(struct xusb_udc *udc) (ep0->rambase << 2)); buffer = req->usb_req.buf + req->usb_req.actual; req->usb_req.actual = req->usb_req.actual + length; -memcpy_toio (ep0rambase, buffer, length); +memcpy (ep0rambase, buffer, length); } udc->write_fn (udc->addr,XUSB_EP_BUF0COUNT_OFFSET , count); udc->write_fn (udc->addr,XUSB_BUFFREADY_OFFSET ,1 );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 34/141 arm64: Restrict ARM64_BTI_KERNEL to clang 12.0.0 and newer
In reply to Greg Kroah-HartmanFrom: Nathan Chancellor <[email protected]>
[ Upstream commit 8cdd23c23c3d481a43b4aa03dcb5738812831115 ]
Commit 97fed779f2a6 ("arm64: bti: Provide Kconfig for kernel mode BTI") disabled CONFIG_ARM64_BTI_KERNEL when CONFIG_GCOV_KERNEL was enabled and compiling with clang because of warnings that were seen with allmodconfig because LLVM was not emitting PAC/BTI instructions for compiler generated functions:
| warning: some functions compiled with BTI and some compiled without BTI | warning: not setting BTI in feature flags
This dependency was fine for avoiding the warnings with allmodconfig until commit 51c2ee6d121c ("Kconfig: Introduce ARCH_WANTS_NO_INSTR and CC_HAS_NO_PROFILE_FN_ATTR"), which prevents CONFIG_GCOV_KERNEL from being enabled with clang 12.0.0 or older because those versions do not support the no_profile_instrument_function attribute.
As a result, CONFIG_ARM64_BTI_KERNEL gets enabled with allmodconfig and there are more warnings like the ones above due to CONFIG_KASAN, which suffers from the same problem as CONFIG_GCOV_KERNEL. This was most likely not noticed at the time because allmodconfig + CONFIG_GCOV_KERNEL=n was not tested. defconfig + CONFIG_KASAN=y is enough to reproduce the same warnings as above.
The root cause of the warnings was resolved in LLVM during the 12.0.0 release so rather than play whack-a-mole with the dependencies, just update CONFIG_ARM64_BTI_KERNEL to require clang 12.0.0, which will have all of the issues ironed out.
Stable-dep-of: c0a454b9044f ("arm64/bti: Disable in kernel BTI when cross section thunks are broken")
--- arch/arm64/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/arm64/Kconfig +2 -1
@@ -1654,7 +1654,8 @@ config ARM64_BTI_KERNEL depends on CC_HAS_BRANCH_PROT_PAC_RET_BTI # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94697 depends on !CC_IS_GCC || GCC_VERSION >= 100100 - depends on !(CC_IS_CLANG && GCOV_KERNEL) + # https://github.com/llvm/llvm-project/commit/a88c722e687e6780dcd6a58718350dc76fcc4cc9 + depends on !CC_IS_CLANG || CLANG_VERSION >= 120000 depends on (!FUNCTION_GRAPH_TRACER || DYNAMIC_FTRACE_WITH_REGS) help Build the kernel with Branch Target Identification annotations
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 35/141 arm64/bti: Disable in kernel BTI when cross section thunks are broken
In reply to Greg Kroah-HartmanFrom: Mark Brown <[email protected]>
[ Upstream commit c0a454b9044fdc99486853aa424e5b3be2107078 ]
GCC does not insert a bti c instruction at the beginning of a function when it believes that all callers reach the function through a direct branch[1]. Unfortunately the logic it uses to determine this is not sufficiently robust, for example not taking account of functions being placed in different sections which may be loaded separately, so we may still see thunks being generated to these functions. If that happens, the first instruction in the callee function will result in a Branch Target Exception due to the missing landing pad.
While this has currently only been observed in the case of modules having their main code loaded sufficiently far from their init section to require thunks it could potentially happen for other cases so the safest thing is to disable BTI for the kernel when building with an affected toolchain.
[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106671
--- arch/arm64/Kconfig | 2 ++ 1 file changed, 2 insertions(+)
arch/arm64/Kconfig +2 -0
@@ -1654,6 +1654,8 @@ config ARM64_BTI_KERNEL depends on CC_HAS_BRANCH_PROT_PAC_RET_BTI # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94697 depends on !CC_IS_GCC || GCC_VERSION >= 100100 + # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106671 + depends on !CC_IS_GCC # https://github.com/llvm/llvm-project/commit/a88c722e687e6780dcd6a58718350dc76fcc4cc9 depends on !CC_IS_CLANG || CLANG_VERSION >= 120000 depends on (!FUNCTION_GRAPH_TRACER || DYNAMIC_FTRACE_WITH_REGS)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 36/141 USB: core: Fix RST error in hub.c
In reply to Greg Kroah-HartmanFrom: Alan Stern <[email protected]>
commit 766a96dc558385be735a370db867e302c8f22153 upstream.
A recent commit added an invalid RST expression to a kerneldoc comment in hub.c. The fix is trivial.
--- drivers/usb/core/hub.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/core/hub.c +1 -1
@@ -5968,7 +5968,7 @@ re_enumerate_no_bos:* * Return: The same as for usb_reset_and_verify_device(). * However, if a reset is already in progress (for instance, if a -* driver doesn't have pre_ or post_reset() callbacks, and while +* driver doesn't have pre_reset() or post_reset() callbacks, and while * being unbound or re-bound during the ongoing reset its disconnect() * or probe() routine tries to perform a second, nested reset), the * routine returns -EINPROGRESS.
Greg Kroah-Hartman
maintainerPATCH 37/141 USB: serial: option: add Quectel BG95 0x0203 composition
In reply to Greg Kroah-HartmanFrom: Carl Yin(殷张成) <[email protected]>
commit f8f67eff6847f9b8d753fa029723bcc54296055a upstream.
Add support for the following Quectel BG95 composition:
0x0203: Diag + GNSS + Modem + ECM
usb-devices output:
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=2c7c ProdID=0203 Rev= 0.00 S: Manufacturer=Quectel, Incorporated S: Product=Quectel LPWA Module S: SerialNumber=71d3a21b C:* #Ifs= 5 Cfg#= 1 Atr=e0 MxPwr=500mA A: FirstIf#= 3 IfCount= 2 Cls=02(comm.) Sub=00 Prot=00 I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=option E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=60 Driver=option E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=2ms E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 3 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=06 Prot=00 Driver=cdc_ether E: Ad=85(I) Atr=03(Int.) MxPS= 64 Ivl=2ms I: If#= 4 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether I:* If#= 4 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
--- drivers/usb/serial/option.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/usb/serial/option.c +2 -0
@@ -1138,6 +1138,8 @@ static const struct usb_device_id option { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_EG95, 0xff, 0xff, 0xff), .driver_info = NUMEP2 }, { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_EG95, 0xff, 0, 0) }, + { USB_DEVICE_INTERFACE_CLASS(QUECTEL_VENDOR_ID, 0x0203, 0xff), /* BG95-M3 */ + .driver_info = ZLP }, { USB_DEVICE(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_BG96), .driver_info = RSVD(4) }, { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_EP06, 0xff, 0xff, 0xff),
Greg Kroah-Hartman
maintainerPATCH 38/141 USB: serial: option: add Quectel RM520N
In reply to Greg Kroah-HartmanFrom: jerry meng <[email protected]>
commit d640c4cb8f2f933c0ca896541f9de7fb1ae245f4 upstream.
add support for Quectel RM520N which is based on Qualcomm SDX62 chip.
0x0801: DIAG + NMEA + AT + MODEM + RMNET
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 10 Spd=480 MxCh= 0 D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=2c7c ProdID=0801 Rev= 5.04 S: Manufacturer=Quectel S: Product=RM520N-GL S: SerialNumber=384af524 C:* #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=option E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=40 Driver=option E: Ad=83(I) Atr=03(Int.) MxPS= 10 Ivl=32ms E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option E: Ad=85(I) Atr=03(Int.) MxPS= 10 Ivl=32ms E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option E: Ad=87(I) Atr=03(Int.) MxPS= 10 Ivl=32ms E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan E: Ad=88(I) Atr=03(Int.) MxPS= 8 Ivl=32ms E: Ad=8e(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=0f(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
--- drivers/usb/serial/option.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/usb/serial/option.c +4 -0
@@ -256,6 +256,7 @@ static void option_instat_callback(struc#define QUECTEL_PRODUCT_EM060K 0x030b#define QUECTEL_PRODUCT_EM12 0x0512#define QUECTEL_PRODUCT_RM500Q 0x0800 +#define QUECTEL_PRODUCT_RM520N 0x0801#define QUECTEL_PRODUCT_EC200S_CN 0x6002#define QUECTEL_PRODUCT_EC200T 0x6026#define QUECTEL_PRODUCT_RM500K 0x7001
@@ -1161,6 +1162,9 @@ static const struct usb_device_id option { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_RM500Q, 0xff, 0, 0) }, { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_RM500Q, 0xff, 0xff, 0x10), .driver_info = ZLP }, + { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_RM520N, 0xff, 0xff, 0x30) }, + { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_RM520N, 0xff, 0, 0x40) }, + { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_RM520N, 0xff, 0, 0) }, { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_EC200S_CN, 0xff, 0, 0) }, { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_EC200T, 0xff, 0, 0) }, { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_RM500K, 0xff, 0x00, 0x00) },
Greg Kroah-Hartman
maintainerPATCH 39/141 ALSA: hda/tegra: set depop delay for tegra
In reply to Greg Kroah-HartmanFrom: Mohan Kumar <[email protected]>
commit 3c4d8c24fb6c44f426e447b04800b0ed61a7b5ae upstream.
Reduce the suspend time by setting depop delay to 10ms for tegra.
--- sound/pci/hda/patch_hdmi.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_hdmi.c +1 -0
@@ -3839,6 +3839,7 @@ static int patch_tegra_hdmi(struct hda_cif (err)return err; + codec->depop_delay =10 ; codec->patch_ops.build_pcms = tegra_hdmi_build_pcms; spec = codec->spec; spec->chmap.ops.chmap_cea_alloc_validate_get_type =
Greg Kroah-Hartman
maintainerPATCH 40/141 ALSA: hda: add Intel 5 Series / 3400 PCI DID
In reply to Greg Kroah-HartmanFrom: Kai Vehmanen <[email protected]>
commit 4d40ceef4745536289012670103c59264e0fb3ec upstream.
Handle 0x3b57 variant with same AZX_DCAPS_INTEL_PCH_NOPM capabilities as 0x3b56. In practise this allow use of HDMI/DP display audio via i915.
--- sound/pci/hda/hda_intel.c | 2 ++ 1 file changed, 2 insertions(+)
sound/pci/hda/hda_intel.c +2 -0
@@ -2584,6 +2584,8 @@ static const struct pci_device_id azx_id/* 5 Series/3400 */ { PCI_DEVICE(0x8086, 0x3b56), .driver_data = AZX_DRIVER_SCH | AZX_DCAPS_INTEL_PCH_NOPM }, + { PCI_DEVICE(0x8086, 0x3b57), + .driver_data = AZX_DRIVER_SCH | AZX_DCAPS_INTEL_PCH_NOPM }, /* Poulsbo */ { PCI_DEVICE(0x8086, 0x811b), .driver_data = AZX_DRIVER_SCH | AZX_DCAPS_INTEL_PCH_BASE },
Greg Kroah-Hartman
maintainerPATCH 41/141 ALSA: hda/realtek: Add quirk for Huawei WRT-WX9
In reply to Greg Kroah-HartmanFrom: huangwenhui <[email protected]>
commit cbcdf8c4d35cd74aee8581eb2f0453e0ecab7b05 upstream.
Fixes headphone and headset microphone detection on Huawei WRT-WX9.
--- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +1 -0
@@ -9134,6 +9134,7 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x17aa ,0x9e54 ,"LENOVO NB" ,ALC269_FIXUP_LENOVO_EAPD ),SND_PCI_QUIRK (0x1849 ,0x1233 ,"ASRock NUC Box 1100" ,ALC233_FIXUP_NO_AUDIO_JACK ),SND_PCI_QUIRK (0x19e5 ,0x3204 ,"Huawei MACH-WX9" ,ALC256_FIXUP_HUAWEI_MACH_WX9_PINS ), +SND_PCI_QUIRK (0x19e5 ,0x320f ,"Huawei WRT-WX9 " ,ALC256_FIXUP_ASUS_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1b35 ,0x1235 ,"CZC B20" ,ALC269_FIXUP_CZC_B20 ),SND_PCI_QUIRK (0x1b35 ,0x1236 ,"CZC TMI" ,ALC269_FIXUP_CZC_TMI ), SND_PCI_QUIRK(0x1b35, 0x1237, "CZC L101", ALC269_FIXUP_CZC_L101),
Greg Kroah-Hartman
maintainerPATCH 42/141 ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5570 laptop
In reply to Greg Kroah-HartmanFrom: Callum Osmotherly <[email protected]>
commit bdc9b7396f7d4d6533e70fd8d5472f505b5ef58f upstream.
The Dell Precision 5570 uses the same 4-speakers-on-ALC289 just like the previous Precision 5560. I replicated that patch onto this one, and can confirm that the audio is much better (the woofers are now working); I've tested it on my Dell Precision 5570.
--- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +1 -0
@@ -8769,6 +8769,7 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1028 ,0x0a9d ,"Dell Latitude 5430" ,ALC269_FIXUP_DELL4_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1028 ,0x0a9e ,"Dell Latitude 5430" ,ALC269_FIXUP_DELL4_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1028 ,0x0b19 ,"Dell XPS 15 9520" ,ALC289_FIXUP_DUAL_SPK ), +SND_PCI_QUIRK (0x1028 ,0x0b1a ,"Dell Precision 5570" ,ALC289_FIXUP_DUAL_SPK ),SND_PCI_QUIRK (0x1028 ,0x164a ,"Dell" ,ALC293_FIXUP_DELL1_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1028 ,0x164b ,"Dell" ,ALC293_FIXUP_DELL1_MIC_NO_PRESENCE ), SND_PCI_QUIRK(0x103c, 0x1586, "HP", ALC269_FIXUP_HP_MUTE_LED_MIC2),
Greg Kroah-Hartman
maintainerPATCH 43/141 ALSA: hda/realtek: Re-arrange quirk table entries
In reply to Greg Kroah-HartmanFrom: Takashi Iwai <[email protected]>
commit b16c8f229a58eaddfc58aab447253464abd3c85e upstream.
A few entries have been mistakenly inserted in wrong positions without considering the SSID ordering. Place them at right positions.
--- sound/pci/hda/patch_realtek.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/pci/hda/patch_realtek.c +3 -3
@@ -8913,10 +8913,11 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1043 ,0x13b0 ,"ASUS Z550SA" ,ALC256_FIXUP_ASUS_MIC ),SND_PCI_QUIRK (0x1043 ,0x1427 ,"Asus Zenbook UX31E" ,ALC269VB_FIXUP_ASUS_ZENBOOK ),SND_PCI_QUIRK (0x1043 ,0x1517 ,"Asus Zenbook UX31A" ,ALC269VB_FIXUP_ASUS_ZENBOOK_UX31A ), +SND_PCI_QUIRK (0x1043 ,0x1662 ,"ASUS GV301QH" ,ALC294_FIXUP_ASUS_DUAL_SPK ), +SND_PCI_QUIRK (0x1043 ,0x16b2 ,"ASUS GU603" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x16e3 ,"ASUS UX50" ,ALC269_FIXUP_STEREO_DMIC ),SND_PCI_QUIRK (0x1043 ,0x1740 ,"ASUS UX430UA" ,ALC295_FIXUP_ASUS_DACS ),SND_PCI_QUIRK (0x1043 ,0x17d1 ,"ASUS UX431FL" ,ALC294_FIXUP_ASUS_DUAL_SPK ), -SND_PCI_QUIRK (0x1043 ,0x1662 ,"ASUS GV301QH" ,ALC294_FIXUP_ASUS_DUAL_SPK ),SND_PCI_QUIRK (0x1043 ,0x1881 ,"ASUS Zephyrus S/M" ,ALC294_FIXUP_ASUS_GX502_PINS ),SND_PCI_QUIRK (0x1043 ,0x18b1 ,"Asus MJ401TA" ,ALC256_FIXUP_ASUS_HEADSET_MIC ), SND_PCI_QUIRK(0x1043, 0x18f1, "Asus FX505DT", ALC256_FIXUP_ASUS_HEADSET_MIC),
@@ -8932,13 +8933,12 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1043 ,0x1bbd ,"ASUS Z550MA" ,ALC255_FIXUP_ASUS_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1043 ,0x1c23 ,"Asus X55U" ,ALC269_FIXUP_LIMIT_INT_MIC_BOOST ),SND_PCI_QUIRK (0x1043 ,0x1ccd ,"ASUS X555UB" ,ALC256_FIXUP_ASUS_MIC ), +SND_PCI_QUIRK (0x1043 ,0x1d42 ,"ASUS Zephyrus G14 2022" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x1d4e ,"ASUS TM420" ,ALC256_FIXUP_ASUS_HPE ),SND_PCI_QUIRK (0x1043 ,0x1e11 ,"ASUS Zephyrus G15" ,ALC289_FIXUP_ASUS_GA502 ),SND_PCI_QUIRK (0x1043 ,0x1e51 ,"ASUS Zephyrus M15" ,ALC294_FIXUP_ASUS_GU502_PINS ),SND_PCI_QUIRK (0x1043 ,0x1e8e ,"ASUS Zephyrus G15" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x1f11 ,"ASUS Zephyrus G14" ,ALC289_FIXUP_ASUS_GA401 ), -SND_PCI_QUIRK (0x1043 ,0x1d42 ,"ASUS Zephyrus G14 2022" ,ALC289_FIXUP_ASUS_GA401 ), -SND_PCI_QUIRK (0x1043 ,0x16b2 ,"ASUS GU603" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x3030 ,"ASUS ZN270IE" ,ALC256_FIXUP_ASUS_AIO_GPIO2 ),SND_PCI_QUIRK (0x1043 ,0x831a ,"ASUS P901" ,ALC269_FIXUP_STEREO_DMIC ), SND_PCI_QUIRK(0x1043, 0x834a, "ASUS S101", ALC269_FIXUP_STEREO_DMIC),
Greg Kroah-Hartman
maintainerPATCH 44/141 ALSA: hda/realtek: Add pincfg for ASUS G513 HP jack
In reply to Greg Kroah-HartmanFrom: Luke D. Jones <[email protected]>
commit c611e659044168e7abcbae8ba1ea833521498fbb upstream.
Fixes up the pincfg for ASUS ROG Strix G513 headphone and mic combo jack
[ Fixed the position in the quirk table by tiwai ]
--- sound/pci/hda/patch_realtek.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
sound/pci/hda/patch_realtek.c +11 -0
@@ -6824,6 +6824,7 @@ enum {ALC294_FIXUP_ASUS_GU502_HP ,ALC294_FIXUP_ASUS_GU502_PINS ,ALC294_FIXUP_ASUS_GU502_VERBS , +ALC294_FIXUP_ASUS_G513_PINS ,ALC285_FIXUP_HP_GPIO_LED ,ALC285_FIXUP_HP_MUTE_LED , ALC236_FIXUP_HP_GPIO_LED,
@@ -8150,6 +8151,15 @@ static const struct hda_fixup alc269_fix .type = HDA_FIXUP_FUNC, .v.func = alc294_fixup_gu502_hp, }, + [ALC294_FIXUP_ASUS_G513_PINS] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x19 ,0x03a11050 },/* front HP mic */ + {0x1a ,0x03a11c30 },/* rear external mic */ + {0x21 ,0x03211420 },/* front HP out */ + { } + }, + }, [ALC294_FIXUP_ASUS_COEF_1B] = { .type = HDA_FIXUP_VERBS, .v.verbs = (const struct hda_verb []) {
@@ -8937,6 +8947,7 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1043 ,0x1d4e ,"ASUS TM420" ,ALC256_FIXUP_ASUS_HPE ),SND_PCI_QUIRK (0x1043 ,0x1e11 ,"ASUS Zephyrus G15" ,ALC289_FIXUP_ASUS_GA502 ),SND_PCI_QUIRK (0x1043 ,0x1e51 ,"ASUS Zephyrus M15" ,ALC294_FIXUP_ASUS_GU502_PINS ), +SND_PCI_QUIRK (0x1043 ,0x1e5e ,"ASUS ROG Strix G513" ,ALC294_FIXUP_ASUS_G513_PINS ),SND_PCI_QUIRK (0x1043 ,0x1e8e ,"ASUS Zephyrus G15" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x1f11 ,"ASUS Zephyrus G14" ,ALC289_FIXUP_ASUS_GA401 ), SND_PCI_QUIRK(0x1043, 0x3030, "ASUS ZN270IE", ALC256_FIXUP_ASUS_AIO_GPIO2),
Greg Kroah-Hartman
maintainerPATCH 45/141 ALSA: hda/realtek: Add pincfg for ASUS G533Z HP jack
In reply to Greg Kroah-HartmanFrom: Luke D. Jones <[email protected]>
commit bc2c23549ccd7105eb6ff0d4f0ac519285628673 upstream.
Fixes up the pincfg for ASUS ROG Strix G15 (G533Z) headphone combo jack
[ Fixed the position in the quirk table by tiwai ]
--- sound/pci/hda/patch_realtek.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
sound/pci/hda/patch_realtek.c +11 -0
@@ -6825,6 +6825,7 @@ enum {ALC294_FIXUP_ASUS_GU502_PINS ,ALC294_FIXUP_ASUS_GU502_VERBS ,ALC294_FIXUP_ASUS_G513_PINS , +ALC285_FIXUP_ASUS_G533Z_PINS ,ALC285_FIXUP_HP_GPIO_LED ,ALC285_FIXUP_HP_MUTE_LED , ALC236_FIXUP_HP_GPIO_LED,
@@ -8160,6 +8161,15 @@ static const struct hda_fixup alc269_fix { } }, }, + [ALC285_FIXUP_ASUS_G533Z_PINS] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl[]) { + { 0x14, 0x90170120 }, + { } + }, + .chained = true, + .chain_id = ALC294_FIXUP_ASUS_G513_PINS, + }, [ALC294_FIXUP_ASUS_COEF_1B] = { .type = HDA_FIXUP_VERBS, .v.verbs = (const struct hda_verb[]) {
@@ -8942,6 +8952,7 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1043 ,0x1b13 ,"Asus U41SV" ,ALC269_FIXUP_INV_DMIC ),SND_PCI_QUIRK (0x1043 ,0x1bbd ,"ASUS Z550MA" ,ALC255_FIXUP_ASUS_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1043 ,0x1c23 ,"Asus X55U" ,ALC269_FIXUP_LIMIT_INT_MIC_BOOST ), +SND_PCI_QUIRK (0x1043 ,0x1c92 ,"ASUS ROG Strix G15" ,ALC285_FIXUP_ASUS_G533Z_PINS ),SND_PCI_QUIRK (0x1043 ,0x1ccd ,"ASUS X555UB" ,ALC256_FIXUP_ASUS_MIC ),SND_PCI_QUIRK (0x1043 ,0x1d42 ,"ASUS Zephyrus G14 2022" ,ALC289_FIXUP_ASUS_GA401 ), SND_PCI_QUIRK(0x1043, 0x1d4e, "ASUS TM420", ALC256_FIXUP_ASUS_HPE),
Greg Kroah-Hartman
maintainerPATCH 46/141 ALSA: hda/realtek: Add quirk for ASUS GA503R laptop
In reply to Greg Kroah-HartmanFrom: Luke D. Jones <[email protected]>
commit ba1f818053b0668a1ce2fe86b840e81b592cc560 upstream.
The ASUS G15 2022 (GA503R) series laptop has the same node-to-DAC pairs as early models and the G14, this includes bass speakers which are by default mapped incorrectly to the 0x06 node.
Add a quirk to use the same DAC pairs as the G14.
--- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +1 -0
@@ -8960,6 +8960,7 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1043 ,0x1e51 ,"ASUS Zephyrus M15" ,ALC294_FIXUP_ASUS_GU502_PINS ),SND_PCI_QUIRK (0x1043 ,0x1e5e ,"ASUS ROG Strix G513" ,ALC294_FIXUP_ASUS_G513_PINS ),SND_PCI_QUIRK (0x1043 ,0x1e8e ,"ASUS Zephyrus G15" ,ALC289_FIXUP_ASUS_GA401 ), +SND_PCI_QUIRK (0x1043 ,0x1c52 ,"ASUS Zephyrus G15 2022" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x1f11 ,"ASUS Zephyrus G14" ,ALC289_FIXUP_ASUS_GA401 ),SND_PCI_QUIRK (0x1043 ,0x3030 ,"ASUS ZN270IE" ,ALC256_FIXUP_ASUS_AIO_GPIO2 ), SND_PCI_QUIRK(0x1043, 0x831a, "ASUS P901", ALC269_FIXUP_STEREO_DMIC),
Greg Kroah-Hartman
maintainerPATCH 47/141 ALSA: hda/realtek: Enable 4-speaker output Dell Precision 5530 laptop
In reply to Greg Kroah-HartmanFrom: Callum Osmotherly <[email protected]>
commit 1885ff13d4c42910b37a0e3f7c2f182520f4eed1 upstream.
Just as with the 5570 (and the other Dell laptops), this enables the two subwoofer speakers on the Dell Precision 5530 together with the main ones, significantly increasing the audio quality. I've tested this myself on a 5530 and can confirm it's working as expected.
--- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +1 -0
@@ -8774,6 +8774,7 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x1028 ,0x0871 ,"Dell Precision 3630" ,ALC255_FIXUP_DELL_HEADSET_MIC ),SND_PCI_QUIRK (0x1028 ,0x0872 ,"Dell Precision 3630" ,ALC255_FIXUP_DELL_HEADSET_MIC ),SND_PCI_QUIRK (0x1028 ,0x0873 ,"Dell Precision 3930" ,ALC255_FIXUP_DUMMY_LINEOUT_VERB ), +SND_PCI_QUIRK (0x1028 ,0x087d ,"Dell Precision 5530" ,ALC289_FIXUP_DUAL_SPK ),SND_PCI_QUIRK (0x1028 ,0x08ad ,"Dell WYSE AIO" ,ALC225_FIXUP_DELL_WYSE_AIO_MIC_NO_PRESENCE ),SND_PCI_QUIRK (0x1028 ,0x08ae ,"Dell WYSE NB" ,ALC225_FIXUP_DELL1_MIC_NO_PRESENCE ), SND_PCI_QUIRK(0x1028, 0x0935, "Dell", ALC274_FIXUP_DELL_AIO_LINEOUT_VERB),
Greg Kroah-Hartman
maintainerPATCH 48/141 iommu/vt-d: Check correct capability for sagaw determination
In reply to Greg Kroah-HartmanFrom: Yi Liu <[email protected]>
commit 154897807050c1161cb2660e502fc0470d46b986 upstream.
Check 5-level paging capability for 57 bits address width instead of checking 1GB large page capability.
--- drivers/iommu/intel/iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/intel/iommu.c +1 -1
@@ -569,7 +569,7 @@ static unsigned long __iommu_calculate_s {unsigned long fl_sagaw, sl_sagaw; - fl_sagaw =BIT (2 ) | (cap_fl1gp_support (iommu->cap) ?BIT (3 ) :0 ); + fl_sagaw =BIT (2 ) | (cap_5lp_support (iommu->cap) ?BIT (3 ) :0 ); sl_sagaw =cap_sagaw (iommu->cap);/* Second level only. */
Greg Kroah-Hartman
maintainerPATCH 49/141 media: flexcop-usb: fix endpoint type check
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 763679f0eeff0185fc431498849bbc1c24460875 upstream.
Commit d725d20e81c2 ("media: flexcop-usb: sanity checking of endpoint type") tried to add an endpoint type sanity check for the single isochronous endpoint but instead broke the driver by checking the wrong descriptor or random data beyond the last endpoint descriptor.
Make sure to check the right endpoint descriptor.
--- drivers/media/usb/b2c2/flexcop-usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/usb/b2c2/flexcop-usb.c +1 -1
@@ -512,7 +512,7 @@ static int flexcop_usb_init(struct flexcif (fc_usb->uintf->cur_altsetting->desc.bNumEndpoints <1 )return -ENODEV ; -if (!usb_endpoint_is_isoc_in (&fc_usb->uintf->cur_altsetting->endpoint[1 ].desc)) +if (!usb_endpoint_is_isoc_in (&fc_usb->uintf->cur_altsetting->endpoint[0 ].desc))return -ENODEV ;switch (fc_usb->udev->speed) {
Greg Kroah-Hartman
maintainerPATCH 50/141 efi: x86: Wipe setup_data on pure EFI boot
In reply to Greg Kroah-HartmanFrom: Ard Biesheuvel <[email protected]>
commit 63bf28ceb3ebbe76048c3fb2987996ca1ae64f83 upstream.
When booting the x86 kernel via EFI using the LoadImage/StartImage boot services [as opposed to the deprecated EFI handover protocol], the setup header is taken from the image directly, and given that EFI's LoadImage has no Linux/x86 specific knowledge regarding struct bootparams or struct setup_header, any absolute addresses in the setup header must originate from the file and not from a prior loading stage.
Since we cannot generally predict where LoadImage() decides to load an image (*), such absolute addresses must be treated as suspect: even if a prior boot stage intended to make them point somewhere inside the [signed] image, there is no way to validate that, and if they point at an arbitrary location in memory, the setup_data nodes will not be covered by any signatures or TPM measurements either, and could be made to contain an arbitrary sequence of SETUP_xxx nodes, which could interfere quite badly with the early x86 boot sequence.
(*) Note that, while LoadImage() does take a buffer/size tuple in addition to a device path, which can be used to provide the image contents directly, it will re-allocate such images, as the memory footprint of an image is generally larger than the PE/COFF file representation.
--- drivers/firmware/efi/libstub/x86-stub.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/firmware/efi/libstub/x86-stub.c +7 -0
@@ -414,6 +414,13 @@ efi_status_t __efiapi efi_pe_entry(efi_h hdr->ramdisk_image =0 ; hdr->ramdisk_size =0 ; +/* +* Disregard any setup data that was provided by the bootloader: +* setup_data could be pointing anywhere, and we have no way of +* authenticating or validating the payload. +*/ + hdr->setup_data =0 ; +efi_stub_entry (handle, sys_table_arg, boot_params);/* not reached */
Greg Kroah-Hartman
maintainerPATCH 51/141 efi: libstub: check Shim mode using MokSBStateRT
In reply to Greg Kroah-HartmanFrom: Ard Biesheuvel <[email protected]>
commit 5f56a74cc0a6d9b9f8ba89cea29cd7c4774cb2b1 upstream.
We currently check the MokSBState variable to decide whether we should treat UEFI secure boot as being disabled, even if the firmware thinks otherwise. This is used by shim to indicate that it is not checking signatures on boot images. In the kernel, we use this to relax lockdown policies.
However, in cases where shim is not even being used, we don't want this variable to interfere with lockdown, given that the variable may be non-volatile and therefore persist across a reboot. This means setting it once will persistently disable lockdown checks on a given system.
So switch to the mirrored version of this variable, called MokSBStateRT, which is supposed to be volatile, and this is something we can check.
--- drivers/firmware/efi/libstub/secureboot.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/firmware/efi/libstub/secureboot.c +4 -4
@@ -19,7 +19,7 @@ static const efi_char16_t efi_SetupMode_/* SHIM variables */ static const efi_guid_t shim_guid =EFI_SHIM_LOCK_GUID ; -static const efi_char16_t shim_MokSBState_name[] =L"MokSBState" ; +static const efi_char16_t shim_MokSBState_name[] =L"MokSBStateRT" ;/* * Determine whether we're in secure boot mode.
@@ -53,8 +53,8 @@ enum efi_secureboot_mode efi_get_secureb/* * See if a user has put the shim into insecure mode. If so, and if the -* variable doesn't have the runtime attribute set, we might as well -* honor that. +* variable doesn't have the non-volatile attribute set, we might as +* well honor that. */ size =sizeof (moksbstate); status = get_efi_var(shim_MokSBState_name, &shim_guid,
@@ -63,7 +63,7 @@ enum efi_secureboot_mode efi_get_secureb/* If it fails, we don't care why. Default to secure */ if (status !=EFI_SUCCESS ) goto secure_boot_enabled; -if (!(attr &EFI_VARIABLE_RUNTIME_ACCESS ) && moksbstate ==1 ) +if (!(attr &EFI_VARIABLE_NON_VOLATILE ) && moksbstate ==1 )return efi_secureboot_mode_disabled; secure_boot_enabled:
Greg Kroah-Hartman
maintainerPATCH 52/141 wifi: mt76: fix reading current per-tid starting sequence number for aggregation
In reply to Greg Kroah-HartmanFrom: Felix Fietkau <[email protected]>
commit c3a510e2b53785df31d882a773c4c0780b4c825f upstream.
The code was accidentally shifting register values down by tid % 32 instead of (tid * field_size) % 32.
--- drivers/net/wireless/mediatek/mt76/mt7615/mac.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/wireless/mediatek/mt76/mt7615/mac.c +1 -1
@@ -950,7 +950,7 @@ u32 mt7615_mac_get_sta_tid_sn(struct mt7 offset %=32 ; val =mt76_rr (dev, addr); - val >>= (tid %32 ); + val >>= offset;if (offset >20 ) { addr +=4 ;
Greg Kroah-Hartman
maintainerPATCH 53/141 gpio: mockup: fix NULL pointer dereference when removing debugfs
In reply to Greg Kroah-HartmanFrom: Bartosz Golaszewski <[email protected]>
commit b7df41a6f79dfb18ba2203f8c5f0e9c0b9b57f68 upstream.
We now remove the device's debugfs entries when unbinding the driver. This now causes a NULL-pointer dereference on module exit because the platform devices are unregistered *after* the global debugfs directory has been recursively removed. Fix it by unregistering the devices first.
--- drivers/gpio/gpio-mockup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpio/gpio-mockup.c +1 -1
@@ -604,9 +604,9 @@ static int __init gpio_mockup_init(void) static void __exit gpio_mockup_exit(void) { +gpio_mockup_unregister_pdevs ();debugfs_remove_recursive (gpio_mockup_dbg_dir);platform_driver_unregister (&gpio_mockup_driver); -gpio_mockup_unregister_pdevs (); }module_init (gpio_mockup_init);
Greg Kroah-Hartman
maintainerPATCH 54/141 gpiolib: cdev: Set lineevent_state::irq after IRQ register successfully
In reply to Greg Kroah-HartmanFrom: Meng Li <[email protected]>
commit 69bef19d6b9700e96285f4b4e28691cda3dcd0d1 upstream.
When running gpio test on nxp-ls1028 platform with below command gpiomon --num-events=3 --rising-edge gpiochip1 25 There will be a warning trace as below:
Call trace: free_irq+0x204/0x360 lineevent_free+0x64/0x70 gpio_ioctl+0x598/0x6a0 __arm64_sys_ioctl+0xb4/0x100 invoke_syscall+0x5c/0x130
......el0t_64_sync+0x1a0/0x1a4
The reason of this issue is that calling request_threaded_irq() function failed, and then lineevent_free() is invoked to release the resource. Since the lineevent_state::irq was already set, so the subsequent invocation of free_irq() would trigger the above warning call trace. To fix this issue, set the lineevent_state::irq after the IRQ register successfully.
--- drivers/gpio/gpiolib-cdev.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpio/gpiolib-cdev.c +3 -2
@@ -1769,7 +1769,6 @@ static int lineevent_create(struct gpio_ ret = -ENODEV ; goto out_free_le; } - le->irq = irq;if (eflags &GPIOEVENT_REQUEST_RISING_EDGE ) irqflags |= test_bit(FLAG_ACTIVE_LOW, &desc->flags) ?
@@ -1783,7 +1782,7 @@ static int lineevent_create(struct gpio_init_waitqueue_head (&le->wait);/* Request a thread to read the events */ - ret = request_threaded_irq(le->irq, + ret = request_threaded_irq(irq, lineevent_irq_handler, lineevent_irq_thread, irqflags,
@@ -1792,6 +1791,8 @@ static int lineevent_create(struct gpio_if (ret) goto out_free_le; + le->irq = irq; + fd =get_unused_fd_flags (O_RDONLY |O_CLOEXEC );if (fd <0 ) { ret = fd;
Greg Kroah-Hartman
maintainerPATCH 55/141 riscv: fix a nasty sigreturn bug...
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
commit 762df359aa5849e010ef04c3ed79d57588ce17d9 upstream.
riscv has an equivalent of arm bug fixed by 653d48b22166 ("arm: fix really nasty sigreturn bug"); if signal gets caught by an interrupt that hits when we have the right value in a0 (-513), *and* another signal gets delivered upon sigreturn() (e.g. included into the blocked mask for the first signal and posted while the handler had been running), the syscall restart logics will see regs->cause equal to EXC_SYSCALL (we are in a syscall, after all) and a0 already restored to its original value (-513, which happens to be -ERESTARTNOINTR) and assume that we need to apply the usual syscall restart logics.
--- arch/riscv/kernel/signal.c | 2 ++ 1 file changed, 2 insertions(+)
arch/riscv/kernel/signal.c +2 -0
@@ -121,6 +121,8 @@ SYSCALL_DEFINE0(rt_sigreturn)if (restore_altstack (&frame->uc.uc_stack)) goto badframe; + regs->cause =-1UL ; +return regs->a0; badframe:
Greg Kroah-Hartman
maintainerPATCH 56/141 can: flexcan: flexcan_mailbox_read() fix return value for drop = true
In reply to Greg Kroah-HartmanFrom: Marc Kleine-Budde <[email protected]>
commit a09721dd47c8468b3f2fdd73f40422699ffe26dd upstream.
The following happened on an i.MX25 using flexcan with many packets on the bus:
The rx-offload queue reached a length more than skb_queue_len_max. In can_rx_offload_offload_one() the drop variable was set to true which made the call to .mailbox_read() (here: flexcan_mailbox_read()) to _always_ return ERR_PTR(-ENOBUFS) and drop the rx'ed CAN frame. So can_rx_offload_offload_one() returned ERR_PTR(-ENOBUFS), too.
can_rx_offload_irq_offload_fifo() looks as follows:
| while (1) {
| skb = can_rx_offload_offload_one(offload, 0);
| if (IS_ERR(skb))
| continue;
| if (!skb)
| break;
| ...
| }The flexcan driver wrongly always returns ERR_PTR(-ENOBUFS) if drop is requested, even if there is no CAN frame pending. As the i.MX25 is a single core CPU, while the rx-offload processing is active, there is no thread to process packets from the offload queue. So the queue doesn't get any shorter and this results is a tight loop.
Instead of always returning ERR_PTR(-ENOBUFS) if drop is requested, return NULL if no CAN frame is pending.
Changes since v1: https://lore.kernel.org/all/[email protected]
- don't break in can_rx_offload_irq_offload_fifo() in case of an error,
return NULL in flexcan_mailbox_read() in case of no pending CAN frame
instead
--- drivers/net/can/flexcan.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/net/can/flexcan.c +5 -5
@@ -954,11 +954,6 @@ static struct sk_buff *flexcan_mailbox_ru32 reg_ctrl, reg_id, reg_iflag1;int i; -if (unlikely (drop)) { - skb =ERR_PTR (-ENOBUFS ); - goto mark_as_read; - } - mb =flexcan_get_mb (priv, n);if (priv->devtype_data->quirks &FLEXCAN_QUIRK_USE_OFF_TIMESTAMP ) {
@@ -987,6 +982,11 @@ static struct sk_buff *flexcan_mailbox_r reg_ctrl = priv->read (&mb->can_ctrl); } +if (unlikely (drop)) { + skb =ERR_PTR (-ENOBUFS ); + goto mark_as_read; + } +if (reg_ctrl &FLEXCAN_MB_CNT_EDL ) skb =alloc_canfd_skb (offload->dev, &cfd);else
Greg Kroah-Hartman
maintainerPATCH 57/141 mm/slub: fix to return errno if kmalloc() fails
In reply to Greg Kroah-HartmanFrom: Chao Yu <[email protected]>
commit 7e9c323c52b379d261a72dc7bd38120a761a93cd upstream.
In create_unique_id(), kmalloc(, GFP_KERNEL) can fail due to out-of-memory, if it fails, return errno correctly rather than triggering panic via BUG_ON();
kernel BUG at mm/slub.c:5893!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Call trace: sysfs_slab_add+0x258/0x260 mm/slub.c:5973 __kmem_cache_create+0x60/0x118 mm/slub.c:4899 create_cache mm/slab_common.c:229 [inline] kmem_cache_create_usercopy+0x19c/0x31c mm/slab_common.c:335 kmem_cache_create+0x1c/0x28 mm/slab_common.c:390 f2fs_kmem_cache_create fs/f2fs/f2fs.h:2766 [inline] f2fs_init_xattr_caches+0x78/0xb4 fs/f2fs/xattr.c:808 f2fs_fill_super+0x1050/0x1e0c fs/f2fs/super.c:4149 mount_bdev+0x1b8/0x210 fs/super.c:1400 f2fs_mount+0x44/0x58 fs/f2fs/super.c:4512 legacy_get_tree+0x30/0x74 fs/fs_context.c:610 vfs_get_tree+0x40/0x140 fs/super.c:1530 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040 path_mount+0x358/0x914 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __arm64_sys_mount+0x2f8/0x408 fs/namespace.c:3568
--- mm/slub.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
mm/slub.c +4 -1
@@ -5559,7 +5559,8 @@ static char *create_unique_id(struct kmechar *name =kmalloc (ID_STR_LENGTH ,GFP_KERNEL );char *p = name; -BUG_ON (!name); +if (!name) +return ERR_PTR (-ENOMEM ); *p++ =':' ;/*
@@ -5617,6 +5618,8 @@ static int sysfs_slab_add(struct kmem_ca* for the symlinks. */ name =create_unique_id (s); +if (IS_ERR (name)) +return PTR_ERR (name); } s->kobj.kset = kset;
Greg Kroah-Hartman
maintainerPATCH 58/141 KVM: SEV: add cache flush to solve SEV cache incoherency issues
In reply to Greg Kroah-HartmanFrom: Mingwei Zhang <[email protected]>
commit 683412ccf61294d727ead4a73d97397396e69a6b upstream.
Flush the CPU caches when memory is reclaimed from an SEV guest (where reclaim also includes it being unmapped from KVM's memslots). Due to lack of coherency for SEV encrypted memory, failure to flush results in silent data corruption if userspace is malicious/broken and doesn't ensure SEV guest memory is properly pinned and unpinned.
Cache coherency is not enforced across the VM boundary in SEV (AMD APM vol.2 Section 15.34.7). Confidential cachelines, generated by confidential VM guests have to be explicitly flushed on the host side. If a memory page containing dirty confidential cachelines was released by VM and reallocated to another user, the cachelines may corrupt the new user at a later time.
KVM takes a shortcut by assuming all confidential memory remain pinned until the end of VM lifetime. Therefore, KVM does not flush cache at mmu_notifier invalidation events. Because of this incorrect assumption and the lack of cache flushing, malicous userspace can crash the host kernel:
creating a malicious VM and continuously allocates/releases unpinned confidential memory pages when the VM is running.
Add cache flush operations to mmu_notifier operations to ensure that any physical memory leaving the guest VM get flushed. In particular, hook mmu_notifier_invalidate_range_start and mmu_notifier_release events and flush cache accordingly. The hook after releasing the mmu lock to avoid contention with other vCPUs.
Message-Id: <[email protected]>
[OP: applied kvm_arch_guest_memory_reclaimed() calls in kvm_set_memslot() and kvm_mmu_notifier_invalidate_range_start();
OP: adjusted kvm_arch_guest_memory_reclaimed() to not use static_call_cond()]
--- arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/svm/sev.c | 8 ++++++++ arch/x86/kvm/svm/svm.c | 1 + arch/x86/kvm/svm/svm.h | 2 ++ arch/x86/kvm/x86.c | 6 ++++++ include/linux/kvm_host.h | 2 ++ virt/kvm/kvm_main.c | 16 ++++++++++++++-- 7 files changed, 34 insertions(+), 2 deletions(-)
arch/x86/include/asm/kvm_host.h +1 -0
@@ -1275,6 +1275,7 @@ struct kvm_x86_ops {int (*mem_enc_op)(struct kvm *kvm,void __user *argp);int (*mem_enc_reg_region)(struct kvm *kvm,struct kvm_enc_region *argp);int (*mem_enc_unreg_region)(struct kvm *kvm,struct kvm_enc_region *argp); +void (*guest_memory_reclaimed)(struct kvm *kvm);int (*get_msr_feature)(struct kvm_msr_entry *entry);
arch/x86/kvm/svm/sev.c +8 -0
@@ -1177,6 +1177,14 @@ void sev_hardware_teardown(void)sev_flush_asids (); } +void sev_guest_memory_reclaimed (struct kvm *kvm) +{ +if (!sev_guest (kvm)) +return ; + +wbinvd_on_all_cpus (); +} +void pre_sev_run (struct vcpu_svm *svm,int cpu) {struct svm_cpu_data *sd =per_cpu (svm_data, cpu);
arch/x86/kvm/svm/svm.c +1 -0
@@ -4325,6 +4325,7 @@ static struct kvm_x86_ops svm_x86_ops __ .mem_enc_op = svm_mem_enc_op, .mem_enc_reg_region = svm_register_enc_region, .mem_enc_unreg_region = svm_unregister_enc_region, + .guest_memory_reclaimed = sev_guest_memory_reclaimed, .can_emulate_instruction = svm_can_emulate_instruction,
arch/x86/kvm/svm/svm.h +2 -0
@@ -491,6 +491,8 @@ int svm_register_enc_region(struct kvm * struct kvm_enc_region *range);int svm_unregister_enc_region (struct kvm *kvm,struct kvm_enc_region *range); +void sev_guest_memory_reclaimed (struct kvm *kvm); +void pre_sev_run (struct vcpu_svm *svm,int cpu);int __init sev_hardware_setup (void );void sev_hardware_teardown (void );
arch/x86/kvm/x86.c +6 -0
@@ -8875,6 +8875,12 @@ void kvm_arch_mmu_notifier_invalidate_rakvm_make_all_cpus_request (kvm,KVM_REQ_APIC_PAGE_RELOAD ); } +void kvm_arch_guest_memory_reclaimed (struct kvm *kvm) +{ +if (kvm_x86_ops.guest_memory_reclaimed) + kvm_x86_ops.guest_memory_reclaimed (kvm); +} +void kvm_vcpu_reload_apic_access_page (struct kvm_vcpu *vcpu) {if (!lapic_in_kernel (vcpu))
include/linux/kvm_host.h +2 -0
@@ -1489,6 +1489,8 @@ static inline long kvm_arch_vcpu_async_ivoid kvm_arch_mmu_notifier_invalidate_range (struct kvm *kvm,unsigned long start,unsigned long end); +void kvm_arch_guest_memory_reclaimed (struct kvm *kvm); +#ifdef CONFIG_HAVE_KVM_VCPU_RUN_PID_CHANGE int kvm_arch_vcpu_run_pid_change (struct kvm_vcpu *vcpu);#else
virt/kvm/kvm_main.c +14 -2
@@ -159,6 +159,10 @@ __weak void kvm_arch_mmu_notifier_invali { } +__weak void kvm_arch_guest_memory_reclaimed (struct kvm *kvm) +{ +} +bool kvm_is_zone_device_pfn (kvm_pfn_t pfn) {/*
@@ -340,6 +344,12 @@ void kvm_reload_remote_mmus(struct kvm *kvm_make_all_cpus_request (kvm,KVM_REQ_MMU_RELOAD ); } +static void kvm_flush_shadow_all (struct kvm *kvm) +{ +kvm_arch_flush_shadow_all (kvm); +kvm_arch_guest_memory_reclaimed (kvm); +} +#ifdef KVM_ARCH_NR_OBJS_PER_MEMORY_CACHE static inline void *mmu_memory_cache_alloc_obj (struct kvm_mmu_memory_cache *mc,gfp_t gfp_flags)
@@ -489,6 +499,7 @@ static int kvm_mmu_notifier_invalidate_rkvm_flush_remote_tlbs (kvm);spin_unlock (&kvm->mmu_lock); +kvm_arch_guest_memory_reclaimed (kvm);srcu_read_unlock (&kvm->srcu, idx);return 0 ;
@@ -592,7 +603,7 @@ static void kvm_mmu_notifier_release(strint idx; idx =srcu_read_lock (&kvm->srcu); -kvm_arch_flush_shadow_all (kvm); +kvm_flush_shadow_all (kvm);srcu_read_unlock (&kvm->srcu, idx); }
@@ -896,7 +907,7 @@ static void kvm_destroy_vm(struct kvm *k#if defined(CONFIG_MMU_NOTIFIER ) && defined(KVM_ARCH_WANT_MMU_NOTIFIER )mmu_notifier_unregister (&kvm->mmu_notifier, kvm->mm);#else -kvm_arch_flush_shadow_all (kvm); +kvm_flush_shadow_all (kvm);#endif kvm_arch_destroy_vm (kvm);kvm_destroy_devices (kvm);
@@ -1238,6 +1249,7 @@ static int kvm_set_memslot(struct kvm *k* - kvm_is_visible_gfn (mmu_check_root) */ kvm_arch_flush_shadow_memslot (kvm, slot); +kvm_arch_guest_memory_reclaimed (kvm); } r =kvm_arch_prepare_memory_region (kvm, new, mem, change);
Greg Kroah-Hartman
maintainerPATCH 59/141 interconnect: qcom: icc-rpmh: Add BCMs to commit list in pre_aggregate
In reply to Greg Kroah-HartmanFrom: Mike Tipton <[email protected]>
commit b95b668eaaa2574e8ee72f143c52075e9955177e upstream.
We're only adding BCMs to the commit list in aggregate(), but there are cases where pre_aggregate() is called without subsequently calling aggregate(). In particular, in icc_sync_state() when a node with initial BW has zero requests. Since BCMs aren't added to the commit list in these cases, we don't actually send the zero BW request to HW. So the resources remain on unnecessarily.
Add BCMs to the commit list in pre_aggregate() instead, which is always called even when there are no requests.
--- drivers/interconnect/qcom/icc-rpmh.c | 10 +++++----- drivers/interconnect/qcom/sm8150.c | 1 - drivers/interconnect/qcom/sm8250.c | 1 - 3 files changed, 5 insertions(+), 7 deletions(-)
drivers/interconnect/qcom/icc-rpmh.c +5 -5
@@ -20,13 +20,18 @@ void qcom_icc_pre_aggregate(struct icc_n {size_t i;struct qcom_icc_node *qn; +struct qcom_icc_provider *qp; qn = node->data; + qp =to_qcom_provider (node->provider);for (i =0 ; i <QCOM_ICC_NUM_BUCKETS ; i++) { qn->sum_avg[i] =0 ; qn->max_peak[i] =0 ; } + +for (i =0 ; i < qn->num_bcms; i++) +qcom_icc_bcm_voter_add (qp->voter, qn->bcms[i]); }EXPORT_SYMBOL_GPL (qcom_icc_pre_aggregate);
@@ -44,10 +49,8 @@ int qcom_icc_aggregate(struct icc_node * {size_t i;struct qcom_icc_node *qn; -struct qcom_icc_provider *qp; qn = node->data; - qp =to_qcom_provider (node->provider);if (!tag) tag =QCOM_ICC_TAG_ALWAYS ;
@@ -67,9 +70,6 @@ int qcom_icc_aggregate(struct icc_node * *agg_avg += avg_bw; *agg_peak =max_t (u32, *agg_peak, peak_bw); -for (i =0 ; i < qn->num_bcms; i++) -qcom_icc_bcm_voter_add (qp->voter, qn->bcms[i]); -return 0 ; }EXPORT_SYMBOL_GPL (qcom_icc_aggregate);
drivers/interconnect/qcom/sm8150.c +0 -1
@@ -627,7 +627,6 @@ static struct platform_driver qnoc_drive .driver = { .name = "qnoc-sm8150", .of_match_table = qnoc_of_match, - .sync_state = icc_sync_state, }, };module_platform_driver (qnoc_driver);
drivers/interconnect/qcom/sm8250.c +0 -1
@@ -643,7 +643,6 @@ static struct platform_driver qnoc_drive .driver = { .name = "qnoc-sm8250", .of_match_table = qnoc_of_match, - .sync_state = icc_sync_state, }, };module_platform_driver (qnoc_driver);
Greg Kroah-Hartman
maintainerPATCH 60/141 xfs: fix up non-directory creation in SGID directories
In reply to Greg Kroah-HartmanFrom: Christoph Hellwig <[email protected]>
commit 01ea173e103edd5ec41acec65b9261b87e123fc2 upstream.
XFS always inherits the SGID bit if it is set on the parent inode, while the generic inode_init_owner does not do this in a few cases where it can create a possible security problem, see commit 0fa3ecd87848 ("Fix up non-directory creation in SGID directories") for details.
Switch XFS to use the generic helper for the normal path to fix this, just keeping the simple field inheritance open coded for the case of the non-sgid case with the bsdgrpid mount option.
--- fs/xfs/xfs_inode.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
fs/xfs/xfs_inode.c +7 -7
@@ -802,6 +802,7 @@ xfs_ialloc( xfs_buf_t **ialloc_context, xfs_inode_t **ipp) { +struct inode *dir = pip ?VFS_I (pip) :NULL ;struct xfs_mount *mp = tp->t_mountp;xfs_ino_t ino;xfs_inode_t *ip;
@@ -847,18 +848,17 @@ xfs_ialloc(return error;ASSERT (ip !=NULL ); inode =VFS_I (ip); - inode->i_mode = mode;set_nlink (inode, nlink); - inode->i_uid =current_fsuid (); inode->i_rdev = rdev; ip->i_d.di_projid = prid; -if (pip &&XFS_INHERIT_GID (pip)) { - inode->i_gid =VFS_I (pip)->i_gid; -if ((VFS_I (pip)->i_mode &S_ISGID ) &&S_ISDIR (mode)) - inode->i_mode |=S_ISGID ; +if (dir && !(dir->i_mode &S_ISGID ) && + (mp->m_flags &XFS_MOUNT_GRPID )) { + inode->i_uid =current_fsuid (); + inode->i_gid = dir->i_gid; + inode->i_mode = mode; }else { - inode->i_gid =current_fsgid (); +inode_init_owner (inode, dir, mode); }/*
Greg Kroah-Hartman
maintainerPATCH 61/141 xfs: reorder iunlink remove operation in xfs_ifree
In reply to Greg Kroah-HartmanFrom: Dave Chinner <[email protected]>
commit 9a5280b312e2e7898b6397b2ca3cfd03f67d7be1 upstream.
[backport for 5.10.y]
The O_TMPFILE creation implementation creates a specific order of operations for inode allocation/freeing and unlinked list modification. Currently both are serialised by the AGI, so the order doesn't strictly matter as long as the are both in the same transaction.
However, if we want to move the unlinked list insertions largely out from under the AGI lock, then we have to be concerned about the order in which we do unlinked list modification operations. O_TMPFILE creation tells us this order is inode allocation/free, then unlinked list modification.
Change xfs_ifree() to use this same ordering on unlinked list removal. This way we always guarantee that when we enter the iunlinked list removal code from this path, we already have the AGI locked and we don't have to worry about lock nesting AGI reads inside unlink list locks because it's already locked and attached to the transaction.
We can do this safely as the inode freeing and unlinked list removal are done in the same transaction and hence are atomic operations with respect to log recovery.
--- fs/xfs/xfs_inode.c | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-)
fs/xfs/xfs_inode.c +12 -10
@@ -2669,14 +2669,13 @@ xfs_ifree_cluster( }/* -* This is called to return an inode to the inode free list. -* The inode should already be truncated to 0 length and have -* no pages associated with it. This routine also assumes that -* the inode is already a part of the transaction. +* This is called to return an inode to the inode free list. The inode should +* already be truncated to 0 length and have no pages associated with it. This +* routine also assumes that the inode is already a part of the transaction. * -* The on-disk copy of the inode will have been added to the list -* of unlinked inodes in the AGI. We need to remove the inode from -* that list atomically with respect to freeing it here. +* The on-disk copy of the inode will have been added to the list of unlinked +* inodes in the AGI. We need to remove the inode from that list atomically with +* respect to freeing it here. */ int xfs_ifree(
@@ -2694,13 +2693,16 @@ xfs_ifree(ASSERT (ip->i_d.di_nblocks ==0 );/* -* Pull the on-disk inode from the AGI unlinked list. +* Free the inode first so that we guarantee that the AGI lock is going +* to be taken before we remove the inode from the unlinked list. This +* makes the AGI lock -> unlinked list modification order the same as +* used in O_TMPFILE creation. */ - error =xfs_iunlink_remove (tp, ip); + error =xfs_difree (tp, ip->i_ino, &xic);if (error)return error; - error =xfs_difree (tp, ip->i_ino, &xic); + error =xfs_iunlink_remove (tp, ip);if (error)return error;
Greg Kroah-Hartman
maintainerPATCH 62/141 xfs: validate inode fork size against fork format
In reply to Greg Kroah-HartmanFrom: Dave Chinner <[email protected]>
commit 1eb70f54c445fcbb25817841e774adb3d912f3e8 upstream.
[backport for 5.10.y]
xfs_repair catches fork size/format mismatches, but the in-kernel verifier doesn't, leading to null pointer failures when attempting to perform operations on the fork. This can occur in the xfs_dir_is_empty() where the in-memory fork format does not match the size and so the fork data pointer is accessed incorrectly.
Note: this causes new failures in xfs/348 which is testing mode vs ftype mismatches. We now detect a regular file that has been changed to a directory or symlink mode as being corrupt because the data fork is for a symlink or directory should be in local form when there are only 3 bytes of data in the data fork. Hence the inode verify for the regular file now fires w/ -EFSCORRUPTED because the inode fork format does not match the format the corrupted mode says it should be in.
--- fs/xfs/libxfs/xfs_inode_buf.c | 35 ++++++++++++++++++++++++++--------- 1 file changed, 26 insertions(+), 9 deletions(-)
fs/xfs/libxfs/xfs_inode_buf.c +26 -9
@@ -358,19 +358,36 @@ xfs_dinode_verify_fork( int whichfork) {uint32_t di_nextents =XFS_DFORK_NEXTENTS (dip, whichfork); +mode_t mode =be16_to_cpu (dip->di_mode); +uint32_t fork_size =XFS_DFORK_SIZE (dip, mp, whichfork); +uint32_t fork_format =XFS_DFORK_FORMAT (dip, whichfork); -switch (XFS_DFORK_FORMAT (dip, whichfork)) { +/* +* For fork types that can contain local data, check that the fork +* format matches the size of local data contained within the fork. +* +* For all types, check that when the size says the should be in extent +* or btree format, the inode isn't claiming it is in local format. +*/ +if (whichfork ==XFS_DATA_FORK ) { +if (S_ISDIR (mode) ||S_ISLNK (mode)) { +if (be64_to_cpu (dip->di_size) <= fork_size && + fork_format !=XFS_DINODE_FMT_LOCAL ) +return __this_address; + } + +if (be64_to_cpu (dip->di_size) > fork_size && + fork_format ==XFS_DINODE_FMT_LOCAL ) +return __this_address; + } + +switch (fork_format) {case XFS_DINODE_FMT_LOCAL :/* -* no local regular files yet +* No local regular files yet. */ -if (whichfork ==XFS_DATA_FORK ) { -if (S_ISREG (be16_to_cpu (dip->di_mode))) -return __this_address; -if (be64_to_cpu (dip->di_size) > -XFS_DFORK_SIZE (dip, mp, whichfork)) -return __this_address; - } +if (S_ISREG (mode) && whichfork ==XFS_DATA_FORK ) +return __this_address;if (di_nextents)return __this_address;break ;
Greg Kroah-Hartman
maintainerPATCH 63/141 arm64: dts: rockchip: Pull up wlan wake# on Gru-Bob
In reply to Greg Kroah-HartmanFrom: Brian Norris <[email protected]>
[ Upstream commit e5467359a725de90b6b8d0dd865500f6373828ca ]
The Gru-Bob board does not have a pull-up resistor on its WLAN_HOST_WAKE# pin, but Kevin does. The production/vendor kernel specified the pin configuration correctly as a pull-up, but this didn't get ported correctly to upstream.
This means Bob's WLAN_HOST_WAKE# pin is floating, causing inconsistent wakeup behavior.
Note that bt_host_wake_l has a similar dynamic, but apparently the upstream choice was to redundantly configure both internal and external pull-up on Kevin (see the "Kevin has an external pull up" comment in rk3399-gru.dtsi). This doesn't cause any functional problem, although it's perhaps wasteful.
--- arch/arm64/boot/dts/rockchip/rk3399-gru-bob.dts | 5 +++++ arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi | 1 + 2 files changed, 6 insertions(+)
arch/arm64/boot/dts/rockchip/rk3399-gru-bob.dts +5 -0
@@ -87,3 +87,8 @@ h1_int_od_l: h1-int-od-l { }; }; }; + +&wlan_host_wake_l { + /* Kevin has an external pull up, but Bob does not. */ + rockchip,pins = <0 RK_PB0 RK_FUNC_GPIO &pcfg_pull_up>; +};
arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi +1 -0
@@ -395,6 +395,7 @@ wifi_perst_l: wifi-perst-l { }; wlan_host_wake_l: wlan-host-wake-l { + /* Kevin has an external pull up, but Bob does not */ rockchip,pins = <0 RK_PB0 RK_FUNC_GPIO &pcfg_pull_none>; }; };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 64/141 drm/mediatek: dsi: Add atomic {destroy,duplicate}_state, reset callbacks
In reply to Greg Kroah-HartmanFrom: AngeloGioacchino Del Regno <[email protected]>
[ Upstream commit eeda05b5e92f51d9a09646ecb493f0a1e872a6ef ]
Add callbacks for atomic_destroy_state, atomic_duplicate_state and atomic_reset to restore functionality of the DSI driver: this solves vblank timeouts when another bridge is present in the chain.
Tested bridge chain: DSI <=> ANX7625 => aux-bus panel
--- drivers/gpu/drm/mediatek/mtk_dsi.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/mediatek/mtk_dsi.c +3 -0
@@ -791,10 +791,13 @@ static void mtk_dsi_bridge_atomic_post_disable(struct drm_bridge *bridge,static const struct drm_bridge_funcs mtk_dsi_bridge_funcs = { .attach = mtk_dsi_bridge_attach, + .atomic_destroy_state = drm_atomic_helper_bridge_destroy_state, .atomic_disable = mtk_dsi_bridge_atomic_disable, + .atomic_duplicate_state = drm_atomic_helper_bridge_duplicate_state, .atomic_enable = mtk_dsi_bridge_atomic_enable, .atomic_pre_enable = mtk_dsi_bridge_atomic_pre_enable, .atomic_post_disable = mtk_dsi_bridge_atomic_post_disable, + .atomic_reset = drm_atomic_helper_bridge_reset, .mode_set = mtk_dsi_bridge_mode_set, };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 65/141 arm64: dts: rockchip: Set RK3399-Gru PCLK_EDP to 24 MHz
In reply to Greg Kroah-HartmanFrom: zain wang <[email protected]>
[ Upstream commit 8123437cf46ea5a0f6ca5cb3c528d8b6db97b9c2 ]
We've found the AUX channel to be less reliable with PCLK_EDP at a higher rate (typically 25 MHz). This is especially important on systems with PSR-enabled panels (like Gru-Kevin), since we make heavy, constant use of AUX.
According to Rockchip, using any rate other than 24 MHz can cause "problems between syncing the PHY an PCLK", which leads to all sorts of unreliabilities around register operations.
--- arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi | 8 ++++++++ 1 file changed, 8 insertions(+)
arch/arm64/boot/dts/rockchip/rk3399-gru-chromebook.dtsi +8 -0
@@ -237,6 +237,14 @@ &cdn_dp { &edp { status = "okay"; + /* + * eDP PHY/clk don't sync reliably at anything other than 24 MHz. Only + * set this here, because rk3399-gru.dtsi ensures we can generate this + * off GPLL=600MHz, whereas some other RK3399 boards may not. + */ + assigned-clocks = <&cru PCLK_EDP>; + assigned-clock-rates = <24000000>; + ports { edp_out: port@1 { reg = <1>;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 66/141 dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
In reply to Greg Kroah-HartmanFrom: Liang He <[email protected]>
[ Upstream commit f9fdb0b86f087c2b7f6c6168dd0985a3c1eda87e ]
We should call of_node_put() for the reference returned by of_parse_phandle() in fail path or when it is not used anymore. Here we only need to move the of_node_put() before the check.
--- drivers/dma/ti/k3-udma-private.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/dma/ti/k3-udma-private.c +3 -3
@@ -31,14 +31,14 @@ struct udma_dev *of_xudma_dev_get(struct device_node *np, const char *property) } pdev =of_find_device_by_node (udma_node); +if (np != udma_node) +of_node_put (udma_node); +if (!pdev) {pr_debug ("UDMA device not found\n" );return ERR_PTR (-EPROBE_DEFER ); } -if (np != udma_node) -of_node_put (udma_node); - ud =platform_get_drvdata (pdev);if (!ud) {pr_debug ("UDMA has not been probed\n" );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 67/141 arm64: dts: rockchip: Remove enable-active-low from rk3399-puma
In reply to Greg Kroah-HartmanFrom: Fabio Estevam <[email protected]>
[ Upstream commit a994b34b9abb9c08ee09e835b4027ff2147f9d94 ]
The 'enable-active-low' property is not a valid one.
Only 'enable-active-high' is valid, and when this property is absent the gpio regulator will act as active low by default.
Remove the invalid 'enable-active-low' property.
--- arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi | 1 - 1 file changed, 1 deletion(-)
arch/arm64/boot/dts/rockchip/rk3399-puma.dtsi +0 -1
@@ -102,7 +102,6 @@ vcc3v3_sys: vcc3v3-sys { vcc5v0_host: vcc5v0-host-regulator { compatible = "regulator-fixed"; gpio = <&gpio4 RK_PA3 GPIO_ACTIVE_LOW>; - enable-active-low; pinctrl-names = "default"; pinctrl-0 = <&vcc5v0_host_en>; regulator-name = "vcc5v0_host";
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 68/141 netfilter: nf_conntrack_sip: fix ct_sip_walk_headers
In reply to Greg Kroah-HartmanFrom: Igor Ryzhov <[email protected]>
[ Upstream commit 39aebedeaaa95757f5c1f2ddb5f43fdddbf478ca ]
ct_sip_next_header and ct_sip_get_header return an absolute value of matchoff, not a shift from current dataoff. So dataoff should be assigned matchoff, not incremented by it.
This issue can be seen in the scenario when there are multiple Contact headers and the first one is using a hostname and other headers use IP addresses. In this case, ct_sip_walk_headers will work as follows:
The first ct_sip_get_header call to will find the first Contact header but will return -1 as the header uses a hostname. But matchoff will be changed to the offset of this header. After that, dataoff should be set to matchoff, so that the next ct_sip_get_header call find the next Contact header. But instead of assigning dataoff to matchoff, it is incremented by it, which is not correct, as matchoff is an absolute value of the offset. So on the next call to the ct_sip_get_header, dataoff will be incorrect, and the next Contact header may not be found at all.
--- net/netfilter/nf_conntrack_sip.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/netfilter/nf_conntrack_sip.c +2 -2
@@ -477,7 +477,7 @@ static int ct_sip_walk_headers(const struct nf_conn *ct, const char *dptr,return ret;if (ret ==0 )break ; - dataoff += *matchoff; + dataoff = *matchoff; } *in_header =0 ; }
@@ -489,7 +489,7 @@ static int ct_sip_walk_headers(const struct nf_conn *ct, const char *dptr,break ;if (ret ==0 )return ret; - dataoff += *matchoff; + dataoff = *matchoff; }if (in_header)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 69/141 netfilter: nf_conntrack_irc: Tighten matching on DCC message
In reply to Greg Kroah-HartmanFrom: David Leadbeater <[email protected]>
[ Upstream commit e8d5dfd1d8747b56077d02664a8838c71ced948e ]
CTCP messages should only be at the start of an IRC message, not anywhere within it.
While the helper only decodes packes in the ORIGINAL direction, its possible to make a client send a CTCP message back by empedding one into a PING request. As-is, thats enough to make the helper believe that it saw a CTCP message.
--- net/netfilter/nf_conntrack_irc.c | 34 ++++++++++++++++++++++++++------ 1 file changed, 28 insertions(+), 6 deletions(-)
net/netfilter/nf_conntrack_irc.c +28 -6
@@ -148,15 +148,37 @@ static int help(struct sk_buff *skb, unsigned int protoff, data = ib_ptr; data_limit = ib_ptr + skb->len - dataoff; -/* strlen("\1DCC SENT t AAAAAAAA P\1\n")=24 -* 5+MINMATCHLEN+strlen("t AAAAAAAA P\1\n")=14 */ -while (data < data_limit - (19 +MINMATCHLEN )) { -if (memcmp (data,"\1DCC " ,5 )) { +/* Skip any whitespace */ +while (data < data_limit -10 ) { +if (*data ==' ' || *data =='\r' || *data =='\n' ) + data++; +else +break ; + } + +/* strlen("PRIVMSG x ")=10 */ +if (data < data_limit -10 ) { +if (strncasecmp ("PRIVMSG " , data,8 )) + goto out; + data +=8 ; + } + +/* strlen(" :\1DCC SENT t AAAAAAAA P\1\n")=26 +* 7+MINMATCHLEN+strlen("t AAAAAAAA P\1\n")=26 +*/ +while (data < data_limit - (21 +MINMATCHLEN )) { +/* Find first " :", the start of message */ +if (memcmp (data," :" ,2 )) { data++;continue ; } + data +=2 ; + +/* then check that place only for the DCC command */ +if (memcmp (data,"\1DCC " ,5 )) + goto out; data +=5 ; -/* we have at least (19+MINMATCHLEN)-5 bytes valid data left */ +/* we have at least (21+MINMATCHLEN)-(2+5) bytes valid data left */ iph =ip_hdr (skb); pr_debug("DCC found in master %pI4:%u %pI4:%u\n",
@@ -172,7 +194,7 @@ static int help(struct sk_buff *skb, unsigned int protoff,pr_debug ("DCC %s detected\n" , dccprotos[i]);/* we have at least -* (19+MINMATCHLEN)-5-dccprotos[i].matchlen bytes valid +* (21+MINMATCHLEN)-7-dccprotos[i].matchlen bytes valid * data left (== 14/13 bytes) */ if (parse_dcc (data, data_limit, &dcc_ip, &dcc_port, &addr_beg_p, &addr_end_p)) {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 70/141 netfilter: nfnetlink_osf: fix possible bogus match in nf_osf_find()
In reply to Greg Kroah-HartmanFrom: Pablo Neira Ayuso <[email protected]>
[ Upstream commit 559c36c5a8d730c49ef805a72b213d3bba155cc8 ]
nf_osf_find() incorrectly returns true on mismatch, this leads to copying uninitialized memory area in nft_osf which can be used to leak stale kernel stack data to userspace.
--- net/netfilter/nfnetlink_osf.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/netfilter/nfnetlink_osf.c +3 -1
@@ -269,6 +269,7 @@ bool nf_osf_find(const struct sk_buff *skb,struct nf_osf_hdr_ctx ctx;const struct tcphdr *tcp;struct tcphdr _tcph; +bool found = false;memset (&ctx,0 ,sizeof (ctx));
@@ -283,10 +284,11 @@ bool nf_osf_find(const struct sk_buff *skb, data->genre = f->genre; data->version = f->version; + found = true;break ; } -return true; +return found; }EXPORT_SYMBOL_GPL (nf_osf_find);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 71/141 iavf: Fix cached head and tail value for iavf_get_tx_pending
In reply to Greg Kroah-HartmanFrom: Brett Creeley <[email protected]>
[ Upstream commit 809f23c0423a43266e47a7dc67e95b5cb4d1cbfc ]
The underlying hardware may or may not allow reading of the head or tail registers and it really makes no difference if we use the software cached values. So, always used the software cached values.
--- drivers/net/ethernet/intel/iavf/iavf_txrx.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/net/ethernet/intel/iavf/iavf_txrx.c +4 -1
@@ -114,8 +114,11 @@ u32 iavf_get_tx_pending(struct iavf_ring *ring, bool in_sw) {u32 head, tail; +/* underlying hardware might not allow access and/or always return +* 0 for the head/tail registers so just use the cached values +*/ head = ring->next_to_clean; - tail =readl (ring->tail); + tail = ring->next_to_use;if (head != tail) return (head < tail) ?
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 72/141 ipvlan: Fix out-of-bound bugs caused by unset skb->mac_header
In reply to Greg Kroah-HartmanFrom: Lu Wei <[email protected]>
[ Upstream commit 81225b2ea161af48e093f58e8dfee6d705b16af4 ]
If an AF_PACKET socket is used to send packets through ipvlan and the default xmit function of the AF_PACKET socket is changed from dev_queue_xmit() to packet_direct_xmit() via setsockopt() with the option name of PACKET_QDISC_BYPASS, the skb->mac_header may not be reset and remains as the initial value of 65535, this may trigger slab-out-of-bounds bugs as following:
=================================================================
UG: KASAN: slab-out-of-bounds in ipvlan_xmit_mode_l2+0xdb/0x330 [ipvlan]
PU: 2 PID: 1768 Comm: raw_send Kdump: loaded Not tainted 6.0.0-rc4+ #6 ardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 all Trace:
print_address_description.constprop.0+0x1d/0x160 print_report.cold+0x4f/0x112 kasan_report+0xa3/0x130 ipvlan_xmit_mode_l2+0xdb/0x330 [ipvlan] ipvlan_start_xmit+0x29/0xa0 [ipvlan] __dev_direct_xmit+0x2e2/0x380 packet_direct_xmit+0x22/0x60 packet_snd+0x7c9/0xc40 sock_sendmsg+0x9a/0xa0 __sys_sendto+0x18a/0x230 __x64_sys_sendto+0x74/0x90 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd
The root cause is:
1. packet_snd() only reset skb->mac_header when sock->type is SOCK_RAW
and skb->protocol is not specified as in packet_parse_headers()
2. packet_direct_xmit() doesn't reset skb->mac_header as dev_queue_xmit()
In this case, skb->mac_header is 65535 when ipvlan_xmit_mode_l2() is called. So when ipvlan_xmit_mode_l2() gets mac header with eth_hdr() which use "skb->head + skb->mac_header", out-of-bound access occurs.
This patch replaces eth_hdr() with skb_eth_hdr() in ipvlan_xmit_mode_l2() and reset mac header in multicast to solve this out-of-bound bug.
--- drivers/net/ipvlan/ipvlan_core.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/net/ipvlan/ipvlan_core.c +4 -2
@@ -496,7 +496,6 @@ static int ipvlan_process_v6_outbound(struct sk_buff *skb)static int ipvlan_process_outbound (struct sk_buff *skb) { -struct ethhdr *ethh =eth_hdr (skb);int ret =NET_XMIT_DROP ;/* The ipvlan is a pseudo-L2 device, so the packets that we receive
@@ -506,6 +505,8 @@ static int ipvlan_process_outbound(struct sk_buff *skb)if (skb_mac_header_was_set (skb)) {/* In this mode we dont care about * multicast and broadcast traffic */ +struct ethhdr *ethh =eth_hdr (skb); +if (is_multicast_ether_addr (ethh->h_dest)) { pr_debug_ratelimited( "Dropped {multi|broad}cast of type=[%x]\n",
@@ -590,7 +591,7 @@ static int ipvlan_xmit_mode_l3(struct sk_buff *skb, struct net_device *dev)static int ipvlan_xmit_mode_l2 (struct sk_buff *skb,struct net_device *dev) {const struct ipvl_dev *ipvlan =netdev_priv (dev); -struct ethhdr *eth =eth_hdr (skb); +struct ethhdr *eth =skb_eth_hdr (skb);struct ipvl_addr *addr;void *lyr3h;int addr_type;
@@ -620,6 +621,7 @@ static int ipvlan_xmit_mode_l2(struct sk_buff *skb, struct net_device *dev)return dev_forward_skb (ipvlan->phy_dev, skb); }else if (is_multicast_ether_addr (eth->h_dest)) { +skb_reset_mac_header (skb);ipvlan_skb_crossing_ns (skb,NULL );ipvlan_multicast_enqueue (ipvlan->port, skb, true);return NET_XMIT_SUCCESS ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 73/141 net: let flow have same hash in two directions
In reply to Greg Kroah-HartmanFrom: zhang kai <[email protected]>
[ Upstream commit 1e60cebf82948cfdc9497ea4553bab125587593c ]
using same source and destination ip/port for flow hash calculation within the two directions.
Stable-dep-of: 64ae13ed4784 ("net: core: fix flow symmetric hash")
--- net/core/flow_dissector.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-)
net/core/flow_dissector.c +9 -9
@@ -1485,7 +1485,7 @@ __be32 flow_get_u32_dst(const struct flow_keys *flow) }EXPORT_SYMBOL (flow_get_u32_dst); -/* Sort the source and destination IP (and the ports if the IP are the same), +/* Sort the source and destination IP and the ports, * to have consistent hash within the two directions */ static inline void __flow_hash_consistentify (struct flow_keys *keys)
@@ -1496,11 +1496,11 @@ static inline void __flow_hash_consistentify(struct flow_keys *keys)case FLOW_DISSECTOR_KEY_IPV4_ADDRS : addr_diff = (__force u32 )keys->addrs.v4addrs.dst - (__force u32 )keys->addrs.v4addrs.src; -if ((addr_diff <0 ) || - (addr_diff ==0 && - ((__force u16 )keys->ports.dst < - (__force u16 )keys->ports.src))) { +if (addr_diff <0 )swap (keys->addrs.v4addrs.src, keys->addrs.v4addrs.dst); + +if ((__force u16 )keys->ports.dst < + (__force u16 )keys->ports.src) {swap (keys->ports.src, keys->ports.dst); }break ;
@@ -1508,13 +1508,13 @@ static inline void __flow_hash_consistentify(struct flow_keys *keys) addr_diff =memcmp (&keys->addrs.v6addrs.dst, &keys->addrs.v6addrs.src,sizeof (keys->addrs.v6addrs.dst)); -if ((addr_diff <0 ) || - (addr_diff ==0 && - ((__force u16 )keys->ports.dst < - (__force u16 )keys->ports.src))) { +if (addr_diff <0 ) {for (i =0 ; i <4 ; i++)swap (keys->addrs.v6addrs.src.s6_addr32[i], keys->addrs.v6addrs.dst.s6_addr32[i]); + } +if ((__force u16 )keys->ports.dst < + (__force u16 )keys->ports.src) {swap (keys->ports.src, keys->ports.dst); }break ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 74/141 net: core: fix flow symmetric hash
In reply to Greg Kroah-HartmanFrom: Ludovic Cintrat <[email protected]>
[ Upstream commit 64ae13ed478428135cddc2f1113dff162d8112d4 ]
__flow_hash_consistentify() wrongly swaps ipv4 addresses in few cases. This function is indirectly used by __skb_get_hash_symmetric(), which is used to fanout packets in AF_PACKET.
Intrusion detection systems may be impacted by this issue.
__flow_hash_consistentify() computes the addresses difference then swaps them if the difference is negative. In few cases src - dst and dst - src are both negative.
The following snippet mimics __flow_hash_consistentify():
```
#include <stdio.h>
#include <stdint.h>
int main(int argc, char** argv) {
int diffs_d, diffd_s;
uint32_t dst = 0xb225a8c0; /* 178.37.168.192 --> 192.168.37.178 */
uint32_t src = 0x3225a8c0; /* 50.37.168.192 --> 192.168.37.50 */
uint32_t dst2 = 0x3325a8c0; /* 51.37.168.192 --> 192.168.37.51 */
diffs_d = src - dst;
diffd_s = dst - src;
printf("src:%08x dst:%08x, diff(s-d)=%d(0x%x) diff(d-s)=%d(0x%x)\n",
src, dst, diffs_d, diffs_d, diffd_s, diffd_s);
diffs_d = src - dst2;
diffd_s = dst2 - src;
printf("src:%08x dst:%08x, diff(s-d)=%d(0x%x) diff(d-s)=%d(0x%x)\n",
src, dst2, diffs_d, diffs_d, diffd_s, diffd_s);
return 0;
}
```Results:
src:3225a8c0 dst:b225a8c0, \
diff(s-d)=-2147483648(0x80000000) \
diff(d-s)=-2147483648(0x80000000)src:3225a8c0 dst:3325a8c0, \
diff(s-d)=-16777216(0xff000000) \
diff(d-s)=16777216(0x1000000)In the first case the addresses differences are always < 0, therefore __flow_hash_consistentify() always swaps, thus dst->src and src->dst packets have differents hashes.
--- net/core/flow_dissector.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
net/core/flow_dissector.c +2 -3
@@ -1494,9 +1494,8 @@ static inline void __flow_hash_consistentify(struct flow_keys *keys)switch (keys->control.addr_type) {case FLOW_DISSECTOR_KEY_IPV4_ADDRS : - addr_diff = (__force u32 )keys->addrs.v4addrs.dst - - (__force u32 )keys->addrs.v4addrs.src; -if (addr_diff <0 ) +if ((__force u32 )keys->addrs.v4addrs.dst < + (__force u32 )keys->addrs.v4addrs.src)swap (keys->addrs.v4addrs.src, keys->addrs.v4addrs.dst); if ((__force u16)keys->ports.dst <
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 75/141 net: phy: aquantia: wait for the suspend/resume operations to finish
In reply to Greg Kroah-HartmanFrom: Ioana Ciornei <[email protected]>
[ Upstream commit ca2dccdeeb49a7e408112d681bf447984c845292 ]
The Aquantia datasheet notes that after issuing a Processor-Intensive MDIO operation, like changing the low-power state of the device, the driver should wait for the operation to finish before issuing a new MDIO command.
The new aqr107_wait_processor_intensive_op() function is added which can be used after these kind of MDIO operations. At the moment, we are only adding it at the end of the suspend/resume calls.
The issue was identified on a board featuring the AQR113C PHY, on which commands like 'ip link (..) up / down' issued without any delays between them would render the link on the PHY to remain down. The issue was easy to reproduce with a one-liner:
$ ip link set dev ethX down; ip link set dev ethX up; \ ip link set dev ethX down; ip link set dev ethX up;
--- drivers/net/phy/aquantia_main.c | 53 ++++++++++++++++++++++++++++++--- 1 file changed, 49 insertions(+), 4 deletions(-)
drivers/net/phy/aquantia_main.c +49 -4
@@ -89,6 +89,9 @@#define VEND1_GLOBAL_FW_ID_MAJOR GENMASK(15, 8)#define VEND1_GLOBAL_FW_ID_MINOR GENMASK(7, 0) +#define VEND1_GLOBAL_GEN_STAT2 0xc831 +#define VEND1_GLOBAL_GEN_STAT2_OP_IN_PROG BIT(15) +#define VEND1_GLOBAL_RSVD_STAT1 0xc885#define VEND1_GLOBAL_RSVD_STAT1_FW_BUILD_ID GENMASK(7, 4)#define VEND1_GLOBAL_RSVD_STAT1_PROV_ID GENMASK(3, 0)
@@ -123,6 +126,12 @@#define VEND1_GLOBAL_INT_VEND_MASK_GLOBAL2 BIT(1)#define VEND1_GLOBAL_INT_VEND_MASK_GLOBAL3 BIT(0) +/* Sleep and timeout for checking if the Processor-Intensive +* MDIO operation is finished +*/ +#define AQR107_OP_IN_PROG_SLEEP 1000 +#define AQR107_OP_IN_PROG_TIMEOUT 100000 +struct aqr107_hw_stat {const char *name;int reg;
@@ -569,16 +578,52 @@ static void aqr107_link_change_notify(struct phy_device *phydev)phydev_info (phydev,"Aquantia 1000Base-T2 mode active\n" ); } +static int aqr107_wait_processor_intensive_op (struct phy_device *phydev) +{ +int val, err; + +/* The datasheet notes to wait at least 1ms after issuing a +* processor intensive operation before checking. +* We cannot use the 'sleep_before_read' parameter of read_poll_timeout +* because that just determines the maximum time slept, not the minimum. +*/ +usleep_range (1000 ,5000 ); + + err =phy_read_mmd_poll_timeout (phydev,MDIO_MMD_VEND1 , +VEND1_GLOBAL_GEN_STAT2 , val, + !(val &VEND1_GLOBAL_GEN_STAT2_OP_IN_PROG ), +AQR107_OP_IN_PROG_SLEEP , +AQR107_OP_IN_PROG_TIMEOUT , false); +if (err) { +phydev_err (phydev,"timeout: processor-intensive MDIO operation\n" ); +return err; + } + +return 0 ; +} +static int aqr107_suspend (struct phy_device *phydev) { -return phy_set_bits_mmd (phydev,MDIO_MMD_VEND1 ,MDIO_CTRL1 , -MDIO_CTRL1_LPOWER ); +int err; + + err =phy_set_bits_mmd (phydev,MDIO_MMD_VEND1 ,MDIO_CTRL1 , +MDIO_CTRL1_LPOWER ); +if (err) +return err; + +return aqr107_wait_processor_intensive_op (phydev); }static int aqr107_resume (struct phy_device *phydev) { -return phy_clear_bits_mmd (phydev,MDIO_MMD_VEND1 ,MDIO_CTRL1 , -MDIO_CTRL1_LPOWER ); +int err; + + err =phy_clear_bits_mmd (phydev,MDIO_MMD_VEND1 ,MDIO_CTRL1 , +MDIO_CTRL1_LPOWER ); +if (err) +return err; + +return aqr107_wait_processor_intensive_op (phydev); }static int aqr107_probe (struct phy_device *phydev)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 76/141 scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region
In reply to Greg Kroah-HartmanFrom: Suganath Prabu S <[email protected]>
[ Upstream commit d6adc251dd2fede6aaaf6c39f7e4ad799eda3758 ]
According to the MPI specification, PCIe SGL buffers can not cross a 4 GB boundary.
While allocating, if any buffer crosses the 4 GB boundary, then:
- Release the already allocated memory pools; and
- Reallocate them by changing the DMA coherent mask to 32-bit
Stable-dep-of: e0e0747de0ea ("scsi: mpt3sas: Fix return value check of dma_get_required_mask()")
--- drivers/scsi/mpt3sas/mpt3sas_base.c | 159 ++++++++++++++++++++-------- drivers/scsi/mpt3sas/mpt3sas_base.h | 1 + 2 files changed, 113 insertions(+), 47 deletions(-)
drivers/scsi/mpt3sas/mpt3sas_base.c +112 -47
@@ -2822,23 +2822,22 @@ static int _base_config_dma_addressing(struct MPT3SAS_ADAPTER *ioc, struct pci_dev *pdev) { struct sysinfo s; -int dma_mask;if (ioc->is_mcpu_endpoint ||sizeof (dma_addr_t) ==4 || ioc->use_32bit_dma ||dma_get_required_mask (&pdev->dev) <=32 ) - dma_mask =32 ; + ioc->dma_mask =32 ;/* Set 63 bit DMA mask for all SAS3 and SAS35 controllers */ else if (ioc->hba_mpi_version_belonged >MPI2_VERSION ) - dma_mask =63 ; + ioc->dma_mask =63 ;else - dma_mask =64 ; + ioc->dma_mask =64 ; -if (dma_set_mask (&pdev->dev,DMA_BIT_MASK (dma_mask)) || -dma_set_coherent_mask (&pdev->dev,DMA_BIT_MASK (dma_mask))) +if (dma_set_mask (&pdev->dev,DMA_BIT_MASK (ioc->dma_mask)) || +dma_set_coherent_mask (&pdev->dev,DMA_BIT_MASK (ioc->dma_mask)))return -ENODEV ; -if (dma_mask >32 ) { +if (ioc->dma_mask >32 ) { ioc->base_add_sg_single = &_base_add_sg_single_64; ioc->sge_size =sizeof (Mpi2SGESimple64_t); }else {
@@ -2848,7 +2847,7 @@ _base_config_dma_addressing(struct MPT3SAS_ADAPTER *ioc, struct pci_dev *pdev)si_meminfo (&s);ioc_info (ioc,"%d BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (%ld kB)\n" , - dma_mask,convert_to_kb (s.totalram)); + ioc->dma_mask,convert_to_kb (s.totalram));return 0 ; }
@@ -4902,10 +4901,10 @@ _base_release_memory_pools(struct MPT3SAS_ADAPTER *ioc)dma_pool_free (ioc->pcie_sgl_dma_pool, ioc->pcie_sg_lookup[i].pcie_sgl, ioc->pcie_sg_lookup[i].pcie_sgl_dma); + ioc->pcie_sg_lookup[i].pcie_sgl =NULL ; }dma_pool_destroy (ioc->pcie_sgl_dma_pool); } -if (ioc->config_page) { dexitprintk(ioc, ioc_info(ioc, "config_page(0x%p): free\n",
@@ -4960,6 +4959,89 @@ mpt3sas_check_same_4gb_region(long reply_pool_start_address, u32 pool_sz)return 0 ; } +/** +* _base_reduce_hba_queue_depth- Retry with reduced queue depth +* @ioc: Adapter object +* +* Return: 0 for success, non-zero for failure. +**/ +static inline int +_base_reduce_hba_queue_depth (struct MPT3SAS_ADAPTER *ioc) +{ +int reduce_sz =64 ; + +if ((ioc->hba_queue_depth - reduce_sz) > + (ioc->internal_depth +INTERNAL_SCSIIO_CMDS_COUNT )) { + ioc->hba_queue_depth -= reduce_sz; +return 0 ; + }else +return -ENOMEM ; +} + +/** +* _base_allocate_pcie_sgl_pool - Allocating DMA'able memory +* for pcie sgl pools. +* @ioc: Adapter object +* @sz: DMA Pool size +* @ct: Chain tracker +* Return: 0 for success, non-zero for failure. +*/ + +static int +_base_allocate_pcie_sgl_pool (struct MPT3SAS_ADAPTER *ioc,u32 sz) +{ +int i =0 , j =0 ; +struct chain_tracker *ct; + + ioc->pcie_sgl_dma_pool = +dma_pool_create ("PCIe SGL pool" , &ioc->pdev->dev, sz, + ioc->page_size,0 ); +if (!ioc->pcie_sgl_dma_pool) { +ioc_err (ioc,"PCIe SGL pool: dma_pool_create failed\n" ); +return -ENOMEM ; + } + + ioc->chains_per_prp_buffer = sz/ioc->chain_segment_sz; + ioc->chains_per_prp_buffer = +min (ioc->chains_per_prp_buffer, ioc->chains_needed_per_io); +for (i =0 ; i < ioc->scsiio_depth; i++) { + ioc->pcie_sg_lookup[i].pcie_sgl = +dma_pool_alloc (ioc->pcie_sgl_dma_pool,GFP_KERNEL , + &ioc->pcie_sg_lookup[i].pcie_sgl_dma); +if (!ioc->pcie_sg_lookup[i].pcie_sgl) { +ioc_err (ioc,"PCIe SGL pool: dma_pool_alloc failed\n" ); +return -EAGAIN ; + } + +if (!mpt3sas_check_same_4gb_region ( + (long )ioc->pcie_sg_lookup[i].pcie_sgl, sz)) { +ioc_err (ioc,"PCIE SGLs are not in same 4G !! pcie sgl (0x%p) dma = (0x%llx)\n" , + ioc->pcie_sg_lookup[i].pcie_sgl, + (unsigned long long ) + ioc->pcie_sg_lookup[i].pcie_sgl_dma); + ioc->use_32bit_dma = true; +return -EAGAIN ; + } + +for (j =0 ; j < ioc->chains_per_prp_buffer; j++) { + ct = &ioc->chain_lookup[i].chains_per_smid[j]; + ct->chain_buffer = + ioc->pcie_sg_lookup[i].pcie_sgl + + (j * ioc->chain_segment_sz); + ct->chain_buffer_dma = + ioc->pcie_sg_lookup[i].pcie_sgl_dma + + (j * ioc->chain_segment_sz); + } + } +dinitprintk (ioc,ioc_info (ioc, +"PCIe sgl pool depth(%d), element_size(%d), pool_size(%d kB)\n" , + ioc->scsiio_depth, sz, (sz * ioc->scsiio_depth)/1024 )); +dinitprintk (ioc,ioc_info (ioc, +"Number of chains can fit in a PRP page(%d)\n" , + ioc->chains_per_prp_buffer)); +return 0 ; +} +/** * base_alloc_rdpq_dma_pool - Allocating DMA'able memory * for reply queues.
@@ -5058,7 +5140,7 @@ _base_allocate_memory_pools(struct MPT3SAS_ADAPTER *ioc)unsigned short sg_tablesize;u16 sge_size;int i, j; -int ret =0 ; +int ret =0 , rc =0 ;struct chain_tracker *ct;dinitprintk (ioc,ioc_info (ioc,"%s\n" , __func__));
@@ -5357,6 +5439,7 @@ _base_allocate_memory_pools(struct MPT3SAS_ADAPTER *ioc)* be required for NVMe PRP's, only each set of NVMe blocks will be * contiguous, so a new set is allocated for each possible I/O. */ + ioc->chains_per_prp_buffer =0 ;if (ioc->facts.ProtocolFlags &MPI2_IOCFACTS_PROTOCOL_NVME_DEVICES ) { nvme_blocks_needed =
@@ -5371,43 +5454,11 @@ _base_allocate_memory_pools(struct MPT3SAS_ADAPTER *ioc) goto out; } sz = nvme_blocks_needed * ioc->page_size; - ioc->pcie_sgl_dma_pool = -dma_pool_create ("PCIe SGL pool" , &ioc->pdev->dev, sz,16 ,0 ); -if (!ioc->pcie_sgl_dma_pool) { -ioc_info (ioc,"PCIe SGL pool: dma_pool_create failed\n" ); - goto out; - } - - ioc->chains_per_prp_buffer = sz/ioc->chain_segment_sz; - ioc->chains_per_prp_buffer =min (ioc->chains_per_prp_buffer, - ioc->chains_needed_per_io); - -for (i =0 ; i < ioc->scsiio_depth; i++) { - ioc->pcie_sg_lookup[i].pcie_sgl =dma_pool_alloc ( - ioc->pcie_sgl_dma_pool,GFP_KERNEL , - &ioc->pcie_sg_lookup[i].pcie_sgl_dma); -if (!ioc->pcie_sg_lookup[i].pcie_sgl) { -ioc_info (ioc,"PCIe SGL pool: dma_pool_alloc failed\n" ); - goto out; - } -for (j =0 ; j < ioc->chains_per_prp_buffer; j++) { - ct = &ioc->chain_lookup[i].chains_per_smid[j]; - ct->chain_buffer = - ioc->pcie_sg_lookup[i].pcie_sgl + - (j * ioc->chain_segment_sz); - ct->chain_buffer_dma = - ioc->pcie_sg_lookup[i].pcie_sgl_dma + - (j * ioc->chain_segment_sz); - } - } - -dinitprintk (ioc, -ioc_info (ioc,"PCIe sgl pool depth(%d), element_size(%d), pool_size(%d kB)\n" , - ioc->scsiio_depth, sz, - (sz * ioc->scsiio_depth) /1024 )); -dinitprintk (ioc, -ioc_info (ioc,"Number of chains can fit in a PRP page(%d)\n" , - ioc->chains_per_prp_buffer)); + rc =_base_allocate_pcie_sgl_pool (ioc, sz); +if (rc == -ENOMEM ) +return -ENOMEM ; +else if (rc == -EAGAIN ) + goto try_32bit_dma; total_sz += sz * ioc->scsiio_depth; }
@@ -5577,6 +5628,19 @@ _base_allocate_memory_pools(struct MPT3SAS_ADAPTER *ioc) ioc->shost->sg_tablesize);return 0 ; +try_32bit_dma: +_base_release_memory_pools (ioc); +if (ioc->use_32bit_dma && (ioc->dma_mask >32 )) { +/* Change dma coherent mask to 32 bit and reallocate */ +if (_base_config_dma_addressing (ioc, ioc->pdev) !=0 ) { +pr_err ("Setting 32 bit coherent DMA mask Failed %s\n" , +pci_name (ioc->pdev)); +return -ENODEV ; + } + }else if (_base_reduce_hba_queue_depth (ioc) !=0 ) +return -ENOMEM ; + goto retry_allocation; + out:return -ENOMEM ; }
@@ -7239,6 +7303,7 @@ mpt3sas_base_attach(struct MPT3SAS_ADAPTER *ioc) ioc->rdpq_array_enable_assigned =0 ; ioc->use_32bit_dma = false; + ioc->dma_mask =64 ;if (ioc->is_aero_ioc) ioc->base_readl = &_base_readl_aero;else
drivers/scsi/mpt3sas/mpt3sas_base.h +1 -0
@@ -1257,6 +1257,7 @@ struct MPT3SAS_ADAPTER {u16 thresh_hold;u8 high_iops_queues;u32 drv_support_bitmap; +u32 dma_mask;bool enable_sdev_max_qd;bool use_32bit_dma;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 77/141 scsi: mpt3sas: Fix return value check of dma_get_required_mask()
In reply to Greg Kroah-HartmanFrom: Sreekanth Reddy <[email protected]>
[ Upstream commit e0e0747de0ea3dd87cdbb0393311e17471a9baf1 ]
Fix the incorrect return value check of dma_get_required_mask(). Due to this incorrect check, the driver was always setting the DMA mask to 63 bit.
--- drivers/scsi/mpt3sas/mpt3sas_base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/mpt3sas/mpt3sas_base.c +1 -1
@@ -2825,7 +2825,7 @@ _base_config_dma_addressing(struct MPT3SAS_ADAPTER *ioc, struct pci_dev *pdev)if (ioc->is_mcpu_endpoint ||sizeof (dma_addr_t) ==4 || ioc->use_32bit_dma || -dma_get_required_mask (&pdev->dev) <=32 ) +dma_get_required_mask (&pdev->dev) <=DMA_BIT_MASK (32 )) ioc->dma_mask =32 ;/* Set 63 bit DMA mask for all SAS3 and SAS35 controllers */ else if (ioc->hba_mpi_version_belonged >MPI2_VERSION )
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 78/141 net: bonding: Share lacpdu_mcast_addr definition
In reply to Greg Kroah-HartmanFrom: Benjamin Poirier <[email protected]>
[ Upstream commit 1d9a143ee3408349700f44a9197b7ae0e4faae5d ]
There are already a few definitions of arrays containing MULTICAST_LACPDU_ADDR and the next patch will add one more use. These all contain the same constant data so define one common instance for all bonding code.
Stable-dep-of: 86247aba599e ("net: bonding: Unsync device addresses on ndo_stop")
--- drivers/net/bonding/bond_3ad.c | 5 +++-- drivers/net/bonding/bond_main.c | 16 ++++------------ include/net/bond_3ad.h | 2 -- include/net/bonding.h | 3 +++ 4 files changed, 10 insertions(+), 16 deletions(-)
drivers/net/bonding/bond_3ad.c +3 -2
@@ -85,8 +85,9 @@ static const u8 null_mac_addr[ETH_ALEN + 2] __long_aligned = {static u16 ad_ticks_per_sec;static const int ad_delta_in_ticks = (AD_TIMER_INTERVAL *HZ ) /1000 ; -static const u8 lacpdu_mcast_addr[ETH_ALEN + 2] __long_aligned = -MULTICAST_LACPDU_ADDR ; +const u8 lacpdu_mcast_addr[ETH_ALEN + 2] __long_aligned = { +0x01 ,0x80 ,0xC2 ,0x00 ,0x00 ,0x02 +};/* ================= main 802.3ad protocol functions ================== */ static int ad_lacpdu_send (struct port *port);
drivers/net/bonding/bond_main.c +4 -12
@@ -827,12 +827,8 @@ static void bond_hw_addr_flush(struct net_device *bond_dev,dev_uc_unsync (slave_dev, bond_dev);dev_mc_unsync (slave_dev, bond_dev); -if (BOND_MODE (bond) ==BOND_MODE_8023AD ) { -/* del lacpdu mc addr from mc list */ -u8 lacpdu_multicast[ETH_ALEN ] =MULTICAST_LACPDU_ADDR ; - -dev_mc_del (slave_dev, lacpdu_multicast); - } +if (BOND_MODE (bond) ==BOND_MODE_8023AD ) +dev_mc_del (slave_dev, lacpdu_mcast_addr); }/*--------------------------- Active slave change ---------------------------*/
@@ -2078,12 +2074,8 @@ int bond_enslave(struct net_device *bond_dev, struct net_device *slave_dev,dev_uc_sync_multiple (slave_dev, bond_dev);netif_addr_unlock_bh (bond_dev); -if (BOND_MODE (bond) ==BOND_MODE_8023AD ) { -/* add lacpdu mc addr to mc list */ -u8 lacpdu_multicast[ETH_ALEN ] =MULTICAST_LACPDU_ADDR ; - -dev_mc_add (slave_dev, lacpdu_multicast); - } +if (BOND_MODE (bond) ==BOND_MODE_8023AD ) +dev_mc_add (slave_dev, lacpdu_mcast_addr); } bond->slave_cnt++;
include/net/bond_3ad.h +0 -2
@@ -15,8 +15,6 @@#define PKT_TYPE_LACPDU cpu_to_be16(ETH_P_SLOW)#define AD_TIMER_INTERVAL 100/*msec*/ -#define MULTICAST_LACPDU_ADDR {0x01, 0x80, 0xC2, 0x00, 0x00, 0x02} -#define AD_LACP_SLOW 0#define AD_LACP_FAST 1
include/net/bonding.h +3 -0
@@ -763,6 +763,9 @@ extern struct rtnl_link_ops bond_link_ops;/* exported from bond_sysfs_slave.c */ extern const struct sysfs_ops slave_sysfs_ops; +/* exported from bond_3ad.c */ +extern const u8 lacpdu_mcast_addr[]; +static inline netdev_tx_t bond_tx_drop (struct net_device *dev,struct sk_buff *skb) {atomic_long_inc (&dev->tx_dropped);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 79/141 net: bonding: Unsync device addresses on ndo_stop
In reply to Greg Kroah-HartmanFrom: Benjamin Poirier <[email protected]>
[ Upstream commit 86247aba599e5b07d7e828e6edaaebb0ef2b1158 ]
Netdev drivers are expected to call dev_{uc,mc}_sync() in their ndo_set_rx_mode method and dev_{uc,mc}_unsync() in their ndo_stop method. This is mentioned in the kerneldoc for those dev_* functions.
The bonding driver calls dev_{uc,mc}_unsync() during ndo_uninit instead of ndo_stop. This is ineffective because address lists (dev->{uc,mc}) have already been emptied in unregister_netdevice_many() before ndo_uninit is called. This mistake can result in addresses being leftover on former bond slaves after a bond has been deleted; see test_LAG_cleanup() in the last patch in this series.
Add unsync calls, via bond_hw_addr_flush(), at their expected location, bond_close().
Add dev_mc_add() call to bond_open() to match the above change.
v3:
* When adding or deleting a slave, only sync/unsync, add/del addresses if the bond is up. In other cases, it is taken care of at the right time by ndo_open/ndo_set_rx_mode/ndo_stop.
--- drivers/net/bonding/bond_main.c | 47 ++++++++++++++++++++++++--------- 1 file changed, 35 insertions(+), 12 deletions(-)
drivers/net/bonding/bond_main.c +35 -12
@@ -848,7 +848,8 @@ static void bond_hw_addr_swap(struct bonding *bond, struct slave *new_active,if (bond->dev->flags &IFF_ALLMULTI )dev_set_allmulti (old_active->dev,-1 ); -bond_hw_addr_flush (bond->dev, old_active->dev); +if (bond->dev->flags &IFF_UP ) +bond_hw_addr_flush (bond->dev, old_active->dev); }if (new_active) {
@@ -859,10 +860,12 @@ static void bond_hw_addr_swap(struct bonding *bond, struct slave *new_active,if (bond->dev->flags &IFF_ALLMULTI )dev_set_allmulti (new_active->dev,1 ); -netif_addr_lock_bh (bond->dev); -dev_uc_sync (new_active->dev, bond->dev); -dev_mc_sync (new_active->dev, bond->dev); -netif_addr_unlock_bh (bond->dev); +if (bond->dev->flags &IFF_UP ) { +netif_addr_lock_bh (bond->dev); +dev_uc_sync (new_active->dev, bond->dev); +dev_mc_sync (new_active->dev, bond->dev); +netif_addr_unlock_bh (bond->dev); + } } }
@@ -2069,13 +2072,15 @@ int bond_enslave(struct net_device *bond_dev, struct net_device *slave_dev, } } -netif_addr_lock_bh (bond_dev); -dev_mc_sync_multiple (slave_dev, bond_dev); -dev_uc_sync_multiple (slave_dev, bond_dev); -netif_addr_unlock_bh (bond_dev); +if (bond_dev->flags &IFF_UP ) { +netif_addr_lock_bh (bond_dev); +dev_mc_sync_multiple (slave_dev, bond_dev); +dev_uc_sync_multiple (slave_dev, bond_dev); +netif_addr_unlock_bh (bond_dev); -if (BOND_MODE (bond) ==BOND_MODE_8023AD ) -dev_mc_add (slave_dev, lacpdu_mcast_addr); +if (BOND_MODE (bond) ==BOND_MODE_8023AD ) +dev_mc_add (slave_dev, lacpdu_mcast_addr); + } } bond->slave_cnt++;
@@ -2302,7 +2307,8 @@ static int __bond_release_one(struct net_device *bond_dev,if (old_flags &IFF_ALLMULTI )dev_set_allmulti (slave_dev,-1 ); -bond_hw_addr_flush (bond_dev, slave_dev); +if (old_flags &IFF_UP ) +bond_hw_addr_flush (bond_dev, slave_dev); }slave_disable_netpoll (slave);
@@ -3764,6 +3770,9 @@ static int bond_open(struct net_device *bond_dev)/* register to receive LACPDUs */ bond->recv_probe = bond_3ad_lacpdu_recv;bond_3ad_initiate_agg_selection (bond,1 ); + +bond_for_each_slave (bond, slave, iter) +dev_mc_add (slave->dev, lacpdu_mcast_addr); }if (bond_mode_can_use_xmit_hash (bond))
@@ -3775,6 +3784,7 @@ static int bond_open(struct net_device *bond_dev)static int bond_close (struct net_device *bond_dev) {struct bonding *bond =netdev_priv (bond_dev); +struct slave *slave;bond_work_cancel_all (bond); bond->send_peer_notif =0 ;
@@ -3782,6 +3792,19 @@ static int bond_close(struct net_device *bond_dev)bond_alb_deinitialize (bond); bond->recv_probe =NULL ; +if (bond_uses_primary (bond)) { +rcu_read_lock (); + slave =rcu_dereference (bond->curr_active_slave); +if (slave) +bond_hw_addr_flush (bond_dev, slave->dev); +rcu_read_unlock (); + }else { +struct list_head *iter; + +bond_for_each_slave (bond, slave, iter) +bond_hw_addr_flush (bond_dev, slave->dev); + } +return 0 ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 80/141 net: team: Unsync device addresses on ndo_stop
In reply to Greg Kroah-HartmanFrom: Benjamin Poirier <[email protected]>
[ Upstream commit bd60234222b2fd5573526da7bcd422801f271f5f ]
Netdev drivers are expected to call dev_{uc,mc}_sync() in their ndo_set_rx_mode method and dev_{uc,mc}_unsync() in their ndo_stop method. This is mentioned in the kerneldoc for those dev_* functions.
The team driver calls dev_{uc,mc}_unsync() during ndo_uninit instead of ndo_stop. This is ineffective because address lists (dev->{uc,mc}) have already been emptied in unregister_netdevice_many() before ndo_uninit is called. This mistake can result in addresses being leftover on former team ports after a team device has been deleted; see test_LAG_cleanup() in the last patch in this series.
Add unsync calls at their expected location, team_close().
v3:
* When adding or deleting a port, only sync/unsync addresses if the team device is up. In other cases, it is taken care of at the right time by ndo_open/ndo_set_rx_mode/ndo_stop.
--- drivers/net/team/team.c | 24 ++++++++++++++++++------ 1 file changed, 18 insertions(+), 6 deletions(-)
drivers/net/team/team.c +18 -6
@@ -1270,10 +1270,12 @@ static int team_port_add(struct team *team, struct net_device *port_dev, } } -netif_addr_lock_bh (dev); -dev_uc_sync_multiple (port_dev, dev); -dev_mc_sync_multiple (port_dev, dev); -netif_addr_unlock_bh (dev); +if (dev->flags &IFF_UP ) { +netif_addr_lock_bh (dev); +dev_uc_sync_multiple (port_dev, dev); +dev_mc_sync_multiple (port_dev, dev); +netif_addr_unlock_bh (dev); + } port->index =-1 ;list_add_tail_rcu (&port->list, &team->port_list);
@@ -1344,8 +1346,10 @@ static int team_port_del(struct team *team, struct net_device *port_dev)netdev_rx_handler_unregister (port_dev);team_port_disable_netpoll (port);vlan_vids_del_by_dev (port_dev, dev); -dev_uc_unsync (port_dev, dev); -dev_mc_unsync (port_dev, dev); +if (dev->flags &IFF_UP ) { +dev_uc_unsync (port_dev, dev); +dev_mc_unsync (port_dev, dev); + }dev_close (port_dev);team_port_leave (team, port);
@@ -1695,6 +1699,14 @@ static int team_open(struct net_device *dev)static int team_close (struct net_device *dev) { +struct team *team =netdev_priv (dev); +struct team_port *port; + +list_for_each_entry (port, &team->port_list, list) { +dev_uc_unsync (port->dev, dev); +dev_mc_unsync (port->dev, dev); + } +return 0 ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 81/141 drm/panel: simple: Fix innolux_g121i1_l01 bus_format
In reply to Greg Kroah-HartmanFrom: Heiko Schocher <[email protected]>
[ Upstream commit a7c48a0ab87ae52c087d663e83e56b8225ac4cce ]
innolux_g121i1_l01 sets bpc to 6, so use the corresponding bus format:MEDIA_BUS_FMT_RGB666_1X7X3_SPWG.
--- drivers/gpu/drm/panel/panel-simple.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/panel/panel-simple.c +1 -1
@@ -2201,7 +2201,7 @@ static const struct panel_desc innolux_g121i1_l01 = { .enable = 200, .disable = 20, }, - .bus_format = MEDIA_BUS_FMT_RGB888_1X7X4_SPWG, + .bus_format = MEDIA_BUS_FMT_RGB666_1X7X3_SPWG, .connector_type = DRM_MODE_CONNECTOR_LVDS, };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 82/141 MIPS: lantiq: export clk_get_io() for lantiq_wdt.ko
In reply to Greg Kroah-HartmanFrom: Randy Dunlap <[email protected]>
[ Upstream commit 502550123bee6a2ffa438409b5b9aad4d6db3a8c ]
The lantiq WDT driver uses clk_get_io(), which is not exported, so export it to fix a build error:
ERROR: modpost: "clk_get_io" [drivers/watchdog/lantiq_wdt.ko] undefined!
--- arch/mips/lantiq/clk.c | 1 + 1 file changed, 1 insertion(+)
arch/mips/lantiq/clk.c +1 -0
@@ -50,6 +50,7 @@ struct clk *clk_get_io(void) {return &cpu_clk_generic[2 ]; } +EXPORT_SYMBOL_GPL (clk_get_io);struct clk *clk_get_ppe (void ) {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 83/141 MIPS: Loongson32: Fix PHY-mode being left unspecified
In reply to Greg Kroah-HartmanFrom: Serge Semin <[email protected]>
[ Upstream commit e9f3f8f488005f6da3cfb66070706770ecaef747 ]
commit 0060c8783330 ("net: stmmac: implement support for passive mode converters via dt") has changed the plat->interface field semantics from containing the PHY-mode to specifying the MAC-PCS interface mode. Due to that the loongson32 platform code will leave the phylink interface uninitialized with the PHY-mode intended by the means of the actual platform setup. The commit-author most likely has just missed the arch-specific code to fix. Let's mend the Loongson32 platform code then by assigning the PHY-mode to the phy_interface field of the STMMAC platform data.
--- arch/mips/loongson32/common/platform.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
arch/mips/loongson32/common/platform.c +8 -8
@@ -98,7 +98,7 @@ int ls1x_eth_mux_init(struct platform_device *pdev, void *priv)if (plat_dat->bus_id) {__raw_writel (__raw_readl (LS1X_MUX_CTRL0 ) |GMAC1_USE_UART1 |GMAC1_USE_UART0 ,LS1X_MUX_CTRL0 ); -switch (plat_dat->interface) { +switch (plat_dat->phy_interface) {case PHY_INTERFACE_MODE_RGMII : val &= ~(GMAC1_USE_TXCLK |GMAC1_USE_PWM23 );break ;
@@ -107,12 +107,12 @@ int ls1x_eth_mux_init(struct platform_device *pdev, void *priv)break ;default :pr_err ("unsupported mii mode %d\n" , - plat_dat->interface); + plat_dat->phy_interface);return -ENOTSUPP ; } val &= ~GMAC1_SHUT ; }else { -switch (plat_dat->interface) { +switch (plat_dat->phy_interface) {case PHY_INTERFACE_MODE_RGMII : val &= ~(GMAC0_USE_TXCLK |GMAC0_USE_PWM01 );break ;
@@ -121,7 +121,7 @@ int ls1x_eth_mux_init(struct platform_device *pdev, void *priv)break ;default :pr_err ("unsupported mii mode %d\n" , - plat_dat->interface); + plat_dat->phy_interface);return -ENOTSUPP ; } val &= ~GMAC0_SHUT ;
@@ -131,7 +131,7 @@ int ls1x_eth_mux_init(struct platform_device *pdev, void *priv) plat_dat =dev_get_platdata (&pdev->dev); val &= ~PHY_INTF_SELI ; -if (plat_dat->interface ==PHY_INTERFACE_MODE_RMII ) +if (plat_dat->phy_interface ==PHY_INTERFACE_MODE_RMII ) val |=0x4 <<PHY_INTF_SELI_SHIFT ;__raw_writel (val,LS1X_MUX_CTRL1 );
@@ -146,9 +146,9 @@ static struct plat_stmmacenet_data ls1x_eth0_pdata = { .bus_id = 0, .phy_addr = -1,#if defined(CONFIG_LOONGSON1_LS1B ) - .interface = PHY_INTERFACE_MODE_MII, + .phy_interface = PHY_INTERFACE_MODE_MII,#elif defined(CONFIG_LOONGSON1_LS1C ) - .interface = PHY_INTERFACE_MODE_RMII, + .phy_interface = PHY_INTERFACE_MODE_RMII, #endif .mdio_bus_data = &ls1x_mdio_bus_data, .dma_cfg = &ls1x_eth_dma_cfg,
@@ -186,7 +186,7 @@ struct platform_device ls1x_eth0_pdev = {static struct plat_stmmacenet_data ls1x_eth1_pdata = { .bus_id =1 , .phy_addr =-1 , - .interface =PHY_INTERFACE_MODE_MII , + .phy_interface =PHY_INTERFACE_MODE_MII , .mdio_bus_data = &ls1x_mdio_bus_data, .dma_cfg = &ls1x_eth_dma_cfg, .has_gmac =1 ,
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 84/141 iavf: Fix bad page state
In reply to Greg Kroah-HartmanFrom: Norbert Zulinski <[email protected]>
[ Upstream commit 66039eb9015eee4f7ff0c99b83c65c7ecb3c8190 ]
Fix bad page state, free inappropriate page in handling dummy descriptor. iavf_build_skb now has to check not only if rx_buffer is NULL but also if size is zero, same thing in iavf_clean_rx_irq. Without this patch driver would free page that will be used by napi_build_skb.
--- drivers/net/ethernet/intel/iavf/iavf_txrx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/intel/iavf/iavf_txrx.c +2 -2
@@ -1371,7 +1371,7 @@ static struct sk_buff *iavf_build_skb(struct iavf_ring *rx_ring,#endif struct sk_buff *skb; -if (!rx_buffer) +if (!rx_buffer || !size)return NULL ;/* prefetch first cache line of first page */ va =page_address (rx_buffer->page) + rx_buffer->page_offset;
@@ -1529,7 +1529,7 @@ static int iavf_clean_rx_irq(struct iavf_ring *rx_ring, int budget)/* exit if we failed to retrieve a buffer */ if (!skb) { rx_ring->rx_stats.alloc_buff_failed++; -if (rx_buffer) +if (rx_buffer && size) rx_buffer->pagecnt_bias++;break ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 85/141 iavf: Fix set max MTU size with port VLAN and jumbo frames
In reply to Greg Kroah-HartmanFrom: Michal Jaron <[email protected]>
[ Upstream commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef ]
After setting port VLAN and MTU to 9000 on VF with ice driver there was an iavf error
"PF returned error -5 (IAVF_ERR_PARAM) to our request 6".
During queue configuration, VF's max packet size was set to IAVF_MAX_RXBUFFER but on ice max frame size was smaller by VLAN_HLEN due to making some space for port VLAN as VF is not aware whether it's in a port VLAN. This mismatch in sizes caused ice to reject queue configuration with ERR_PARAM error. Proper max_mtu is sent from ice PF to VF with GET_VF_RESOURCES msg but VF does not look at this.
In iavf change max_frame from IAVF_MAX_RXBUFFER to max_mtu received from pf with GET_VF_RESOURCES msg to make vf's max_frame_size dependent from pf. Add check if received max_mtu is not in eligible range then set it to IAVF_MAX_RXBUFFER.
--- drivers/net/ethernet/intel/iavf/iavf_virtchnl.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/net/ethernet/intel/iavf/iavf_virtchnl.c +5 -2
@@ -241,11 +241,14 @@ int iavf_get_vf_config(struct iavf_adapter *adapter)void iavf_configure_queues (struct iavf_adapter *adapter) {struct virtchnl_vsi_queue_config_info *vqci; -struct virtchnl_queue_pair_info *vqpi; +int i, max_frame = adapter->vf_res->max_mtu;int pairs = adapter->num_active_queues; -int i, max_frame =IAVF_MAX_RXBUFFER ; +struct virtchnl_queue_pair_info *vqpi;size_t len; +if (max_frame >IAVF_MAX_RXBUFFER || !max_frame) + max_frame =IAVF_MAX_RXBUFFER ; +if (adapter->current_op !=VIRTCHNL_OP_UNKNOWN ) {/* bail because we already have a command pending */ dev_err(&adapter->pdev->dev, "Cannot configure queues, command %d pending\n",
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 86/141 i40e: Fix VF set max MTU size
In reply to Greg Kroah-HartmanFrom: Michal Jaron <[email protected]>
[ Upstream commit 372539def2824c43b6afe2403045b140f65c5acc ]
Max MTU sent to VF is set to 0 during memory allocation. It cause that max MTU on VF is changed to IAVF_MAX_RXBUFFER and does not depend on data from HW.
Set max_mtu field in virtchnl_vf_resource struct to inform VF in GET_VF_RESOURCES msg what size should be max frame.
--- .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+)
drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c +20 -0
@@ -1985,6 +1985,25 @@ static void i40e_del_qch(struct i40e_vf *vf) } } +/** +* i40e_vc_get_max_frame_size +* @vf: pointer to the VF +* +* Max frame size is determined based on the current port's max frame size and +* whether a port VLAN is configured on this VF. The VF is not aware whether +* it's in a port VLAN so the PF needs to account for this in max frame size +* checks and sending the max frame size to the VF. +**/ +static u16 i40e_vc_get_max_frame_size (struct i40e_vf *vf) +{ +u16 max_frame_size = vf->pf->hw.phy.link_info.max_frame_size; + +if (vf->port_vlan_id) + max_frame_size -=VLAN_HLEN ; + +return max_frame_size; +} +/** * i40e_vc_get_vf_resources_msg * @vf: pointer to the VF info
@@ -2085,6 +2104,7 @@ static int i40e_vc_get_vf_resources_msg(struct i40e_vf *vf, u8 *msg) vfres->max_vectors = pf->hw.func_caps.num_msix_vectors_vf; vfres->rss_key_size =I40E_HKEY_ARRAY_SIZE ; vfres->rss_lut_size =I40E_VF_HLUT_ARRAY_SIZE ; + vfres->max_mtu =i40e_vc_get_max_frame_size (vf);if (vf->lan_vsi_idx) { vfres->vsi_res[0 ].vsi_id = vf->lan_vsi_id;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 87/141 i40e: Fix set max_tx_rate when it is lower than 1 Mbps
In reply to Greg Kroah-HartmanFrom: Michal Jaron <[email protected]>
[ Upstream commit 198eb7e1b81d8ba676d0f4f120c092032ae69a8e ]
While converting max_tx_rate from bytes to Mbps, this value was set to 0, if the original value was lower than 125000 bytes (1 Mbps). This would cause no transmission rate limiting to occur. This happened due to lack of check of max_tx_rate against the 1 Mbps value for max_tx_rate and the following division by 125000. Fix this issue by adding a helper i40e_bw_bytes_to_mbits() which sets max_tx_rate to minimum usable value of 50 Mbps, if its value is less than 1 Mbps, otherwise do the required conversion by dividing by 125000.
--- drivers/net/ethernet/intel/i40e/i40e_main.c | 32 +++++++++++++++++---- 1 file changed, 26 insertions(+), 6 deletions(-)
drivers/net/ethernet/intel/i40e/i40e_main.c +26 -6
@@ -5733,6 +5733,26 @@ static int i40e_get_link_speed(struct i40e_vsi *vsi) } } +/** +* i40e_bw_bytes_to_mbits - Convert max_tx_rate from bytes to mbits +* @vsi: Pointer to vsi structure +* @max_tx_rate: max TX rate in bytes to be converted into Mbits +* +* Helper function to convert units before send to set BW limit +**/ +static u64 i40e_bw_bytes_to_mbits (struct i40e_vsi *vsi,u64 max_tx_rate) +{ +if (max_tx_rate <I40E_BW_MBPS_DIVISOR ) { +dev_warn (&vsi->back->pdev->dev, +"Setting max tx rate to minimum usable value of 50Mbps.\n" ); + max_tx_rate =I40E_BW_CREDIT_DIVISOR ; + }else { +do_div (max_tx_rate,I40E_BW_MBPS_DIVISOR ); + } + +return max_tx_rate; +} +/** * i40e_set_bw_limit - setup BW limit for Tx traffic based on max_tx_rate * @vsi: VSI to be configured
@@ -5755,10 +5775,10 @@ int i40e_set_bw_limit(struct i40e_vsi *vsi, u16 seid, u64 max_tx_rate) max_tx_rate, seid);return -EINVAL ; } -if (max_tx_rate && max_tx_rate <50 ) { +if (max_tx_rate && max_tx_rate <I40E_BW_CREDIT_DIVISOR ) {dev_warn (&pf->pdev->dev,"Setting max tx rate to minimum usable value of 50Mbps.\n" ); - max_tx_rate =50 ; + max_tx_rate =I40E_BW_CREDIT_DIVISOR ; }/* Tx rate credits are in values of 50Mbps, 0 is disabled */
@@ -7719,9 +7739,9 @@ static int i40e_setup_tc(struct net_device *netdev, void *type_data)if (pf->flags &I40E_FLAG_TC_MQPRIO ) {if (vsi->mqprio_qopt.max_rate[0 ]) { -u64 max_tx_rate = vsi->mqprio_qopt.max_rate[0 ]; +u64 max_tx_rate =i40e_bw_bytes_to_mbits (vsi, + vsi->mqprio_qopt.max_rate[0 ]); -do_div (max_tx_rate,I40E_BW_MBPS_DIVISOR ); ret =i40e_set_bw_limit (vsi, vsi->seid, max_tx_rate);if (!ret) {u64 credits = max_tx_rate;
@@ -10366,10 +10386,10 @@ static void i40e_rebuild(struct i40e_pf *pf, bool reinit, bool lock_acquired) }if (vsi->mqprio_qopt.max_rate[0 ]) { -u64 max_tx_rate = vsi->mqprio_qopt.max_rate[0 ]; +u64 max_tx_rate =i40e_bw_bytes_to_mbits (vsi, + vsi->mqprio_qopt.max_rate[0 ]);u64 credits =0 ; -do_div (max_tx_rate,I40E_BW_MBPS_DIVISOR ); ret =i40e_set_bw_limit (vsi, vsi->seid, max_tx_rate);if (ret) goto end_unlock;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 88/141 sfc: fix TX channel offset when using legacy interrupts
In reply to Greg Kroah-HartmanFrom: Íñigo Huguet <[email protected]>
[ Upstream commit f232af4295653afa4ade3230462b3be15ad16419 ]
In legacy interrupt mode the tx_channel_offset was hardcoded to 1, but that's not correct if efx_sepparate_tx_channels is false. In that case, the offset is 0 because the tx queues are in the single existing channel at index 0, together with the rx queue.
Without this fix, as soon as you try to send any traffic, it tries to get the tx queues from an uninitialized channel getting these errors:
WARNING: CPU: 1 PID: 0 at drivers/net/ethernet/sfc/tx.c:540 efx_hard_start_xmit+0x12e/0x170 [sfc] [...] RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc] [...] Call Trace: <IRQ> dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc] [...] Call Trace: <IRQ> dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...]
--- drivers/net/ethernet/sfc/efx_channels.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/sfc/efx_channels.c +1 -1
@@ -308,7 +308,7 @@ int efx_probe_interrupts(struct efx_nic *efx) efx->n_channels =1 + (efx_separate_tx_channels ?1 :0 ); efx->n_rx_channels =1 ; efx->n_tx_channels =1 ; - efx->tx_channel_offset =1 ; + efx->tx_channel_offset = efx_separate_tx_channels ?1 :0 ; efx->n_xdp_channels =0 ; efx->xdp_channel_offset = efx->n_channels; efx->legacy_irq = efx->pci_dev->irq;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 89/141 sfc: fix null pointer dereference in efx_hard_start_xmit
In reply to Greg Kroah-HartmanFrom: Íñigo Huguet <[email protected]>
[ Upstream commit 0a242eb2913a4aa3d6fbdb86559f27628e9466f3 ]
Trying to get the channel from the tx_queue variable here is wrong because we can only be here if tx_queue is NULL, so we shouldn't dereference it. As the above comment in the code says, this is very unlikely to happen, but it's wrong anyway so let's fix it.
I hit this issue because of a different bug that caused tx_queue to be NULL. If that happens, this is the error message that we get here:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc]
--- drivers/net/ethernet/sfc/tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/sfc/tx.c +1 -1
@@ -545,7 +545,7 @@ netdev_tx_t efx_hard_start_xmit(struct sk_buff *skb,* previous packets out. */ if (!netdev_xmit_more ()) -efx_tx_send_pending (tx_queue->channel); +efx_tx_send_pending (efx_get_tx_channel (efx, index));return NETDEV_TX_OK ; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 90/141 drm/hisilicon/hibmc: Allow to be built if COMPILE_TEST is enabled
In reply to Greg Kroah-HartmanFrom: Javier Martinez Canillas <[email protected]>
[ Upstream commit a0f25a6bb319aa05e04dcf51707c97c2881b4f47 ]
The commit feeb07d0ca5a ("drm/hisilicon/hibmc: Make CONFIG_DRM_HISI_HIBMC depend on ARM64") made the driver Kconfig symbol to depend on ARM64 since it only supports that architecture and loading the module on others would lead to incorrect video modes being used.
But it also prevented the driver to be built on other architectures which is useful to have compile test coverage when doing subsystem wide changes.
Make the dependency instead to be (ARM64 || COMPILE_TEST), so the driver is buildable when the CONFIG_COMPILE_TEST option is enabled.
Stable-dep-of: d8a79c030549 ("drm/hisilicon: Add depends on MMU")
--- drivers/gpu/drm/hisilicon/hibmc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/hisilicon/hibmc/Kconfig +1 -1
@@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0-only config DRM_HISI_HIBMC tristate "DRM Support for Hisilicon Hibmc" - depends on DRM && PCI && ARM64 + depends on DRM && PCI && (ARM64 || COMPILE_TEST) select DRM_KMS_HELPER select DRM_VRAM_HELPER select DRM_TTM
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 91/141 drm/hisilicon: Add depends on MMU
In reply to Greg Kroah-HartmanFrom: Randy Dunlap <[email protected]>
[ Upstream commit d8a79c03054911c375a2252627a429c9bc4615b6 ]
The Kconfig symbol depended on MMU but was dropped by the commit acad3fe650a5 ("drm/hisilicon: Removed the dependency on the mmu") because it already had as a dependency ARM64 that already selects MMU.
But later, commit a0f25a6bb319 ("drm/hisilicon/hibmc: Allow to be built if COMPILE_TEST is enabled") allowed the driver to be built for non-ARM64 when COMPILE_TEST is set but that could lead to unmet direct dependencies and linking errors.
Prevent a kconfig warning when MMU is not enabled by making DRM_HISI_HIBMC depend on MMU.
WARNING: unmet direct dependencies detected for DRM_TTM
Depends on [n]: HAS_IOMEM [=y] && DRM [=m] && MMU [=n]
Selected by [m]:
- DRM_TTM_HELPER [=m] && HAS_IOMEM [=y] && DRM [=m]
- DRM_HISI_HIBMC [=m] && HAS_IOMEM [=y] && DRM [=m] && PCI [=y] && (ARM64 || COMPILE_TEST [=y])
--- drivers/gpu/drm/hisilicon/hibmc/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/hisilicon/hibmc/Kconfig +1 -0
@@ -2,6 +2,7 @@ config DRM_HISI_HIBMC tristate "DRM Support for Hisilicon Hibmc" depends on DRM && PCI && (ARM64 || COMPILE_TEST) + depends on MMU select DRM_KMS_HELPER select DRM_VRAM_HELPER select DRM_TTM
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 92/141 of: mdio: Add of_node_put() when breaking out of for_each_xx
In reply to Greg Kroah-HartmanFrom: Liang He <[email protected]>
[ Upstream commit 1c48709e6d9d353acaaac1d8e33474756b121d78 ]
In of_mdiobus_register(), we should call of_node_put() for 'child' escaped out of for_each_available_child_of_node().
--- drivers/net/mdio/of_mdio.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/mdio/of_mdio.c +1 -0
@@ -332,6 +332,7 @@ int of_mdiobus_register(struct mii_bus *mdio, struct device_node *np)return 0 ; unregister: +of_node_put (child);mdiobus_unregister (mdio);return rc; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 93/141 net: ipa: fix assumptions about DMA address size
In reply to Greg Kroah-HartmanFrom: Alex Elder <[email protected]>
[ Upstream commit d2fd2311de909a7f4e99b4bd11a19e6b671d6a6b ]
Some build time checks in ipa_table_validate_build() assume that a DMA address is 64 bits wide. That is more restrictive than it has to be. A route or filter table is 64 bits wide no matter what the size of a DMA address is on the AP. The code actually uses a pointer to __le64 to access table entries, and a fixed constant IPA_TABLE_ENTRY_SIZE to describe the size of those entries.
Loosen up two checks so they still verify some requirements, but such that they do not assume the size of a DMA address is 64 bits.
Stable-dep-of: cf412ec33325 ("net: ipa: properly limit modem routing table use")
--- drivers/net/ipa/ipa_table.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-)
drivers/net/ipa/ipa_table.c +8 -6
@@ -126,13 +126,15 @@ static void ipa_table_validate_build(void)*/ BUILD_BUG_ON (ARCH_DMA_MINALIGN %IPA_TABLE_ALIGN ); -/* Filter and route tables contain DMA addresses that refer to -* filter or route rules. We use a fixed constant to represent -* the size of either type of table entry. Code in ipa_table_init() -* uses a pointer to __le64 to initialize table entriews. +/* Filter and route tables contain DMA addresses that refer +* to filter or route rules. But the size of a table entry +* is 64 bits regardless of what the size of an AP DMA address +* is. A fixed constant defines the size of an entry, and +* code in ipa_table_init() uses a pointer to __le64 to +* initialize tables. */ -BUILD_BUG_ON (IPA_TABLE_ENTRY_SIZE !=sizeof (dma_addr_t)); -BUILD_BUG_ON (sizeof (dma_addr_t) !=sizeof (__le64)); +BUILD_BUG_ON (sizeof (dma_addr_t) >IPA_TABLE_ENTRY_SIZE ); +BUILD_BUG_ON (sizeof (__le64) !=IPA_TABLE_ENTRY_SIZE );/* A "zero rule" is used to represent no filtering or no routing. * It is a 64-bit block of zeroed memory. Code in ipa_table_init()
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 94/141 net: ipa: fix table alignment requirement
In reply to Greg Kroah-HartmanFrom: Alex Elder <[email protected]>
[ Upstream commit e5d4e96b44cf20330c970c3e30ea0a8c3a23feca ]
We currently have a build-time check to ensure that the minimum DMA allocation alignment satisfies the constraint that IPA filter and route tables must point to rules that are 128-byte aligned.
But what's really important is that the actual allocated DMA memory has that alignment, even if the minimum is smaller than that.
Remove the BUILD_BUG_ON() call checking against minimim DMA alignment and instead verify at rutime that the allocated memory is properly aligned.
Stable-dep-of: cf412ec33325 ("net: ipa: properly limit modem routing table use")
--- drivers/net/ipa/ipa_table.c | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-)
drivers/net/ipa/ipa_table.c +12 -8
@@ -118,14 +118,6 @@/* Check things that can be validated at build time. */ static void ipa_table_validate_build (void ) { -/* IPA hardware accesses memory 128 bytes at a time. Addresses -* referred to by entries in filter and route tables must be -* aligned on 128-byte byte boundaries. The only rule address -* ever use is the "zero rule", and it's aligned at the base -* of a coherent DMA allocation. -*/ -BUILD_BUG_ON (ARCH_DMA_MINALIGN %IPA_TABLE_ALIGN ); -/* Filter and route tables contain DMA addresses that refer * to filter or route rules. But the size of a table entry * is 64 bits regardless of what the size of an AP DMA address
@@ -669,6 +661,18 @@ int ipa_table_init(struct ipa *ipa)if (!virt)return -ENOMEM ; +/* We put the "zero rule" at the base of our table area. The IPA +* hardware requires rules to be aligned on a 128-byte boundary. +* Make sure the allocation satisfies this constraint. +*/ +if (addr %IPA_TABLE_ALIGN ) { +dev_err (dev,"table address %pad not %u-byte aligned\n" , + &addr,IPA_TABLE_ALIGN ); +dma_free_coherent (dev, size, virt, addr); + +return -ERANGE ; + } + ipa->table_virt = virt; ipa->table_addr = addr;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 95/141 net: ipa: avoid 64-bit modulus
In reply to Greg Kroah-HartmanFrom: Alex Elder <[email protected]>
[ Upstream commit 437c78f976f5b39fc4b2a1c65903a229f55912dd ]
It is possible for a 32 bit x86 build to use a 64 bit DMA address.
There are two remaining spots where the IPA driver does a modulo operation to check alignment of a DMA address, and under certain conditions this can lead to a build error on i386 (at least).
The alignment checks we're doing are for power-of-2 values, and this means the lower 32 bits of the DMA address can be used. This ensures both operands to the modulo operator are 32 bits wide.
Stable-dep-of: cf412ec33325 ("net: ipa: properly limit modem routing table use")
--- drivers/net/ipa/gsi.c | 11 +++++++---- drivers/net/ipa/ipa_table.c | 9 ++++++--- 2 files changed, 13 insertions(+), 7 deletions(-)
drivers/net/ipa/gsi.c +7 -4
@@ -1251,15 +1251,18 @@ static void gsi_evt_ring_rx_update(struct gsi_evt_ring *evt_ring, u32 index)/* Initialize a ring, including allocating DMA memory for its entries */ static int gsi_ring_alloc (struct gsi *gsi,struct gsi_ring *ring,u32 count) { -size_t size = count *GSI_RING_ELEMENT_SIZE ; +u32 size = count *GSI_RING_ELEMENT_SIZE ;struct device *dev = gsi->dev;dma_addr_t addr; -/* Hardware requires a 2^n ring size, with alignment equal to size */ +/* Hardware requires a 2^n ring size, with alignment equal to size. +* The size is a power of 2, so we can check alignment using just +* the bottom 32 bits for a DMA address of any size. +*/ ring->virt =dma_alloc_coherent (dev, size, &addr,GFP_KERNEL ); -if (ring->virt && addr % size) { +if (ring->virt &&lower_32_bits (addr) % size) {dma_free_coherent (dev, size, ring->virt, addr); -dev_err (dev,"unable to alloc 0x%zx-aligned ring buffer\n" , +dev_err (dev,"unable to alloc 0x%x-aligned ring buffer\n" , size);return -EINVAL ;/* Not a good error value, but distinct */ }else if (!ring->virt) {
drivers/net/ipa/ipa_table.c +6 -3
@@ -662,10 +662,13 @@ int ipa_table_init(struct ipa *ipa)return -ENOMEM ;/* We put the "zero rule" at the base of our table area. The IPA -* hardware requires rules to be aligned on a 128-byte boundary. -* Make sure the allocation satisfies this constraint. +* hardware requires route and filter table rules to be aligned +* on a 128-byte boundary. As long as the alignment constraint +* is a power of 2, we can check alignment using just the bottom +* 32 bits for a DMA address of any size. */ -if (addr %IPA_TABLE_ALIGN ) { +BUILD_BUG_ON (!is_power_of_2 (IPA_TABLE_ALIGN )); +if (lower_32_bits (addr) %IPA_TABLE_ALIGN ) {dev_err (dev,"table address %pad not %u-byte aligned\n" , &addr,IPA_TABLE_ALIGN );dma_free_coherent (dev, size, virt, addr);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 96/141 net: ipa: DMA addresses are nicely aligned
In reply to Greg Kroah-HartmanFrom: Alex Elder <[email protected]>
[ Upstream commit 19aaf72c0c7a26ab7ffc655a6d84da6a379f899b ]
A recent patch avoided doing 64-bit modulo operations by checking the alignment of some DMA allocations using only the lower 32 bits of the address.
David Laight pointed out (after the fix was committed) that DMA allocations might already satisfy the alignment requirements. And he was right.
Remove the alignment checks that occur after DMA allocation requests, and update comments to explain why the constraint is satisfied. The only place IPA_TABLE_ALIGN was used was to check the alignment; it is therefore no longer needed, so get rid of it.
Add comments where GSI_RING_ELEMENT_SIZE and the tre_count and event_count channel data fields are defined to make explicit they are required to be powers of 2.
Revise a comment in gsi_trans_pool_init_dma(), taking into account that dma_alloc_coherent() guarantees its result is aligned to a page size (or order thereof).
Don't bother printing an error if a DMA allocation fails.
Stable-dep-of: cf412ec33325 ("net: ipa: properly limit modem routing table use")
--- drivers/net/ipa/gsi.c | 13 ++++--------- drivers/net/ipa/gsi_private.h | 2 +- drivers/net/ipa/gsi_trans.c | 9 ++++----- drivers/net/ipa/ipa_data.h | 4 ++-- drivers/net/ipa/ipa_table.c | 24 ++++++------------------ 5 files changed, 17 insertions(+), 35 deletions(-)
drivers/net/ipa/gsi.c +4 -9
@@ -1256,18 +1256,13 @@ static int gsi_ring_alloc(struct gsi *gsi, struct gsi_ring *ring, u32 count)dma_addr_t addr;/* Hardware requires a 2^n ring size, with alignment equal to size. -* The size is a power of 2, so we can check alignment using just -* the bottom 32 bits for a DMA address of any size. +* The DMA address returned by dma_alloc_coherent() is guaranteed to +* be a power-of-2 number of pages, which satisfies the requirement. */ ring->virt =dma_alloc_coherent (dev, size, &addr,GFP_KERNEL ); -if (ring->virt &&lower_32_bits (addr) % size) { -dma_free_coherent (dev, size, ring->virt, addr); -dev_err (dev,"unable to alloc 0x%x-aligned ring buffer\n" , - size); -return -EINVAL ;/* Not a good error value, but distinct */ - }else if (!ring->virt) { +if (!ring->virt)return -ENOMEM ; - } + ring->addr = addr; ring->count = count;
drivers/net/ipa/gsi_private.h +1 -1
@@ -14,7 +14,7 @@ struct gsi_trans;struct gsi_ring ;struct gsi_channel ; -#define GSI_RING_ELEMENT_SIZE 16/* bytes */ +#define GSI_RING_ELEMENT_SIZE 16/* bytes; must be a power of 2 */ /* Return the entry that follows one provided in a transaction pool */ void *gsi_trans_pool_next (struct gsi_trans_pool *pool,void *element);
drivers/net/ipa/gsi_trans.c +4 -5
@@ -153,11 +153,10 @@ int gsi_trans_pool_init_dma(struct device *dev, struct gsi_trans_pool *pool, size =__roundup_pow_of_two (size); total_size = (count + max_alloc -1 ) * size; -/* The allocator will give us a power-of-2 number of pages. But we -* can't guarantee that, so request it. That way we won't waste any -* memory that would be available beyond the required space. -* -* Note that gsi_trans_pool_exit_dma() assumes the total allocated +/* The allocator will give us a power-of-2 number of pages +* sufficient to satisfy our request. Round up our requested +* size to avoid any unused space in the allocation. This way +* gsi_trans_pool_exit_dma() can assume the total allocated * size is exactly (count * size). */ total_size =get_order (total_size) <<PAGE_SHIFT ;
drivers/net/ipa/ipa_data.h +2 -2
@@ -72,8 +72,8 @@* that can be included in a single transaction. */ struct gsi_channel_data { -u16 tre_count; -u16 event_count; +u16 tre_count;/* must be a power of 2 */ +u16 event_count;/* must be a power of 2 */ u8 tlv_count; };
drivers/net/ipa/ipa_table.c +6 -18
@@ -96,9 +96,6 @@* ---------------------- */ -/* IPA hardware constrains filter and route tables alignment */ -#define IPA_TABLE_ALIGN 128/* Minimum table alignment */ -/* Assignment of route table entries to the modem and AP */ #define IPA_ROUTE_MODEM_MIN 0#define IPA_ROUTE_MODEM_COUNT 8
@@ -656,26 +653,17 @@ int ipa_table_init(struct ipa *ipa)ipa_table_validate_build (); +/* The IPA hardware requires route and filter table rules to be +* aligned on a 128-byte boundary. We put the "zero rule" at the +* base of the table area allocated here. The DMA address returned +* by dma_alloc_coherent() is guaranteed to be a power-of-2 number +* of pages, which satisfies the rule alignment requirement. +*/ size =IPA_ZERO_RULE_SIZE + (1 + count) *IPA_TABLE_ENTRY_SIZE ; virt =dma_alloc_coherent (dev, size, &addr,GFP_KERNEL );if (!virt)return -ENOMEM ; -/* We put the "zero rule" at the base of our table area. The IPA -* hardware requires route and filter table rules to be aligned -* on a 128-byte boundary. As long as the alignment constraint -* is a power of 2, we can check alignment using just the bottom -* 32 bits for a DMA address of any size. -*/ -BUILD_BUG_ON (!is_power_of_2 (IPA_TABLE_ALIGN )); -if (lower_32_bits (addr) %IPA_TABLE_ALIGN ) { -dev_err (dev,"table address %pad not %u-byte aligned\n" , - &addr,IPA_TABLE_ALIGN ); -dma_free_coherent (dev, size, virt, addr); - -return -ERANGE ; - } - ipa->table_virt = virt; ipa->table_addr = addr;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 97/141 net: ipa: kill IPA_TABLE_ENTRY_SIZE
In reply to Greg Kroah-HartmanFrom: Alex Elder <[email protected]>
[ Upstream commit 4ea29143ebe6c453f5fddc80ffe4ed046f44aa3a ]
Entries in an IPA route or filter table are 64-bit little-endian addresses, each of which refers to a routing or filtering rule.
The format of these table slots are fixed, but IPA_TABLE_ENTRY_SIZE is used to define their size. This symbol doesn't really add value, and I think it unnecessarily obscures what a table entry *is*.
So get rid of IPA_TABLE_ENTRY_SIZE, and just use sizeof(__le64) in its place throughout the code.
Update the comments in "ipa_table.c" to provide a little better explanation of these table slots.
Stable-dep-of: cf412ec33325 ("net: ipa: properly limit modem routing table use")
--- drivers/net/ipa/ipa_cmd.c | 2 +- drivers/net/ipa/ipa_qmi.c | 10 +++---- drivers/net/ipa/ipa_table.c | 59 +++++++++++++++++++++---------------- drivers/net/ipa/ipa_table.h | 3 -- 4 files changed, 39 insertions(+), 35 deletions(-)
drivers/net/ipa/ipa_cmd.c +1 -1
@@ -154,7 +154,7 @@ static void ipa_cmd_validate_build(void)* of entries, as and IPv4 and IPv6 route tables have the same number * of entries. */ -#define TABLE_SIZE (TABLE_COUNT_MAX * IPA_TABLE_ENTRY_SIZE) +#define TABLE_SIZE (TABLE_COUNT_MAX * sizeof(__le64))#define TABLE_COUNT_MAX max_t(u32, IPA_ROUTE_COUNT_MAX, IPA_FILTER_COUNT_MAX)BUILD_BUG_ON (TABLE_SIZE >field_max (IP_FLTRT_FLAGS_HASH_SIZE_FMASK ));BUILD_BUG_ON (TABLE_SIZE >field_max (IP_FLTRT_FLAGS_NHASH_SIZE_FMASK ));
drivers/net/ipa/ipa_qmi.c +4 -6
@@ -308,12 +308,12 @@ init_modem_driver_req(struct ipa_qmi *ipa_qmi) mem = &ipa->mem[IPA_MEM_V4_ROUTE ]; req.v4_route_tbl_info_valid =1 ; req.v4_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v4_route_tbl_info.count = mem->size /IPA_TABLE_ENTRY_SIZE ; + req.v4_route_tbl_info.count = mem->size /sizeof (__le64); mem = &ipa->mem[IPA_MEM_V6_ROUTE ]; req.v6_route_tbl_info_valid =1 ; req.v6_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v6_route_tbl_info.count = mem->size /IPA_TABLE_ENTRY_SIZE ; + req.v6_route_tbl_info.count = mem->size /sizeof (__le64); mem = &ipa->mem[IPA_MEM_V4_FILTER ]; req.v4_filter_tbl_start_valid =1 ;
@@ -352,8 +352,7 @@ init_modem_driver_req(struct ipa_qmi *ipa_qmi) req.v4_hash_route_tbl_info_valid =1 ; req.v4_hash_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v4_hash_route_tbl_info.count = - mem->size /IPA_TABLE_ENTRY_SIZE ; + req.v4_hash_route_tbl_info.count = mem->size /sizeof (__le64); } mem = &ipa->mem[IPA_MEM_V6_ROUTE_HASHED ];
@@ -361,8 +360,7 @@ init_modem_driver_req(struct ipa_qmi *ipa_qmi) req.v6_hash_route_tbl_info_valid =1 ; req.v6_hash_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v6_hash_route_tbl_info.count = - mem->size /IPA_TABLE_ENTRY_SIZE ; + req.v6_hash_route_tbl_info.count = mem->size /sizeof (__le64); } mem = &ipa->mem[IPA_MEM_V4_FILTER_HASHED ];
drivers/net/ipa/ipa_table.c +34 -25
117 lines not on this page · raw message
drivers/net/ipa/ipa_table.h +0 -3
@@ -10,9 +10,6 @@struct ipa ; -/* The size of a filter or route table entry */ -#define IPA_TABLE_ENTRY_SIZE sizeof(__le64)/* Holds a physical address */ -/* The maximum number of filter table entries (IPv4, IPv6; hashed or not) */ #define IPA_FILTER_COUNT_MAX 14
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 98/141 net: ipa: properly limit modem routing table use
In reply to Greg Kroah-HartmanFrom: Alex Elder <[email protected]>
[ Upstream commit cf412ec333250cb82bafe57169204e14a9f1c2ac ]
IPA can route packets between IPA-connected entities. The AP and modem are currently the only such entities supported, and no routing is required to transfer packets between them.
The number of entries in each routing table is fixed, and defined at initialization time. Some of these entries are designated for use by the modem, and the rest are available for the AP to use. The AP sends a QMI message to the modem which describes (among other things) information about routing table memory available for the modem to use.
Currently the QMI initialization packet gives wrong information in its description of routing tables. What *should* be supplied is the maximum index that the modem can use for the routing table memory located at a given location. The current code instead supplies the total *number* of routing table entries. Furthermore, the modem is granted the entire table, not just the subset it's supposed to use.
This patch fixes this. First, the ipa_mem_bounds structure is generalized so its "end" field can be interpreted either as a final byte offset, or a final array index. Second, the IPv4 and IPv6 (non-hashed and hashed) table information fields in the QMI ipa_init_modem_driver_req structure are changed to be ipa_mem_bounds rather than ipa_mem_array structures. Third, we set the "end" value for each routing table to be the last index, rather than setting the "count" to be the number of indices. Finally, instead of allowing the modem to use all of a routing table's memory, it is limited to just the portion meant to be used by the modem. In all versions of IPA currently supported, that is IPA_ROUTE_MODEM_COUNT (8) entries.
Update a few comments for clarity.
--- drivers/net/ipa/ipa_qmi.c | 8 ++++---- drivers/net/ipa/ipa_qmi_msg.c | 8 ++++---- drivers/net/ipa/ipa_qmi_msg.h | 37 ++++++++++++++++++++--------------- drivers/net/ipa/ipa_table.c | 2 -- drivers/net/ipa/ipa_table.h | 3 +++ 5 files changed, 32 insertions(+), 26 deletions(-)
drivers/net/ipa/ipa_qmi.c +4 -4
@@ -308,12 +308,12 @@ init_modem_driver_req(struct ipa_qmi *ipa_qmi) mem = &ipa->mem[IPA_MEM_V4_ROUTE ]; req.v4_route_tbl_info_valid =1 ; req.v4_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v4_route_tbl_info.count = mem->size /sizeof (__le64); + req.v4_route_tbl_info.end =IPA_ROUTE_MODEM_COUNT -1 ; mem = &ipa->mem[IPA_MEM_V6_ROUTE ]; req.v6_route_tbl_info_valid =1 ; req.v6_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v6_route_tbl_info.count = mem->size /sizeof (__le64); + req.v6_route_tbl_info.end =IPA_ROUTE_MODEM_COUNT -1 ; mem = &ipa->mem[IPA_MEM_V4_FILTER ]; req.v4_filter_tbl_start_valid =1 ;
@@ -352,7 +352,7 @@ init_modem_driver_req(struct ipa_qmi *ipa_qmi) req.v4_hash_route_tbl_info_valid =1 ; req.v4_hash_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v4_hash_route_tbl_info.count = mem->size /sizeof (__le64); + req.v4_hash_route_tbl_info.end =IPA_ROUTE_MODEM_COUNT -1 ; } mem = &ipa->mem[IPA_MEM_V6_ROUTE_HASHED ];
@@ -360,7 +360,7 @@ init_modem_driver_req(struct ipa_qmi *ipa_qmi) req.v6_hash_route_tbl_info_valid =1 ; req.v6_hash_route_tbl_info.start = ipa->mem_offset + mem->offset; - req.v6_hash_route_tbl_info.count = mem->size /sizeof (__le64); + req.v6_hash_route_tbl_info.end =IPA_ROUTE_MODEM_COUNT -1 ; } mem = &ipa->mem[IPA_MEM_V4_FILTER_HASHED ];
drivers/net/ipa/ipa_qmi_msg.c +4 -4
@@ -271,7 +271,7 @@ struct qmi_elem_info ipa_init_modem_driver_req_ei[] = { .tlv_type = 0x12, .offset = offsetof(struct ipa_init_modem_driver_req, v4_route_tbl_info), - .ei_array = ipa_mem_array_ei, + .ei_array = ipa_mem_bounds_ei, }, { .data_type = QMI_OPT_FLAG,
@@ -292,7 +292,7 @@ struct qmi_elem_info ipa_init_modem_driver_req_ei[] = { .tlv_type = 0x13, .offset = offsetof(struct ipa_init_modem_driver_req, v6_route_tbl_info), - .ei_array = ipa_mem_array_ei, + .ei_array = ipa_mem_bounds_ei, }, { .data_type = QMI_OPT_FLAG,
@@ -456,7 +456,7 @@ struct qmi_elem_info ipa_init_modem_driver_req_ei[] = { .tlv_type = 0x1b, .offset = offsetof(struct ipa_init_modem_driver_req, v4_hash_route_tbl_info), - .ei_array = ipa_mem_array_ei, + .ei_array = ipa_mem_bounds_ei, }, { .data_type = QMI_OPT_FLAG,
@@ -477,7 +477,7 @@ struct qmi_elem_info ipa_init_modem_driver_req_ei[] = { .tlv_type = 0x1c, .offset = offsetof(struct ipa_init_modem_driver_req, v6_hash_route_tbl_info), - .ei_array = ipa_mem_array_ei, + .ei_array = ipa_mem_bounds_ei, }, { .data_type = QMI_OPT_FLAG,
drivers/net/ipa/ipa_qmi_msg.h +21 -16
@@ -82,9 +82,11 @@ enum ipa_platform_type { IPA_QMI_PLATFORM_TYPE_MSM_QNX_V01 = 5, /* QNX MSM */ }; -/* This defines the start and end offset of a range of memory. Both -* fields are offsets relative to the start of IPA shared memory. -* The end value is the last addressable byte *within* the range. +/* This defines the start and end offset of a range of memory. The start +* value is a byte offset relative to the start of IPA shared memory. The +* end value is the last addressable unit *within* the range. Typically +* the end value is in units of bytes, however it can also be a maximum +* array index value. */ struct ipa_mem_bounds {u32 start;
@@ -125,18 +127,19 @@ struct ipa_init_modem_driver_req {u8 hdr_tbl_info_valid;struct ipa_mem_bounds hdr_tbl_info; -/* Routing table information. These define the location and size of -* non-hashable IPv4 and IPv6 filter tables. The start values are -* offsets relative to the start of IPA shared memory. +/* Routing table information. These define the location and maximum +* *index* (not byte) for the modem portion of non-hashable IPv4 and +* IPv6 routing tables. The start values are byte offsets relative +* to the start of IPA shared memory. */ u8 v4_route_tbl_info_valid; -struct ipa_mem_array v4_route_tbl_info; +struct ipa_mem_bounds v4_route_tbl_info;u8 v6_route_tbl_info_valid; -struct ipa_mem_array v6_route_tbl_info; +struct ipa_mem_bounds v6_route_tbl_info;/* Filter table information. These define the location of the * non-hashable IPv4 and IPv6 filter tables. The start values are -* offsets relative to the start of IPA shared memory. +* byte offsets relative to the start of IPA shared memory. */ u8 v4_filter_tbl_start_valid;u32 v4_filter_tbl_start;
@@ -177,18 +180,20 @@ struct ipa_init_modem_driver_req {u8 zip_tbl_info_valid;struct ipa_mem_bounds zip_tbl_info; -/* Routing table information. These define the location and size -* of hashable IPv4 and IPv6 filter tables. The start values are -* offsets relative to the start of IPA shared memory. +/* Routing table information. These define the location and maximum +* *index* (not byte) for the modem portion of hashable IPv4 and IPv6 +* routing tables (if supported by hardware). The start values are +* byte offsets relative to the start of IPA shared memory. */ u8 v4_hash_route_tbl_info_valid; -struct ipa_mem_array v4_hash_route_tbl_info; +struct ipa_mem_bounds v4_hash_route_tbl_info;u8 v6_hash_route_tbl_info_valid; -struct ipa_mem_array v6_hash_route_tbl_info; +struct ipa_mem_bounds v6_hash_route_tbl_info;/* Filter table information. These define the location and size -* of hashable IPv4 and IPv6 filter tables. The start values are -* offsets relative to the start of IPA shared memory. +* of hashable IPv4 and IPv6 filter tables (if supported by hardware). +* The start values are byte offsets relative to the start of IPA +* shared memory. */ u8 v4_hash_filter_tbl_start_valid;u32 v4_hash_filter_tbl_start;
drivers/net/ipa/ipa_table.c +0 -2
@@ -108,8 +108,6 @@/* Assignment of route table entries to the modem and AP */ #define IPA_ROUTE_MODEM_MIN 0 -#define IPA_ROUTE_MODEM_COUNT 8 -#define IPA_ROUTE_AP_MIN IPA_ROUTE_MODEM_COUNT#define IPA_ROUTE_AP_COUNT \ (IPA_ROUTE_COUNT_MAX - IPA_ROUTE_MODEM_COUNT)
drivers/net/ipa/ipa_table.h +3 -0
@@ -13,6 +13,9 @@ struct ipa;/* The maximum number of filter table entries (IPv4, IPv6; hashed or not) */ #define IPA_FILTER_COUNT_MAX 14 +/* The number of route table entries allotted to the modem */ +#define IPA_ROUTE_MODEM_COUNT 8 +/* The maximum number of route table entries (IPv4, IPv6; hashed or not) */ #define IPA_ROUTE_COUNT_MAX 15
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 99/141 wireguard: ratelimiter: disable timings test by default
In reply to Greg Kroah-HartmanFrom: Jason A. Donenfeld <[email protected]>
[ Upstream commit 684dec3cf45da2b0848298efae4adf3b2aeafeda ]
A previous commit tried to make the ratelimiter timings test more reliable but in the process made it less reliable on other configurations. This is an impossible problem to solve without increasingly ridiculous heuristics. And it's not even a problem that actually needs to be solved in any comprehensive way, since this is only ever used during development. So just cordon this off with a DEBUG_ ifdef, just like we do for the trie's randomized tests, so it can be enabled while hacking on the code, and otherwise disabled in CI. In the process we also revert 151c8e499f47.
--- drivers/net/wireguard/selftest/ratelimiter.c | 25 ++++++++------------ 1 file changed, 10 insertions(+), 15 deletions(-)
drivers/net/wireguard/selftest/ratelimiter.c +10 -15
@@ -6,29 +6,28 @@#ifdef DEBUG #include <linux/jiffies.h> -#include <linux/hrtimer.h> static const struct {bool result; -u64 nsec_to_sleep_before; +unsigned int msec_to_sleep_before; } expected_results[]__initconst = { [0 ...PACKETS_BURSTABLE -1 ] = { true,0 }, [PACKETS_BURSTABLE ] = { false,0 }, - [PACKETS_BURSTABLE +1 ] = { true,NSEC_PER_SEC /PACKETS_PER_SECOND }, + [PACKETS_BURSTABLE +1 ] = { true,MSEC_PER_SEC /PACKETS_PER_SECOND }, [PACKETS_BURSTABLE +2 ] = { false,0 }, - [PACKETS_BURSTABLE +3 ] = { true, (NSEC_PER_SEC /PACKETS_PER_SECOND ) *2 }, + [PACKETS_BURSTABLE +3 ] = { true, (MSEC_PER_SEC /PACKETS_PER_SECOND ) *2 }, [PACKETS_BURSTABLE +4 ] = { true,0 }, [PACKETS_BURSTABLE +5 ] = { false,0 } };static __init unsigned int maximum_jiffies_at_index (int index) { -u64 total_nsecs =2 *NSEC_PER_SEC /PACKETS_PER_SECOND /3 ; +unsigned int total_msecs =2 *MSEC_PER_SEC /PACKETS_PER_SECOND /3 ;int i;for (i =0 ; i <= index; ++i) - total_nsecs += expected_results[i].nsec_to_sleep_before; -return nsecs_to_jiffies (total_nsecs); + total_msecs += expected_results[i].msec_to_sleep_before; +return msecs_to_jiffies (total_msecs); } static __init int timings_test(struct sk_buff *skb4, struct iphdr *hdr4,
@@ -43,12 +42,8 @@ static __init int timings_test(struct sk_buff *skb4, struct iphdr *hdr4, loop_start_time = jiffies;for (i =0 ; i <ARRAY_SIZE (expected_results); ++i) { -if (expected_results[i].nsec_to_sleep_before) { -ktime_t timeout =ktime_add (ktime_add_ns (ktime_get_coarse_boottime (),TICK_NSEC *4 /3 ), -ns_to_ktime (expected_results[i].nsec_to_sleep_before)); -set_current_state (TASK_UNINTERRUPTIBLE ); -schedule_hrtimeout_range_clock (&timeout,0 ,HRTIMER_MODE_ABS ,CLOCK_BOOTTIME ); - } +if (expected_results[i].msec_to_sleep_before) +msleep (expected_results[i].msec_to_sleep_before);if (time_is_before_jiffies (loop_start_time +maximum_jiffies_at_index (i)))
@@ -132,7 +127,7 @@ bool __init wg_ratelimiter_selftest(void)if (IS_ENABLED (CONFIG_KASAN ) ||IS_ENABLED (CONFIG_UBSAN ))return true; -BUILD_BUG_ON (NSEC_PER_SEC %PACKETS_PER_SECOND !=0 ); +BUILD_BUG_ON (MSEC_PER_SEC %PACKETS_PER_SECOND !=0 );if (wg_ratelimiter_init ()) goto out;
@@ -172,7 +167,7 @@ bool __init wg_ratelimiter_selftest(void) ++test;#endif -for (trials =TRIALS_BEFORE_GIVING_UP ;;) { +for (trials =TRIALS_BEFORE_GIVING_UP ;IS_ENABLED (DEBUG_RATELIMITER_TIMINGS );) {int test_count =0 , ret; ret =timings_test (skb4, hdr4, skb6, hdr6, &test_count);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 100/141 wireguard: netlink: avoid variable-sized memcpy on sockaddr
In reply to Greg Kroah-HartmanFrom: Jason A. Donenfeld <[email protected]>
[ Upstream commit 26c013108c12b94bc023bf19198a4300596c98b1 ]
Doing a variable-sized memcpy is slower, and the compiler isn't smart enough to turn this into a constant-size assignment.
Further, Kees' latest fortified memcpy will actually bark, because the destination pointer is type sockaddr, not explicitly sockaddr_in or sockaddr_in6, so it thinks there's an overflow:
memcpy: detected field-spanning write (size 28) of single field "&endpoint.addr" at drivers/net/wireguard/netlink.c:446 (size 16)
Fix this by just assigning by using explicit casts for each checked case.
--- drivers/net/wireguard/netlink.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
drivers/net/wireguard/netlink.c +6 -7
@@ -436,14 +436,13 @@ static int set_peer(struct wg_device *wg, struct nlattr **attrs)if (attrs[WGPEER_A_ENDPOINT ]) {struct sockaddr *addr =nla_data (attrs[WGPEER_A_ENDPOINT ]);size_t len =nla_len (attrs[WGPEER_A_ENDPOINT ]); +struct endpoint endpoint = { { {0 } } }; -if ((len ==sizeof (struct sockaddr_in ) && - addr->sa_family ==AF_INET ) || - (len ==sizeof (struct sockaddr_in6 ) && - addr->sa_family ==AF_INET6 )) { -struct endpoint endpoint = { { {0 } } }; - -memcpy (&endpoint.addr, addr, len); +if (len ==sizeof (struct sockaddr_in ) && addr->sa_family ==AF_INET ) { + endpoint.addr4 = *(struct sockaddr_in *)addr; +wg_socket_set_peer_endpoint (peer, &endpoint); + }else if (len ==sizeof (struct sockaddr_in6 ) && addr->sa_family ==AF_INET6 ) { + endpoint.addr6 = *(struct sockaddr_in6 *)addr;wg_socket_set_peer_endpoint (peer, &endpoint); } }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 101/141 net: enetc: move enetc_set_psfp() out of the common enetc_set_features()
In reply to Greg Kroah-HartmanFrom: Vladimir Oltean <[email protected]>
[ Upstream commit fed38e64d9b99d65a36c0dbadc3d3f8ddd9ea030 ]
The VF netdev driver shouldn't respond to changes in the NETIF_F_HW_TC flag; only PFs should. Moreover, TSN-specific code should go to enetc_qos.c, which should not be included in the VF driver.
--- drivers/net/ethernet/freescale/enetc/enetc.c | 32 +------------------ drivers/net/ethernet/freescale/enetc/enetc.h | 9 ++++-- .../net/ethernet/freescale/enetc/enetc_pf.c | 11 ++++++- .../net/ethernet/freescale/enetc/enetc_qos.c | 23 +++++++++++++ .../net/ethernet/freescale/enetc/enetc_vf.c | 4 ++- 5 files changed, 44 insertions(+), 35 deletions(-)
drivers/net/ethernet/freescale/enetc/enetc.c +1 -31
@@ -1671,29 +1671,6 @@ static int enetc_set_rss(struct net_device *ndev, int en)return 0 ; } -static int enetc_set_psfp (struct net_device *ndev,int en) -{ -struct enetc_ndev_priv *priv =netdev_priv (ndev); -int err; - -if (en) { - err =enetc_psfp_enable (priv); -if (err) -return err; - - priv->active_offloads |=ENETC_F_QCI ; -return 0 ; - } - - err =enetc_psfp_disable (priv); -if (err) -return err; - - priv->active_offloads &= ~ENETC_F_QCI ; - -return 0 ; -} -static void enetc_enable_rxvlan (struct net_device *ndev,bool en) {struct enetc_ndev_priv *priv =netdev_priv (ndev);
@@ -1712,11 +1689,9 @@ static void enetc_enable_txvlan(struct net_device *ndev, bool en)enetc_bdr_enable_txvlan (&priv->si->hw, i, en); } -int enetc_set_features (struct net_device *ndev, -netdev_features_t features) +void enetc_set_features (struct net_device *ndev,netdev_features_t features) {netdev_features_t changed = ndev->features ^ features; -int err =0 ;if (changed &NETIF_F_RXHASH )enetc_set_rss (ndev, !!(features &NETIF_F_RXHASH ));
@@ -1728,11 +1703,6 @@ int enetc_set_features(struct net_device *ndev,if (changed &NETIF_F_HW_VLAN_CTAG_TX )enetc_enable_txvlan (ndev, !!(features &NETIF_F_HW_VLAN_CTAG_TX )); - -if (changed &NETIF_F_HW_TC ) - err =enetc_set_psfp (ndev, !!(features &NETIF_F_HW_TC )); - -return err; }#ifdef CONFIG_FSL_ENETC_PTP_CLOCK
drivers/net/ethernet/freescale/enetc/enetc.h +7 -2
@@ -301,8 +301,7 @@ void enetc_start(struct net_device *ndev);void enetc_stop (struct net_device *ndev);netdev_tx_t enetc_xmit (struct sk_buff *skb,struct net_device *ndev);struct net_device_stats *enetc_get_stats (struct net_device *ndev); -int enetc_set_features (struct net_device *ndev, -netdev_features_t features); +void enetc_set_features (struct net_device *ndev,netdev_features_t features);int enetc_ioctl (struct net_device *ndev,struct ifreq *rq,int cmd);int enetc_setup_tc (struct net_device *ndev,enum tc_setup_type type,void *type_data);
@@ -335,6 +334,7 @@ int enetc_setup_tc_block_cb(enum tc_setup_type type, void *type_data,int enetc_setup_tc_psfp (struct net_device *ndev,void *type_data);int enetc_psfp_init (struct enetc_ndev_priv *priv);int enetc_psfp_clean (struct enetc_ndev_priv *priv); +int enetc_set_psfp (struct net_device *ndev,bool en);static inline void enetc_get_max_cap (struct enetc_ndev_priv *priv) {
@@ -410,4 +410,9 @@ static inline int enetc_psfp_disable(struct enetc_ndev_priv *priv) {return 0 ; } + +static inline int enetc_set_psfp (struct net_device *ndev,bool en) +{ +return 0 ; +}#endif
drivers/net/ethernet/freescale/enetc/enetc_pf.c +10 -1
@@ -671,6 +671,13 @@ static int enetc_pf_set_features(struct net_device *ndev, {netdev_features_t changed = ndev->features ^ features;struct enetc_ndev_priv *priv =netdev_priv (ndev); +int err; + +if (changed &NETIF_F_HW_TC ) { + err =enetc_set_psfp (ndev, !!(features &NETIF_F_HW_TC )); +if (err) +return err; + }if (changed &NETIF_F_HW_VLAN_CTAG_FILTER ) {struct enetc_pf *pf =enetc_si_priv (priv->si);
@@ -684,7 +691,9 @@ static int enetc_pf_set_features(struct net_device *ndev,if (changed &NETIF_F_LOOPBACK )enetc_set_loopback (ndev, !!(features &NETIF_F_LOOPBACK )); -return enetc_set_features (ndev, features); +enetc_set_features (ndev, features); + +return 0 ; }static const struct net_device_ops enetc_ndev_ops = {
drivers/net/ethernet/freescale/enetc/enetc_qos.c +23 -0
@@ -1525,6 +1525,29 @@ int enetc_setup_tc_block_cb(enum tc_setup_type type, void *type_data, } } +int enetc_set_psfp (struct net_device *ndev,bool en) +{ +struct enetc_ndev_priv *priv =netdev_priv (ndev); +int err; + +if (en) { + err =enetc_psfp_enable (priv); +if (err) +return err; + + priv->active_offloads |=ENETC_F_QCI ; +return 0 ; + } + + err =enetc_psfp_disable (priv); +if (err) +return err; + + priv->active_offloads &= ~ENETC_F_QCI ; + +return 0 ; +} +int enetc_psfp_init (struct enetc_ndev_priv *priv) {if (epsfp.psfp_sfi_bitmap)
drivers/net/ethernet/freescale/enetc/enetc_vf.c +3 -1
@@ -88,7 +88,9 @@ static int enetc_vf_set_mac_addr(struct net_device *ndev, void *addr)static int enetc_vf_set_features (struct net_device *ndev,netdev_features_t features) { -return enetc_set_features (ndev, features); +enetc_set_features (ndev, features); + +return 0 ; }/* Probing/ Init */
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 102/141 net: socket: remove register_gifconf
In reply to Greg Kroah-HartmanFrom: Arnd Bergmann <[email protected]>
[ Upstream commit b0e99d03778b2418aec20db99d97d19d25d198b6 ]
Since dynamic registration of the gifconf() helper is only used for IPv4, and this can not be in a loadable module, this can be simplified noticeably by turning it into a direct function call as a preparation for cleaning up the compat handling.
Stable-dep-of: 5641c751fe2f ("net: enetc: deny offload of tc-based TSN features on VF interfaces")
--- include/linux/inetdevice.h | 9 ++++++++ include/linux/netdevice.h | 8 ------- net/core/dev_ioctl.c | 43 +++++++++----------------------------- net/ipv4/devinet.c | 4 +--- 4 files changed, 20 insertions(+), 44 deletions(-)
include/linux/inetdevice.h +9 -0
@@ -178,6 +178,15 @@ static inline struct net_device *ip_dev_find(struct net *net, __be32 addr)int inet_addr_onlink (struct in_device *in_dev,__be32 a,__be32 b);int devinet_ioctl (struct net *net,unsigned int cmd,struct ifreq *); +#ifdef CONFIG_INET +int inet_gifconf (struct net_device *dev,char __user *buf,int len,int size); +#else +static inline int inet_gifconf (struct net_device *dev,char __user *buf, +int len,int size) +{ +return 0 ; +} +#endif void devinet_init (void );struct in_device *inetdev_by_index (struct net *,int );__be32 inet_select_addr (const struct net_device *dev,__be32 dst,int scope);
include/linux/netdevice.h +0 -8
@@ -3201,14 +3201,6 @@ static inline bool dev_has_header(const struct net_device *dev)return dev->header_ops && dev->header_ops->create; } -typedef int gifconf_func_t (struct net_device * dev,char __user * bufptr, -int len,int size); -int register_gifconf (unsigned int family,gifconf_func_t *gifconf); -static inline int unregister_gifconf (unsigned int family) -{ -return register_gifconf (family,NULL ); -} -#ifdef CONFIG_NET_FLOW_LIMIT #define FLOW_LIMIT_HISTORY (1 << 7)/* must be ^2 and !overflow buckets */ struct sd_flow_limit {
net/core/dev_ioctl.c +10 -33
61 lines not on this page · raw message
net/ipv4/devinet.c +1 -3
@@ -1244,7 +1244,7 @@ int devinet_ioctl(struct net *net, unsigned int cmd, struct ifreq *ifr)return ret; } -static int inet_gifconf (struct net_device *dev,char __user *buf,int len,int size) +int inet_gifconf (struct net_device *dev,char __user *buf,int len,int size) {struct in_device *in_dev =__in_dev_get_rtnl (dev);const struct in_ifaddr *ifa;
@@ -2766,8 +2766,6 @@ void __init devinet_init(void)INIT_HLIST_HEAD (&inet_addr_lst[i]);register_pernet_subsys (&devinet_ops); - -register_gifconf (PF_INET , inet_gifconf);register_netdevice_notifier (&ip_netdev_notifier);queue_delayed_work (system_power_efficient_wq, &check_lifetime_work,0 );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 103/141 net/sched: taprio: avoid disabling offload when it was never enabled
In reply to Greg Kroah-HartmanFrom: Vladimir Oltean <[email protected]>
[ Upstream commit db46e3a88a09c5cf7e505664d01da7238cd56c92 ]
In an incredibly strange API design decision, qdisc->destroy() gets called even if qdisc->init() never succeeded, not exclusively since commit 87b60cfacf9f ("net_sched: fix error recovery at qdisc creation"), but apparently also earlier (in the case of qdisc_create_dflt()).
The taprio qdisc does not fully acknowledge this when it attempts full offload, because it starts off with q->flags = TAPRIO_FLAGS_INVALID in taprio_init(), then it replaces q->flags with TCA_TAPRIO_ATTR_FLAGS parsed from netlink (in taprio_change(), tail called from taprio_init()).
But in taprio_destroy(), we call taprio_disable_offload(), and this determines what to do based on FULL_OFFLOAD_IS_ENABLED(q->flags).
But looking at the implementation of FULL_OFFLOAD_IS_ENABLED() (a bitwise check of bit 1 in q->flags), it is invalid to call this macro on q->flags when it contains TAPRIO_FLAGS_INVALID, because that is set to U32_MAX, and therefore FULL_OFFLOAD_IS_ENABLED() will return true on an invalid set of flags.
As a result, it is possible to crash the kernel if user space forces an error between setting q->flags = TAPRIO_FLAGS_INVALID, and the calling of taprio_enable_offload(). This is because drivers do not expect the offload to be disabled when it was never enabled.
The error that we force here is to attach taprio as a non-root qdisc, but instead as child of an mqprio root qdisc:
$ tc qdisc add dev swp0 root handle 1: \ mqprio num_tc 8 map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 hw 0 $ tc qdisc replace dev swp0 parent 1:1 \ taprio num_tc 8 map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 base-time 0 \ sched-entry S 0x7f 990000 sched-entry S 0x80 100000 \ flags 0x0 clockid CLOCK_TAI Unable to handle kernel paging request at virtual address fffffffffffffff8 [fffffffffffffff8] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 96000004 [#1] PREEMPT SMP Call trace: taprio_dump+0x27c/0x310 vsc9959_port_setup_tc+0x1f4/0x460 felix_port_setup_tc+0x24/0x3c dsa_slave_setup_tc+0x54/0x27c taprio_disable_offload.isra.0+0x58/0xe0 taprio_destroy+0x80/0x104 qdisc_create+0x240/0x470 tc_modify_qdisc+0x1fc/0x6b0 rtnetlink_rcv_msg+0x12c/0x390 netlink_rcv_skb+0x5c/0x130 rtnetlink_rcv+0x1c/0x2c
Fix this by keeping track of the operations we made, and undo the offload only if we actually did it.
I've added "bool offloaded" inside a 4 byte hole between "int clockid" and "atomic64_t picos_per_byte". Now the first cache line looks like below:
$ pahole -C taprio_sched net/sched/sch_taprio.o
struct taprio_sched {
struct Qdisc * * qdiscs; /* 0 8 */
struct Qdisc * root; /* 8 8 */
u32 flags; /* 16 4 */
enum tk_offsets tk_offset; /* 20 4 */
int clockid; /* 24 4 */
bool offloaded; /* 28 1 *//* XXX 3 bytes hole, try to pack */
atomic64_t picos_per_byte; /* 32 0 */
/* XXX 8 bytes hole, try to pack */
spinlock_t current_entry_lock; /* 40 0 */
/* XXX 8 bytes hole, try to pack */
struct sched_entry * current_entry; /* 48 8 */
struct sched_gate_list * oper_sched; /* 56 8 */
/* --- cacheline 1 boundary (64 bytes) --- */
--- net/sched/sch_taprio.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
net/sched/sch_taprio.c +6 -4
@@ -65,6 +65,7 @@ struct taprio_sched {u32 flags;enum tk_offsets tk_offset;int clockid; +bool offloaded;atomic64_t picos_per_byte;/* Using picoseconds because for 10Gbps+ * speeds it's sub-nanoseconds per byte */
@@ -1267,6 +1268,8 @@ static int taprio_enable_offload(struct net_device *dev, goto done; } + q->offloaded = true; + done:taprio_offload_free (offload);
@@ -1281,12 +1284,9 @@ static int taprio_disable_offload(struct net_device *dev,struct tc_taprio_qopt_offload *offload;int err; -if (!FULL_OFFLOAD_IS_ENABLED (q->flags)) +if (!q->offloaded)return 0 ; -if (!ops->ndo_setup_tc) -return -EOPNOTSUPP ; - offload =taprio_offload_alloc (0 );if (!offload) { NL_SET_ERR_MSG(extack,
@@ -1302,6 +1302,8 @@ static int taprio_disable_offload(struct net_device *dev, goto out; } + q->offloaded = false; + out:taprio_offload_free (offload);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 104/141 net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs
In reply to Greg Kroah-HartmanFrom: Vladimir Oltean <[email protected]>
[ Upstream commit 1461d212ab277d8bba1a753d33e9afe03d81f9d4 ]
taprio can only operate as root qdisc, and to that end, there exists the following check in taprio_init(), just as in mqprio:
if (sch->parent != TC_H_ROOT) return -EOPNOTSUPP;
And indeed, when we try to attach taprio to an mqprio child, it fails as expected:
$ tc qdisc add dev swp0 root handle 1: mqprio num_tc 8 \ map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 hw 0 $ tc qdisc replace dev swp0 parent 1:2 taprio num_tc 8 \ map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \ base-time 0 sched-entry S 0x7f 990000 sched-entry S 0x80 100000 \ flags 0x0 clockid CLOCK_TAI Error: sch_taprio: Can only be attached as root qdisc.
(extack message added by me)
But when we try to attach a taprio child to a taprio root qdisc, surprisingly it doesn't fail:
$ tc qdisc replace dev swp0 root handle 1: taprio num_tc 8 \ map 0 1 2 3 4 5 6 7 queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \ base-time 0 sched-entry S 0x7f 990000 sched-entry S 0x80 100000 \ flags 0x0 clockid CLOCK_TAI $ tc qdisc replace dev swp0 parent 1:2 taprio num_tc 8 \ map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \ base-time 0 sched-entry S 0x7f 990000 sched-entry S 0x80 100000 \ flags 0x0 clockid CLOCK_TAI
This is because tc_modify_qdisc() behaves differently when mqprio is root, vs when taprio is root.
In the mqprio case, it finds the parent qdisc through
p = qdisc_lookup(dev, TC_H_MAJ(clid)), and then the child qdisc through q = qdisc_leaf(p, clid). This leaf qdisc q has handle 0, so it is ignored according to the comment right below ("It may be default qdisc, ignore it"). As a result, tc_modify_qdisc() goes through the qdisc_create() code path, and this gives taprio_init() a chance to check for sch_parent != TC_H_ROOT and error out.
Whereas in the taprio case, the returned q = qdisc_leaf(p, clid) is different. It is not the default qdisc created for each netdev queue (both taprio and mqprio call qdisc_create_dflt() and keep them in a private q->qdiscs[], or priv->qdiscs[], respectively). Instead, taprio makes qdisc_leaf() return the _root_ qdisc, aka itself.
When taprio does that, tc_modify_qdisc() goes through the qdisc_change() code path, because the qdisc layer never finds out about the child qdisc of the root. And through the ->change() ops, taprio has no reason to check whether its parent is root or not, just through ->init(), which is not called.
The problem is the taprio_leaf() implementation. Even though code wise, it does the exact same thing as mqprio_leaf() which it is copied from, it works with different input data. This is because mqprio does not attach itself (the root) to each device TX queue, but one of the default qdiscs from its private array.
In fact, since commit 13511704f8d7 ("net: taprio offload: enforce qdisc to netdev queue mapping"), taprio does this too, but just for the full offload case. So if we tried to attach a taprio child to a fully offloaded taprio root qdisc, it would properly fail too; just not to a software root taprio.
To fix the problem, stop looking at the Qdisc that's attached to the TX queue, and instead, always return the default qdiscs that we've allocated (and to which we privately enqueue and dequeue, in software scheduling mode).
Since Qdisc_class_ops :: leaf is only called from tc_modify_qdisc(), the risk of unforeseen side effects introduced by this change is minimal.
--- net/sched/sch_taprio.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
net/sched/sch_taprio.c +5 -3
@@ -1906,12 +1906,14 @@ static int taprio_dump(struct Qdisc *sch, struct sk_buff *skb)static struct Qdisc *taprio_leaf (struct Qdisc *sch,unsigned long cl) { -struct netdev_queue *dev_queue =taprio_queue_get (sch, cl); +struct taprio_sched *q =qdisc_priv (sch); +struct net_device *dev =qdisc_dev (sch); +unsigned int ntx = cl -1 ; -if (!dev_queue) +if (ntx >= dev->num_tx_queues)return NULL ; -return dev_queue->qdisc_sleeping; +return q->qdiscs[ntx]; }static unsigned long taprio_find (struct Qdisc *sch,u32 classid)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 105/141 netfilter: nf_tables: fix nft_counters_enabled underflow at nf_tables_addchain()
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
[ Upstream commit 921ebde3c0d22c8cba74ce8eb3cc4626abff1ccd ]
syzbot is reporting underflow of nft_counters_enabled counter at nf_tables_addchain() [1], for commit 43eb8949cfdffa76 ("netfilter:nf_tables: do not leave chain stats enabled on error") missed that nf_tables_chain_destroy() after nft_basechain_init() in the error path of nf_tables_addchain() decrements the counter because nft_basechain_init() makes nft_is_base_chain() return true by setting NFT_CHAIN_BASE flag.
Increment the counter immediately after returning from nft_basechain_init().
--- net/netfilter/nf_tables_api.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
net/netfilter/nf_tables_api.c +3 -4
@@ -2001,7 +2001,6 @@ static int nf_tables_addchain(struct nft_ctx *ctx, u8 family, u8 genmask, u8 policy, u32 flags) {const struct nlattr *const *nla = ctx->nla; -struct nft_stats __percpu *stats =NULL ;struct nft_table *table = ctx->table;struct nft_base_chain *basechain;struct net *net = ctx->net;
@@ -2015,6 +2014,7 @@ static int nf_tables_addchain(struct nft_ctx *ctx, u8 family, u8 genmask,return -EOVERFLOW ;if (nla[NFTA_CHAIN_HOOK ]) { +struct nft_stats __percpu *stats =NULL ;struct nft_chain_hook hook;if (flags &NFT_CHAIN_BINDING )
@@ -2047,6 +2047,8 @@ static int nf_tables_addchain(struct nft_ctx *ctx, u8 family, u8 genmask,kfree (basechain);return err; } +if (stats) +static_branch_inc (&nft_counters_enabled); }else {if (flags &NFT_CHAIN_BASE )return -EINVAL ;
@@ -2121,9 +2123,6 @@ static int nf_tables_addchain(struct nft_ctx *ctx, u8 family, u8 genmask, goto err_unregister_hook; } -if (stats) -static_branch_inc (&nft_counters_enabled); - table->use++;return 0 ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 106/141 netfilter: nf_tables: fix percpu memory leak at nf_tables_addchain()
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
[ Upstream commit 9a4d6dd554b86e65581ef6b6638a39ae079b17ac ]
It seems to me that percpu memory for chain stats started leaking since commit 3bc158f8d0330f0a ("netfilter: nf_tables: map basechain priority to hardware priority") when nft_chain_offload_priority() returned an error.
--- net/netfilter/nf_tables_api.c | 1 + 1 file changed, 1 insertion(+)
net/netfilter/nf_tables_api.c +1 -0
@@ -2045,6 +2045,7 @@ static int nf_tables_addchain(struct nft_ctx *ctx, u8 family, u8 genmask,if (err <0 ) {nft_chain_release_hook (&hook);kfree (basechain); +free_percpu (stats);return err; }if (stats)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 107/141 netfilter: ebtables: fix memory leak when blob is malformed
In reply to Greg Kroah-HartmanFrom: Florian Westphal <[email protected]>
[ Upstream commit 62ce44c4fff947eebdf10bb582267e686e6835c9 ]
The bug fix was incomplete, it "replaced" crash with a memory leak. The old code had an assignment to "ret" embedded into the conditional, restore this.
--- net/bridge/netfilter/ebtables.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/bridge/netfilter/ebtables.c +3 -1
@@ -999,8 +999,10 @@ static int do_replace_finish(struct net *net, struct ebt_replace *repl, goto free_iterate; } -if (repl->valid_hooks != t->valid_hooks) +if (repl->valid_hooks != t->valid_hooks) { + ret = -EINVAL ; goto free_unlock; + }if (repl->num_counters && repl->num_counters != t->private->nentries) { ret = -EINVAL ;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 108/141 can: gs_usb: gs_can_open(): fix race dev->can.state condition
In reply to Greg Kroah-HartmanFrom: Marc Kleine-Budde <[email protected]>
[ Upstream commit 5440428b3da65408dba0241985acb7a05258b85e ]
The dev->can.state is set to CAN_STATE_ERROR_ACTIVE, after the device has been started. On busy networks the CAN controller might receive CAN frame between and go into an error state before the dev->can.state is assigned.
Assign dev->can.state before starting the controller to close the race window.
--- drivers/net/can/usb/gs_usb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/can/usb/gs_usb.c +2 -2
@@ -678,6 +678,7 @@ static int gs_can_open(struct net_device *netdev) flags |=GS_CAN_MODE_TRIPLE_SAMPLE ;/* finally start device */ + dev->can.state =CAN_STATE_ERROR_ACTIVE ; dm->mode =cpu_to_le32 (GS_CAN_MODE_START ); dm->flags =cpu_to_le32 (flags); rc = usb_control_msg(interface_to_usbdev(dev->iface),
@@ -694,13 +695,12 @@ static int gs_can_open(struct net_device *netdev)if (rc <0 ) {netdev_err (netdev,"Couldn't start device (err=%d)\n" , rc);kfree (dm); + dev->can.state =CAN_STATE_STOPPED ;return rc; }kfree (dm); - dev->can.state =CAN_STATE_ERROR_ACTIVE ; - parent->active_channels++;if (!(dev->can.ctrlmode &CAN_CTRLMODE_LISTENONLY ))netif_start_queue (netdev);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 109/141 perf jit: Include program header in ELF files
In reply to Greg Kroah-HartmanFrom: Lieven Hey <[email protected]>
[ Upstream commit babd04386b1df8c364cdaa39ac0e54349502e1e5 ]
The missing header makes it hard for programs like elfutils to open these files.
--- tools/perf/util/genelf.c | 14 ++++++++++++++ tools/perf/util/genelf.h | 4 ++++ 2 files changed, 18 insertions(+)
tools/perf/util/genelf.c +14 -0
@@ -251,6 +251,7 @@ jit_write_elf(int fd, uint64_t load_addr, const char *sym,Elf_Data *d;Elf_Scn *scn;Elf_Ehdr *ehdr; +Elf_Phdr *phdr;Elf_Shdr *shdr;uint64_t eh_frame_base_offset;char *strsym =NULL ;
@@ -285,6 +286,19 @@ jit_write_elf(int fd, uint64_t load_addr, const char *sym, ehdr->e_version =EV_CURRENT ; ehdr->e_shstrndx= unwinding ?4 :2 ;/* shdr index for section name */ +/* +* setup program header +*/ + phdr =elf_newphdr (e,1 ); + phdr[0 ].p_type =PT_LOAD ; + phdr[0 ].p_offset =0 ; + phdr[0 ].p_vaddr =0 ; + phdr[0 ].p_paddr =0 ; + phdr[0 ].p_filesz = csize; + phdr[0 ].p_memsz = csize; + phdr[0 ].p_flags =PF_X |PF_R ; + phdr[0 ].p_align =8 ; +/* * setup text section */
tools/perf/util/genelf.h +4 -0
@@ -50,8 +50,10 @@ int jit_add_debug_info(Elf *e, uint64_t code_addr, void *debug, int nr_debug_ent#if GEN_ELF_CLASS ==ELFCLASS64 #define elf_newehdr elf64_newehdr +#define elf_newphdr elf64_newphdr#define elf_getshdr elf64_getshdr#define Elf_Ehdr Elf64_Ehdr +#define Elf_Phdr Elf64_Phdr#define Elf_Shdr Elf64_Shdr#define Elf_Sym Elf64_Sym#define ELF_ST_TYPE (a) ELF64_ST_TYPE(a)
@@ -59,8 +61,10 @@ int jit_add_debug_info(Elf *e, uint64_t code_addr, void *debug, int nr_debug_ent#define ELF_ST_VIS (a) ELF64_ST_VISIBILITY(a)#else #define elf_newehdr elf32_newehdr +#define elf_newphdr elf32_newphdr#define elf_getshdr elf32_getshdr#define Elf_Ehdr Elf32_Ehdr +#define Elf_Phdr Elf32_Phdr#define Elf_Shdr Elf32_Shdr#define Elf_Sym Elf32_Sym#define ELF_ST_TYPE (a) ELF32_ST_TYPE(a)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 110/141 perf kcore_copy: Do not check /proc/modules is unchanged
In reply to Greg Kroah-HartmanFrom: Adrian Hunter <[email protected]>
[ Upstream commit 5b427df27b94aec1312cace48a746782a0925c53 ]
/proc/kallsyms and /proc/modules are compared before and after the copy in order to ensure no changes during the copy.
However /proc/modules also might change due to reference counts changing even though that does not make any difference.
Any modules loaded or unloaded should be visible in changes to kallsyms, so it is not necessary to check /proc/modules also anyway.
Remove the comparison checking that /proc/modules is unchanged.
--- tools/perf/util/symbol-elf.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)
tools/perf/util/symbol-elf.c +2 -5
@@ -2002,8 +2002,8 @@ static int kcore_copy__compare_file(const char *from_dir, const char *to_dir,* unusual. One significant peculiarity is that the mapping (start -> pgoff) * is not the same for the kernel map and the modules map. That happens because * the data is copied adjacently whereas the original kcore has gaps. Finally, -* kallsyms and modules files are compared with their copies to check that -* modules have not been loaded or unloaded while the copies were taking place. +* kallsyms file is compared with its copy to check that modules have not been +* loaded or unloaded while the copies were taking place. * * Return: %0 on success, %-1 on failure. */
@@ -2066,9 +2066,6 @@ int kcore_copy(const char *from_dir, const char *to_dir) goto out_extract_close; } -if (kcore_copy__compare_file (from_dir, to_dir,"modules" )) - goto out_extract_close; -if (kcore_copy__compare_file (from_dir, to_dir,"kallsyms" )) goto out_extract_close;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 111/141 drm/mediatek: dsi: Move mtk_dsi_stop() call back to mtk_dsi_poweroff()
In reply to Greg Kroah-HartmanFrom: Nícolas F. R. A. Prado <[email protected]>
[ Upstream commit 90144dd8b0d137d9e78ef34b3c418e51a49299ad ]
As the comment right before the mtk_dsi_stop() call advises, mtk_dsi_stop() should only be called after mtk_drm_crtc_atomic_disable(). That's because that function calls drm_crtc_wait_one_vblank(), which requires the vblank irq to be enabled.
Previously mtk_dsi_stop(), being in mtk_dsi_poweroff() and guarded by a refcount, would only be called at the end of mtk_drm_crtc_atomic_disable(), through the call to mtk_crtc_ddp_hw_fini(). Commit cde7e2e35c28 ("drm/mediatek: Separate poweron/poweroff from enable/disable and define new funcs") moved the mtk_dsi_stop() call to mtk_output_dsi_disable(), causing it to be called before mtk_drm_crtc_atomic_disable(), and consequently generating vblank timeout warnings during suspend.
Move the mtk_dsi_stop() call back to mtk_dsi_poweroff() so that we have a working vblank irq during mtk_drm_crtc_atomic_disable() and stop getting vblank timeout warnings.
--- drivers/gpu/drm/mediatek/mtk_dsi.c | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-)
drivers/gpu/drm/mediatek/mtk_dsi.c +10 -11
@@ -668,6 +668,16 @@ static void mtk_dsi_poweroff(struct mtk_dsi *dsi)if (--dsi->refcount !=0 )return ; +/* +* mtk_dsi_stop() and mtk_dsi_start() is asymmetric, since +* mtk_dsi_stop() should be called after mtk_drm_crtc_atomic_disable(), +* which needs irq for vblank, and mtk_dsi_stop() will disable irq. +* mtk_dsi_start() needs to be called in mtk_output_dsi_enable(), +* after dsi is fully set. +*/ +mtk_dsi_stop (dsi); + +mtk_dsi_switch_to_cmd_mode (dsi,VM_DONE_INT_FLAG ,500 );mtk_dsi_reset_engine (dsi);mtk_dsi_lane0_ulp_mode_enter (dsi);mtk_dsi_clk_ulp_mode_enter (dsi);
@@ -718,17 +728,6 @@ static void mtk_output_dsi_disable(struct mtk_dsi *dsi)if (!dsi->enabled)return ; -/* -* mtk_dsi_stop() and mtk_dsi_start() is asymmetric, since -* mtk_dsi_stop() should be called after mtk_drm_crtc_atomic_disable(), -* which needs irq for vblank, and mtk_dsi_stop() will disable irq. -* mtk_dsi_start() needs to be called in mtk_output_dsi_enable(), -* after dsi is fully set. -*/ -mtk_dsi_stop (dsi); - -mtk_dsi_switch_to_cmd_mode (dsi,VM_DONE_INT_FLAG ,500 ); - dsi->enabled = false; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 112/141 net/smc: Stop the CLC flow if no link to map buffers on
In reply to Greg Kroah-HartmanFrom: Wen Gu <[email protected]>
[ Upstream commit e738455b2c6dcdab03e45d97de36476f93f557d2 ]
There might be a potential race between SMC-R buffer map and link group termination.
smc_smcr_terminate_all() | smc_connect_rdma()
--------------------------------------------------------------
| smc_conn_create()
for links in smcibdev |
schedule links down |
| smc_buf_create()
| \- smcr_buf_map_usable_links()
| \- no usable links found,
| (rmb->mr = NULL)
|
| smc_clc_send_confirm()
| \- access conn->rmb_desc->mr[]->rkey
| (panic)During reboot and IB device module remove, all links will be set down and no usable links remain in link groups. In such situation smcr_buf_map_usable_links() should return an error and stop the CLC flow accessing to uninitialized mr.
--- net/smc/smc_core.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
net/smc/smc_core.c +4 -1
@@ -1584,7 +1584,7 @@ static struct smc_buf_desc *smcr_new_buf_create(struct smc_link_group *lgr,static int smcr_buf_map_usable_links (struct smc_link_group *lgr,struct smc_buf_desc *buf_desc,bool is_rmb) { -int i, rc =0 ; +int i, rc =0 , cnt =0 ;/* protect against parallel link reconfiguration */ mutex_lock (&lgr->llc_conf_mutex);
@@ -1597,9 +1597,12 @@ static int smcr_buf_map_usable_links(struct smc_link_group *lgr, rc = -ENOMEM ; goto out; } + cnt++; } out:mutex_unlock (&lgr->llc_conf_mutex); +if (!rc && !cnt) + rc = -EINVAL ;return rc; }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 113/141 net: sunhme: Fix packet reception for len < RX_COPY_THRESHOLD
In reply to Greg Kroah-HartmanFrom: Sean Anderson <[email protected]>
[ Upstream commit 878e2405710aacfeeb19364c300f38b7a9abfe8f ]
There is a separate receive path for small packets (under 256 bytes). Instead of allocating a new dma-capable skb to be used for the next packet, this path allocates a skb and copies the data into it (reusing the existing sbk for the next packet). There are two bytes of junk data at the beginning of every packet. I believe these are inserted in order to allow aligned DMA and IP headers. We skip over them using skb_reserve. Before copying over the data, we must use a barrier to ensure we see the whole packet. The current code only synchronizes len bytes, starting from the beginning of the packet, including the junk bytes. However, this leaves off the final two bytes in the packet. Synchronize the whole packet.
To reproduce this problem, ping a HME with a payload size between 17 and 214
$ ping -s 17 <hme_address>
which will complain rather loudly about the data mismatch. Small packets (below 60 bytes on the wire) do not have this issue. I suspect this is related to the padding added to increase the minimum packet size.
--- drivers/net/ethernet/sun/sunhme.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/sun/sunhme.c +2 -2
@@ -2063,9 +2063,9 @@ static void happy_meal_rx(struct happy_meal *hp, struct net_device *dev)skb_reserve (copy_skb,2 );skb_put (copy_skb, len); -dma_sync_single_for_cpu (hp->dma_dev, dma_addr, len,DMA_FROM_DEVICE ); +dma_sync_single_for_cpu (hp->dma_dev, dma_addr, len +2 ,DMA_FROM_DEVICE );skb_copy_from_linear_data (skb, copy_skb->data, len); -dma_sync_single_for_device (hp->dma_dev, dma_addr, len,DMA_FROM_DEVICE ); +dma_sync_single_for_device (hp->dma_dev, dma_addr, len +2 ,DMA_FROM_DEVICE );/* Reuse original ring buffer. */ hme_write_rxd(hp, this, (RXFLAG_OWN|((RX_BUF_ALLOC_SIZE-RX_OFFSET)<<16)),
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 114/141 net: sched: fix possible refcount leak in tc_new_tfilter()
In reply to Greg Kroah-HartmanFrom: Hangyu Hua <[email protected]>
[ Upstream commit c2e1cfefcac35e0eea229e148c8284088ce437b5 ]
tfilter_put need to be called to put the refount got by tp->ops->get to avoid possible refcount leak when chain->tmplt_ops != NULL and chain->tmplt_ops != tp->ops.
--- net/sched/cls_api.c | 1 + 1 file changed, 1 insertion(+)
net/sched/cls_api.c +1 -0
@@ -2124,6 +2124,7 @@ static int tc_new_tfilter(struct sk_buff *skb, struct nlmsghdr *n, }if (chain->tmplt_ops && chain->tmplt_ops != tp->ops) { +tfilter_put (tp, fh);NL_SET_ERR_MSG (extack,"Chain template is set to a different filter kind" ); err = -EINVAL ; goto errout;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 115/141 selftests: forwarding: add shebang for sch_red.sh
In reply to Greg Kroah-HartmanFrom: Hangbin Liu <[email protected]>
[ Upstream commit 83e4b196838d90799a8879e5054a3beecf9ed256 ]
RHEL/Fedora RPM build checks are stricter, and complain when executable files don't have a shebang line, e.g.
*** WARNING: ./kselftests/net/forwarding/sch_red.sh is executable but has no shebang, removing executable bit
Fix it by adding shebang line.
--- tools/testing/selftests/net/forwarding/sch_red.sh | 1 + 1 file changed, 1 insertion(+)
tools/testing/selftests/net/forwarding/sch_red.sh +1 -0
@@ -1,3 +1,4 @@ +#!/bin/bash # SPDX-License-Identifier: GPL-2.0 # This test sends one stream of traffic from H1 through a TBF shaper, to a RED
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 116/141 drm/amd/amdgpu: fixing read wrong pf2vf data in SRIOV
In reply to Greg Kroah-HartmanFrom: Jingwen Chen <[email protected]>
commit 9a458402fb69bda886aa6cbe067311b6e3d9c52a upstream.
[Why]
This fixes 892deb48269c ("drm/amdgpu: Separate vf2pf work item init from virt data exchange"). we should read pf2vf data based at mman.fw_vram_usage_va after gmcsw_init. commit 892deb48269c breaks this logic.
[How]
calling amdgpu_virt_exchange_data in amdgpu_virt_init_data_exchange to set the right base in the right sequence.
v2:
call amdgpu_virt_init_data_exchange after gmc sw_init to make data exchange workqueue run
v3:
clean up the code logic
v4:
add some comment and make the code more readable
--- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c | 20 +++++++------------- 2 files changed, 8 insertions(+), 14 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c +1 -1
@@ -2224,7 +2224,7 @@ static int amdgpu_device_ip_init(struct }if (amdgpu_sriov_vf (adev)) -amdgpu_virt_exchange_data (adev); +amdgpu_virt_init_data_exchange (adev); r =amdgpu_ib_pool_init (adev);if (r) {
drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c +7 -13
@@ -584,20 +584,20 @@ void amdgpu_virt_init_data_exchange(stru adev->virt.fw_reserve.p_vf2pf =NULL ; adev->virt.vf2pf_update_interval_ms =0 ; -if (adev->bios !=NULL ) { - adev->virt.vf2pf_update_interval_ms =2000 ; +if (adev->mman.fw_vram_usage_va !=NULL ) { +/* go through this logic in ip_init and reset to init workqueue*/ +amdgpu_virt_exchange_data (adev); +INIT_DELAYED_WORK (&adev->virt.vf2pf_work, amdgpu_virt_update_vf2pf_work_item); +schedule_delayed_work (&(adev->virt.vf2pf_work),msecs_to_jiffies (adev->virt.vf2pf_update_interval_ms)); + }else if (adev->bios !=NULL ) { +/* got through this logic in early init stage to get necessary flags, e.g. rlcg_acc related*/ adev->virt.fw_reserve.p_pf2vf = (struct amd_sriov_msg_pf2vf_info_header *) (adev->bios + (AMD_SRIOV_MSG_PF2VF_OFFSET_KB <<10 ));amdgpu_virt_read_pf2vf_data (adev); } - -if (adev->virt.vf2pf_update_interval_ms !=0 ) { -INIT_DELAYED_WORK (&adev->virt.vf2pf_work, amdgpu_virt_update_vf2pf_work_item); -schedule_delayed_work (&(adev->virt.vf2pf_work),msecs_to_jiffies (adev->virt.vf2pf_update_interval_ms)); - } }
@@ -633,12 +633,6 @@ void amdgpu_virt_exchange_data(struct amif (adev->virt.ras_init_done)amdgpu_virt_add_bad_page (adev, bp_block_offset, bp_block_size); } - }else if (adev->bios !=NULL ) { - adev->virt.fw_reserve.p_pf2vf = - (struct amd_sriov_msg_pf2vf_info_header *) - (adev->bios + (AMD_SRIOV_MSG_PF2VF_OFFSET_KB <<10 )); - -amdgpu_virt_read_pf2vf_data (adev); } }
Greg Kroah-Hartman
maintainerPATCH 117/141 serial: Create uart_xmit_advance()
In reply to Greg Kroah-HartmanFrom: Ilpo Järvinen <[email protected]>
commit e77cab77f2cb3a1ca2ba8df4af45bb35617ac16d upstream.
A very common pattern in the drivers is to advance xmit tail index and do bookkeeping of Tx'ed characters. Create uart_xmit_advance() to handle it.
--- include/linux/serial_core.h | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
include/linux/serial_core.h +17 -0
@@ -300,6 +300,23 @@ struct uart_state {/* number of characters left in xmit buffer before we ask for more */ #define WAKEUP_CHARS 256 +/** +* uart_xmit_advance - Advance xmit buffer and account Tx'ed chars +* @up: uart_port structure describing the port +* @chars: number of characters sent +* +* This function advances the tail of circular xmit buffer by the number of +* @chars transmitted and handles accounting of transmitted bytes (into +* @up's icount.tx). +*/ +static inline void uart_xmit_advance (struct uart_port *up,unsigned int chars) +{ +struct circ_buf *xmit = &up->state->xmit; + + xmit->tail = (xmit->tail + chars) & (UART_XMIT_SIZE -1 ); + up->icount.tx += chars; +} +struct module ;struct tty_driver ;
Greg Kroah-Hartman
maintainerPATCH 118/141 serial: tegra: Use uart_xmit_advance(), fixes icount.tx accounting
In reply to Greg Kroah-HartmanFrom: Ilpo Järvinen <[email protected]>
commit 754f68044c7dd6c52534ba3e0f664830285c4b15 upstream.
DMA complete & stop paths did not correctly account Tx'ed characters into icount.tx. Using uart_xmit_advance() fixes the problem.
--- drivers/tty/serial/serial-tegra.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/tty/serial/serial-tegra.c +2 -3
@@ -520,7 +520,7 @@ static void tegra_uart_tx_dma_complete(v count = tup->tx_bytes_requested - state.residue;async_tx_ack (tup->tx_dma_desc);spin_lock_irqsave (&tup->uport.lock, flags); - xmit->tail = (xmit->tail + count) & (UART_XMIT_SIZE -1 ); +uart_xmit_advance (&tup->uport, count); tup->tx_in_progress =0 ;if (uart_circ_chars_pending (xmit) <WAKEUP_CHARS )uart_write_wakeup (&tup->uport);
@@ -608,7 +608,6 @@ static unsigned int tegra_uart_tx_empty(static void tegra_uart_stop_tx (struct uart_port *u) {struct tegra_uart_port *tup =to_tegra_uport (u); -struct circ_buf *xmit = &tup->uport.state->xmit;struct dma_tx_state state;unsigned int count;
@@ -619,7 +618,7 @@ static void tegra_uart_stop_tx(struct uadmaengine_tx_status (tup->tx_dma_chan, tup->tx_cookie, &state); count = tup->tx_bytes_requested - state.residue;async_tx_ack (tup->tx_dma_desc); - xmit->tail = (xmit->tail + count) & (UART_XMIT_SIZE -1 ); +uart_xmit_advance (&tup->uport, count); tup->tx_in_progress =0 ; }
Greg Kroah-Hartman
maintainerPATCH 119/141 serial: tegra-tcu: Use uart_xmit_advance(), fixes icount.tx accounting
In reply to Greg Kroah-HartmanFrom: Ilpo Järvinen <[email protected]>
commit 1d10cd4da593bc0196a239dcc54dac24b6b0a74e upstream.
Tx'ing does not correctly account Tx'ed characters into icount.tx. Using uart_xmit_advance() fixes the problem.
--- drivers/tty/serial/tegra-tcu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/tty/serial/tegra-tcu.c +1 -1
@@ -101,7 +101,7 @@ static void tegra_tcu_uart_start_tx(strubreak ;tegra_tcu_write (tcu, &xmit->buf[xmit->tail], count); - xmit->tail = (xmit->tail + count) & (UART_XMIT_SIZE -1 ); +uart_xmit_advance (port, count); }uart_write_wakeup (port);
Greg Kroah-Hartman
maintainerPATCH 120/141 s390/dasd: fix Oops in dasd_alias_get_start_dev due to missing pavgroup
In reply to Greg Kroah-HartmanFrom: Stefan Haberland <[email protected]>
commit db7ba07108a48c0f95b74fabbfd5d63e924f992d upstream.
Fix Oops in dasd_alias_get_start_dev() function caused by the pavgroup pointer being NULL.
The pavgroup pointer is checked on the entrance of the function but without the lcu->lock being held. Therefore there is a race window between dasd_alias_get_start_dev() and _lcu_update() which sets pavgroup to NULL with the lcu->lock held.
Fix by checking the pavgroup pointer with lcu->lock held.
--- drivers/s390/block/dasd_alias.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)
drivers/s390/block/dasd_alias.c +7 -2
@@ -675,12 +675,12 @@ int dasd_alias_remove_device(struct dasdstruct dasd_device *dasd_alias_get_start_dev (struct dasd_device *base_device) {struct dasd_eckd_private *alias_priv, *private = base_device->private; -struct alias_pav_group *group = private->pavgroup;struct alias_lcu *lcu = private->lcu;struct dasd_device *alias_device; +struct alias_pav_group *group;unsigned long flags; -if (!group || !lcu) +if (!lcu)return NULL ;if (lcu->pav ==NO_PAV || lcu->flags & (NEED_UAC_UPDATE |UPDATE_PENDING ))
@@ -697,6 +697,11 @@ struct dasd_device *dasd_alias_get_start }spin_lock_irqsave (&lcu->lock, flags); + group = private->pavgroup; +if (!group) { +spin_unlock_irqrestore (&lcu->lock, flags); +return NULL ; + } alias_device = group->next;if (!alias_device) {if (list_empty (&group->aliaslist)) {
Greg Kroah-Hartman
maintainerPATCH 121/141 usb: xhci-mtk: fix issue of out-of-bounds array access
In reply to Greg Kroah-HartmanFrom: Chunfeng Yun <[email protected]>
commit de5107f473190538a65aac7edea85209cd5c1a8f upstream.
Bus bandwidth array access is based on esit, increase one will cause out-of-bounds issue; for example, when esit is XHCI_MTK_MAX_ESIT, will overstep boundary.
--- drivers/usb/host/xhci-mtk-sch.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
drivers/usb/host/xhci-mtk-sch.c +6 -4
@@ -539,10 +539,12 @@ static u32 get_esit_boundary(struct mu3hu32 boundary = sch_ep->esit;if (sch_ep->sch_tt) {/* LS/FS with TT */ -/* tune for CS */ -if (sch_ep->ep_type !=ISOC_OUT_EP ) - boundary++; -else if (boundary >1 )/* normally esit >= 8 for FS/LS */ +/* +* tune for CS, normally esit >= 8 for FS/LS, +* not add one for other types to avoid access array +* out of boundary +*/ +if (sch_ep->ep_type ==ISOC_OUT_EP && boundary >1 ) boundary--; }
Greg Kroah-Hartman
maintainerPATCH 122/141 vfio/type1: fix vaddr_get_pfns() return in vfio_pin_page_external()
In reply to Greg Kroah-HartmanFrom: Daniel Jordan <[email protected]>
commit 4ab4fcfce5b540227d80eb32f1db45ab615f7c92 upstream.
vaddr_get_pfns() now returns the positive number of pfns successfully gotten instead of zero. vfio_pin_page_external() might return 1 to vfio_iommu_type1_pin_pages(), which will treat it as an error, if vaddr_get_pfns() is successful but vfio_pin_page_external() doesn't reach vfio_lock_acct().
Fix it up in vfio_pin_page_external(). Found by inspection.
Message-Id: <[email protected]>
--- drivers/vfio/vfio_iommu_type1.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/vfio/vfio_iommu_type1.c +7 -1
@@ -671,7 +671,12 @@ static int vfio_pin_page_external(structreturn -ENODEV ; ret =vaddr_get_pfns (mm, vaddr,1 , dma->prot, pfn_base, pages); -if (ret ==1 && do_accounting && !is_invalid_reserved_pfn (*pfn_base)) { +if (ret !=1 ) + goto out; + + ret =0 ; + +if (do_accounting && !is_invalid_reserved_pfn (*pfn_base)) { ret =vfio_lock_acct (dma,1 , true);if (ret) {put_pfn (*pfn_base, dma->prot);
@@ -683,6 +688,7 @@ static int vfio_pin_page_external(struct } } +out:mmput (mm);return ret; }
Greg Kroah-Hartman
maintainerPATCH 123/141 drm/amdgpu: Fix check for RAS support
In reply to Greg Kroah-HartmanFrom: Luben Tuikov <[email protected]>
[ Upstream commit 084e2640e51626f413f85663e3ba7e32d4272477 ]
Use positive logic to check for RAS
support. Rename the function to actually indicate
what it is testing for. Essentially, make the
function a predicate with the correct name.
Stable-dep-of: 6c2049066355 ("drm/amdgpu: Don't enable LTR if not supported")
--- drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)
drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c +6 -9
@@ -1979,15 +1979,12 @@ int amdgpu_ras_request_reset_on_boot(struct amdgpu_device *adev,return 0 ; } -static int amdgpu_ras_check_asic_type (struct amdgpu_device *adev) +static bool amdgpu_ras_asic_supported (struct amdgpu_device *adev) { -if (adev->asic_type !=CHIP_VEGA10 && - adev->asic_type !=CHIP_VEGA20 && - adev->asic_type !=CHIP_ARCTURUS && - adev->asic_type !=CHIP_SIENNA_CICHLID ) -return 1 ; -else -return 0 ; +return adev->asic_type ==CHIP_VEGA10 || + adev->asic_type ==CHIP_VEGA20 || + adev->asic_type ==CHIP_ARCTURUS || + adev->asic_type ==CHIP_SIENNA_CICHLID ; }/*
@@ -2006,7 +2003,7 @@ static void amdgpu_ras_check_supported(struct amdgpu_device *adev, *supported =0 ;if (amdgpu_sriov_vf (adev) || !adev->is_atom_fw || -amdgpu_ras_check_asic_type (adev)) + !amdgpu_ras_asic_supported (adev))return ;if (amdgpu_atomfirmware_mem_ecc_supported (adev)) {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 124/141 cifs: use discard iterator to discard unneeded network data more efficiently
In reply to Greg Kroah-HartmanFrom: David Howells <[email protected]>
[ Upstream commit cf0604a686b11175d8beae60281c4ccc95aaa5c2 ]
The iterator, ITER_DISCARD, that can only be used in READ mode and just discards any data copied to it, was added to allow a network filesystem to discard any unwanted data sent by a server. Convert cifs_discard_from_socket() to use this.
Stable-dep-of: bedc8f76b353 ("cifs: always initialize struct msghdr smb_msg completely")
--- fs/cifs/cifsproto.h | 2 ++ fs/cifs/cifssmb.c | 6 +++--- fs/cifs/connect.c | 17 +++++++++++++++++ 3 files changed, 22 insertions(+), 3 deletions(-)
fs/cifs/cifsproto.h +2 -0
@@ -230,6 +230,8 @@ extern unsigned int setup_special_user_owner_ACE(struct cifs_ace *pace);extern void dequeue_mid (struct mid_q_entry *mid,bool malformed);extern int cifs_read_from_socket (struct TCP_Server_Info *server,char *buf,unsigned int to_read); +extern ssize_t cifs_discard_from_socket (struct TCP_Server_Info *server, +size_t to_read); extern int cifs_read_page_from_socket(struct TCP_Server_Info *server, struct page *page, unsigned int page_offset,
fs/cifs/cifssmb.c +3 -3
@@ -1451,9 +1451,9 @@ cifs_discard_remaining_data(struct TCP_Server_Info *server)while (remaining >0 ) {int length; - length =cifs_read_from_socket (server, server->bigbuf, - min_t(unsigned int, remaining, - CIFSMaxBufSize +MAX_HEADER_SIZE (server))); + length =cifs_discard_from_socket (server, +min_t (size_t, remaining, + CIFSMaxBufSize +MAX_HEADER_SIZE (server)));if (length <0 )return length; server->total_read += length;
fs/cifs/connect.c +17 -0
@@ -755,6 +755,23 @@ cifs_read_from_socket(struct TCP_Server_Info *server, char *buf,return cifs_readv_from_socket (server, &smb_msg); } +ssize_t +cifs_discard_from_socket (struct TCP_Server_Info *server,size_t to_read) +{ +struct msghdr smb_msg; + +/* +* iov_iter_discard already sets smb_msg.type and count and iov_offset +* and cifs_readv_from_socket sets msg_control and msg_controllen +* so little to initialize in struct msghdr +*/ + smb_msg.msg_name =NULL ; + smb_msg.msg_namelen =0 ; +iov_iter_discard (&smb_msg.msg_iter,READ , to_read); + +return cifs_readv_from_socket (server, &smb_msg); +} +int cifs_read_page_from_socket (struct TCP_Server_Info *server,struct page *page,unsigned int page_offset,unsigned int to_read)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 125/141 cifs: always initialize struct msghdr smb_msg completely
In reply to Greg Kroah-HartmanFrom: Stefan Metzmacher <[email protected]>
[ Upstream commit bedc8f76b3539ac4f952114b316bcc2251e808ce ]
So far we were just lucky because the uninitialized members of struct msghdr are not used by default on a SOCK_STREAM tcp socket.
But as new things like msg_ubuf and sg_from_iter where added recently, we should play on the safe side and avoid potention problems in future.
--- fs/cifs/connect.c | 11 +++-------- fs/cifs/transport.c | 6 +----- 2 files changed, 4 insertions(+), 13 deletions(-)
fs/cifs/connect.c +3 -8
@@ -695,9 +695,6 @@ cifs_readv_from_socket(struct TCP_Server_Info *server, struct msghdr *smb_msg)int length =0 ;int total_read; - smb_msg->msg_control =NULL ; - smb_msg->msg_controllen =0 ; -for (total_read =0 ;msg_data_left (smb_msg); total_read += length) {try_to_freeze ();
@@ -748,7 +745,7 @@ int cifs_read_from_socket(struct TCP_Server_Info *server, char *buf, unsigned int to_read) { - struct msghdr smb_msg; + struct msghdr smb_msg = {};struct kvec iov = {.iov_base = buf, .iov_len = to_read};iov_iter_kvec (&smb_msg.msg_iter,READ , &iov,1 , to_read);
@@ -758,15 +755,13 @@ cifs_read_from_socket(struct TCP_Server_Info *server, char *buf,ssize_t cifs_discard_from_socket (struct TCP_Server_Info *server,size_t to_read) { -struct msghdr smb_msg; +struct msghdr smb_msg = {};/* * iov_iter_discard already sets smb_msg.type and count and iov_offset * and cifs_readv_from_socket sets msg_control and msg_controllen * so little to initialize in struct msghdr */ - smb_msg.msg_name =NULL ; - smb_msg.msg_namelen =0 ;iov_iter_discard (&smb_msg.msg_iter,READ , to_read);return cifs_readv_from_socket (server, &smb_msg);
@@ -776,7 +771,7 @@ int cifs_read_page_from_socket(struct TCP_Server_Info *server, struct page *page, unsigned int page_offset, unsigned int to_read) { - struct msghdr smb_msg; + struct msghdr smb_msg = {};struct bio_vec bv = { .bv_page = page, .bv_len = to_read, .bv_offset = page_offset};iov_iter_bvec (&smb_msg.msg_iter,READ , &bv,1 , to_read);
fs/cifs/transport.c +1 -5
@@ -209,10 +209,6 @@ smb_send_kvec(struct TCP_Server_Info *server, struct msghdr *smb_msg, *sent =0 ; - smb_msg->msg_name =NULL ; - smb_msg->msg_namelen =0 ; - smb_msg->msg_control =NULL ; - smb_msg->msg_controllen =0 ;if (server->noblocksnd) smb_msg->msg_flags =MSG_DONTWAIT +MSG_NOSIGNAL ;else
@@ -324,7 +320,7 @@ __smb_send_rqst(struct TCP_Server_Info *server, int num_rqst,sigset_t mask, oldmask;size_t total_len =0 , sent, size;struct socket *ssocket = server->ssocket; -struct msghdr smb_msg; +struct msghdr smb_msg = {};__be32 rfc1002_marker;if (cifs_rdma_enabled (server)) {
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 126/141 Drivers: hv: Never allocate anything besides framebuffer from framebuffer memory region
In reply to Greg Kroah-HartmanFrom: Vitaly Kuznetsov <[email protected]>
[ Upstream commit f0880e2cb7e1f8039a048fdd01ce45ab77247221 ]
Passed through PCI device sometimes misbehave on Gen1 VMs when Hyper-V DRM driver is also loaded. Looking at IOMEM assignment, we can see e.g.
$ cat /proc/iomem
...
f8000000-fffbffff : PCI Bus 0000:00
f8000000-fbffffff : 0000:00:08.0
f8000000-f8001fff : bb8c4f33-2ba2-4808-9f7f-02f3b4da22fe
...
fe0000000-fffffffff : PCI Bus 0000:00
fe0000000-fe07fffff : bb8c4f33-2ba2-4808-9f7f-02f3b4da22fe
fe0000000-fe07fffff : 2ba2:00:02.0
fe0000000-fe07fffff : mlx4_corethe interesting part is the 'f8000000' region as it is actually the VM's framebuffer:
$ lspci -v ... 0000:00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA (prog-if 00 [VGA controller]) Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f8000000 (32-bit, non-prefetchable) [size=64M] ...
hv_vmbus: registering driver hyperv_drm
hyperv_drm 5620e0c7-8062-4dce-aeb7-520c7ef76171: [drm] Synthvid Version major 3, minor 5 hyperv_drm 0000:00:08.0: vgaarb: deactivate vga console
hyperv_drm 0000:00:08.0: BAR 0: can't reserve [mem 0xf8000000-0xfbffffff]
hyperv_drm 5620e0c7-8062-4dce-aeb7-520c7ef76171: [drm] Cannot request framebuffer, boot fb still active?
Note: "Cannot request framebuffer" is not a fatal error in hyperv_setup_gen1() as the code assumes there's some other framebuffer device there but we actually have some other PCI device (mlx4 in this case) config space there!
The problem appears to be that vmbus_allocate_mmio() can use dedicated framebuffer region to serve any MMIO request from any device. The semantics one might assume of a parameter named "fb_overlap_ok" aren't implemented because !fb_overlap_ok essentially has no effect. The existing semantics are really "prefer_fb_overlap". This patch implements the expected and needed semantics, which is to not allocate from the frame buffer space when !fb_overlap_ok.
Note, Gen2 VMs are usually unaffected by the issue because framebuffer region is already taken by EFI fb (in case kernel supports it) but Gen1 VMs may have this region unclaimed by the time Hyper-V PCI pass-through driver tries allocating MMIO space if Hyper-V DRM/FB drivers load after it. Devices can be brought up in any sequence so let's resolve the issue by always ignoring 'fb_mmio' region for non-FB requests, even if the region is unclaimed.
--- drivers/hv/vmbus_drv.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
drivers/hv/vmbus_drv.c +9 -1
@@ -2251,7 +2251,7 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj, bool fb_overlap_ok) {struct resource *iter, *shadow; -resource_size_t range_min, range_max, start; +resource_size_t range_min, range_max, start, end;const char *dev_n =dev_name (&device_obj->device);int retval;
@@ -2286,6 +2286,14 @@ int vmbus_allocate_mmio(struct resource **new, struct hv_device *device_obj, range_max = iter->end; start = (range_min + align -1 ) & ~(align -1 );for (; start + size -1 <= range_max; start += align) { + end = start + size -1 ; + +/* Skip the whole fb_mmio region if not fb_overlap_ok */ +if (!fb_overlap_ok && fb_mmio && + (((start >= fb_mmio->start) && (start <= fb_mmio->end)) || + ((end >= fb_mmio->start) && (end <= fb_mmio->end)))) +continue ; + shadow =__request_region (iter, start, size,NULL ,IORESOURCE_BUSY );if (!shadow)
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 127/141 drm/gma500: Fix BUG: sleeping function called from invalid context errors
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
[ Upstream commit 63e37a79f7bd939314997e29c2f5a9f0ef184281 ]
gma_crtc_page_flip() was holding the event_lock spinlock while calling crtc_funcs->mode_set_base() which takes ww_mutex.
The only reason to hold event_lock is to clear gma_crtc->page_flip_event on mode_set_base() errors.
Instead unlock it after setting gma_crtc->page_flip_event and on errors re-take the lock and clear gma_crtc->page_flip_event it it is still set.
This fixes the following WARN/stacktrace:
[ 512.122953] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:870 [ 512.123004] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1253, name: gnome-shell [ 512.123031] preempt_count: 1, expected: 0 [ 512.123048] RCU nest depth: 0, expected: 0 [ 512.123066] INFO: lockdep is turned off. [ 512.123080] irq event stamp: 0 [ 512.123094] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 512.123134] hardirqs last disabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123176] softirqs last enabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123207] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 512.123233] Preemption disabled at: [ 512.123241] [<0000000000000000>] 0x0 [ 512.123275] CPU: 3 PID: 1253 Comm: gnome-shell Tainted: G W 5.19.0+ #1 [ 512.123304] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013 [ 512.123323] Call Trace: [ 512.123346] <TASK> [ 512.123370] dump_stack_lvl+0x5b/0x77 [ 512.123412] __might_resched.cold+0xff/0x13a [ 512.123458] ww_mutex_lock+0x1e/0xa0 [ 512.123495] psb_gem_pin+0x2c/0x150 [gma500_gfx] [ 512.123601] gma_pipe_set_base+0x76/0x240 [gma500_gfx] [ 512.123708] gma_crtc_page_flip+0x95/0x130 [gma500_gfx] [ 512.123808] drm_mode_page_flip_ioctl+0x57d/0x5d0 [ 512.123897] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.123936] drm_ioctl_kernel+0xa1/0x150 [ 512.123984] drm_ioctl+0x21f/0x420 [ 512.124025] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.124070] ? rcu_read_lock_bh_held+0xb/0x60 [ 512.124104] ? lock_release+0x1ef/0x2d0 [ 512.124161] __x64_sys_ioctl+0x8d/0xd0 [ 512.124203] do_syscall_64+0x58/0x80 [ 512.124239] ? do_syscall_64+0x67/0x80 [ 512.124267] ? trace_hardirqs_on_prepare+0x55/0xe0 [ 512.124300] ? do_syscall_64+0x67/0x80 [ 512.124340] ? rcu_read_lock_sched_held+0x10/0x80 [ 512.124377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 512.124411] RIP: 0033:0x7fcc4a70740f [ 512.124442] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 512.124470] RSP: 002b:00007ffda73f5390 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 512.124503] RAX: ffffffffffffffda RBX: 000055cc9e474500 RCX: 00007fcc4a70740f [ 512.124524] RDX: 00007ffda73f5420 RSI: 00000000c01864b0 RDI: 0000000000000009 [ 512.124544] RBP: 00007ffda73f5420 R08: 000055cc9c0b0cb0 R09: 0000000000000034 [ 512.124564] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01864b0 [ 512.124584] R13: 0000000000000009 R14: 000055cc9df484d0 R15: 000055cc9af5d0c0 [ 512.124647] </TASK>
--- drivers/gpu/drm/gma500/gma_display.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/gpu/drm/gma500/gma_display.c +7 -4
@@ -529,15 +529,18 @@ int gma_crtc_page_flip(struct drm_crtc *crtc,WARN_ON (drm_crtc_vblank_get (crtc) !=0 ); gma_crtc->page_flip_event = event; +spin_unlock_irqrestore (&dev->event_lock, flags);/* Call this locked if we want an event at vblank interrupt. */ ret = crtc_funcs->mode_set_base (crtc, crtc->x, crtc->y, old_fb);if (ret) { - gma_crtc->page_flip_event =NULL ; -drm_crtc_vblank_put (crtc); +spin_lock_irqsave (&dev->event_lock, flags); +if (gma_crtc->page_flip_event) { + gma_crtc->page_flip_event =NULL ; +drm_crtc_vblank_put (crtc); + } +spin_unlock_irqrestore (&dev->event_lock, flags); } - -spin_unlock_irqrestore (&dev->event_lock, flags); }else { ret = crtc_funcs->mode_set_base (crtc, crtc->x, crtc->y, old_fb); }
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 128/141 gpio: ixp4xx: Make irqchip immutable
In reply to Greg Kroah-HartmanFrom: Linus Walleij <[email protected]>
[ Upstream commit 94e9bc73d85aa6ecfe249e985ff57abe0ab35f34 ]
This turns the IXP4xx GPIO irqchip into an immutable irqchip, a bit different from the standard template due to being hierarchical.
Tested on the IXP4xx which uses drivers/ata/pata_ixp4xx_cf.c for a rootfs on compact flash with IRQs from this GPIO block to the CF ATA controller.
--- drivers/gpio/gpio-ixp4xx.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
drivers/gpio/gpio-ixp4xx.c +14 -3
@@ -67,6 +67,14 @@ static void ixp4xx_gpio_irq_ack(struct irq_data *d)__raw_writel (BIT (d->hwirq), g->base +IXP4XX_REG_GPIS ); } +static void ixp4xx_gpio_mask_irq (struct irq_data *d) +{ +struct gpio_chip *gc =irq_data_get_irq_chip_data (d); + +irq_chip_mask_parent (d); +gpiochip_disable_irq (gc, d->hwirq); +} +static void ixp4xx_gpio_irq_unmask (struct irq_data *d) {struct gpio_chip *gc =irq_data_get_irq_chip_data (d);
@@ -76,6 +84,7 @@ static void ixp4xx_gpio_irq_unmask(struct irq_data *d)if (!(g->irq_edge &BIT (d->hwirq)))ixp4xx_gpio_irq_ack (d); +gpiochip_enable_irq (gc, d->hwirq);irq_chip_unmask_parent (d); }
@@ -153,12 +162,14 @@ static int ixp4xx_gpio_irq_set_type(struct irq_data *d, unsigned int type)return irq_chip_set_type_parent (d,IRQ_TYPE_LEVEL_HIGH ); } -static struct irq_chip ixp4xx_gpio_irqchip = { +static const struct irq_chip ixp4xx_gpio_irqchip = { .name ="IXP4GPIO" , .irq_ack = ixp4xx_gpio_irq_ack, - .irq_mask = irq_chip_mask_parent, + .irq_mask = ixp4xx_gpio_mask_irq, .irq_unmask = ixp4xx_gpio_irq_unmask, .irq_set_type = ixp4xx_gpio_irq_set_type, + .flags =IRQCHIP_IMMUTABLE , +GPIOCHIP_IRQ_RESOURCE_HELPERS , }; static int ixp4xx_gpio_child_to_parent_hwirq(struct gpio_chip *gc,
@@ -282,7 +293,7 @@ static int ixp4xx_gpio_probe(struct platform_device *pdev) g->gc.owner =THIS_MODULE ; girq = &g->gc.irq; - girq->chip = &ixp4xx_gpio_irqchip; +gpio_irq_chip_set_chip (girq, &ixp4xx_gpio_irqchip); girq->fwnode = g->fwnode; girq->parent_domain = parent; girq->child_to_parent_hwirq = ixp4xx_gpio_child_to_parent_hwirq;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 129/141 drm/amdgpu: use dirty framebuffer helper
In reply to Greg Kroah-HartmanFrom: Hamza Mahfooz <[email protected]>
[ Upstream commit 66f99628eb24409cb8feb5061f78283c8b65f820 ]
Currently, we aren't handling DRM_IOCTL_MODE_DIRTYFB. So, use drm_atomic_helper_dirtyfb() as the dirty callback in the amdgpu_fb_funcs struct.
--- drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c +2 -0
@@ -35,6 +35,7 @@#include <linux/pci.h> #include <linux/pm_runtime.h> #include <drm/drm_crtc_helper.h> +#include <drm/drm_damage_helper.h> #include <drm/drm_edid.h> #include <drm/drm_gem_framebuffer_helper.h> #include <drm/drm_fb_helper.h>
@@ -498,6 +499,7 @@ bool amdgpu_display_ddc_probe(struct amdgpu_connector *amdgpu_connector,static const struct drm_framebuffer_funcs amdgpu_fb_funcs = { .destroy = drm_gem_fb_destroy, .create_handle = drm_gem_fb_create_handle, + .dirty = drm_atomic_helper_dirtyfb, }; uint32_t amdgpu_display_supported_domains(struct amdgpu_device *adev,
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 130/141 drm/amd/display: Limit user regamma to a valid value
In reply to Greg Kroah-HartmanFrom: Yao Wang1 <[email protected]>
[ Upstream commit 3601d620f22e37740cf73f8278eabf9f2aa19eb7 ]
[Why]
For HDR mode, we get total 512 tf_point and after switching to SDR mode we actually get 400 tf_point and the rest of points(401~512) still use dirty value from HDR mode. We should limit the rest of the points to max value.
[How]
Limit the value when coordinates_x.x > 1, just like what we do in translate_from_linear_space for other re-gamma build paths.
--- drivers/gpu/drm/amd/display/modules/color/color_gamma.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/amd/display/modules/color/color_gamma.c +4 -0
@@ -1524,6 +1524,7 @@ static void interpolate_user_regamma(uint32_t hw_points_num,struct fixed31_32 lut2;struct fixed31_32 delta_lut;struct fixed31_32 delta_index; +const struct fixed31_32 one =dc_fixpt_from_int (1 ); i =0 ;/* fixed_pt library has problems handling too small values */
@@ -1552,6 +1553,9 @@ static void interpolate_user_regamma(uint32_t hw_points_num, }else hw_x = coordinates_x[i].x; +if (dc_fixpt_le (one, hw_x)) + hw_x = one; + norm_x =dc_fixpt_mul (norm_factor, hw_x); index =dc_fixpt_floor (norm_x);if (index <0 || index >255 )
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 131/141 drm/amd/display: Mark dml30s UseMinimumDCFCLK() as noinline for stack usage
In reply to Greg Kroah-HartmanFrom: Nathan Chancellor <[email protected]>
[ Upstream commit 41012d715d5d7b9751ae84b8fb255e404ac9c5d0 ]
This function consumes a lot of stack space and it blows up the size of dml30_ModeSupportAndSystemConfigurationFull() with clang:
drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c:3542:6: error: stack frame size (2200) exceeds limit (2048) in 'dml30_ModeSupportAndSystemConfigurationFull' [-Werror,-Wframe-larger-than] void dml30_ModeSupportAndSystemConfigurationFull(struct display_mode_lib *mode_lib)
^
1 error generated.
Commit a0f7e7f759cf ("drm/amd/display: fix i386 frame size warning") aimed to address this for i386 but it did not help x86_64.
To reduce the amount of stack space that dml30_ModeSupportAndSystemConfigurationFull() uses, mark UseMinimumDCFCLK() as noinline, using the _for_stack variant for documentation. While this will increase the total amount of stack usage between the two functions (1632 and 1304 bytes respectively), it will make sure both stay below the limit of 2048 bytes for these files. The aforementioned change does help reduce UseMinimumDCFCLK()'s stack usage so it should not be reverted in favor of this change.
--- drivers/gpu/drm/amd/display/dc/dml/dcn30/display_mode_vba_30.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/gpu/drm/amd/display/dc/dml/dcn30/display_mode_vba_30.c +1 -2
@@ -6653,8 +6653,7 @@ static double CalculateUrgentLatency(return ret; } - -static void UseMinimumDCFCLK( +static noinline_for_stack void UseMinimumDCFCLK( struct display_mode_lib *mode_lib, int MaxInterDCNTileRepeaters, int MaxPrefetchMode,
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 132/141 drm/rockchip: Fix return type of cdn_dp_connector_mode_valid
In reply to Greg Kroah-HartmanFrom: Nathan Huckleberry <[email protected]>
[ Upstream commit b0b9408f132623dc88e78adb5282f74e4b64bb57 ]
The mode_valid field in drm_connector_helper_funcs is expected to be of type:
enum drm_mode_status (* mode_valid) (struct drm_connector *connector,
struct drm_display_mode *mode);
The mismatched return type breaks forward edge kCFI since the underlying function definition does not match the function hook definition.
The return type of cdn_dp_connector_mode_valid should be changed from int to enum drm_mode_status.
--- drivers/gpu/drm/rockchip/cdn-dp-core.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/rockchip/cdn-dp-core.c +3 -2
@@ -276,8 +276,9 @@ static int cdn_dp_connector_get_modes(struct drm_connector *connector)return ret; } -static int cdn_dp_connector_mode_valid (struct drm_connector *connector, -struct drm_display_mode *mode) +static enum drm_mode_status +cdn_dp_connector_mode_valid (struct drm_connector *connector, +struct drm_display_mode *mode) {struct cdn_dp_device *dp =connector_to_dp (connector);struct drm_display_info *display_info = &dp->connector.display_info;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 133/141 workqueue: dont skip lockdep work dependency in cancel_work_sync()
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
[ Upstream commit c0feea594e058223973db94c1c32a830c9807c86 ]
Like Hillf Danton mentioned
syzbot should have been able to catch cancel_work_sync() in work context by checking lockdep_map in __flush_work() for both flush and cancel.
in [1], being unable to report an obvious deadlock scenario shown below is broken. From locking dependency perspective, sync version of cancel request should behave as if flush request, for it waits for completion of work if that work has already started execution.
----------
#include <linux/module.h>
#include <linux/sched.h>
static DEFINE_MUTEX(mutex);
static void work_fn(struct work_struct *work)
{
schedule_timeout_uninterruptible(HZ / 5);
mutex_lock(&mutex);
mutex_unlock(&mutex);
}
static DECLARE_WORK(work, work_fn);
static int __init test_init(void)
{
schedule_work(&work);
schedule_timeout_uninterruptible(HZ / 10);
mutex_lock(&mutex);
cancel_work_sync(&work);
mutex_unlock(&mutex);
return -EINVAL;
}
module_init(test_init);
MODULE_LICENSE("GPL");
----------The check this patch restores was added by commit 0976dfc1d0cd80a4 ("workqueue: Catch more locking problems with flush_work()").
Then, lockdep's crossrelease feature was added by commit b09be676e0ff25bd ("locking/lockdep: Implement the 'crossrelease' feature"). As a result, this check was once removed by commit fd1a5b04dfb899f8 ("workqueue: Remove now redundant lock acquisitions wrt. workqueue flushes").
But lockdep's crossrelease feature was removed by commit e966eaeeb623f099 ("locking/lockdep: Remove the cross-release locking checks"). At this point, this check should have been restored.
Then, commit d6e89786bed977f3 ("workqueue: skip lockdep wq dependency in cancel_work_sync()") introduced a boolean flag in order to distinguish flush_work() and cancel_work_sync(), for checking "struct workqueue_struct" dependency when called from cancel_work_sync() was causing false positives.
Then, commit 87915adc3f0acdf0 ("workqueue: re-add lockdep dependencies for flushing") tried to restore "struct work_struct" dependency check, but by error checked this boolean flag. Like an example shown above indicates, "struct work_struct" dependency needs to be checked for both flush_work() and cancel_work_sync().
--- kernel/workqueue.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
kernel/workqueue.c +2 -4
@@ -3047,10 +3047,8 @@ static bool __flush_work(struct work_struct *work, bool from_cancel)if (WARN_ON (!work->func))return false; -if (!from_cancel) { -lock_map_acquire (&work->lockdep_map); -lock_map_release (&work->lockdep_map); - } +lock_map_acquire (&work->lockdep_map); +lock_map_release (&work->lockdep_map);if (start_flush_work (work, &barr, from_cancel)) {wait_for_completion (&barr.done);
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 134/141 i2c: imx: If pm_runtime_get_sync() returned 1 device access is possible
In reply to Greg Kroah-HartmanFrom: Uwe Kleine-König <[email protected]>
[ Upstream commit 085aacaa73163f4b8a89dec24ecb32cfacd34017 ]
pm_runtime_get_sync() returning 1 also means the device is powered. So resetting the chip registers in .remove() is possible and should be done.
--- drivers/i2c/busses/i2c-imx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-imx.c +1 -1
@@ -1289,7 +1289,7 @@ static int i2c_imx_remove(struct platform_device *pdev)if (i2c_imx->dma)i2c_imx_dma_free (i2c_imx); -if (ret ==0 ) { +if (ret >=0 ) {/* setup chip registers to defaults */ imx_i2c_write_reg (0 , i2c_imx,IMX_I2C_IADR );imx_i2c_write_reg (0 , i2c_imx,IMX_I2C_IFDR );
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 135/141 i2c: mlxbf: incorrect base address passed during io write
In reply to Greg Kroah-HartmanFrom: Asmaa Mnebhi <[email protected]>
[ Upstream commit 2a5be6d1340c0fefcee8a6489cff7fd88a0d5b85 ]
Correct the base address used during io write.
This bug had no impact over the overall functionality of the read and write transactions. MLXBF_I2C_CAUSE_OR_CLEAR=0x18 so writing to (smbus->io + 0x18) instead of (mst_cause->ioi + 0x18) actually writes to the sc_low_timeout register which just sets the timeout value before a read/write aborts.
--- drivers/i2c/busses/i2c-mlxbf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-mlxbf.c +1 -1
@@ -675,7 +675,7 @@ static int mlxbf_i2c_smbus_enable(struct mlxbf_i2c_priv *priv, u8 slave,/* Clear status bits. */ writel (0x0 , priv->smbus->io +MLXBF_I2C_SMBUS_MASTER_STATUS );/* Set the cause data. */ -writel (~0x0 , priv->smbus->io +MLXBF_I2C_CAUSE_OR_CLEAR ); +writel (~0x0 , priv->mst_cause->io +MLXBF_I2C_CAUSE_OR_CLEAR );/* Zero PEC byte. */ writel (0x0 , priv->smbus->io +MLXBF_I2C_SMBUS_MASTER_PEC );/* Zero byte count. */
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 136/141 i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
In reply to Greg Kroah-HartmanFrom: Asmaa Mnebhi <[email protected]>
[ Upstream commit de24aceb07d426b6f1c59f33889d6a964770547b ]
memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments.
--- drivers/i2c/busses/i2c-mlxbf.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/i2c/busses/i2c-mlxbf.c +3 -0
@@ -744,6 +744,9 @@ mlxbf_i2c_smbus_start_transaction(struct mlxbf_i2c_priv *priv,if (flags &MLXBF_I2C_F_WRITE ) { write_en =1 ; write_len += operation->length; +if (data_idx + operation->length > +MLXBF_I2C_MASTER_DATA_DESC_SIZE ) +return -ENOBUFS ;memcpy (data_desc + data_idx, operation->buffer, operation->length); data_idx += operation->length;
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 137/141 i2c: mlxbf: Fix frequency calculation
In reply to Greg Kroah-HartmanFrom: Asmaa Mnebhi <[email protected]>
[ Upstream commit 37f071ec327b04c83d47637c5e5c2199b39899ca ]
The i2c-mlxbf.c driver is currently broken because there is a bug in the calculation of the frequency. core_f, core_r and core_od are components read from hardware registers and are used to compute the frequency used to compute different timing parameters. The shifting mechanism used to get core_f, core_r and core_od is wrong. Use FIELD_GET to mask and shift the bitfields properly.
--- drivers/i2c/busses/i2c-mlxbf.c | 63 +++++++++++++--------------------- 1 file changed, 23 insertions(+), 40 deletions(-)
drivers/i2c/busses/i2c-mlxbf.c +23 -40
@@ -6,6 +6,7 @@*/ #include <linux/acpi.h> +#include <linux/bitfield.h> #include <linux/delay.h> #include <linux/err.h> #include <linux/interrupt.h>
@@ -63,13 +64,14 @@*/ #define MLXBF_I2C_TYU_PLL_OUT_FREQ (400 * 1000 * 1000)/* Reference clock for Bluefield - 156 MHz. */ -#define MLXBF_I2C_PLL_IN_FREQ (156 * 1000 * 1000) +#define MLXBF_I2C_PLL_IN_FREQ 156250000ULL/* Constant used to determine the PLL frequency. */ -#define MLNXBF_I2C_COREPLL_CONST 16384 +#define MLNXBF_I2C_COREPLL_CONST 16384ULL + +#define MLXBF_I2C_FREQUENCY_1GHZ 1000000000ULL/* PLL registers. */ -#define MLXBF_I2C_CORE_PLL_REG0 0x0#define MLXBF_I2C_CORE_PLL_REG1 0x4#define MLXBF_I2C_CORE_PLL_REG2 0x8
@@ -187,22 +189,15 @@ enum {#define MLXBF_I2C_COREPLL_FREQ MLXBF_I2C_TYU_PLL_OUT_FREQ/* Core PLL TYU configuration. */ -#define MLXBF_I2C_COREPLL_CORE_F_TYU_MASK GENMASK(12, 0) -#define MLXBF_I2C_COREPLL_CORE_OD_TYU_MASK GENMASK(3, 0) -#define MLXBF_I2C_COREPLL_CORE_R_TYU_MASK GENMASK(5, 0) - -#define MLXBF_I2C_COREPLL_CORE_F_TYU_SHIFT 3 -#define MLXBF_I2C_COREPLL_CORE_OD_TYU_SHIFT 16 -#define MLXBF_I2C_COREPLL_CORE_R_TYU_SHIFT 20 +#define MLXBF_I2C_COREPLL_CORE_F_TYU_MASK GENMASK(15, 3) +#define MLXBF_I2C_COREPLL_CORE_OD_TYU_MASK GENMASK(19, 16) +#define MLXBF_I2C_COREPLL_CORE_R_TYU_MASK GENMASK(25, 20)/* Core PLL YU configuration. */ #define MLXBF_I2C_COREPLL_CORE_F_YU_MASK GENMASK(25, 0)#define MLXBF_I2C_COREPLL_CORE_OD_YU_MASK GENMASK(3, 0) -#define MLXBF_I2C_COREPLL_CORE_R_YU_MASK GENMASK(5, 0) +#define MLXBF_I2C_COREPLL_CORE_R_YU_MASK GENMASK(31, 26) -#define MLXBF_I2C_COREPLL_CORE_F_YU_SHIFT 0 -#define MLXBF_I2C_COREPLL_CORE_OD_YU_SHIFT 1 -#define MLXBF_I2C_COREPLL_CORE_R_YU_SHIFT 26/* Core PLL frequency. */ static u64 mlxbf_i2c_corepll_frequency;
@@ -485,8 +480,6 @@ static struct mutex mlxbf_i2c_bus_lock;#define MLXBF_I2C_MASK_8 GENMASK(7, 0)#define MLXBF_I2C_MASK_16 GENMASK(15, 0) -#define MLXBF_I2C_FREQUENCY_1GHZ 1000000000 -/* * Function to poll a set of bits at a specific address; it checks whether * the bits are equal to zero when eq_zero is set to 'true', and not equal
@@ -1416,24 +1409,19 @@ static int mlxbf_i2c_init_master(struct platform_device *pdev,return 0 ; } -static u64 mlxbf_calculate_freq_from_tyu (struct mlxbf_i2c_resource *corepll_res) +static u64 mlxbf_i2c_calculate_freq_from_tyu (struct mlxbf_i2c_resource *corepll_res) { -u64 core_frequency, pad_frequency; +u64 core_frequency;u8 core_od, core_r;u32 corepll_val;u16 core_f; - pad_frequency =MLXBF_I2C_PLL_IN_FREQ ; - corepll_val =readl (corepll_res->io +MLXBF_I2C_CORE_PLL_REG1 );/* Get Core PLL configuration bits. */ - core_f =rol32 (corepll_val,MLXBF_I2C_COREPLL_CORE_F_TYU_SHIFT ) & -MLXBF_I2C_COREPLL_CORE_F_TYU_MASK ; - core_od =rol32 (corepll_val,MLXBF_I2C_COREPLL_CORE_OD_TYU_SHIFT ) & -MLXBF_I2C_COREPLL_CORE_OD_TYU_MASK ; - core_r =rol32 (corepll_val,MLXBF_I2C_COREPLL_CORE_R_TYU_SHIFT ) & -MLXBF_I2C_COREPLL_CORE_R_TYU_MASK ; + core_f =FIELD_GET (MLXBF_I2C_COREPLL_CORE_F_TYU_MASK , corepll_val); + core_od =FIELD_GET (MLXBF_I2C_COREPLL_CORE_OD_TYU_MASK , corepll_val); + core_r =FIELD_GET (MLXBF_I2C_COREPLL_CORE_R_TYU_MASK , corepll_val);/* * Compute PLL output frequency as follow:
@@ -1445,31 +1433,26 @@ static u64 mlxbf_calculate_freq_from_tyu(struct mlxbf_i2c_resource *corepll_res)* Where PLL_OUT_FREQ and PLL_IN_FREQ refer to CoreFrequency * and PadFrequency, respectively. */ - core_frequency = pad_frequency * (++core_f); + core_frequency =MLXBF_I2C_PLL_IN_FREQ * (++core_f); core_frequency /= (++core_r) * (++core_od);return core_frequency; } -static u64 mlxbf_calculate_freq_from_yu (struct mlxbf_i2c_resource *corepll_res) +static u64 mlxbf_i2c_calculate_freq_from_yu (struct mlxbf_i2c_resource *corepll_res) {u32 corepll_reg1_val, corepll_reg2_val; -u64 corepll_frequency, pad_frequency; +u64 corepll_frequency;u8 core_od, core_r;u32 core_f; - pad_frequency =MLXBF_I2C_PLL_IN_FREQ ; - corepll_reg1_val =readl (corepll_res->io +MLXBF_I2C_CORE_PLL_REG1 ); corepll_reg2_val =readl (corepll_res->io +MLXBF_I2C_CORE_PLL_REG2 );/* Get Core PLL configuration bits */ - core_f =rol32 (corepll_reg1_val,MLXBF_I2C_COREPLL_CORE_F_YU_SHIFT ) & -MLXBF_I2C_COREPLL_CORE_F_YU_MASK ; - core_r =rol32 (corepll_reg1_val,MLXBF_I2C_COREPLL_CORE_R_YU_SHIFT ) & -MLXBF_I2C_COREPLL_CORE_R_YU_MASK ; - core_od =rol32 (corepll_reg2_val,MLXBF_I2C_COREPLL_CORE_OD_YU_SHIFT ) & -MLXBF_I2C_COREPLL_CORE_OD_YU_MASK ; + core_f =FIELD_GET (MLXBF_I2C_COREPLL_CORE_F_YU_MASK , corepll_reg1_val); + core_r =FIELD_GET (MLXBF_I2C_COREPLL_CORE_R_YU_MASK , corepll_reg1_val); + core_od =FIELD_GET (MLXBF_I2C_COREPLL_CORE_OD_YU_MASK , corepll_reg2_val);/* * Compute PLL output frequency as follow:
@@ -1481,7 +1464,7 @@ static u64 mlxbf_calculate_freq_from_yu(struct mlxbf_i2c_resource *corepll_res)* Where PLL_OUT_FREQ and PLL_IN_FREQ refer to CoreFrequency * and PadFrequency, respectively. */ - corepll_frequency = (pad_frequency * core_f) /MLNXBF_I2C_COREPLL_CONST ; + corepll_frequency = (MLXBF_I2C_PLL_IN_FREQ * core_f) /MLNXBF_I2C_COREPLL_CONST ; corepll_frequency /= (++core_r) * (++core_od);return corepll_frequency;
@@ -2189,14 +2172,14 @@ static struct mlxbf_i2c_chip_info mlxbf_i2c_chip[] = { [1] = &mlxbf_i2c_corepll_res[MLXBF_I2C_CHIP_TYPE_1], [2 ] = &mlxbf_i2c_gpio_res[MLXBF_I2C_CHIP_TYPE_1 ] }, - .calculate_freq = mlxbf_calculate_freq_from_tyu + .calculate_freq = mlxbf_i2c_calculate_freq_from_tyu }, [MLXBF_I2C_CHIP_TYPE_2] = { .type = MLXBF_I2C_CHIP_TYPE_2, .shared_res = { [0 ] = &mlxbf_i2c_corepll_res[MLXBF_I2C_CHIP_TYPE_2 ] }, - .calculate_freq = mlxbf_calculate_freq_from_yu + .calculate_freq = mlxbf_i2c_calculate_freq_from_yu } };
Signature · 1 line
2.35.1
Greg Kroah-Hartman
maintainerPATCH 138/141 devdax: Fix soft-reservation memory description
In reply to Greg Kroah-HartmanFrom: Dan Williams <[email protected]>
commit 67feaba413ec68daf4124e9870878899b4ed9a0e upstream.
The "hmem" platform-devices that are created to represent the platform-advertised "Soft Reserved" memory ranges end up inserting a resource that causes the iomem_resource tree to look like this:
340000000-43fffffff : hmem.0
340000000-43fffffff : Soft Reserved
340000000-43fffffff : dax0.0
This is because insert_resource() reparents ranges when they completely intersect an existing range.
This matters because code that uses region_intersects() to scan for a given IORES_DESC will only check that top-level 'hmem.0' resource and not the 'Soft Reserved' descendant.
So, to support EINJ (via einj_error_inject()) to inject errors into memory hosted by a dax-device, be sure to describe the memory as IORES_DESC_SOFT_RESERVED. This is a follow-on to:
commit b13a3e5fd40b ("ACPI: APEI: Fix _EINJ vs EFI_MEMORY_SP")
...that fixed EINJ support for "Soft Reserved" ranges in the first instance.
--- drivers/dax/hmem/device.c | 1 + 1 file changed, 1 insertion(+)
drivers/dax/hmem/device.c +1 -0
@@ -15,6 +15,7 @@ void hmem_register_device(int target_nid .start = r->start, .end = r->end, .flags = IORESOURCE_MEM, + .desc = IORES_DESC_SOFT_RESERVED, };struct platform_device *pdev;struct memregion_info info;
Greg Kroah-Hartman
maintainerPATCH 139/141 ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0
In reply to Greg Kroah-HartmanFrom: Luís Henriques <[email protected]>
commit 29a5b8a137ac8eb410cc823653a29ac0e7b7e1b0 upstream.
When walking through an inode extents, the ext4_ext_binsearch_idx() function assumes that the extent header has been previously validated. However, there are no checks that verify that the number of entries (eh->eh_entries) is non-zero when depth is > 0. And this will lead to problems because the EXT_FIRST_INDEX() and EXT_LAST_INDEX() will return garbage and result in this:
[ 135.245946] ------------[ cut here ]------------ [ 135.247579] kernel BUG at fs/ext4/extents.c:2258! [ 135.249045] invalid opcode: 0000 [#1] PREEMPT SMP [ 135.250320] CPU: 2 PID: 238 Comm: tmp118 Not tainted 5.19.0-rc8+ #4 [ 135.252067] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 135.255065] RIP: 0010:ext4_ext_map_blocks+0xc20/0xcb0 [ 135.256475] Code: [ 135.261433] RSP: 0018:ffffc900005939f8 EFLAGS: 00010246 [ 135.262847] RAX: 0000000000000024 RBX: ffffc90000593b70 RCX: 0000000000000023 [ 135.264765] RDX: ffff8880038e5f10 RSI: 0000000000000003 RDI: ffff8880046e922c [ 135.266670] RBP: ffff8880046e9348 R08: 0000000000000001 R09: ffff888002ca580c [ 135.268576] R10: 0000000000002602 R11: 0000000000000000 R12: 0000000000000024 [ 135.270477] R13: 0000000000000000 R14: 0000000000000024 R15: 0000000000000000 [ 135.272394] FS: 00007fdabdc56740(0000) GS:ffff88807dd00000(0000) knlGS:0000000000000000 [ 135.274510] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 135.276075] CR2: 00007ffc26bd4f00 CR3: 0000000006261004 CR4: 0000000000170ea0 [ 135.277952] Call Trace: [ 135.278635] <TASK> [ 135.279247] ? preempt_count_add+0x6d/0xa0 [ 135.280358] ? percpu_counter_add_batch+0x55/0xb0 [ 135.281612] ? _raw_read_unlock+0x18/0x30 [ 135.282704] ext4_map_blocks+0x294/0x5a0 [ 135.283745] ? xa_load+0x6f/0xa0 [ 135.284562] ext4_mpage_readpages+0x3d6/0x770 [ 135.285646] read_pages+0x67/0x1d0 [ 135.286492] ? folio_add_lru+0x51/0x80 [ 135.287441] page_cache_ra_unbounded+0x124/0x170 [ 135.288510] filemap_get_pages+0x23d/0x5a0 [ 135.289457] ? path_openat+0xa72/0xdd0 [ 135.290332] filemap_read+0xbf/0x300 [ 135.291158] ? _raw_spin_lock_irqsave+0x17/0x40 [ 135.292192] new_sync_read+0x103/0x170 [ 135.293014] vfs_read+0x15d/0x180 [ 135.293745] ksys_read+0xa1/0xe0 [ 135.294461] do_syscall_64+0x3c/0x80 [ 135.295284] entry_SYSCALL_64_after_hwframe+0x46/0xb0
This patch simply adds an extra check in __ext4_ext_check(), verifying that eh_entries is not 0 when eh_depth is > 0.
--- fs/ext4/extents.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/ext4/extents.c +4 -0
@@ -459,6 +459,10 @@ static int __ext4_ext_check(const char * error_msg ="invalid eh_entries" ; goto corrupted; } +if (unlikely ((eh->eh_entries ==0 ) && (depth >0 ))) { + error_msg ="eh_entries is 0 but eh_depth is > 0" ; + goto corrupted; + }if (!ext4_valid_extent_entries (inode, eh, lblk, &pblk, depth)) { error_msg ="invalid extent entries" ; goto corrupted;
Greg Kroah-Hartman
maintainerPATCH 140/141 ext4: limit the number of retries after discarding preallocations blocks
In reply to Greg Kroah-HartmanFrom: Theodore Ts'o <[email protected]>
commit 80fa46d6b9e7b1527bfd2197d75431fd9c382161 upstream.
This patch avoids threads live-locking for hours when a large number threads are competing over the last few free extents as they blocks getting added and removed from preallocation pools. From our bug reporter:
A reliable way for triggering this has multiple writers continuously write() to files when the filesystem is full, while small amounts of space are freed (e.g. by truncating a large file -1MiB at a time). In the local filesystem, this can be done by simply not checking the return code of write (0) and/or the error (ENOSPACE) that is set. Over NFS with an async mount, even clients with proper error checking will behave this way since the linux NFS client implementation will not propagate the server errors [the write syscalls immediately return success] until the file handle is closed. This leads to a situation where NFS clients send a continuous stream of WRITE rpcs which result in ERRNOSPACE -- but since the client isn't seeing this, the stream of writes continues at maximum network speed.
When some space does appear, multiple writers will all attempt to claim it for their current write. For NFS, we may see dozens to hundreds of threads that do this.
The real-world scenario of this is database backup tooling (in particular, github.com/mdkent/percona-xtrabackup) which may write large files (>1TiB) to NFS for safe keeping. Some temporary files are written, rewound, and read back -- all before closing the file handle (the temp file is actually unlinked, to trigger automatic deletion on close/crash.) An application like this operating on an async NFS mount will not see an error code until TiB have been written/read.
The lockup was observed when running this database backup on large filesystems (64 TiB in this case) with a high number of block groups and no free space. Fragmentation is generally not a factor in this filesystem (~thousands of large files, mostly contiguous except for the parts written while the filesystem is at capacity.)
--- fs/ext4/mballoc.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
fs/ext4/mballoc.c +3 -1
@@ -4959,6 +4959,7 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_text4_fsblk_t block =0 ;unsigned int inquota =0 ;unsigned int reserv_clstrs =0 ; +int retries =0 ;u64 seq;might_sleep ();
@@ -5061,7 +5062,8 @@ repeat: ar->len = ac->ac_b_ex.fe_len; } }else { -if (ext4_mb_discard_preallocations_should_retry (sb, ac, &seq)) +if (++retries <3 && +ext4_mb_discard_preallocations_should_retry (sb, ac, &seq)) goto repeat;/* * If block allocation fails then the pa allocated above
Greg Kroah-Hartman
maintainerPATCH 141/141 ext4: make directory inode spreading reflect flexbg size
In reply to Greg Kroah-HartmanFrom: Jan Kara <[email protected]>
commit 613c5a85898d1cd44e68f28d65eccf64a8ace9cf upstream.
Currently the Orlov inode allocator searches for free inodes for a directory only in flex block groups with at most inodes_per_group/16 more directory inodes than average per flex block group. However with growing size of flex block group this becomes unnecessarily strict. Scale allowed difference from average directory count per flex block group with flex block group size as we do with other metrics.
--- fs/ext4/ialloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/ialloc.c +1 -1
@@ -508,7 +508,7 @@ static int find_group_orlov(struct super goto fallback; } - max_dirs = ndirs / ngroups + inodes_per_group /16 ; + max_dirs = ndirs / ngroups + inodes_per_group*flex_size /16 ; min_inodes = avefreei - inodes_per_group*flex_size /4 ;if (min_inodes <1 ) min_inodes =1 ;
Hi!
Quoted 4 lines
This is the start of the stable review cycle for the 5.10.146 release. There are 141 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.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y
Best regards,
Pavel
Signature · 2 lines
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.146 release. There are 141 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, 28 Sep 2022 10:07:26 +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.146-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
Following build warnings / errors noticed on arm and powerpc on stable-rc 5.10
Regressions found on arm:
- build-gcc-12-ixp4xx_defconfig
- build-gcc-8-ixp4xx_defconfig
- build-gcc-11-ixp4xx_defconfig
- build-gcc-9-ixp4xx_defconfig
- build-gcc-10-ixp4xx_defconfig
arm build errors:
-----------------
drivers/gpio/gpio-ixp4xx.c:171:18: error: 'IRQCHIP_IMMUTABLE' undeclared here (not in a function); did you mean 'IS_IMMUTABLE'?
171 | .flags = IRQCHIP_IMMUTABLE,
| ^~~~~~~~~~~~~~~~~
| IS_IMMUTABLE
drivers/gpio/gpio-ixp4xx.c:172:9: error:
'GPIOCHIP_IRQ_RESOURCE_HELPERS' undeclared here (not in a function)
172 | GPIOCHIP_IRQ_RESOURCE_HELPERS,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~drivers/gpio/gpio-ixp4xx.c:172:9: warning: excess elements in struct initializer drivers/gpio/gpio-ixp4xx.c:172:9: note: (near initialization for 'ixp4xx_gpio_irqchip')drivers/gpio/gpio-ixp4xx.c: In function 'ixp4xx_gpio_probe':drivers/gpio/gpio-ixp4xx.c:296:9: error: implicit declaration of function 'gpio_irq_chip_set_chip' [-Werror=implicit-function-declaration]
296 | gpio_irq_chip_set_chip(girq, &ixp4xx_gpio_irqchip);
| ^~~~~~~~~~~~~~~~~~~~~~cc1: some warnings being treated as errors
Error was caused by below patch
gpio: ixp4xx: Make irqchip immutable
[ Upstream commit 94e9bc73d85aa6ecfe249e985ff57abe0ab35f34 ]
This turns the IXP4xx GPIO irqchip into an immutable irqchip, a bit different from the standard template due to being hierarchical.
Tested on the IXP4xx which uses drivers/ata/pata_ixp4xx_cf.c for a rootfs on compact flash with IRQs from this GPIO block to the CF ATA controller.
net/core/dev_ioctl.c: In function 'dev_ifconf':net/core/dev_ioctl.c:41:13: warning: unused variable 'i' [-Wunused-variable]
41 | int i;
| ^
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1832: drivers] Error 2
warning is caused by:
net: socket: remove register_gifconf
[ Upstream commit b0e99d03778b2418aec20db99d97d19d25d198b6 ]
Since dynamic registration of the gifconf() helper is only used for IPv4, and this can not be in a loadable module, this can be simplified noticeably by turning it into a direct function call as a preparation for cleaning up the compat handling.
Stable-dep-of: 5641c751fe2f ("net: enetc: deny offload of tc-based TSN features on VF interfaces")
--
Linaro LKFT
https://lkft.linaro.org
Greg Kroah-Hartman
maintainerQuoted 93 lines · Naresh Kamboju
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.10.146 release. There are 141 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, 28 Sep 2022 10:07:26 +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.146-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
Following build warnings / errors noticed on arm and powerpc on stable-rc 5.10
Regressions found on arm:
- build-gcc-12-ixp4xx_defconfig
- build-gcc-8-ixp4xx_defconfig
- build-gcc-11-ixp4xx_defconfig
- build-gcc-9-ixp4xx_defconfig
- build-gcc-10-ixp4xx_defconfigarm build errors:
-----------------
drivers/gpio/gpio-ixp4xx.c:171:18: error: 'IRQCHIP_IMMUTABLE' undeclared here (not in a function); did you mean 'IS_IMMUTABLE'?171 | .flags = IRQCHIP_IMMUTABLE, | ^~~~~~~~~~~~~~~~~ | IS_IMMUTABLE drivers/gpio/gpio-ixp4xx.c:172:9: error: 'GPIOCHIP_IRQ_RESOURCE_HELPERS' undeclared here (not in a function) 172 | GPIOCHIP_IRQ_RESOURCE_HELPERS, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpio/gpio-ixp4xx.c:172:9: warning: excess elements in struct initializerdrivers/gpio/gpio-ixp4xx.c:172:9: note: (near initialization for 'ixp4xx_gpio_irqchip')drivers/gpio/gpio-ixp4xx.c: In function 'ixp4xx_gpio_probe':drivers/gpio/gpio-ixp4xx.c:296:9: error: implicit declaration of function 'gpio_irq_chip_set_chip' [-Werror=implicit-function-declaration]296 | gpio_irq_chip_set_chip(girq, &ixp4xx_gpio_irqchip); | ^~~~~~~~~~~~~~~~~~~~~~cc1: some warnings being treated as errors
Error was caused by below patch
gpio: ixp4xx: Make irqchip immutable
[ Upstream commit94e9bc73d85aa6ecfe249e985ff57abe0ab35f34]This turns the IXP4xx GPIO irqchip into an immutable irqchip, a bit different from the standard template due to being hierarchical.
Tested on the IXP4xx which uses
drivers/ata/pata_ixp4xx_cf.cfor a rootfs on compact flash with IRQs from this GPIO block to the CF ATA controller.Cc Marc Zyngier <[email protected]>Signed-off-by Linus Walleij <[email protected]>Acked-by Marc Zyngier <[email protected]>Signed-off-by Bartosz Golaszewski <[email protected]>Signed-off-by Sasha Levin <[email protected]>
net/core/dev_ioctl.c: In function 'dev_ifconf':net/core/dev_ioctl.c:41:13: warning: unused variable 'i' [-Wunused-variable]
41 | int i;
| ^
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:1832: drivers] Error 2warning is caused by:
net: socket: removeregister_gifconf
[ Upstream commitb0e99d03778b2418aec20db99d97d19d25d198b6]Since dynamic registration of the
gifconf()helper is only used for IPv4, and this can not be in a loadable module, this can be simplified noticeably by turning it into a direct function call as a preparation for cleaning up the compat handling.
Quoted 6 lines
Signed-off-by Arnd Bergmann <[email protected]>Reviewed-by Christoph Hellwig <[email protected]>Signed-off-by David S. Miller <[email protected]>Stable-dep-of:
5641c751fe2f("net: enetc: deny offload of tc-based TSN features on VF interfaces")Signed-off-by Sasha Levin <[email protected]>
Now dropped thanks. I'll do a -rc2 soon.
greg k-h