6.1.66-rc1 review
Subsystems (6)
Greg Kroah-Hartman
maintainercover 6.1.66-rc1 review
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +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/v6.x/stable-review/patch-6.1.66-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-6.1.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 6.1.66-rc1
Koichiro Den <[email protected]>
x86/apic/msi: Fix misconfigured non-maskable MSI quirk
Juergen Gross <[email protected]>
x86/xen: fix percpu vcpu_info allocation
Juergen Gross <[email protected]>
xen: simplify evtchn_do_upcall() call maze
David Woodhouse <[email protected]>
xen: Allow platform PCI interrupt to be shared
Heiner Kallweit <[email protected]>
r8169: fix deadlock on RTL8125 in jumbo mtu mode
Heiner Kallweit <[email protected]>
r8169: disable ASPM in case of tx timeout
Ilya Bakoulin <[email protected]>
drm/amd/display: Fix MPCC 1DLUT programming
Harry Wentland <[email protected]>
drm/amd/display: Fix the delta clamping for shaper LUT
Melissa Wen <[email protected]>
drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut
Rodrigo Siqueira <[email protected]>
drm/amd/display: Expand kernel doc for DC
Wenchao Chen <[email protected]>
mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled
Heiner Kallweit <[email protected]>
mmc: core: add helpers mmc_regulator_enable/disable_vqmmc
Dinghao Liu <[email protected]>
drm/amd/pm: fix a memleak in aldebaran_tables_init
Lu Baolu <[email protected]>
iommu/vt-d: Make context clearing consistent with context mapping
Lu Baolu <[email protected]>
iommu/vt-d: Disable PCI ATS in legacy passthrough mode
Lu Baolu <[email protected]>
iommu/vt-d: Add device_block_translation() helper
Lu Baolu <[email protected]>
iommu/vt-d: Allocate pasid table in device probe path
Lu Baolu <[email protected]>
iommu/vt-d: Omit devTLB invalidation requests when TES=0
Christoph Niedermaier <[email protected]>
cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily
Christoph Niedermaier <[email protected]>
cpufreq: imx6q: don't warn for disabling a non-existing frequency
Nicholas Kazlauskas <[email protected]>
drm/amd/display: Guard against invalid RPTR/WPTR being set
JinZe.Xu <[email protected]>
drm/amd/display: Restore rptr/wptr for DMCUB as workaround
Mark Hasemeyer <[email protected]>
spi: Fix null dereference on suspend
Alexandre Ghiti <[email protected]>
drivers: perf: Check find_first_bit() return value
Helge Deller <[email protected]>
fbdev: stifb: Make the STI next font pointer a 32-bit signed offset
Manivannan Sadhasivam <[email protected]>
PCI: qcom-ep: Add dedicated callback for writing to DBI2 registers
Heiko Carstens <[email protected]>
s390/cmma: fix handling of swapper_pg_dir and invalid_pg_dir
Gaurav Batra <[email protected]>
powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
Lukas Wunner <[email protected]>
PCI: Lengthen reset delay for VideoPropulsion Torrent QN16e card
Haitao Shan <[email protected]>
KVM: x86: Fix lapic timer interrupt lost after loading a snapshot.
Claudiu Beznea <[email protected]>
net: ravb: Keep reverse order of operations in ravb_remove()
Claudiu Beznea <[email protected]>
net: ravb: Stop DMA in case of failures on ravb_open()
Claudiu Beznea <[email protected]>
net: ravb: Start TX queues after HW initialization succeeded
Claudiu Beznea <[email protected]>
net: ravb: Make write access to CXR35 first before accessing other EMAC registers
Claudiu Beznea <[email protected]>
net: ravb: Use pm_runtime_resume_and_get()
Claudiu Beznea <[email protected]>
net: ravb: Check return value of reset_control_deassert()
Yoshihiro Shimoda <[email protected]>
ravb: Fix races between ravb_tx_timeout_work() and net related ops
Heiner Kallweit <[email protected]>
r8169: prevent potential deadlock in rtl8169_close
Subbaraya Sundeep <[email protected]>
octeontx2-pf: Restore TC ingress police rules when interface is up
Suman Ghosh <[email protected]>
octeontx2-af: Install TC filter rules in hardware based on priority
Geetha sowjanya <[email protected]>
octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64
Furong Xu <[email protected]>
net: stmmac: xgmac: Disable FPE MMC interrupts
Elena Salomatkina <[email protected]>
octeontx2-af: Fix possible buffer overflow
Willem de Bruijn <[email protected]>
selftests/net: mptcp: fix uninitialized variable warnings
Willem de Bruijn <[email protected]>
selftests/net: unix: fix unused variable compiler warning
Willem de Bruijn <[email protected]>
selftests/net: fix a char signedness issue
Willem de Bruijn <[email protected]>
selftests/net: ipsec: fix constant out of range
Dmitry Antipov <[email protected]>
uapi: propagate __struct_group() attributes to the container union
Ioana Ciornei <[email protected]>
dpaa2-eth: increase the needed headroom to account for alignment
Zhengchao Shao <[email protected]>
ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet
Niklas Neronin <[email protected]>
usb: config: fix iteration issue in 'usb_get_bos_descriptor()'
Alan Stern <[email protected]>
USB: core: Change configuration warnings to notices
Johan Hovold <[email protected]>
USB: xhci-plat: fix legacy PHY double init
Johannes Berg <[email protected]>
wifi: cfg80211: fix CQM for non-range use
Hugo Villeneuve <[email protected]>
serial: sc16is7xx: add missing support for rs485 devicetree properties
Hui Wang <[email protected]>
serial: sc16is7xx: Put IOControl register into regmap_volatile
Hugo Villeneuve <[email protected]>
auxdisplay: hd44780: move cursor home after clear display command
Max Nguyen <[email protected]>
Input: xpad - add HyperX Clutch Gladiate Support
David Sterba <[email protected]>
btrfs: fix 64bit compat send ioctl arguments not initializing version member
Filipe Manana <[email protected]>
btrfs: make error messages more clear when getting a chunk map
Jann Horn <[email protected]>
btrfs: send: ensure send_fd is writable
Filipe Manana <[email protected]>
btrfs: fix off-by-one when checking chunk map includes logical address
Bragatheswaran Manickavel <[email protected]>
btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
Qu Wenruo <[email protected]>
btrfs: add dmesg output for first mount and last unmount of a filesystem
Helge Deller <[email protected]>
parisc: Mark altinstructions read-only and 32-bit aligned
Helge Deller <[email protected]>
parisc: Ensure 32-bit alignment on parisc unwind section
Helge Deller <[email protected]>
parisc: Mark jump_table naturally aligned
Helge Deller <[email protected]>
parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes
Helge Deller <[email protected]>
parisc: Mark lock_aligned variables 16-byte aligned on SMP
Helge Deller <[email protected]>
parisc: Use natural CPU alignment for bug_table
Helge Deller <[email protected]>
parisc: Mark ex_table entries 32-bit aligned in uaccess.h
Helge Deller <[email protected]>
parisc: Mark ex_table entries 32-bit aligned in assembly.h
Timothy Pearson <[email protected]>
powerpc: Don't clobber f0/vs0 during fp|altivec register save
Nicholas Piggin <[email protected]>
KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers
Abdul Halim, Mohd Syazwan <[email protected]>
iommu/vt-d: Add MTL to quirk list to skip TE disabling
Markus Weippert <[email protected]>
bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
Christian König <[email protected]>
dma-buf: fix check in dma_resv_add_fence
Gautham R. Shenoy <[email protected]>
cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch()
Lukasz Luba <[email protected]>
powercap: DTPM: Fix unneeded conversions to micro-Watts
Ewan D. Milne <[email protected]>
nvme: check for valid nvme_identify_ns() before using it
Wu Bo <[email protected]>
dm verity: don't perform FEC for failed readahead IO
Wu Bo <[email protected]>
dm verity: initialize fec io before freeing it
Hamza Mahfooz <[email protected]>
drm/amd/display: fix ABM disablement
Nicholas Kazlauskas <[email protected]>
drm/amd/display: Update min Z8 residency time to 2100 for DCN314
Alvin Lee <[email protected]>
drm/amd/display: Use DRAM speed from validation for dummy p-state
Nicholas Kazlauskas <[email protected]>
drm/amd/display: Remove min_dst_y_next_start check for Z8
Alvin Lee <[email protected]>
drm/amd/display: Include udelay when waiting for INBOX0 ACK
Alex Sierra <[email protected]>
drm/amdgpu: Force order between a read and write to the same address
Mario Limonciello <[email protected]>
drm/amd: Enable PCIe PME from D3
Damien Le Moal <[email protected]>
scsi: sd: Fix system start for ATA devices
Damien Le Moal <[email protected]>
scsi: Change SCSI device boolean fields to single bit flags
Mikulas Patocka <[email protected]>
dm-verity: align struct dm_verity_fec_io properly
Kailang Yang <[email protected]>
ALSA: hda/realtek: Add supported ALC257 for ChromeOS
Kailang Yang <[email protected]>
ALSA: hda/realtek: Headset Mic VREF to 100%
Takashi Iwai <[email protected]>
ALSA: hda: Disable power-save on KONTRON SinglePC
Adrian Hunter <[email protected]>
mmc: block: Be sure to wait while busy in CQE error recovery
Adrian Hunter <[email protected]>
mmc: block: Do not lose cache flush during CQE error recovery
Adrian Hunter <[email protected]>
mmc: block: Retry commands in CQE error recovery
Adrian Hunter <[email protected]>
mmc: cqhci: Fix task clearing in CQE error recovery
Adrian Hunter <[email protected]>
mmc: cqhci: Warn of halt or task clear failure
Adrian Hunter <[email protected]>
mmc: cqhci: Increase recovery halt timeout
Kornel Dulęba <[email protected]>
mmc: sdhci-pci-gli: Disable LPM during initialization
Yang Yingliang <[email protected]>
firewire: core: fix possible memory leak in create_units()
Maria Yu <[email protected]>
pinctrl: avoid reload of p state in list iteration
Paulo Alcantara <[email protected]>
smb: client: report correct st_size for SMB and NFS symlinks
David Howells <[email protected]>
cifs: Fix FALLOC_FL_INSERT_RANGE by setting i_size after EOF moved
David Howells <[email protected]>
cifs: Fix FALLOC_FL_ZERO_RANGE by setting i_size if EOF moved
-------------
Diffstat:
Makefile | 4 +- arch/arm/xen/enlighten.c | 2 +- arch/parisc/include/asm/alternative.h | 9 +- arch/parisc/include/asm/assembly.h | 1 + arch/parisc/include/asm/bug.h | 30 +- arch/parisc/include/asm/jump_label.h | 8 +- arch/parisc/include/asm/ldcw.h | 2 +- arch/parisc/include/asm/uaccess.h | 1 + arch/parisc/include/uapi/asm/errno.h | 2 - arch/parisc/kernel/vmlinux.lds.S | 1 + arch/powerpc/kernel/fpu.S | 13 + arch/powerpc/kernel/process.c | 6 +- arch/powerpc/kernel/vector.S | 2 + arch/powerpc/platforms/pseries/iommu.c | 8 +- arch/s390/mm/page-states.c | 6 + arch/x86/entry/common.c | 2 +- arch/x86/include/asm/kvm-x86-ops.h | 1 + arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kernel/apic/msi.c | 8 +- arch/x86/kvm/lapic.c | 4 + arch/x86/kvm/vmx/vmx.c | 4 +- arch/x86/xen/enlighten.c | 8 +- arch/x86/xen/enlighten_hvm.c | 2 +- arch/x86/xen/xen-ops.h | 2 +- drivers/ata/libata-scsi.c | 9 +- drivers/auxdisplay/hd44780_common.c | 10 +- drivers/cpufreq/amd-pstate.c | 4 +- drivers/cpufreq/imx6q-cpufreq.c | 32 +- drivers/dma-buf/dma-resv.c | 2 +- drivers/firewire/core-device.c | 11 +- drivers/firewire/sbp2.c | 6 +- drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 2 + drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 8 + drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 8 +- drivers/gpu/drm/amd/display/dc/dc.h | 19 +- drivers/gpu/drm/amd/display/dc/dc_stream.h | 11 + .../gpu/drm/amd/display/dc/dcn10/dcn10_cm_common.c | 19 +- .../gpu/drm/amd/display/dc/dcn10/dcn10_cm_common.h | 1 + .../drm/amd/display/dc/dcn10/dcn10_hw_sequencer.c | 2 +- drivers/gpu/drm/amd/display/dc/dcn20/dcn20_hwseq.c | 6 +- .../gpu/drm/amd/display/dc/dcn30/dcn30_dwb_cm.c | 2 +- drivers/gpu/drm/amd/display/dc/dcn30/dcn30_hwseq.c | 37 +- .../drm/amd/display/dc/dcn314/dcn314_resource.c | 2 +- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c | 8 +- drivers/gpu/drm/amd/display/dc/dml/dc_features.h | 7 + .../gpu/drm/amd/display/dc/dml/dcn20/dcn20_fpu.c | 15 +- .../gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c | 3 +- .../drm/amd/display/dc/dml/display_mode_enums.h | 25 ++ .../gpu/drm/amd/display/dc/dml/display_mode_vba.h | 9 + drivers/gpu/drm/amd/display/dc/inc/core_types.h | 7 + drivers/gpu/drm/amd/display/dc/inc/hw/hw_shared.h | 7 + drivers/gpu/drm/amd/display/dmub/dmub_srv.h | 14 + drivers/gpu/drm/amd/display/dmub/src/dmub_dcn20.c | 5 + drivers/gpu/drm/amd/display/dmub/src/dmub_dcn20.h | 2 + drivers/gpu/drm/amd/display/dmub/src/dmub_dcn31.c | 5 + drivers/gpu/drm/amd/display/dmub/src/dmub_dcn31.h | 2 + drivers/gpu/drm/amd/display/dmub/src/dmub_dcn32.c | 5 + drivers/gpu/drm/amd/display/dmub/src/dmub_dcn32.h | 2 + drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c | 30 ++ .../drm/amd/include/asic_reg/gc/gc_11_0_0_offset.h | 2 + drivers/gpu/drm/amd/pm/swsmu/smu13/aldebaran_ppt.c | 5 +- drivers/input/joystick/xpad.c | 2 + drivers/iommu/intel/dmar.c | 18 + drivers/iommu/intel/iommu.c | 71 +++- drivers/md/bcache/btree.c | 2 +- drivers/md/dm-verity-fec.c | 3 +- drivers/md/dm-verity-target.c | 7 +- drivers/md/dm-verity.h | 6 - drivers/mmc/core/block.c | 2 + drivers/mmc/core/core.c | 9 +- drivers/mmc/core/regulator.c | 41 ++ drivers/mmc/host/cqhci-core.c | 44 +-- drivers/mmc/host/sdhci-pci-gli.c | 54 +-- drivers/mmc/host/sdhci-sprd.c | 25 ++ drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c | 8 +- drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.h | 2 +- drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 9 +- .../net/ethernet/marvell/octeontx2/af/rvu_nix.c | 4 +- .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 9 +- .../net/ethernet/marvell/octeontx2/af/rvu_switch.c | 6 +- drivers/net/ethernet/marvell/octeontx2/nic/cn10k.c | 3 + .../ethernet/marvell/octeontx2/nic/otx2_common.h | 13 +- .../ethernet/marvell/octeontx2/nic/otx2_devlink.c | 1 - .../ethernet/marvell/octeontx2/nic/otx2_ethtool.c | 1 + .../ethernet/marvell/octeontx2/nic/otx2_flows.c | 2 + .../net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 9 +- .../net/ethernet/marvell/octeontx2/nic/otx2_tc.c | 440 +++++++++++++++------ drivers/net/ethernet/realtek/r8169_main.c | 23 +- drivers/net/ethernet/renesas/ravb_main.c | 69 ++-- drivers/net/ethernet/stmicro/stmmac/mmc_core.c | 4 + drivers/nvme/host/core.c | 9 + drivers/pci/controller/dwc/pcie-qcom-ep.c | 17 + drivers/pci/quirks.c | 12 + drivers/perf/riscv_pmu_sbi.c | 5 + drivers/pinctrl/core.c | 6 +- drivers/powercap/dtpm_cpu.c | 6 +- drivers/powercap/dtpm_devfreq.c | 11 +- drivers/scsi/sd.c | 9 +- drivers/spi/spi.c | 56 ++- drivers/tty/serial/sc16is7xx.c | 5 + drivers/usb/core/config.c | 85 ++-- drivers/usb/host/xhci-plat.c | 29 +- drivers/video/fbdev/sticore.h | 2 +- drivers/xen/events/events_base.c | 22 +- drivers/xen/platform-pci.c | 5 +- fs/btrfs/disk-io.c | 1 + fs/btrfs/ioctl.c | 1 + fs/btrfs/ref-verify.c | 2 + fs/btrfs/send.c | 2 +- fs/btrfs/super.c | 5 +- fs/btrfs/volumes.c | 9 +- fs/smb/client/inode.c | 2 + fs/smb/client/smb2ops.c | 13 +- include/linux/dma-fence.h | 15 + include/linux/irq.h | 24 +- include/linux/mmc/host.h | 3 + include/linux/spi/spi.h | 1 + include/scsi/scsi_device.h | 12 +- include/uapi/linux/stddef.h | 2 +- include/xen/events.h | 3 +- kernel/irq/debugfs.c | 1 - kernel/irq/msi.c | 12 +- lib/errname.c | 6 - net/ipv4/igmp.c | 6 +- net/wireless/core.h | 1 + net/wireless/nl80211.c | 50 ++- sound/pci/hda/hda_intel.c | 2 + sound/pci/hda/patch_realtek.c | 12 + tools/arch/parisc/include/uapi/asm/errno.h | 2 - tools/testing/selftests/net/af_unix/diag_uid.c | 1 - tools/testing/selftests/net/cmsg_sender.c | 2 +- tools/testing/selftests/net/ipsec.c | 4 +- tools/testing/selftests/net/mptcp/mptcp_connect.c | 11 +- tools/testing/selftests/net/mptcp/mptcp_inq.c | 11 +- 134 files changed, 1282 insertions(+), 571 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/107 cifs: Fix FALLOC_FL_ZERO_RANGE by setting i_size if EOF moved
6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Howells <[email protected]>
commit 83d5518b124dfd605f10a68128482c839a239f9d upstream.
Fix the cifs filesystem implementations of FALLOC_FL_ZERO_RANGE, in smb3_zero_range(), to set i_size after extending the file on the server.
--- fs/smb/client/smb2ops.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
fs/smb/client/smb2ops.c +8 -2
@@ -3424,6 +3424,7 @@ static long smb3_zero_range(struct filestruct inode *inode =file_inode (file);struct cifsInodeInfo *cifsi =CIFS_I (inode);struct cifsFileInfo *cfile = file->private_data; +unsigned long long new_size;long rc;unsigned int xid;__le64 eof;
@@ -3454,10 +3455,15 @@ static long smb3_zero_range(struct file/* * do we also need to change the size of the file? */ -if (keep_size == false &&i_size_read (inode) < offset + len) { - eof =cpu_to_le64 (offset + len); + new_size = offset + len; +if (keep_size == false && (unsigned long long )i_size_read (inode) < new_size) { + eof =cpu_to_le64 (new_size); rc =SMB2_set_eof (xid, tcon, cfile->fid.persistent_fid, cfile->fid.volatile_fid, cfile->pid, &eof); +if (rc >=0 ) { +truncate_setsize (inode, new_size); +fscache_resize_cookie (cifs_inode_cookie (inode), new_size); + } } zero_range_exit:
Greg Kroah-Hartman
maintainerPATCH 2/107 cifs: Fix FALLOC_FL_INSERT_RANGE by setting i_size after EOF moved
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Howells <[email protected]>
commit 88010155f02b2c3b03c71609ba6ceeb457ece095 upstream.
Fix the cifs filesystem implementations of FALLOC_FL_INSERT_RANGE, in smb3_insert_range(), to set i_size after extending the file on the server and before we do the copy to open the gap (as we don't clean up the EOF marker if the copy fails).
--- fs/smb/client/smb2ops.c | 3 +++ 1 file changed, 3 insertions(+)
fs/smb/client/smb2ops.c +3 -0
@@ -3858,6 +3858,9 @@ static long smb3_insert_range(struct filif (rc <0 ) goto out_2; +truncate_setsize (inode, old_eof + len); +fscache_resize_cookie (cifs_inode_cookie (inode),i_size_read (inode)); + rc =smb2_copychunk_range (xid, cfile, cfile, off, count, off + len);if (rc <0 ) goto out_2;
Greg Kroah-Hartman
maintainerPATCH 3/107 smb: client: report correct st_size for SMB and NFS symlinks
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Paulo Alcantara <[email protected]>
commit 9d63509547a940225d06d7eba1dc412befae255d upstream.
We can't rely on FILE_STANDARD_INFORMATION::EndOfFile for reparse points as they will be always zero. Set it to symlink target's length as specified by POSIX.
This will make stat() family of syscalls return the correct st_size for such files.
--- fs/smb/client/inode.c | 2 ++ 1 file changed, 2 insertions(+)
fs/smb/client/inode.c +2 -0
@@ -772,6 +772,8 @@ static void cifs_open_info_to_fattr(stru }if (S_ISLNK (fattr->cf_mode)) { +if (likely (data->symlink_target)) + fattr->cf_eof =strnlen (data->symlink_target,PATH_MAX ); fattr->cf_symlink_target = data->symlink_target; data->symlink_target =NULL ; }
Greg Kroah-Hartman
maintainerPATCH 4/107 pinctrl: avoid reload of p state in list iteration
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Maria Yu <[email protected]>
commit 4198a9b571065978632276264e01d71d68000ac5 upstream.
When in the list_for_each_entry iteration, reload of p->state->settings with a local setting from old_state will turn the list iteration into an infinite loop.
The typical symptom when the issue happens, will be a printk message like:
"not freeing pin xx (xxx) as part of deactivating group xxx - it is
already used for some other setting".
This is a compiler-dependent problem, one instance occurred using Clang version 10.0 on the arm64 architecture with linux version 4.19.
--- drivers/pinctrl/core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/pinctrl/core.c +3 -3
@@ -1239,17 +1239,17 @@ static void pinctrl_link_add(struct pincstatic int pinctrl_commit_state (struct pinctrl *p,struct pinctrl_state *state) {struct pinctrl_setting *setting, *setting2; -struct pinctrl_state *old_state = p->state; +struct pinctrl_state *old_state =READ_ONCE (p->state);int ret; -if (p->state) { +if (old_state) {/* * For each pinmux setting in the old state, forget SW's record * of mux owner for that pingroup. Any pingroups which are * still owned by the new state will be re-acquired by the call * to pinmux_enable_setting() in the loop below. */ -list_for_each_entry (setting, &p->state->settings, node) { +list_for_each_entry (setting, &old_state->settings, node) {if (setting->type !=PIN_MAP_TYPE_MUX_GROUP )continue ;pinmux_disable_setting (setting);
Greg Kroah-Hartman
maintainerPATCH 5/107 firewire: core: fix possible memory leak in create_units()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yang Yingliang <[email protected]>
commit 891e0eab32a57fca4d36c5162628eb0bcb1f0edf upstream.
If device_register() fails, the refcount of device is not 0, the name allocated in dev_set_name() is leaked. To fix this by calling put_device(), so that it will be freed in callback function kobject_cleanup().
unreferenced object 0xffff9d99035c7a90 (size 8):
comm "systemd-udevd", pid 168, jiffies 4294672386 (age 152.089s) hex dump (first 8 bytes):
66 77 30 2e 30 00 ff ff fw0.0...
backtrace:
[<00000000e1d62bac>] __kmem_cache_alloc_node+0x1e9/0x360
[<00000000bbeaff31>] __kmalloc_node_track_caller+0x44/0x1a0
[<00000000491f2fb4>] kvasprintf+0x67/0xd0
[<000000005b960ddc>] kobject_set_name_vargs+0x1e/0x90
[<00000000427ac591>] dev_set_name+0x4e/0x70
[<000000003b4e447d>] create_units+0xc5/0x110fw_unit_release() will be called in the error path, move fw_device_get() before calling device_register() to keep balanced with fw_device_put() in fw_unit_release().
--- drivers/firewire/core-device.c | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)
drivers/firewire/core-device.c +4 -7
@@ -717,14 +717,11 @@ static void create_units(struct fw_devic fw_unit_attributes, &unit->attribute_group); -if (device_register (&unit->device) <0 ) - goto skip_unit; -fw_device_get (device); -continue ; - - skip_unit: -kfree (unit); +if (device_register (&unit->device) <0 ) { +put_device (&unit->device); +continue ; + } } }
Greg Kroah-Hartman
maintainerPATCH 6/107 mmc: sdhci-pci-gli: Disable LPM during initialization
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kornel Dulęba <[email protected]>
commit d9ed644f58670865cf067351deb71010bd87a52f upstream.
To address IO performance commit f9e5b33934ce
("mmc: host: Improve I/O read/write performance for GL9763E") limited LPM negotiation to runtime suspend state. The problem is that it only flips the switch in the runtime PM resume/suspend logic.
Disable LPM negotiation in gl9763e_add_host.
This helps in two ways:
1. It was found that the LPM switch stays in the same position after warm reboot. Having it set in init helps with consistency.
2. Disabling LPM during the first runtime resume leaves us susceptible to the performance issue in the time window between boot and the first runtime suspend.
--- drivers/mmc/host/sdhci-pci-gli.c | 54 ++++++++++++++++++++------------------- 1 file changed, 29 insertions(+), 25 deletions(-)
drivers/mmc/host/sdhci-pci-gli.c +29 -25
@@ -801,6 +801,32 @@ static void gl9763e_hs400_enhanced_strobsdhci_writel (host, val,SDHCI_GLI_9763E_HS400_ES_REG ); } +static void gl9763e_set_low_power_negotiation (struct sdhci_pci_slot *slot, +bool enable) +{ +struct pci_dev *pdev = slot->chip->pdev; +u32 value; + +pci_read_config_dword (pdev,PCIE_GLI_9763E_VHS , &value); + value &= ~GLI_9763E_VHS_REV ; + value |=FIELD_PREP (GLI_9763E_VHS_REV ,GLI_9763E_VHS_REV_W ); +pci_write_config_dword (pdev,PCIE_GLI_9763E_VHS , value); + +pci_read_config_dword (pdev,PCIE_GLI_9763E_CFG , &value); + +if (enable) + value &= ~GLI_9763E_CFG_LPSN_DIS ; +else + value |=GLI_9763E_CFG_LPSN_DIS ; + +pci_write_config_dword (pdev,PCIE_GLI_9763E_CFG , value); + +pci_read_config_dword (pdev,PCIE_GLI_9763E_VHS , &value); + value &= ~GLI_9763E_VHS_REV ; + value |=FIELD_PREP (GLI_9763E_VHS_REV ,GLI_9763E_VHS_REV_R ); +pci_write_config_dword (pdev,PCIE_GLI_9763E_VHS , value); +} +static void sdhci_set_gl9763e_signaling (struct sdhci_host *host,unsigned int timing) {
@@ -909,6 +935,9 @@ static int gl9763e_add_host(struct sdhciif (ret) goto cleanup; +/* Disable LPM negotiation to avoid entering L1 state. */ +gl9763e_set_low_power_negotiation (slot, false); +return 0 ; cleanup:
@@ -960,31 +989,6 @@ static void gli_set_gl9763e(struct sdhci }#ifdef CONFIG_PM -static void gl9763e_set_low_power_negotiation (struct sdhci_pci_slot *slot,bool enable) -{ -struct pci_dev *pdev = slot->chip->pdev; -u32 value; - -pci_read_config_dword (pdev,PCIE_GLI_9763E_VHS , &value); - value &= ~GLI_9763E_VHS_REV ; - value |=FIELD_PREP (GLI_9763E_VHS_REV ,GLI_9763E_VHS_REV_W ); -pci_write_config_dword (pdev,PCIE_GLI_9763E_VHS , value); - -pci_read_config_dword (pdev,PCIE_GLI_9763E_CFG , &value); - -if (enable) - value &= ~GLI_9763E_CFG_LPSN_DIS ; -else - value |=GLI_9763E_CFG_LPSN_DIS ; - -pci_write_config_dword (pdev,PCIE_GLI_9763E_CFG , value); - -pci_read_config_dword (pdev,PCIE_GLI_9763E_VHS , &value); - value &= ~GLI_9763E_VHS_REV ; - value |=FIELD_PREP (GLI_9763E_VHS_REV ,GLI_9763E_VHS_REV_R ); -pci_write_config_dword (pdev,PCIE_GLI_9763E_VHS , value); -} -static int gl9763e_runtime_suspend (struct sdhci_pci_chip *chip) {struct sdhci_pci_slot *slot = chip->slots[0 ];
Greg Kroah-Hartman
maintainerPATCH 7/107 mmc: cqhci: Increase recovery halt timeout
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Hunter <[email protected]>
commit b578d5d18e929aa7c007a98cce32657145dde219 upstream.
Failing to halt complicates the recovery. Additionally, unless the card or controller are stuck, which is expected to be very rare, then the halt should succeed, so it is better to wait. Set a large timeout.
--- drivers/mmc/host/cqhci-core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/mmc/host/cqhci-core.c +3 -3
@@ -984,10 +984,10 @@ static bool cqhci_halt(struct mmc_host */* * After halting we expect to be able to use the command line. We interpret the * failure to halt to mean the data lines might still be in use (and the upper -* layers will need to send a STOP command), so we set the timeout based on a -* generous command timeout. +* layers will need to send a STOP command), however failing to halt complicates +* the recovery, so set a timeout that would reasonably allow I/O to complete. */ -#define CQHCI_START_HALT_TIMEOUT 5 +#define CQHCI_START_HALT_TIMEOUT 500static void cqhci_recovery_start (struct mmc_host *mmc) {
Greg Kroah-Hartman
maintainerPATCH 8/107 mmc: cqhci: Warn of halt or task clear failure
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Hunter <[email protected]>
commit 35597bdb04ec27ef3b1cea007dc69f8ff5df75a5 upstream.
A correctly operating controller should successfully halt and clear tasks. Failure may result in errors elsewhere, so promote messages from debug to warnings.
--- drivers/mmc/host/cqhci-core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/mmc/host/cqhci-core.c +3 -3
@@ -942,8 +942,8 @@ static bool cqhci_clear_all_tasks(struct ret =cqhci_tasks_cleared (cq_host);if (!ret) -pr_debug ("%s: cqhci: Failed to clear tasks\n" , -mmc_hostname (mmc)); +pr_warn ("%s: cqhci: Failed to clear tasks\n" , +mmc_hostname (mmc));return ret; }
@@ -976,7 +976,7 @@ static bool cqhci_halt(struct mmc_host * ret =cqhci_halted (cq_host);if (!ret) -pr_debug ("%s: cqhci: Failed to halt\n" ,mmc_hostname (mmc)); +pr_warn ("%s: cqhci: Failed to halt\n" ,mmc_hostname (mmc));return ret; }
Greg Kroah-Hartman
maintainerPATCH 9/107 mmc: cqhci: Fix task clearing in CQE error recovery
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Hunter <[email protected]>
commit 1de1b77982e1a1df9707cb11f9b1789e6b8919d4 upstream.
If a task completion notification (TCN) is received when there is no outstanding task, the cqhci driver issues a "spurious TCN" warning. This was observed to happen right after CQE error recovery.
When an error interrupt is received the driver runs recovery logic. It halts the controller, clears all pending tasks, and then re-enables it. On some platforms, like Intel Jasper Lake, a stale task completion event was observed, regardless of the CQHCI_CLEAR_ALL_TASKS bit being set.
This results in either:
a) Spurious TC completion event for an empty slot.
b) Corrupted data being passed up the stack, as a result of premature completion for a newly added task.
Rather than add a quirk for affected controllers, ensure tasks are cleared by toggling CQHCI_ENABLE, which would happen anyway if cqhci_clear_all_tasks() timed out. This is simpler and should be safe and effective for all controllers.
--- drivers/mmc/host/cqhci-core.c | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-)
drivers/mmc/host/cqhci-core.c +16 -16
@@ -1075,28 +1075,28 @@ static void cqhci_recovery_finish(struct ok =cqhci_halt (mmc,CQHCI_FINISH_HALT_TIMEOUT ); -if (!cqhci_clear_all_tasks (mmc,CQHCI_CLEAR_TIMEOUT )) - ok = false; -/* * The specification contradicts itself, by saying that tasks cannot be * cleared if CQHCI does not halt, but if CQHCI does not halt, it should * be disabled/re-enabled, but not to disable before clearing tasks. * Have a go anyway. */ -if (!ok) { -pr_debug ("%s: cqhci: disable / re-enable\n" ,mmc_hostname (mmc)); - cqcfg =cqhci_readl (cq_host,CQHCI_CFG ); - cqcfg &= ~CQHCI_ENABLE ; -cqhci_writel (cq_host, cqcfg,CQHCI_CFG ); - cqcfg |=CQHCI_ENABLE ; -cqhci_writel (cq_host, cqcfg,CQHCI_CFG ); -/* Be sure that there are no tasks */ - ok =cqhci_halt (mmc,CQHCI_FINISH_HALT_TIMEOUT ); -if (!cqhci_clear_all_tasks (mmc,CQHCI_CLEAR_TIMEOUT )) - ok = false; -WARN_ON (!ok); - } +if (!cqhci_clear_all_tasks (mmc,CQHCI_CLEAR_TIMEOUT )) + ok = false; + +/* Disable to make sure tasks really are cleared */ + cqcfg =cqhci_readl (cq_host,CQHCI_CFG ); + cqcfg &= ~CQHCI_ENABLE ; +cqhci_writel (cq_host, cqcfg,CQHCI_CFG ); + + cqcfg =cqhci_readl (cq_host,CQHCI_CFG ); + cqcfg |=CQHCI_ENABLE ; +cqhci_writel (cq_host, cqcfg,CQHCI_CFG ); + +cqhci_halt (mmc,CQHCI_FINISH_HALT_TIMEOUT ); + +if (!ok) +cqhci_clear_all_tasks (mmc,CQHCI_CLEAR_TIMEOUT );cqhci_recover_mrqs (cq_host);
Greg Kroah-Hartman
maintainerPATCH 10/107 mmc: block: Retry commands in CQE error recovery
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Hunter <[email protected]>
commit 8155d1fa3a747baad5caff5f8303321d68ddd48c upstream.
It is important that MMC_CMDQ_TASK_MGMT command to discard the queue is successful because otherwise a subsequent reset might fail to flush the cache first. Retry it and the previous STOP command.
--- drivers/mmc/core/core.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/mmc/core/core.c +5 -2
@@ -552,7 +552,7 @@ int mmc_cqe_recovery(struct mmc_host *ho cmd.flags =MMC_RSP_R1B |MMC_CMD_AC ; cmd.flags &= ~MMC_RSP_CRC ;/* Ignore CRC */ cmd.busy_timeout =MMC_CQE_RECOVERY_TIMEOUT ; -mmc_wait_for_cmd (host, &cmd,0 ); +mmc_wait_for_cmd (host, &cmd,MMC_CMD_RETRIES );memset (&cmd,0 ,sizeof (cmd)); cmd.opcode =MMC_CMDQ_TASK_MGMT ;
@@ -560,10 +560,13 @@ int mmc_cqe_recovery(struct mmc_host *ho cmd.flags =MMC_RSP_R1B |MMC_CMD_AC ; cmd.flags &= ~MMC_RSP_CRC ;/* Ignore CRC */ cmd.busy_timeout =MMC_CQE_RECOVERY_TIMEOUT ; - err =mmc_wait_for_cmd (host, &cmd,0 ); + err =mmc_wait_for_cmd (host, &cmd,MMC_CMD_RETRIES ); host->cqe_ops->cqe_recovery_finish (host); +if (err) + err =mmc_wait_for_cmd (host, &cmd,MMC_CMD_RETRIES ); +mmc_retune_release (host);return err;
Greg Kroah-Hartman
maintainerPATCH 11/107 mmc: block: Do not lose cache flush during CQE error recovery
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Hunter <[email protected]>
commit 174925d340aac55296318e43fd96c0e1d196e105 upstream.
During CQE error recovery, error-free data commands get requeued if there is any data left to transfer, but non-data commands are completed even though they have not been processed. Requeue them instead.
Note the only non-data command is cache flush, which would have resulted in a cache flush being lost if it was queued at the time of CQE recovery.
--- drivers/mmc/core/block.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/mmc/core/block.c +2 -0
@@ -1505,6 +1505,8 @@ static void mmc_blk_cqe_complete_rq(strublk_mq_requeue_request (req, true); else__blk_mq_end_request (req ,BLK_STS_OK ); + }else if (mq->in_recovery) { +blk_mq_requeue_request (req, true); }else {blk_mq_end_request (req,BLK_STS_OK ); }
Greg Kroah-Hartman
maintainerPATCH 12/107 mmc: block: Be sure to wait while busy in CQE error recovery
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Adrian Hunter <[email protected]>
commit c616696a902987352426fdaeec1b0b3240949e6b upstream.
STOP command does not guarantee to wait while busy, but subsequent command MMC_CMDQ_TASK_MGMT to discard the queue will fail if the card is busy, so be sure to wait by employing mmc_poll_for_busy().
--- drivers/mmc/core/core.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/mmc/core/core.c +2 -0
@@ -554,6 +554,8 @@ int mmc_cqe_recovery(struct mmc_host *ho cmd.busy_timeout =MMC_CQE_RECOVERY_TIMEOUT ;mmc_wait_for_cmd (host, &cmd,MMC_CMD_RETRIES ); +mmc_poll_for_busy (host->card,MMC_CQE_RECOVERY_TIMEOUT , true,MMC_BUSY_IO ); +memset (&cmd,0 ,sizeof (cmd)); cmd.opcode =MMC_CMDQ_TASK_MGMT ; cmd.arg =1 ;/* Discard entire queue */
Greg Kroah-Hartman
maintainerPATCH 13/107 ALSA: hda: Disable power-save on KONTRON SinglePC
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit a337c355719c42a6c5b67e985ad753590ed844fb upstream.
It's been reported that the runtime PM on KONTRON SinglePC (PCI SSID 1734:1232) caused a stall of playback after a bunch of invocations. (FWIW, this looks like an timing issue, and the stall happens rather on the controller side.)
As a workaround, disable the default power-save on this platform.
--- sound/pci/hda/hda_intel.c | 2 ++ 1 file changed, 2 insertions(+)
sound/pci/hda/hda_intel.c +2 -0
@@ -2215,6 +2215,8 @@ static const struct snd_pci_quirk power_SND_PCI_QUIRK (0x17aa ,0x36a7 ,"Lenovo C50 All in one" ,0 ),/* https://bugs.launchpad.net/bugs/1821663 */ SND_PCI_QUIRK (0x1631 ,0xe017 ,"Packard Bell NEC IMEDIA 5204" ,0 ), +/* KONTRON SinglePC may cause a stall at runtime resume */ + SND_PCI_QUIRK(0x1734, 0x1232, "KONTRON SinglePC", 0), {} };#endif /* CONFIG_PM */
Greg Kroah-Hartman
maintainerPATCH 14/107 ALSA: hda/realtek: Headset Mic VREF to 100%
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kailang Yang <[email protected]>
commit baaacbff64d9f34b64f294431966d035aeadb81c upstream.
This platform need to set Mic VREF to 100%.
--- sound/pci/hda/patch_realtek.c | 9 +++++++++ 1 file changed, 9 insertions(+)
sound/pci/hda/patch_realtek.c +9 -0
@@ -1986,6 +1986,7 @@ enum {ALC887_FIXUP_ASUS_AUDIO ,ALC887_FIXUP_ASUS_HMIC ,ALCS1200A_FIXUP_MIC_VREF , + ALC888VD_FIXUP_MIC_100VREF, }; static void alc889_fixup_coef(struct hda_codec *codec,
@@ -2539,6 +2540,13 @@ static const struct hda_fixup alc882_fix {} } }, + [ALC888VD_FIXUP_MIC_100VREF ] = { + .type =HDA_FIXUP_PINCTLS , + .v.pins = (const struct hda_pintbl []) { + {0x18 ,PIN_VREF100 },/* headset mic */ + {} + } + }, };static const struct snd_pci_quirk alc882_fixup_tbl[] = {
@@ -2608,6 +2616,7 @@ static const struct snd_pci_quirk alc882SND_PCI_QUIRK (0x106b ,0x4a00 ,"Macbook 5,2" ,ALC889_FIXUP_MBA11_VREF ),SND_PCI_QUIRK (0x1071 ,0x8258 ,"Evesham Voyaeger" ,ALC882_FIXUP_EAPD ), +SND_PCI_QUIRK (0x10ec ,0x12d8 ,"iBase Elo Touch" ,ALC888VD_FIXUP_MIC_100VREF ),SND_PCI_QUIRK (0x13fe ,0x1009 ,"Advantech MIT-W101" ,ALC886_FIXUP_EAPD ),SND_PCI_QUIRK (0x1458 ,0xa002 ,"Gigabyte EP45-DS3/Z87X-UD3H" ,ALC889_FIXUP_FRONT_HP_NO_PRESENCE ), SND_PCI_QUIRK(0x1458, 0xa0b8, "Gigabyte AZ370-Gaming", ALC1220_FIXUP_GB_DUAL_CODECS),
Greg Kroah-Hartman
maintainerPATCH 15/107 ALSA: hda/realtek: Add supported ALC257 for ChromeOS
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kailang Yang <[email protected]>
commit cae2bdb579ecc9d4219c58a7d3fde1958118dc1d upstream.
ChromeOS want to support ALC257.
Add codec ID to some relation function.
--- sound/pci/hda/patch_realtek.c | 3 +++ 1 file changed, 3 insertions(+)
sound/pci/hda/patch_realtek.c +3 -0
@@ -3264,6 +3264,7 @@ static void alc_disable_headset_jack_keycase 0x10ec0230 :case 0x10ec0236 :case 0x10ec0256 : +case 0x10ec0257 :case 0x19e58326 :alc_write_coef_idx (codec,0x48 ,0x0 );alc_update_coef_idx (codec,0x49 ,0x0045 ,0x0 );
@@ -3293,6 +3294,7 @@ static void alc_enable_headset_jack_key(case 0x10ec0230 :case 0x10ec0236 :case 0x10ec0256 : +case 0x10ec0257 :case 0x19e58326 :alc_write_coef_idx (codec,0x48 ,0xd011 );alc_update_coef_idx (codec,0x49 ,0x007f ,0x0045 );
@@ -6504,6 +6506,7 @@ static void alc_combo_jack_hp_jd_restartcase 0x10ec0236 :case 0x10ec0255 :case 0x10ec0256 : +case 0x10ec0257 :case 0x19e58326 :alc_update_coef_idx (codec,0x1b ,0x8000 ,1 <<15 );/* Reset HP JD */ alc_update_coef_idx (codec,0x1b ,0x8000 ,0 <<15 );
Greg Kroah-Hartman
maintainerPATCH 16/107 dm-verity: align struct dm_verity_fec_io properly
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mikulas Patocka <[email protected]>
commit 38bc1ab135db87577695816b190e7d6d8ec75879 upstream.
dm_verity_fec_io is placed after the end of two hash digests. If the hash digest has unaligned length, struct dm_verity_fec_io could be unaligned.
This commit fixes the placement of struct dm_verity_fec_io, so that it's aligned.
--- drivers/md/dm-verity-fec.c | 3 ++- drivers/md/dm-verity.h | 6 ------ 2 files changed, 2 insertions(+), 7 deletions(-)
drivers/md/dm-verity-fec.c +2 -1
@@ -24,7 +24,8 @@ bool verity_fec_is_enabled(struct dm_ver*/ static inline struct dm_verity_fec_io *fec_io (struct dm_verity_io *io) { -return (struct dm_verity_fec_io *)verity_io_digest_end (io->v, io); +return (struct dm_verity_fec_io *) + ((char *)io + io->v->ti->per_io_data_size -sizeof (struct dm_verity_fec_io )); }/*
drivers/md/dm-verity.h +0 -6
@@ -115,12 +115,6 @@ static inline u8 *verity_io_want_digest(return (u8 *)(io +1 ) + v->ahash_reqsize + v->digest_size; } -static inline u8 *verity_io_digest_end (struct dm_verity *v, -struct dm_verity_io *io) -{ -return verity_io_want_digest (v, io) + v->digest_size; -} - extern int verity_for_bv_block(struct dm_verity *v, struct dm_verity_io *io, struct bvec_iter *iter, int (*process)(struct dm_verity *v,
Greg Kroah-Hartman
maintainerPATCH 17/107 scsi: Change SCSI device boolean fields to single bit flags
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Damien Le Moal <[email protected]>
commit 6371be7aeb986905bb60ec73d002fc02343393b4 upstream.
Commit 3cc2ffe5c16d ("scsi: sd: Differentiate system and runtime start/stop management") changed the single bit manage_start_stop flag into 2 boolean fields of the SCSI device structure. Commit 24eca2dce0f8 ("scsi: sd:
Introduce manage_shutdown device flag") introduced the manage_shutdown boolean field for the same structure. Together, these 2 commits increase the size of struct scsi_device by 8 bytes by using booleans instead of defining the manage_xxx fields as single bit flags, similarly to other flags of this structure.
Avoid this unnecessary structure size increase and be consistent with the definition of other flags by reverting the definitions of the manage_xxx fields as single bit flags.
--- drivers/ata/libata-scsi.c | 4 ++-- drivers/firewire/sbp2.c | 6 +++--- include/scsi/scsi_device.h | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-)
drivers/ata/libata-scsi.c +2 -2
@@ -1087,8 +1087,8 @@ int ata_scsi_dev_config(struct scsi_devi* and resume and shutdown only. For system level suspend/resume, * devices power state is handled directly by libata EH. */ - sdev->manage_runtime_start_stop = true; - sdev->manage_shutdown = true; + sdev->manage_runtime_start_stop =1 ; + sdev->manage_shutdown =1 ; }/*
drivers/firewire/sbp2.c +3 -3
@@ -1519,9 +1519,9 @@ static int sbp2_scsi_slave_configure(str sdev->use_10_for_rw =1 ;if (sbp2_param_exclusive_login) { - sdev->manage_system_start_stop = true; - sdev->manage_runtime_start_stop = true; - sdev->manage_shutdown = true; + sdev->manage_system_start_stop =1 ; + sdev->manage_runtime_start_stop =1 ; + sdev->manage_shutdown =1 ; }if (sdev->type ==TYPE_ROM )
include/scsi/scsi_device.h +3 -3
@@ -167,19 +167,19 @@ struct scsi_device {* power state for system suspend/resume (suspend to RAM and * hibernation) operations. */ -bool manage_system_start_stop; + unsigned manage_system_start_stop:1;/* * If true, let the high-level device driver (sd) manage the device * power state for runtime device suspand and resume operations. */ -bool manage_runtime_start_stop; + unsigned manage_runtime_start_stop:1;/* * If true, let the high-level device driver (sd) manage the device * power state for system shutdown (power off) operations. */ -bool manage_shutdown; + unsigned manage_shutdown:1; unsigned removable:1; unsigned changed:1; /* Data invalid due to media change */
Greg Kroah-Hartman
maintainerPATCH 18/107 scsi: sd: Fix system start for ATA devices
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Damien Le Moal <[email protected]>
commit b09d7f8fd50f6e93cbadd8d27fde178f745b42a1 upstream.
It is not always possible to keep a device in the runtime suspended state when a system level suspend/resume cycle is executed. E.g. for ATA devices connected to AHCI adapters, system resume resets the ATA ports, which causes connected devices to spin up. In such case, a runtime suspended disk will incorrectly be seen with a suspended runtime state because the device is not resumed by sd_resume_system(). The power state seen by the user is different than the actual device physical power state.
Fix this issue by introducing the struct scsi_device flag force_runtime_start_on_system_start. When set, this flag causes sd_resume_system() to request a runtime resume operation for runtime suspended devices. This results in the user seeing the device runtime_state as active after a system resume, thus correctly reflecting the device physical power state.
--- drivers/ata/libata-scsi.c | 5 +++++ drivers/scsi/sd.c | 9 ++++++++- include/scsi/scsi_device.h | 6 ++++++ 3 files changed, 19 insertions(+), 1 deletion(-)
drivers/ata/libata-scsi.c +5 -0
@@ -1086,9 +1086,14 @@ int ata_scsi_dev_config(struct scsi_devi* Ask the sd driver to issue START STOP UNIT on runtime suspend * and resume and shutdown only. For system level suspend/resume, * devices power state is handled directly by libata EH. +* Given that disks are always spun up on system resume, also +* make sure that the sd driver forces runtime suspended disks +* to be resumed to correctly reflect the power state of the +* device. */ sdev->manage_runtime_start_stop =1 ; sdev->manage_shutdown =1 ; + sdev->force_runtime_start_on_system_start =1 ; }/*
drivers/scsi/sd.c +8 -1
@@ -3834,8 +3834,15 @@ static int sd_resume(struct device *dev,static int sd_resume_system (struct device *dev) { -if (pm_runtime_suspended (dev)) +if (pm_runtime_suspended (dev)) { +struct scsi_disk *sdkp =dev_get_drvdata (dev); +struct scsi_device *sdp = sdkp ? sdkp->device :NULL ; + +if (sdp && sdp->force_runtime_start_on_system_start) +pm_request_resume (dev); +return 0 ; + }return sd_resume (dev, false); }
include/scsi/scsi_device.h +6 -0
@@ -181,6 +181,12 @@ struct scsi_device {*/ unsigned manage_shutdown:1; +/* +* If set and if the device is runtime suspended, ask the high-level +* device driver (sd) to force a runtime resume of the device. +*/ + unsigned force_runtime_start_on_system_start:1; + unsigned removable:1; unsigned changed:1; /* Data invalid due to media change */ unsigned busy:1; /* Used to prevent races */
Greg Kroah-Hartman
maintainerPATCH 19/107 drm/amd: Enable PCIe PME from D3
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mario Limonciello <[email protected]>
commit 6967741d26c87300a51b5e50d4acd104bc1a9759 upstream.
When dGPU is put into BOCO it may be in D3cold but still able send PME on display hotplug event. For this to work it must be enabled as wake source from D3.
When runpm is enabled use pci_wake_from_d3() to mark wakeup as enabled by default.
--- drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c +2 -0
@@ -2200,6 +2200,8 @@ retry_init:pm_runtime_mark_last_busy (ddev->dev);pm_runtime_put_autosuspend (ddev->dev); +pci_wake_from_d3 (pdev, TRUE); +/* * For runpm implemented via BACO, PMFW will handle the * timing for BACO in and out:
Greg Kroah-Hartman
maintainerPATCH 20/107 drm/amdgpu: Force order between a read and write to the same address
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Sierra <[email protected]>
commit 4b27a33c3b173bef1d19ba89e0b9b812b4fddd25 upstream.
Setting register to force ordering to prevent read/write or write/read hazards for un-cached modes.
--- drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 8 ++++++++ drivers/gpu/drm/amd/include/asic_reg/gc/gc_11_0_0_offset.h | 2 ++ 2 files changed, 10 insertions(+)
drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c +8 -0
@@ -82,6 +82,10 @@ MODULE_FIRMWARE("amdgpu/gc_11_0_4_me.binMODULE_FIRMWARE ("amdgpu/gc_11_0_4_mec.bin" );MODULE_FIRMWARE ("amdgpu/gc_11_0_4_rlc.bin" ); +static const struct soc15_reg_golden golden_settings_gc_11_0[] = { +SOC15_REG_GOLDEN_VALUE (GC ,0 , regTCP_CNTL,0x20000000 ,0x20000000 ) +}; +static const struct soc15_reg_golden golden_settings_gc_11_0_1[] = {SOC15_REG_GOLDEN_VALUE (GC ,0 , regCGTT_GS_NGG_CLK_CTRL,0x9fff8fff ,0x00000010 ),
@@ -274,6 +278,10 @@ static void gfx_v11_0_init_golden_registdefault :break ; } +soc15_program_register_sequence (adev, + golden_settings_gc_11_0, + (const u32 )ARRAY_SIZE (golden_settings_gc_11_0)); + } static void gfx_v11_0_write_data_to_reg(struct amdgpu_ring *ring, int eng_sel,
drivers/gpu/drm/amd/include/asic_reg/gc/gc_11_0_0_offset.h +2 -0
@@ -6369,6 +6369,8 @@#define regTCP_INVALIDATE_BASE_IDX 1#define regTCP_STATUS 0x19a1#define regTCP_STATUS_BASE_IDX 1 +#define regTCP_CNTL 0x19a2 +#define regTCP_CNTL_BASE_IDX 1#define regTCP_CNTL2 0x19a3#define regTCP_CNTL2_BASE_IDX 1#define regTCP_DEBUG_INDEX 0x19a5
Greg Kroah-Hartman
maintainerPATCH 21/107 drm/amd/display: Include udelay when waiting for INBOX0 ACK
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alvin Lee <[email protected]>
commit 3c9ea68cb61bd7e5bd312c06a12adada74ff5805 upstream.
When waiting for the ACK for INBOX0 message, we have to ensure to include the udelay
for proper wait time
--- drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c +1 -0
@@ -964,6 +964,7 @@ enum dmub_status dmub_srv_wait_for_inbox ack = dmub->hw_funcs.read_inbox0_ack_register (dmub);if (ack)return DMUB_STATUS_OK ; +udelay (1 ); }return DMUB_STATUS_TIMEOUT ; }
Greg Kroah-Hartman
maintainerPATCH 22/107 drm/amd/display: Remove min_dst_y_next_start check for Z8
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Kazlauskas <[email protected]>
commit 08448812acb2ab701cd5ff7e1a1dc97f7f10260c upstream.
[Why]
Flickering occurs on DRR supported panels when engaged in DRR due to min_dst_y_next becoming larger than the frame size itself.
[How]
In general, we should be able to enter Z8 when this is engaged but it might be a net power loss even if the calculation wasn't bugged.
Don't support enabling Z8 during the DRR region.
--- drivers/gpu/drm/amd/display/dc/dml/dcn20/dcn20_fpu.c | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-)
drivers/gpu/drm/amd/display/dc/dml/dcn20/dcn20_fpu.c +1 -14
@@ -948,10 +948,8 @@ static enum dcn_zstate_support_state de {int plane_count;int i; -unsigned int min_dst_y_next_start_us; plane_count =0 ; - min_dst_y_next_start_us =0 ;for (i =0 ; i < dc->res_pool->pipe_count; i++) {if (context->res_ctx.pipe_ctx[i].plane_state) plane_count++;
@@ -973,26 +971,15 @@ static enum dcn_zstate_support_state deelse if (context->stream_count ==1 && context->streams[0 ]->signal ==SIGNAL_TYPE_EDP ) {struct dc_link *link = context->streams[0 ]->sink->link;struct dc_stream_status *stream_status = &context->stream_status[0 ]; -struct dc_stream_state *current_stream = context->streams[0 ];int minmum_z8_residency = dc->debug.minimum_z8_residency_time >0 ? dc->debug.minimum_z8_residency_time :1000 ;bool allow_z8 = context->bw_ctx.dml.vba.StutterPeriod > (double )minmum_z8_residency;bool is_pwrseq0 = link->link_index ==0 ; -bool isFreesyncVideo; - - isFreesyncVideo = current_stream->adjust.v_total_min == current_stream->adjust.v_total_max; - isFreesyncVideo = isFreesyncVideo && current_stream->timing.v_total < current_stream->adjust.v_total_min; -for (i =0 ; i < dc->res_pool->pipe_count; i++) { -if (context->res_ctx.pipe_ctx[i].stream == current_stream && isFreesyncVideo) { - min_dst_y_next_start_us = context->res_ctx.pipe_ctx[i].dlg_regs.min_dst_y_next_start_us; -break ; - } - }/* Don't support multi-plane configurations */ if (stream_status->plane_count >1 )return DCN_ZSTATE_SUPPORT_DISALLOW ; -if (is_pwrseq0 && (context->bw_ctx.dml.vba.StutterPeriod >5000.0 || min_dst_y_next_start_us >5000 )) +if (is_pwrseq0 && context->bw_ctx.dml.vba.StutterPeriod >5000.0 )return DCN_ZSTATE_SUPPORT_ALLOW ;else if (is_pwrseq0 && link->psr_settings.psr_version ==DC_PSR_VERSION_1 && !link->panel_config.psr.disable_psr)return allow_z8 ?DCN_ZSTATE_SUPPORT_ALLOW_Z8_Z10_ONLY :DCN_ZSTATE_SUPPORT_ALLOW_Z10_ONLY ;
Greg Kroah-Hartman
maintainerPATCH 23/107 drm/amd/display: Use DRAM speed from validation for dummy p-state
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alvin Lee <[email protected]>
commit 9be601135ba8ac69880c01606c82140f2dde105e upstream.
[Description]
When choosing which dummy p-state latency to use, we need to use the DRAM speed from validation. The DRAMSpeed DML variable can change because we use different input params to DML when populating watermarks set B.
--- drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c +2 -1
@@ -1788,6 +1788,7 @@ void dcn32_calculate_wm_and_dlg_fpu(struint i, pipe_idx, vlevel_temp =0 ;double dcfclk = dcn3_2_soc.clock_limits[0 ].dcfclk_mhz;double dcfclk_from_validation = context->bw_ctx.dml.vba.DCFCLKState[vlevel][context->bw_ctx.dml.vba.maxMpcComb]; +double dram_speed_from_validation = context->bw_ctx.dml.vba.DRAMSpeed;double dcfclk_from_fw_based_mclk_switching = dcfclk_from_validation;bool pstate_en = context->bw_ctx.dml.vba.DRAMClockChangeSupport[vlevel][context->bw_ctx.dml.vba.maxMpcComb] != dm_dram_clock_change_unsupported;
@@ -1921,7 +1922,7 @@ void dcn32_calculate_wm_and_dlg_fpu(stru }if (dc->clk_mgr->bw_params->wm_table.nv_entries[WM_C ].valid) { - min_dram_speed_mts = context->bw_ctx.dml.vba.DRAMSpeed; + min_dram_speed_mts = dram_speed_from_validation; min_dram_speed_mts_margin =160 ; context->bw_ctx.dml.soc.dram_clock_change_latency_us =
Greg Kroah-Hartman
maintainerPATCH 24/107 drm/amd/display: Update min Z8 residency time to 2100 for DCN314
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Kazlauskas <[email protected]>
commit 4636a211980052ca0df90265c8a3ed2d46099091 upstream.
[Why]
Some panels with residency period of 2054 exhibit flickering with Z8 at the end of the frame.
[How]
As a workaround, increase the limit to block these panels.
--- drivers/gpu/drm/amd/display/dc/dcn314/dcn314_resource.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/display/dc/dcn314/dcn314_resource.c +1 -1
@@ -884,7 +884,7 @@ static const struct dc_plane_cap plane_cstatic const struct dc_debug_options debug_defaults_drv = { .disable_z10 = false, .enable_z9_disable_interface = true, - .minimum_z8_residency_time =2000 , + .minimum_z8_residency_time =2100 , .psr_skip_crtc_disable = true, .disable_dmcu = true, .force_abm_enable = false,
Greg Kroah-Hartman
maintainerPATCH 25/107 drm/amd/display: fix ABM disablement
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hamza Mahfooz <[email protected]>
commit b9f46f0b98784e40288ee393f863f553fde062fa upstream.
On recent versions of DMUB firmware, if we want to completely disable ABM we have to pass ABM_LEVEL_IMMEDIATE_DISABLE as the requested ABM level to DMUB. Otherwise, LCD eDP displays are unable to reach their maximum brightness levels. So, to fix this whenever the user requests an ABM level of 0 pass ABM_LEVEL_IMMEDIATE_DISABLE to DMUB instead. Also, to keep the user's experience consistent map ABM_LEVEL_IMMEDIATE_DISABLE to 0 when a user tries to read the requested ABM level.
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +5 -3
@@ -6149,7 +6149,7 @@ int amdgpu_dm_connector_atomic_set_prope dm_new_state->underscan_enable = val; ret =0 ; }else if (property == adev->mode_info.abm_level_property) { - dm_new_state->abm_level = val; + dm_new_state->abm_level = val ?:ABM_LEVEL_IMMEDIATE_DISABLE ; ret =0 ; }
@@ -6194,7 +6194,8 @@ int amdgpu_dm_connector_atomic_get_prope *val = dm_state->underscan_enable; ret =0 ; }else if (property == adev->mode_info.abm_level_property) { - *val = dm_state->abm_level; + *val = (dm_state->abm_level !=ABM_LEVEL_IMMEDIATE_DISABLE ) ? + dm_state->abm_level :0 ; ret =0 ; }
@@ -6274,7 +6275,8 @@ void amdgpu_dm_connector_funcs_reset(str state->pbn =0 ;if (connector->connector_type == DRM_MODE_CONNECTOR_eDP) - state->abm_level = amdgpu_dm_abm_level; + state->abm_level = amdgpu_dm_abm_level ?: +ABM_LEVEL_IMMEDIATE_DISABLE ;__drm_atomic_helper_connector_reset (connector, &state->base); }
Greg Kroah-Hartman
maintainerPATCH 26/107 dm verity: initialize fec io before freeing it
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wu Bo <[email protected]>
commit 7be05bdfb4efc1396f7692562c7161e2b9f595f1 upstream.
If BIO error, verity_end_io() can call verity_finish_io() before verity_fec_init_io(). Therefore, fec_io->rs is not initialized and may crash when doing memory freeing in verity_fec_finish_io().
Crash call stack:
die+0x90/0x2b8 __do_kernel_fault+0x260/0x298 do_bad_area+0x2c/0xdc do_translation_fault+0x3c/0x54 do_mem_abort+0x54/0x118 el1_abort+0x38/0x5c el1h_64_sync_handler+0x50/0x90 el1h_64_sync+0x64/0x6c free_rs+0x18/0xac fec_rs_free+0x10/0x24 mempool_free+0x58/0x148 verity_fec_finish_io+0x4c/0xb0 verity_end_io+0xb8/0x150
--- drivers/md/dm-verity-target.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/md/dm-verity-target.c +2 -1
@@ -631,7 +631,6 @@ static void verity_work(struct work_stru io->in_tasklet = false; -verity_fec_init_io (io);verity_finish_io (io,errno_to_blk_status (verity_verify_io (io))); }
@@ -779,6 +778,8 @@ static int verity_map(struct dm_target * bio->bi_private = io; io->iter = bio->bi_iter; +verity_fec_init_io (io); +verity_submit_prefetch (v, io);submit_bio_noacct (bio);
Greg Kroah-Hartman
maintainerPATCH 27/107 dm verity: dont perform FEC for failed readahead IO
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wu Bo <[email protected]>
commit 0193e3966ceeeef69e235975918b287ab093082b upstream.
We found an issue under Android OTA scenario that many BIOs have to do FEC where the data under dm-verity is 100% complete and no corruption.
Android OTA has many dm-block layers, from upper to lower:
dm-verity
dm-snapshot
dm-origin & dm-cow
dm-linear
ufs
DM tables have to change 2 times during Android OTA merging process. When doing table change, the dm-snapshot will be suspended for a while. During this interval, many readahead IOs are submitted to dm_verity from filesystem. Then the kverity works are busy doing FEC process which cost too much time to finish dm-verity IO. This causes needless delay which feels like system is hung.
After adding debugging it was found that each readahead IO needed around 10s to finish when this situation occurred. This is due to IO amplification:
dm-snapshot suspenderofs_readahead // 300+ io is submitted
dm_submit_bio (dm_verity) dm_submit_bio (dm_snapshot) bio return EIO bio got nothing, it's empty verity_end_io verity_verify_io forloop range(0, io->n_blocks) // each io->nblocks ~= 20 verity_fec_decode fec_decode_rsb fec_read_bufs forloop range(0, v->fec->rsn) // v->fec->rsn = 253 new_read submit_bio (dm_snapshot) end loop end loop
dm-snapshot resume
Readahead BIOs get nothing while dm-snapshot is suspended, so all of them will cause verity's FEC.
Each readahead BIO needs to verify ~20 (io->nblocks) blocks. Each block needs to do FEC, and every block needs to do 253 (v->fec->rsn) reads.
So during the suspend interval(~200ms), 300 readahead BIOs trigger ~1518000 (300*20*253) IOs to dm-snapshot.
As readahead IO is not required by userspace, and to fix this issue, it is best to pass readahead errors to upper layer to handle it.
--- drivers/md/dm-verity-target.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/md/dm-verity-target.c +3 -1
@@ -656,7 +656,9 @@ static void verity_end_io(struct bio *bistruct dm_verity_io *io = bio->bi_private;if (bio->bi_status && - (!verity_fec_is_enabled (io->v) ||verity_is_system_shutting_down ())) { + (!verity_fec_is_enabled (io->v) || +verity_is_system_shutting_down () || + (bio->bi_opf &REQ_RAHEAD ))) {verity_finish_io (io, bio->bi_status);return ; }
Greg Kroah-Hartman
maintainerPATCH 28/107 nvme: check for valid nvme_identify_ns() before using it
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ewan D. Milne <[email protected]>
commit d8b90d600aff181936457f032d116dbd8534db06 upstream.
When scanning namespaces, it is possible to get valid data from the first call to nvme_identify_ns() in nvme_alloc_ns(), but not from the second call in nvme_update_ns_info_block(). In particular, if the NSID becomes inactive between the two commands, a storage device may return a buffer filled with zero as per 4.1.5.1. In this case, we can get a kernel crash due to a divide-by-zero in blk_stack_limits() because ns->lba_shift will be set to zero.
PID: 326 TASK: ffff95fec3cd8000 CPU: 29 COMMAND: "kworker/u98:10"
#0 [ffffad8f8702f9e0] machine_kexec at ffffffff91c76ec7 #1 [ffffad8f8702fa38] __crash_kexec at ffffffff91dea4fa #2 [ffffad8f8702faf8] crash_kexec at ffffffff91deb788 #3 [ffffad8f8702fb00] oops_end at ffffffff91c2e4bb #4 [ffffad8f8702fb20] do_trap at ffffffff91c2a4ce
#5 [ffffad8f8702fb70] do_error_trap at ffffffff91c2a595 #6 [ffffad8f8702fbb0] exc_divide_error at ffffffff928506e6 #7 [ffffad8f8702fbd0] asm_exc_divide_error at ffffffff92a00926
[exception RIP: blk_stack_limits+434]
RIP: ffffffff92191872 RSP: ffffad8f8702fc80 RFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff95efa0c91800 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: 00000000ffffffff R8: ffff95fec7df35a8 R9: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: ffff95fed33c09a8
ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #8 [ffffad8f8702fce0] nvme_update_ns_info_block at ffffffffc06d3533 [nvme_core] #9 [ffffad8f8702fd18] nvme_scan_ns at ffffffffc06d6fa7 [nvme_core]
This happened when the check for valid data was moved out of nvme_identify_ns() into one of the callers. Fix this by checking in both callers.
--- drivers/nvme/host/core.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/nvme/host/core.c +9 -0
@@ -2058,6 +2058,13 @@ static int nvme_update_ns_info_block(strif (ret)return ret; +if (id->ncap ==0 ) { +/* namespace not allocated or attached */ + info->is_removed = true; + ret = -ENODEV ; + goto error; + } +blk_mq_freeze_queue (ns->disk->queue); lbaf =nvme_lbaf_index (id->flbas); ns->lba_shift = id->lbaf[lbaf].ds;
@@ -2107,6 +2114,8 @@ out:set_bit (NVME_NS_READY , &ns->flags); ret =0 ; } + +error:kfree (id);return ret; }
Greg Kroah-Hartman
maintainerPATCH 29/107 powercap: DTPM: Fix unneeded conversions to micro-Watts
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lukasz Luba <[email protected]>
commit b817f1488fca548fe50e2654d84a1956a16a1a8a upstream.
The power values coming from the Energy Model are already in uW.
The PowerCap and DTPM frameworks operate on uW, so all places should just use the values from the EM.
Fix the code by removing all of the conversion to uW still present in it.
--- drivers/powercap/dtpm_cpu.c | 6 +----- drivers/powercap/dtpm_devfreq.c | 11 +++-------- 2 files changed, 4 insertions(+), 13 deletions(-)
drivers/powercap/dtpm_cpu.c +1 -5
@@ -24,7 +24,6 @@#include <linux/of.h> #include <linux/pm_qos.h> #include <linux/slab.h> -#include <linux/units.h> struct dtpm_cpu {struct dtpm dtpm;
@@ -104,8 +103,7 @@ static u64 get_pd_power_uw(struct dtpm *dtpm)if (pd->table[i].frequency < freq)continue ; -return scale_pd_power_uw (pd_mask, pd->table[i].power * -MICROWATT_PER_MILLIWATT ); +return scale_pd_power_uw (pd_mask, pd->table[i].power); }return 0 ;
@@ -122,11 +120,9 @@ static int update_pd_power_uw(struct dtpm *dtpm) nr_cpus =cpumask_weight (&cpus); dtpm->power_min = em->table[0 ].power; - dtpm->power_min *=MICROWATT_PER_MILLIWATT ; dtpm->power_min *= nr_cpus; dtpm->power_max = em->table[em->nr_perf_states -1 ].power; - dtpm->power_max *=MICROWATT_PER_MILLIWATT ; dtpm->power_max *= nr_cpus;return 0 ;
drivers/powercap/dtpm_devfreq.c +3 -8
@@ -39,10 +39,8 @@ static int update_pd_power_uw(struct dtpm *dtpm)struct em_perf_domain *pd =em_pd_get (dev); dtpm->power_min = pd->table[0 ].power; - dtpm->power_min *=MICROWATT_PER_MILLIWATT ; dtpm->power_max = pd->table[pd->nr_perf_states -1 ].power; - dtpm->power_max *=MICROWATT_PER_MILLIWATT ;return 0 ; }
@@ -54,13 +52,10 @@ static u64 set_pd_power_limit(struct dtpm *dtpm, u64 power_limit)struct device *dev = devfreq->dev.parent;struct em_perf_domain *pd =em_pd_get (dev);unsigned long freq; -u64 power;int i;for (i =0 ; i < pd->nr_perf_states; i++) { - - power = pd->table[i].power *MICROWATT_PER_MILLIWATT ; -if (power > power_limit) +if (pd->table[i].power > power_limit)break ; }
@@ -68,7 +63,7 @@ static u64 set_pd_power_limit(struct dtpm *dtpm, u64 power_limit)dev_pm_qos_update_request (&dtpm_devfreq->qos_req, freq); - power_limit = pd->table[i -1 ].power *MICROWATT_PER_MILLIWATT ; + power_limit = pd->table[i -1 ].power;return power_limit; }
@@ -110,7 +105,7 @@ static u64 get_pd_power_uw(struct dtpm *dtpm)if (pd->table[i].frequency < freq)continue ; - power = pd->table[i].power *MICROWATT_PER_MILLIWATT ; + power = pd->table[i].power; power *= status.busy_time; power >>=10 ;
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 30/107 cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gautham R. Shenoy <[email protected]>
commit bb87be267b8ee9b40917fb5bf51be5ddb33c37c2 upstream.
cpufreq_driver->fast_switch() callback expects a frequency as a return value. amd_pstate_fast_switch() was returning the return value of amd_pstate_update_freq(), which only indicates a success or failure.
Fix this by making amd_pstate_fast_switch() return the target_freq when the call to amd_pstate_update_freq() is successful, and return the current frequency from policy->cur when the call to amd_pstate_update_freq() is unsuccessful.
--- drivers/cpufreq/amd-pstate.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/cpufreq/amd-pstate.c +3 -1
@@ -296,7 +296,9 @@ static int amd_pstate_target(struct cpufstatic unsigned int amd_pstate_fast_switch (struct cpufreq_policy *policy,unsigned int target_freq) { -return amd_pstate_update_freq (policy, target_freq, true); +if (!amd_pstate_update_freq (policy, target_freq, true)) +return target_freq; +return policy->cur; } static void amd_pstate_adjust_perf(unsigned int cpu,
Greg Kroah-Hartman
maintainerPATCH 31/107 dma-buf: fix check in dma_resv_add_fence
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christian König <[email protected]>
commit 95ba893c9f4feb836ddce627efd0bb6af6667031 upstream.
It's valid to add the same fence multiple times to a dma-resv object and we shouldn't need one extra slot for each.
--- drivers/dma-buf/dma-resv.c | 2 +- include/linux/dma-fence.h | 15 +++++++++++++++ 2 files changed, 16 insertions(+), 1 deletion(-)
drivers/dma-buf/dma-resv.c +1 -1
@@ -296,7 +296,7 @@ void dma_resv_add_fence(struct dma_resvdma_resv_list_entry (fobj, i, obj, &old, &old_usage);if ((old->context == fence->context && old_usage >= usage && -dma_fence_is_later (fence, old)) || +dma_fence_is_later_or_same (fence, old)) ||dma_fence_is_signaled (old)) {dma_resv_list_set (fobj, i, fence, usage);dma_fence_put (old);
include/linux/dma-fence.h +15 -0
@@ -479,6 +479,21 @@ static inline bool dma_fence_is_later(st }/** +* dma_fence_is_later_or_same - return true if f1 is later or same as f2 +* @f1: the first fence from the same context +* @f2: the second fence from the same context +* +* Returns true if f1 is chronologically later than f2 or the same fence. Both +* fences must be from the same context, since a seqno is not re-used across +* contexts. +*/ +static inline bool dma_fence_is_later_or_same (struct dma_fence *f1, +struct dma_fence *f2) +{ +return f1 == f2 ||dma_fence_is_later (f1, f2); +} + +/** * dma_fence_later - return the chronologically later fence * @f1: the first fence from the same context * @f2: the second fence from the same context
Greg Kroah-Hartman
maintainerPATCH 32/107 bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Markus Weippert <[email protected]>
commit bb6cc253861bd5a7cf8439e2118659696df9619f upstream.
Commit 028ddcac477b ("bcache: Remove unnecessary NULL point check in node allocations") replaced IS_ERR_OR_NULL by IS_ERR. This leads to a NULL pointer dereference.
BUG: kernel NULL pointer dereference, address: 0000000000000080 Call Trace: ? __die_body.cold+0x1a/0x1f ? page_fault_oops+0xd2/0x2b0 ? exc_page_fault+0x70/0x170 ? asm_exc_page_fault+0x22/0x30 ? btree_node_free+0xf/0x160 [bcache] ? up_write+0x32/0x60 btree_gc_coalesce+0x2aa/0x890 [bcache] ? bch_extent_bad+0x70/0x170 [bcache] btree_gc_recurse+0x130/0x390 [bcache] ? btree_gc_mark_node+0x72/0x230 [bcache] bch_btree_gc+0x5da/0x600 [bcache] ? cpuusage_read+0x10/0x10 ? bch_btree_gc+0x600/0x600 [bcache] bch_gc_thread+0x135/0x180 [bcache]
The relevant code starts with:
new_nodes[0] = NULL;
for (i = 0; i < nodes; i++) {
if (__bch_keylist_realloc(&keylist, bkey_u64s(&r[i].b->key)))
goto out_nocoalesce;
// ...
out_nocoalesce:
// ...
for (i = 0; i < nodes; i++)
if (!IS_ERR(new_nodes[i])) { // IS_ERR_OR_NULL before
028ddcac477b
btree_node_free(new_nodes[i]); // new_nodes[0] is NULL
rw_unlock(true, new_nodes[i]);
}This patch replaces IS_ERR() by IS_ERR_OR_NULL() to fix this.
--- drivers/md/bcache/btree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/md/bcache/btree.c +1 -1
@@ -1489,7 +1489,7 @@ out_nocoalesce:bch_keylist_free (&keylist);for (i =0 ; i < nodes; i++) -if (!IS_ERR (new_nodes[i])) { +if (!IS_ERR_OR_NULL (new_nodes[i])) {btree_node_free (new_nodes[i]);rw_unlock (true, new_nodes[i]); }
Greg Kroah-Hartman
maintainerPATCH 33/107 iommu/vt-d: Add MTL to quirk list to skip TE disabling
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Abdul Halim, Mohd Syazwan <[email protected]>
commit 85b80fdffa867d75dfb9084a839e7949e29064e8 upstream.
The VT-d spec requires (10.4.4 Global Command Register, TE field) that:
Hardware implementations supporting DMA draining must drain any in-flight DMA read/write requests queued within the Root-Complex before switching address translation on or off and reflecting the status of the command through the TES field in the Global Status register.
Unfortunately, some integrated graphic devices fail to do so after some kind of power state transition. As the result, the system might stuck in iommu_disable_translation(), waiting for the completion of TE transition.
Add MTL to the quirk list for those devices and skips TE disabling if the qurik hits.
--- drivers/iommu/intel/iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/intel/iommu.c +1 -1
@@ -4872,7 +4872,7 @@ static void quirk_igfx_skip_te_disable(s ver = (dev->device >>8 ) &0xff ;if (ver !=0x45 && ver !=0x46 && ver !=0x4c && ver !=0x4e && ver !=0x8a && ver !=0x98 && - ver !=0x9a && ver !=0xa7 ) + ver !=0x9a && ver !=0xa7 && ver !=0x7d )return ;if (risky_device (dev))
Greg Kroah-Hartman
maintainerPATCH 34/107 KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Piggin <[email protected]>
commit dc158d23b33df9033bcc8e7117e8591dd2f9d125 upstream.
Before running a guest, the host process (e.g., QEMU) FP/VEC registers are saved if they were being used, similarly to when the kernel uses FP registers. The guest values are then loaded into regs, and the host process registers will be restored lazily when it uses FP/VEC.
KVM HV has a bug here: the host process registers do get saved, but the user MSR bits remain enabled, which indicates the registers are valid for the process. After they are clobbered by running the guest, this valid indication causes the host process to take on the FP/VEC register values of the guest.
--- arch/powerpc/kernel/process.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/powerpc/kernel/process.c +3 -3
@@ -1163,11 +1163,11 @@ void kvmppc_save_user_regs(void) usermsr = current->thread.regs->msr; +/* Caller has enabled FP/VEC/VSX/TM in MSR */ if (usermsr &MSR_FP ) -save_fpu (current); - +__giveup_fpu (current);if (usermsr &MSR_VEC ) -save_altivec (current); +__giveup_altivec (current);#ifdef CONFIG_PPC_TRANSACTIONAL_MEM if (usermsr &MSR_TM ) {
Greg Kroah-Hartman
maintainerPATCH 35/107 powerpc: Dont clobber f0/vs0 during fp|altivec register save
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Timothy Pearson <[email protected]>
commit 5e1d824f9a283cbf90f25241b66d1f69adb3835b upstream.
During floating point and vector save to thread data f0/vs0 are clobbered by the FPSCR/VSCR store routine. This has been obvserved to lead to userspace register corruption and application data corruption with io-uring.
Fix it by restoring f0/vs0 after FPSCR/VSCR store has completed for all the FP, altivec, VMX register save paths.
Tested under QEMU in kvm mode, running on a Talos II workstation with dual POWER9 DD2.2 CPUs.
Additional detail (mpe):
Typically save_fpu() is called from __giveup_fpu() which saves the FP regs and also *turns off FP* in the tasks MSR, meaning the kernel will reload the FP regs from the thread struct before letting the task use FP again. So in that case save_fpu() is free to clobber f0 because the FP regs no longer hold live values for the task.
There is another case though, which is the path via:
sys_clone()
...
copy_process()
dup_task_struct()
arch_dup_task_struct()
flush_all_to_thread()
save_all()That path saves the FP regs but leaves them live. That's meant as an optimisation for a process that's using FP/VSX and then calls fork(), leaving the regs live means the parent process doesn't have to take a fault after the fork to get its FP regs back. The optimisation was added in commit 8792468da5e1 ("powerpc: Add the ability to save FPU without giving it up").
That path does clobber f0, but f0 is volatile across function calls, and typically programs reach copy_process() from userspace via a syscall wrapper function. So in normal usage f0 being clobbered across a syscall doesn't cause visible data corruption.
But there is now a new path, because io-uring can call copy_process() via create_io_thread() from the signal handling path. That's OK if the signal is handled as part of syscall return, but it's not OK if the signal is handled due to some other interrupt.
That path is:
interrupt_return_srr_user()
interrupt_exit_user_prepare()
interrupt_exit_user_prepare_main()
do_notify_resume()
get_signal()
task_work_run()
create_worker_cb()
create_io_worker()
copy_process()
dup_task_struct()
arch_dup_task_struct()
flush_all_to_thread()
save_all()
if (tsk->thread.regs->msr & MSR_FP)
save_fpu()
# f0 is clobbered and potentially live in userspaceNote the above discussion applies equally to save_altivec().
--- arch/powerpc/kernel/fpu.S | 13 +++++++++++++ arch/powerpc/kernel/vector.S | 2 ++ 2 files changed, 15 insertions(+)
arch/powerpc/kernel/fpu.S +13 -0
@@ -23,6 +23,15 @@ #include <asm/feature-fixups.h> #ifdef CONFIG_VSX +#define __REST_1FPVSR(n,c,base) \ +BEGIN_FTR_SECTION \ + b 2f; \ +END_FTR_SECTION_IFSET(CPU_FTR_VSX); \ + REST_FPR(n,base); \ + b 3f; \ +2: REST_VSR(n,c,base); \ +3: + #define __REST_32FPVSRS(n,c,base) \ BEGIN_FTR_SECTION \ b 2f; \
@@ -41,9 +50,11 @@ END_FTR_SECTION_IFSET(CPU_FTR_VSX); 2: SAVE_32VSRS(n,c,base); \ 3: #else +#define __REST_1FPVSR(n,b,base) REST_FPR(n, base) #define __REST_32FPVSRS(n,b,base) REST_32FPRS(n, base) #define __SAVE_32FPVSRS(n,b,base) SAVE_32FPRS(n, base) #endif +#define REST_1FPVSR(n,c,base) __REST_1FPVSR(n,__REG_##c,__REG_##base) #define REST_32FPVSRS(n,c,base) __REST_32FPVSRS(n,__REG_##c,__REG_##base) #define SAVE_32FPVSRS(n,c,base) __SAVE_32FPVSRS(n,__REG_##c,__REG_##base)
@@ -67,6 +78,7 @@ _GLOBAL(store_fp_state) SAVE_32FPVSRS(0, R4, R3) mffs fr0 stfd fr0,FPSTATE_FPSCR(r3) + REST_1FPVSR(0, R4, R3) blr EXPORT_SYMBOL(store_fp_state)
@@ -138,4 +150,5 @@ _GLOBAL(save_fpu) 2: SAVE_32FPVSRS(0, R4, R6) mffs fr0 stfd fr0,FPSTATE_FPSCR(r6) + REST_1FPVSR(0, R4, R6) blr
arch/powerpc/kernel/vector.S +2 -0
@@ -32,6 +32,7 @@ _GLOBAL(store_vr_state) mfvscr v0 li r4, VRSTATE_VSCR stvx v0, r4, r3 + lvx v0, 0, r3 blr EXPORT_SYMBOL(store_vr_state)
@@ -108,6 +109,7 @@ _GLOBAL(save_altivec) mfvscr v0 li r4,VRSTATE_VSCR stvx v0,r4,r7 + lvx v0,0,r7 blr #ifdef CONFIG_VSX
Greg Kroah-Hartman
maintainerPATCH 36/107 parisc: Mark ex_table entries 32-bit aligned in assembly.h
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit e11d4cccd094a7cd4696c8c42e672c76c092dad5 upstream.
Add an align statement to tell the linker that all ex_table entries and as such the whole ex_table section should be 32-bit aligned in vmlinux and modules.
--- arch/parisc/include/asm/assembly.h | 1 + 1 file changed, 1 insertion(+)
arch/parisc/include/asm/assembly.h +1 -0
@@ -574,6 +574,7 @@*/ #define ASM_EXCEPTIONTABLE_ENTRY (fault_addr, except_addr) \ .section __ex_table,"aw" ! \ + .align 4 ! \ .word (fault_addr - .), (except_addr - .) ! \ .previous
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 37/107 parisc: Mark ex_table entries 32-bit aligned in uaccess.h
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit a80aeb86542a50aa8521729ea4cc731ee7174f03 upstream.
Add an align statement to tell the linker that all ex_table entries and as such the whole ex_table section should be 32-bit aligned in vmlinux and modules.
--- arch/parisc/include/asm/uaccess.h | 1 + 1 file changed, 1 insertion(+)
arch/parisc/include/asm/uaccess.h +1 -0
@@ -41,6 +41,7 @@ struct exception_table_entry {#define ASM_EXCEPTIONTABLE_ENTRY ( fault_addr, except_addr )\ ".section __ex_table,\"aw\"\n" \ + ".align 4\n" \ ".word (" #fault_addr " - .), (" #except_addr " - .)\n\t" \ ".previous\n"
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 38/107 parisc: Use natural CPU alignment for bug_table
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit fe76a1349f235969381832c83d703bc911021eb6 upstream.
Make sure that the __bug_table section gets 32- or 64-bit aligned, depending if a 32- or 64-bit kernel is being built.
Mark it non-writeable and use .blockz instead of the .org assembler directive to pad the struct.
--- arch/parisc/include/asm/bug.h | 30 ++++++++++++++++++------------ 1 file changed, 18 insertions(+), 12 deletions(-)
arch/parisc/include/asm/bug.h +18 -12
@@ -28,13 +28,15 @@do { \ asmvolatile ("\n" \"1:\t" PARISC_BUG_BREAK_ASM "\n" \ -"\t.pushsection __bug_table,\"aw\"\n" \ +"\t.pushsection __bug_table,\"a\"\n" \ +"\t.align %4\n" \"2:\t" ASM_WORD_INSN "1b, %c0\n" \ -"\t.short %c1, %c2\n" \ -"\t.org 2b+%c3\n" \ +"\t.short %1, %2\n" \ +"\t.blockz %3-2*%4-2*2\n" \"\t.popsection" \ : :"i" (__FILE__),"i" (__LINE__), \ -"i" (0 ),"i" (sizeof (struct bug_entry )) ); \ +"i" (0 ),"i" (sizeof (struct bug_entry )), \ +"i" (sizeof (long )) ); \unreachable (); \ }while (0 )
@@ -51,27 +53,31 @@do { \ asmvolatile ("\n" \"1:\t" PARISC_BUG_BREAK_ASM "\n" \ -"\t.pushsection __bug_table,\"aw\"\n" \ +"\t.pushsection __bug_table,\"a\"\n" \ +"\t.align %4\n" \"2:\t" ASM_WORD_INSN "1b, %c0\n" \ -"\t.short %c1, %c2\n" \ -"\t.org 2b+%c3\n" \ +"\t.short %1, %2\n" \ +"\t.blockz %3-2*%4-2*2\n" \"\t.popsection" \ : :"i" (__FILE__),"i" (__LINE__), \"i" (BUGFLAG_WARNING |(flags)), \ -"i" (sizeof (struct bug_entry )) ); \ +"i" (sizeof (struct bug_entry )), \ +"i" (sizeof (long )) ); \ } while(0)#else #define __WARN_FLAGS (flags) \ do { \ asm volatile("\n" \ "1:\t" PARISC_BUG_BREAK_ASM "\n" \ - "\t.pushsection __bug_table,\"aw\"\n" \ + "\t.pushsection __bug_table,\"a\"\n" \ + "\t.align %2\n" \ "2:\t" ASM_WORD_INSN "1b\n" \ - "\t.short %c0\n" \ - "\t.org 2b+%c1\n" \ + "\t.short %0\n" \ + "\t.blockz %1-%2-2\n" \ "\t.popsection" \ : : "i" (BUGFLAG_WARNING|(flags)), \ - "i" (sizeof(struct bug_entry)) ); \ + "i" (sizeof(struct bug_entry)), \ + "i" (sizeof(long)) ); \ } while(0)#endif
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 39/107 parisc: Mark lock_aligned variables 16-byte aligned on SMP
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit b28fc0d8739c03e7b6c44914a9d00d4c6dddc0ea upstream.
On parisc we need 16-byte alignment for variables which are used for locking. Mark the __lock_aligned attribute acordingly so that the .data..lock_aligned section will get that alignment in the generated object files.
--- arch/parisc/include/asm/ldcw.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/parisc/include/asm/ldcw.h +1 -1
@@ -56,7 +56,7 @@ })#ifdef CONFIG_SMP -# define __lock_aligned __section(".data..lock_aligned") +# define __lock_aligned __section(".data..lock_aligned") __aligned(16)#endif #endif /* __PARISC_LDCW_H */
Greg Kroah-Hartman
maintainerPATCH 40/107 parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit e5f3e299a2b1e9c3ece24a38adfc089aef307e8a upstream.
Those return codes are only defined for the parisc architecture and are leftovers from when we wanted to be HP-UX compatible.
They are not returned by any Linux kernel syscall but do trigger problems with the glibc strerrorname_np() and strerror() functions as reported in glibc issue #31080.
There is no need to keep them, so simply remove them.
--- arch/parisc/include/uapi/asm/errno.h | 2 -- lib/errname.c | 6 ------ tools/arch/parisc/include/uapi/asm/errno.h | 2 -- 3 files changed, 10 deletions(-)
arch/parisc/include/uapi/asm/errno.h +0 -2
@@ -75,7 +75,6 @@/* We now return you to your regularly scheduled HPUX. */ -#define ENOSYM 215/* symbol does not exist in executable */ #define ENOTSOCK 216/* Socket operation on non-socket */ #define EDESTADDRREQ 217/* Destination address required */ #define EMSGSIZE 218/* Message too long */
@@ -101,7 +100,6 @@#define ETIMEDOUT 238/* Connection timed out */ #define ECONNREFUSED 239/* Connection refused */ #define EREFUSED ECONNREFUSED/* for HP's NFS apparently */ -#define EREMOTERELEASE 240/* Remote peer released connection */ #define EHOSTDOWN 241/* Host is down */ #define EHOSTUNREACH 242/* No route to host */
lib/errname.c +0 -6
@@ -111,9 +111,6 @@ static const char *names_0[] = {E (ENOSPC ),E (ENOSR ),E (ENOSTR ), -#ifdef ENOSYM -E (ENOSYM ), -#endifE (ENOSYS ),E (ENOTBLK ), E(ENOTCONN),
@@ -144,9 +141,6 @@ static const char *names_0[] = {#endif E (EREMOTE ),E (EREMOTEIO ), -#ifdef EREMOTERELEASE -E (EREMOTERELEASE ), -#endifE (ERESTART ),E (ERFKILL ), E(EROFS),
tools/arch/parisc/include/uapi/asm/errno.h +0 -2
@@ -75,7 +75,6 @@/* We now return you to your regularly scheduled HPUX. */ -#define ENOSYM 215/* symbol does not exist in executable */ #define ENOTSOCK 216/* Socket operation on non-socket */ #define EDESTADDRREQ 217/* Destination address required */ #define EMSGSIZE 218/* Message too long */
@@ -101,7 +100,6 @@#define ETIMEDOUT 238/* Connection timed out */ #define ECONNREFUSED 239/* Connection refused */ #define EREFUSED ECONNREFUSED/* for HP's NFS apparently */ -#define EREMOTERELEASE 240/* Remote peer released connection */ #define EHOSTDOWN 241/* Host is down */ #define EHOSTUNREACH 242/* No route to host */
Greg Kroah-Hartman
maintainerPATCH 41/107 parisc: Mark jump_table naturally aligned
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit 07eecff8ae78df7f28800484d31337e1f9bfca3a upstream.
The jump_table stores two 32-bit words and one 32- (on 32-bit kernel) or one 64-bit word (on 64-bit kernel).
Ensure that the last word is always 64-bit aligned on a 64-bit kernel by aligning the whole structure on sizeof(long).
--- arch/parisc/include/asm/jump_label.h | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
arch/parisc/include/asm/jump_label.h +6 -2
@@ -15,10 +15,12 @@ static __always_inline bool arch_static_branch(struct static_key *key, bool bran asm_volatile_goto("1:\n\t" "nop\n\t" ".pushsection __jump_table, \"aw\"\n\t" + ".align %1\n\t" ".word 1b - ., %l[l_yes] - .\n\t" __stringify(ASM_ULONG_INSN) " %c0 - .\n\t" ".popsection\n\t" - : : "i" (&((char *)key)[branch]) : : l_yes); + : : "i" (&((char *)key)[branch]), "i" (sizeof(long)) + : : l_yes);return false; l_yes:
@@ -30,10 +32,12 @@ static __always_inline bool arch_static_branch_jump(struct static_key *key, bool asm_volatile_goto("1:\n\t" "b,n %l[l_yes]\n\t" ".pushsection __jump_table, \"aw\"\n\t" + ".align %1\n\t" ".word 1b - ., %l[l_yes] - .\n\t" __stringify(ASM_ULONG_INSN) " %c0 - .\n\t" ".popsection\n\t" - : : "i" (&((char *)key)[branch]) : : l_yes); + : : "i" (&((char *)key)[branch]), "i" (sizeof(long)) + : : l_yes);return false; l_yes:
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 42/107 parisc: Ensure 32-bit alignment on parisc unwind section
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit c9fcb2b65c2849e8ff3be23fd8828312fb68dc19 upstream.
Make sure the .PARISC.unwind section will be 32-bit aligned.
--- arch/parisc/kernel/vmlinux.lds.S | 1 + 1 file changed, 1 insertion(+)
arch/parisc/kernel/vmlinux.lds.S +1 -0
@@ -131,6 +131,7 @@ SECTIONS RO_DATA(8) /* unwind info */ + . = ALIGN(4); .PARISC.unwind : { __start___unwind = .; *(.PARISC.unwind)
Greg Kroah-Hartman
maintainerPATCH 43/107 parisc: Mark altinstructions read-only and 32-bit aligned
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
commit 33f806da2df68606f77d7b892cd1298ba3d463e8 upstream.
--- arch/parisc/include/asm/alternative.h | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
arch/parisc/include/asm/alternative.h +6 -3
@@ -34,7 +34,8 @@ void apply_alternatives(struct alt_instr *start, struct alt_instr *end,/* Alternative SMP implementation. */ #define ALTERNATIVE (cond, replacement) "!0:" \ - ".section .altinstructions, \"aw\" !" \ + ".section .altinstructions, \"a\" !" \ + ".align 4 !" \ ".word (0b-4-.) !" \ ".hword 1, " __stringify(cond) " !" \ ".word " __stringify(replacement) " !" \
@@ -44,7 +45,8 @@ void apply_alternatives(struct alt_instr *start, struct alt_instr *end,/* to replace one single instructions by a new instruction */ #define ALTERNATIVE (from, to, cond, replacement)\ - .section .altinstructions, "aw" ! \ + .section .altinstructions, "a" ! \ + .align 4 ! \ .word (from - .) ! \ .hword (to - from)/4, cond ! \ .word replacement ! \
@@ -52,7 +54,8 @@ void apply_alternatives(struct alt_instr *start, struct alt_instr *end,/* to replace multiple instructions by new code */ #define ALTERNATIVE_CODE (from, num_instructions, cond, new_instr_ptr)\ - .section .altinstructions, "aw" ! \ + .section .altinstructions, "a" ! \ + .align 4 ! \ .word (from - .) ! \ .hword -num_instructions, cond ! \ .word (new_instr_ptr - .) ! \
Signature · 1 line
2.43.0
Greg Kroah-Hartman
maintainerPATCH 44/107 btrfs: add dmesg output for first mount and last unmount of a filesystem
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Qu Wenruo <[email protected]>
commit 2db313205f8b96eea467691917138d646bb50aef upstream.
There is a feature request to add dmesg output when unmounting a btrfs. There are several alternative methods to do the same thing, but with their own problems:
- Use eBPF to watch btrfs_put_super()/open_ctree()
Not end user friendly, they have to dip their head into the source code.
- Watch for directory /sys/fs/<uuid>/
This is way more simple, but still requires some simple device -> uuid lookups. And a script needs to use inotify to watch /sys/fs/.
Compared to all these, directly outputting the information into dmesg would be the most simple one, with both device and UUID included.
And since we're here, also add the output when mounting a filesystem for the first time for parity. A more fine grained monitoring of subvolume mounts should be done by another layer, like audit.
Now mounting a btrfs with all default mkfs options would look like this:
[81.906566] BTRFS info (device dm-8): first mount of filesystem 633b5c16-afe3-4b79-b195-138fe145e4f2 [81.907494] BTRFS info (device dm-8): using crc32c (crc32c-intel) checksum algorithm [81.908258] BTRFS info (device dm-8): using free space tree [81.912644] BTRFS info (device dm-8): auto enabling async discard [81.913277] BTRFS info (device dm-8): checking UUID tree [91.668256] BTRFS info (device dm-8): last unmount of filesystem 633b5c16-afe3-4b79-b195-138fe145e4f2
--- fs/btrfs/disk-io.c | 1 + fs/btrfs/super.c | 5 ++++- 2 files changed, 5 insertions(+), 1 deletion(-)
fs/btrfs/disk-io.c +1 -0
@@ -3493,6 +3493,7 @@ int __cold open_ctree(struct super_block goto fail_alloc; } +btrfs_info (fs_info,"first mount of filesystem %pU" , disk_super->fsid);/* * Verify the type first, if that or the checksum value are * corrupted, we'll find out
fs/btrfs/super.c +4 -1
@@ -391,7 +391,10 @@ void __btrfs_panic(struct btrfs_fs_infostatic void btrfs_put_super (struct super_block *sb) { -close_ctree (btrfs_sb (sb)); +struct btrfs_fs_info *fs_info =btrfs_sb (sb); + +btrfs_info (fs_info,"last unmount of filesystem %pU" , fs_info->fs_devices->fsid); +close_ctree (fs_info); }enum {
Greg Kroah-Hartman
maintainerPATCH 45/107 btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bragatheswaran Manickavel <[email protected]>
commit f91192cd68591c6b037da345bc9fcd5e50540358 upstream.
In btrfs_ref_tree_mod(), when !parent 're' was allocated through kmalloc(). In the following code, if an error occurs, the execution will be redirected to 'out' or 'out_unlock' and the function will be exited. However, on some of the paths, 're' are not deallocated and may lead to memory leaks.
For example: lookup_block_entry() for 'be' returns NULL, the out label will be invoked. During that flow ref and 'ra' are freed but not 're', which can potentially lead to a memory leak.
--- fs/btrfs/ref-verify.c | 2 ++ 1 file changed, 2 insertions(+)
fs/btrfs/ref-verify.c +2 -0
@@ -788,6 +788,7 @@ int btrfs_ref_tree_mod(struct btrfs_fs_idump_ref_action (fs_info, ra);kfree (ref);kfree (ra); +kfree (re); goto out_unlock; }else if (be->num_refs ==0 ) { btrfs_err(fs_info,
@@ -797,6 +798,7 @@ int btrfs_ref_tree_mod(struct btrfs_fs_idump_ref_action (fs_info, ra);kfree (ref);kfree (ra); +kfree (re); goto out_unlock; }
Greg Kroah-Hartman
maintainerPATCH 46/107 btrfs: fix off-by-one when checking chunk map includes logical address
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Filipe Manana <[email protected]>
commit 5fba5a571858ce2d787fdaf55814e42725bfa895 upstream.
At btrfs_get_chunk_map() we get the extent map for the chunk that contains the given logical address stored in the 'logical' argument. Then we do sanity checks to verify the extent map contains the logical address. One of these checks verifies if the extent map covers a range with an end offset behind the target logical address - however this check has an off-by-one error since it will consider an extent map whose start offset plus its length matches the target logical address as inclusive, while the fact is that the last byte it covers is behind the target logical address (by 1).
So fix this condition by using '<=' rather than '<' when comparing the extent map's "start + length" against the target logical address.
--- fs/btrfs/volumes.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/btrfs/volumes.c +1 -1
@@ -3079,7 +3079,7 @@ struct extent_map *btrfs_get_chunk_map(sreturn ERR_PTR (-EINVAL ); } -if (em->start > logical || em->start + em->len < logical) { +if (em->start > logical || em->start + em->len <= logical) {btrfs_crit (fs_info,"found a bad mapping, wanted %llu-%llu, found %llu-%llu" , logical, length, em->start, em->start + em->len);
Greg Kroah-Hartman
maintainerPATCH 47/107 btrfs: send: ensure send_fd is writable
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jann Horn <[email protected]>
commit 0ac1d13a55eb37d398b63e6ff6db4a09a2c9128c upstream.
kernel_write() requires the caller to ensure that the file is writable. Let's do that directly after looking up the ->send_fd.
We don't need a separate bailout path because the "out" path already does fput() if ->send_filp is non-NULL.
This has no security impact for two reasons:
- the ioctl requires CAP_SYS_ADMIN
- __kernel_write() bails out on read-only files - but only since 5.8, see commit a01ac27be472 ("fs: check FMODE_WRITE in __kernel_write")
--- fs/btrfs/send.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/btrfs/send.c +1 -1
@@ -7885,7 +7885,7 @@ long btrfs_ioctl_send(struct inode *inod } sctx->send_filp =fget (arg->send_fd); -if (!sctx->send_filp) { +if (!sctx->send_filp || !(sctx->send_filp->f_mode &FMODE_WRITE )) { ret = -EBADF ; goto out; }
Greg Kroah-Hartman
maintainerPATCH 48/107 btrfs: make error messages more clear when getting a chunk map
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Filipe Manana <[email protected]>
commit 7d410d5efe04e42a6cd959bfe6d59d559fdf8b25 upstream.
When getting a chunk map, at btrfs_get_chunk_map(), we do some sanity checks to verify we found a chunk map and that map found covers the logical address the caller passed in. However the messages aren't very clear in the sense that don't mention the issue is with a chunk map and one of them prints the 'length' argument as if it were the end offset of the requested range (while the in the string format we use %llu-%llu which suggests a range, and the second %llu-%llu is actually a range for the chunk map). So improve these two details in the error messages.
--- fs/btrfs/volumes.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
fs/btrfs/volumes.c +4 -3
@@ -3074,15 +3074,16 @@ struct extent_map *btrfs_get_chunk_map(sread_unlock (&em_tree->lock);if (!em) { -btrfs_crit (fs_info,"unable to find logical %llu length %llu" , +btrfs_crit (fs_info, +"unable to find chunk map for logical %llu length %llu" , logical, length);return ERR_PTR (-EINVAL ); }if (em->start > logical || em->start + em->len <= logical) {btrfs_crit (fs_info, -"found a bad mapping, wanted %llu-%llu, found %llu-%llu" , - logical, length, em->start, em->start + em->len); +"found a bad chunk map, wanted %llu-%llu, found %llu-%llu" , + logical, logical + length, em->start, em->start + em->len);free_extent_map (em);return ERR_PTR (-EINVAL ); }
Greg Kroah-Hartman
maintainerPATCH 49/107 btrfs: fix 64bit compat send ioctl arguments not initializing version member
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Sterba <[email protected]>
commit 5de0434bc064606d6b7467ec3e5ad22963a18c04 upstream.
When the send protocol versioning was added in 5.16 e77fbf990316 ("btrfs: send: prepare for v2 protocol"), the 32/64bit compat code was not updated (added by 2351f431f727 ("btrfs: fix send ioctl on 32bit with 64bit kernel")), missing the version struct member. The compat code is probably rarely used, nobody reported any bugs.
Found by tool https://github.com/jirislaby/clang-struct .
--- fs/btrfs/ioctl.c | 1 + 1 file changed, 1 insertion(+)
fs/btrfs/ioctl.c +1 -0
@@ -5236,6 +5236,7 @@ static int _btrfs_ioctl_send(struct inod arg->clone_sources =compat_ptr (args32.clone_sources); arg->parent_root = args32.parent_root; arg->flags = args32.flags; + arg->version = args32.version;memcpy (arg->reserved, args32.reserved,sizeof (args32.reserved));#else
Greg Kroah-Hartman
maintainerPATCH 50/107 Input: xpad - add HyperX Clutch Gladiate Support
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Max Nguyen <[email protected]>
commit e28a0974d749e5105d77233c0a84d35c37da047e upstream.
Add HyperX controller support to xpad_device and xpad_table.
--- drivers/input/joystick/xpad.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/input/joystick/xpad.c +2 -0
@@ -136,6 +136,7 @@ static const struct xpad_device { { 0x044f, 0x0f07, "Thrustmaster, Inc. Controller", 0, XTYPE_XBOX }, { 0x044f, 0x0f10, "Thrustmaster Modena GT Wheel", 0, XTYPE_XBOX }, { 0x044f, 0xb326, "Thrustmaster Gamepad GP XID", 0, XTYPE_XBOX360 }, + { 0x03f0, 0x0495, "HyperX Clutch Gladiate", 0, XTYPE_XBOXONE }, { 0x045e, 0x0202, "Microsoft X-Box pad v1 (US)", 0, XTYPE_XBOX }, { 0x045e, 0x0285, "Microsoft X-Box pad (Japan)", 0, XTYPE_XBOX }, { 0x045e, 0x0287, "Microsoft Xbox Controller S", 0, XTYPE_XBOX },
@@ -459,6 +460,7 @@ static const struct usb_device_id xpad_tXPAD_XBOX360_VENDOR (0x0079 ),/* GPD Win 2 Controller */ XPAD_XBOX360_VENDOR (0x03eb ),/* Wooting Keyboards (Legacy) */ XPAD_XBOX360_VENDOR (0x044f ),/* Thrustmaster X-Box 360 controllers */ +XPAD_XBOXONE_VENDOR (0x03f0 ),/* HP HyperX Xbox One Controllers */ XPAD_XBOX360_VENDOR (0x045e ),/* Microsoft X-Box 360 controllers */ XPAD_XBOXONE_VENDOR (0x045e ),/* Microsoft X-Box One controllers */ XPAD_XBOX360_VENDOR(0x046d), /* Logitech X-Box 360 style controllers */
Greg Kroah-Hartman
maintainerPATCH 51/107 auxdisplay: hd44780: move cursor home after clear display command
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hugo Villeneuve <[email protected]>
commit 35b464e32c8bccef435e415db955787ead4ab44c upstream.
The DISPLAY_CLEAR command on the NewHaven NHD-0220DZW-AG5 display does NOT change the DDRAM address to 00h (home position) like the standard Hitachi HD44780 controller. As a consequence, the starting position of the initial string LCD_INIT_TEXT is not guaranteed to be at 0,0 depending on where the cursor was before the DISPLAY_CLEAR command.
Extract of DISPLAY_CLEAR command from datasheets of:
Hitachi HD44780:
... It then sets DDRAM address 0 into the address counter...
NewHaven NHD-0220DZW-AG5 datasheet:
... This instruction does not change the DDRAM Address
Move the cursor home after sending DISPLAY_CLEAR command to support non-standard LCDs.
--- drivers/auxdisplay/hd44780_common.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
drivers/auxdisplay/hd44780_common.c +9 -1
@@ -82,7 +82,15 @@ int hd44780_common_clear_display(struct hdc->write_cmd (hdc,LCD_CMD_DISPLAY_CLEAR );/* datasheet says to wait 1,64 milliseconds */ long_sleep (2 ); -return 0 ; + +/* +* The Hitachi HD44780 controller (and compatible ones) reset the DDRAM +* address when executing the DISPLAY_CLEAR command, thus the +* following call is not required. However, other controllers do not +* (e.g. NewHaven NHD-0220DZW-AG5), thus move the cursor to home +* unconditionally to support both. +*/ +return hd44780_common_home (lcd); }EXPORT_SYMBOL_GPL (hd44780_common_clear_display);
Re: [PATCH 6.1 051/107] auxdisplay: hd44780: move cursor home after clear display command
Quoted 27 lines · Greg Kroah-Hartman
6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hugo Villeneuve <[email protected]>
commit
35b464e32c8bccef435e415db955787ead4ab44cupstream.The
DISPLAY_CLEARcommand on the NewHaven NHD-0220DZW-AG5 display does NOT change the DDRAM address to 00h (home position) like the standard Hitachi HD44780 controller. As a consequence, the starting position of the initial stringLCD_INIT_TEXTis not guaranteed to be at 0,0 depending on where the cursor was before theDISPLAY_CLEARcommand.Extract of
DISPLAY_CLEARcommand from datasheets of:Hitachi HD44780:
... It then sets DDRAM address 0 into the address counter...NewHaven NHD-0220DZW-AG5 datasheet:
... This instruction does not change the DDRAM AddressMove the cursor home after sending
DISPLAY_CLEARcommand to support non-standard LCDs.
Quoted 6 lines
Signed-off-by Hugo Villeneuve <[email protected]>Reviewed-by Geert Uytterhoeven <[email protected]>Tested-by David Reaver <[email protected]>Signed-off-by Miguel Ojeda <[email protected]>Signed-off-by Greg Kroah-Hartman <[email protected]>
The commit enables more hardware to work, so it is a "feature" in sense. It does not break the current supported hardware (as far as we know -- David's Tested-by was on HD44780), but as usual, there is always a risk with any change.
If it is OK to take commits like this into stable or somebody wanted to use that hardware in 6.1, then I assume it is fine, but I wanted to point it out just in case.
Thanks!
Cheers,
Miguel
Greg Kroah-Hartman
maintainerPATCH 52/107 serial: sc16is7xx: Put IOControl register into regmap_volatile
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hui Wang <[email protected]>
commit 77a82cebf0eb023203b4cb2235cab75afc77cccf upstream.
According to the IOControl register bits description in the page 31 of the product datasheet, we know the bit 3 of IOControl register is softreset, this bit will self-clearing once the reset finish.
In the probe, the softreset bit is set, and when we read this register from debugfs/regmap interface, we found the softreset bit is still setting, this confused us for a while. Finally we found this register is cached, to read the real value from register, we could put it into the regmap_volatile().
--- drivers/tty/serial/sc16is7xx.c | 1 + 1 file changed, 1 insertion(+)
drivers/tty/serial/sc16is7xx.c +1 -0
@@ -486,6 +486,7 @@ static bool sc16is7xx_regmap_volatile(stcase SC16IS7XX_TXLVL_REG :case SC16IS7XX_RXLVL_REG :case SC16IS7XX_IOSTATE_REG : +case SC16IS7XX_IOCONTROL_REG :return true;default :break ;
Greg Kroah-Hartman
maintainerPATCH 53/107 serial: sc16is7xx: add missing support for rs485 devicetree properties
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hugo Villeneuve <[email protected]>
commit b4a778303ea0fcabcaff974721477a5743e1f8ec upstream.
Retrieve rs485 devicetree properties on registration of sc16is7xx ports in case they are attached to an rs485 transceiver.
--- drivers/tty/serial/sc16is7xx.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/tty/serial/sc16is7xx.c +4 -0
@@ -1556,6 +1556,10 @@ static int sc16is7xx_probe(struct device goto out_ports; } + ret =uart_get_rs485_mode (&s->p[i].port); +if (ret) + goto out_ports; +/* Disable all interrupts */ sc16is7xx_port_write (&s->p[i].port,SC16IS7XX_IER_REG ,0 );/* Disable TX/RX */
Greg Kroah-Hartman
maintainerPATCH 54/107 wifi: cfg80211: fix CQM for non-range use
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johannes Berg <[email protected]>
commit 7e7efdda6adb385fbdfd6f819d76bc68c923c394 upstream.
My prior race fix here broke CQM when ranges aren't used, as the reporting worker now requires the cqm_config to be set in the wdev, but isn't set when there's no range configured.
Rather than continuing to special-case the range version, set the cqm_config always and configure accordingly, also tracking if range was used or not to be able to clear the configuration appropriately with the same API, which was actually not right if both were implemented by a driver for some reason, as is the case with mac80211 (though there the implementations are equivalent so it doesn't matter.)
Also, the original multiple-RSSI commit lost checking for the callback, so might have potentially crashed if a driver had neither implementation, and userspace tried to use it despite not being advertised as supported.
--- net/wireless/core.h | 1 net/wireless/nl80211.c | 50 ++++++++++++++++++++++++++++++------------------- 2 files changed, 32 insertions(+), 19 deletions(-)
net/wireless/core.h +1 -0
@@ -297,6 +297,7 @@ struct cfg80211_cqm_config {u32 rssi_hyst;s32 last_rssi_event_value;enum nl80211_cqm_rssi_threshold_event last_rssi_event_type; +bool use_range_api;int n_rssi_thresholds;s32 rssi_thresholds[]; };
net/wireless/nl80211.c +31 -19
88 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 55/107 USB: xhci-plat: fix legacy PHY double init
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johan Hovold <[email protected]>
[ Upstream commit 16b7e0cccb243033de4406ffb4d892365041a1e7 ]
Commits 7b8ef22ea547 ("usb: xhci: plat: Add USB phy support") and 9134c1fd0503 ("usb: xhci: plat: Add USB 3.0 phy support") added support for looking up legacy PHYs from the sysdev devicetree node and initialising them.
This broke drivers such as dwc3 which manages PHYs themself as the PHYs would now be initialised twice, something which specifically can lead to resources being left enabled during suspend (e.g. with the usb_phy_generic PHY driver).
As the dwc3 driver uses driver-name matching for the xhci platform device, fix this by only looking up and initialising PHYs for devices that have been matched using OF.
Note that checking that the platform device has a devicetree node would currently be sufficient, but that could lead to subtle breakages in case anyone ever tries to reuse an ancestor's node.
--- drivers/usb/host/xhci-plat.c | 29 ++++++++++++++++++----------- 1 file changed, 18 insertions(+), 11 deletions(-)
drivers/usb/host/xhci-plat.c +18 -11
@@ -184,7 +184,7 @@ static int xhci_plat_probe(struct platform_device *pdev)int ret;int irq;struct xhci_plat_priv *priv =NULL ; - +bool of_match;if (usb_disabled ())return -ENODEV ;
@@ -305,16 +305,23 @@ static int xhci_plat_probe(struct platform_device *pdev) &xhci->imod_interval); } - hcd->usb_phy =devm_usb_get_phy_by_phandle (sysdev,"usb-phy" ,0 ); -if (IS_ERR (hcd->usb_phy)) { - ret =PTR_ERR (hcd->usb_phy); -if (ret == -EPROBE_DEFER ) - goto disable_clk; - hcd->usb_phy =NULL ; - }else { - ret =usb_phy_init (hcd->usb_phy); -if (ret) - goto disable_clk; +/* +* Drivers such as dwc3 manages PHYs themself (and rely on driver name +* matching for the xhci platform device). +*/ + of_match =of_match_device (pdev->dev.driver->of_match_table, &pdev->dev); +if (of_match) { + hcd->usb_phy =devm_usb_get_phy_by_phandle (sysdev,"usb-phy" ,0 ); +if (IS_ERR (hcd->usb_phy)) { + ret =PTR_ERR (hcd->usb_phy); +if (ret == -EPROBE_DEFER ) + goto disable_clk; + hcd->usb_phy =NULL ; + }else { + ret =usb_phy_init (hcd->usb_phy); +if (ret) + goto disable_clk; + } } hcd->tpl_support =of_usb_host_tpl_support (sysdev->of_node);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 56/107 USB: core: Change configuration warnings to notices
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alan Stern <[email protected]>
[ Upstream commit 7a09c1269702db8eccb6f718da2b00173e1e0034 ]
It has been pointed out that the kernel log messages warning about problems in USB configuration and related descriptors are vexing for users. The warning log level has a fairly high priority, but the user can do nothing to fix the underlying errors in the device's firmware.
To reduce the amount of useless information produced by tools that filter high-priority log messages, we can change these warnings to notices, i.e., change dev_warn() to dev_notice(). The same holds for a few messages that currently use dev_err(): Unless they indicate a failure that might make a device unusable (such as inability to transfer a config descriptor), change them to dev_notice() also.
Stable-dep-of: 974bba5c118f ("usb: config: fix iteration issue in 'usb_get_bos_descriptor()'")
--- drivers/usb/core/config.c | 82 +++++++++++++++++++-------------------- 1 file changed, 41 insertions(+), 41 deletions(-)
drivers/usb/core/config.c +41 -41
@@ -61,7 +61,7 @@ static void usb_parse_ssp_isoc_endpoint_companion(struct device *ddev, desc = (struct usb_ssp_isoc_ep_comp_descriptor *) buffer;if (desc->bDescriptorType !=USB_DT_SSP_ISOC_ENDPOINT_COMP || size <USB_DT_SSP_ISOC_EP_COMP_SIZE ) { -dev_warn (ddev,"Invalid SuperSpeedPlus isoc endpoint companion" +dev_notice (ddev,"Invalid SuperSpeedPlus isoc endpoint companion" "for config %d interface %d altsetting %d ep %d.\n" , cfgno, inum, asnum, ep->desc.bEndpointAddress);return ;
@@ -83,7 +83,7 @@ static void usb_parse_ss_endpoint_companion(struct device *ddev, int cfgno,if (desc->bDescriptorType !=USB_DT_SS_ENDPOINT_COMP || size <USB_DT_SS_EP_COMP_SIZE ) { -dev_warn (ddev,"No SuperSpeed endpoint companion for config %d " +dev_notice (ddev,"No SuperSpeed endpoint companion for config %d " " interface %d altsetting %d ep %d: " "using minimum values\n" , cfgno, inum, asnum, ep->desc.bEndpointAddress);
@@ -109,13 +109,13 @@ static void usb_parse_ss_endpoint_companion(struct device *ddev, int cfgno,/* Check the various values */ if (usb_endpoint_xfer_control (&ep->desc) && desc->bMaxBurst !=0 ) { -dev_warn (ddev,"Control endpoint with bMaxBurst = %d in " +dev_notice (ddev,"Control endpoint with bMaxBurst = %d in " "config %d interface %d altsetting %d ep %d: " "setting to zero\n" , desc->bMaxBurst, cfgno, inum, asnum, ep->desc.bEndpointAddress); ep->ss_ep_comp.bMaxBurst =0 ; }else if (desc->bMaxBurst >15 ) { -dev_warn (ddev,"Endpoint with bMaxBurst = %d in " +dev_notice (ddev,"Endpoint with bMaxBurst = %d in " "config %d interface %d altsetting %d ep %d: " "setting to 15\n" , desc->bMaxBurst, cfgno, inum, asnum, ep->desc.bEndpointAddress);
@@ -125,7 +125,7 @@ static void usb_parse_ss_endpoint_companion(struct device *ddev, int cfgno,if ((usb_endpoint_xfer_control (&ep->desc) ||usb_endpoint_xfer_int (&ep->desc)) && desc->bmAttributes !=0 ) { - dev_warn(ddev, "%s endpoint with bmAttributes = %d in " + dev_notice(ddev, "%s endpoint with bmAttributes = %d in " "config %d interface %d altsetting %d ep %d: " "setting to zero\n", usb_endpoint_xfer_control(&ep->desc) ? "Control" : "Bulk",
@@ -134,7 +134,7 @@ static void usb_parse_ss_endpoint_companion(struct device *ddev, int cfgno, ep->ss_ep_comp.bmAttributes =0 ; }else if (usb_endpoint_xfer_bulk (&ep->desc) && desc->bmAttributes >16 ) { -dev_warn (ddev,"Bulk endpoint with more than 65536 streams in " +dev_notice (ddev,"Bulk endpoint with more than 65536 streams in " "config %d interface %d altsetting %d ep %d: " "setting to max\n" , cfgno, inum, asnum, ep->desc.bEndpointAddress);
@@ -142,7 +142,7 @@ static void usb_parse_ss_endpoint_companion(struct device *ddev, int cfgno, }else if (usb_endpoint_xfer_isoc (&ep->desc) && !USB_SS_SSP_ISOC_COMP (desc->bmAttributes) &&USB_SS_MULT (desc->bmAttributes) >3 ) { - dev_warn(ddev, "Isoc endpoint has Mult of %d in " + dev_notice(ddev, "Isoc endpoint has Mult of %d in " "config %d interface %d altsetting %d ep %d: " "setting to 3\n", USB_SS_MULT(desc->bmAttributes),
@@ -160,7 +160,7 @@ static void usb_parse_ss_endpoint_companion(struct device *ddev, int cfgno,else max_tx =999999 ;if (le16_to_cpu (desc->wBytesPerInterval) > max_tx) { - dev_warn(ddev, "%s endpoint with wBytesPerInterval of %d in " + dev_notice(ddev, "%s endpoint with wBytesPerInterval of %d in " "config %d interface %d altsetting %d ep %d: " "setting to %d\n", usb_endpoint_xfer_isoc(&ep->desc) ? "Isoc" : "Int",
@@ -273,7 +273,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno,else if (d->bLength >=USB_DT_ENDPOINT_SIZE ) n =USB_DT_ENDPOINT_SIZE ;else { -dev_warn (ddev,"config %d interface %d altsetting %d has an " +dev_notice (ddev,"config %d interface %d altsetting %d has an " "invalid endpoint descriptor of length %d, skipping\n" , cfgno, inum, asnum, d->bLength); goto skip_to_next_endpoint_or_interface_descriptor;
@@ -281,7 +281,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno, i = d->bEndpointAddress & ~USB_ENDPOINT_DIR_MASK ;if (i >=16 || i ==0 ) { -dev_warn (ddev,"config %d interface %d altsetting %d has an " +dev_notice (ddev,"config %d interface %d altsetting %d has an " "invalid endpoint with address 0x%X, skipping\n" , cfgno, inum, asnum, d->bEndpointAddress); goto skip_to_next_endpoint_or_interface_descriptor;
@@ -293,7 +293,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno,/* Check for duplicate endpoint addresses */ if (config_endpoint_is_duplicate (config, inum, asnum, d)) { -dev_warn (ddev,"config %d interface %d altsetting %d has a duplicate endpoint with address 0x%X, skipping\n" , +dev_notice (ddev,"config %d interface %d altsetting %d has a duplicate endpoint with address 0x%X, skipping\n" , cfgno, inum, asnum, d->bEndpointAddress); goto skip_to_next_endpoint_or_interface_descriptor; }
@@ -301,7 +301,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno,/* Ignore some endpoints */ if (udev->quirks &USB_QUIRK_ENDPOINT_IGNORE ) {if (usb_endpoint_is_ignored (udev, ifp, d)) { -dev_warn (ddev,"config %d interface %d altsetting %d has an ignored endpoint with address 0x%X, skipping\n" , +dev_notice (ddev,"config %d interface %d altsetting %d has an ignored endpoint with address 0x%X, skipping\n" , cfgno, inum, asnum, d->bEndpointAddress); goto skip_to_next_endpoint_or_interface_descriptor;
@@ -378,7 +378,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno, } }if (d->bInterval < i || d->bInterval > j) { - dev_warn(ddev, "config %d interface %d altsetting %d " + dev_notice(ddev, "config %d interface %d altsetting %d " "endpoint 0x%X has an invalid bInterval %d, " "changing to %d\n", cfgno, inum, asnum,
@@ -391,7 +391,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno,* them usable, we will try treating them as Interrupt endpoints. */ if (udev->speed ==USB_SPEED_LOW &&usb_endpoint_xfer_bulk (d)) { -dev_warn (ddev,"config %d interface %d altsetting %d " +dev_notice (ddev,"config %d interface %d altsetting %d " "endpoint 0x%X is Bulk; changing to Interrupt\n" , cfgno, inum, asnum, d->bEndpointAddress); endpoint->desc.bmAttributes =USB_ENDPOINT_XFER_INT ;
@@ -408,7 +408,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno,*/ maxp =le16_to_cpu (endpoint->desc.wMaxPacketSize);if (maxp ==0 && !(usb_endpoint_xfer_isoc (d) && asnum ==0 )) { -dev_warn (ddev,"config %d interface %d altsetting %d endpoint 0x%X has invalid wMaxPacketSize 0\n" , +dev_notice (ddev,"config %d interface %d altsetting %d endpoint 0x%X has invalid wMaxPacketSize 0\n" , cfgno, inum, asnum, d->bEndpointAddress); }
@@ -439,7 +439,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno, j = maxpacket_maxes[usb_endpoint_type (&endpoint->desc)];if (maxp > j) { -dev_warn (ddev,"config %d interface %d altsetting %d endpoint 0x%X has invalid maxpacket %d, setting to %d\n" , +dev_notice (ddev,"config %d interface %d altsetting %d endpoint 0x%X has invalid maxpacket %d, setting to %d\n" , cfgno, inum, asnum, d->bEndpointAddress, maxp, j); maxp = j; endpoint->desc.wMaxPacketSize =cpu_to_le16 (i | maxp);
@@ -452,7 +452,7 @@ static int usb_parse_endpoint(struct device *ddev, int cfgno,*/ if (udev->speed ==USB_SPEED_HIGH &&usb_endpoint_xfer_bulk (d)) {if (maxp !=512 ) -dev_warn (ddev,"config %d interface %d altsetting %d " +dev_notice (ddev,"config %d interface %d altsetting %d " "bulk endpoint 0x%X has invalid maxpacket %d\n" , cfgno, inum, asnum, d->bEndpointAddress, maxp);
@@ -533,7 +533,7 @@ static int usb_parse_interface(struct device *ddev, int cfgno, i < intfc->num_altsetting; (++i, ++alt)) {if (alt->desc.bAlternateSetting == asnum) { -dev_warn (ddev,"Duplicate descriptor for config %d " +dev_notice (ddev,"Duplicate descriptor for config %d " "interface %d altsetting %d, skipping\n" , cfgno, inum, asnum); goto skip_to_next_interface_descriptor;
@@ -559,7 +559,7 @@ static int usb_parse_interface(struct device *ddev, int cfgno, num_ep = num_ep_orig = alt->desc.bNumEndpoints; alt->desc.bNumEndpoints =0 ;/* Use as a counter */ if (num_ep >USB_MAXENDPOINTS ) { -dev_warn (ddev,"too many endpoints for config %d interface %d " +dev_notice (ddev,"too many endpoints for config %d interface %d " "altsetting %d: %d, using maximum allowed: %d\n" , cfgno, inum, asnum, num_ep,USB_MAXENDPOINTS ); num_ep =USB_MAXENDPOINTS ;
@@ -590,7 +590,7 @@ static int usb_parse_interface(struct device *ddev, int cfgno, }if (n != num_ep_orig) -dev_warn (ddev,"config %d interface %d altsetting %d has %d " +dev_notice (ddev,"config %d interface %d altsetting %d has %d " "endpoint descriptor%s, different from the interface " "descriptor's value: %d\n" , cfgno, inum, asnum, n,plural (n), num_ep_orig);
@@ -625,7 +625,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx,if (config->desc.bDescriptorType !=USB_DT_CONFIG || config->desc.bLength <USB_DT_CONFIG_SIZE || config->desc.bLength > size) { -dev_err (ddev,"invalid descriptor for config index %d: " +dev_notice (ddev,"invalid descriptor for config index %d: " "type = 0x%X, length = %d\n" , cfgidx, config->desc.bDescriptorType, config->desc.bLength);return -EINVAL ;
@@ -636,7 +636,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, size -= config->desc.bLength;if (nintf >USB_MAXINTERFACES ) { -dev_warn (ddev,"config %d has too many interfaces: %d, " +dev_notice (ddev,"config %d has too many interfaces: %d, " "using maximum allowed: %d\n" , cfgno, nintf,USB_MAXINTERFACES ); nintf =USB_MAXINTERFACES ;
@@ -650,7 +650,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, (buffer2 += header->bLength, size2 -= header->bLength)) {if (size2 <sizeof (struct usb_descriptor_header )) { -dev_warn (ddev,"config %d descriptor has %d excess " +dev_notice (ddev,"config %d descriptor has %d excess " "byte%s, ignoring\n" , cfgno, size2,plural (size2));break ;
@@ -658,7 +658,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, header = (struct usb_descriptor_header *) buffer2;if ((header->bLength > size2) || (header->bLength <2 )) { -dev_warn (ddev,"config %d has an invalid descriptor " +dev_notice (ddev,"config %d has an invalid descriptor " "of length %d, skipping remainder of the config\n" , cfgno, header->bLength);break ;
@@ -670,7 +670,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, d = (struct usb_interface_descriptor *) header;if (d->bLength <USB_DT_INTERFACE_SIZE ) { -dev_warn (ddev,"config %d has an invalid " +dev_notice (ddev,"config %d has an invalid " "interface descriptor of length %d, " "skipping\n" , cfgno, d->bLength);continue ;
@@ -680,7 +680,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx,if ((dev->quirks &USB_QUIRK_HONOR_BNUMINTERFACES ) && n >= nintf_orig) { -dev_warn (ddev,"config %d has more interface " +dev_notice (ddev,"config %d has more interface " "descriptors, than it declares in " "bNumInterfaces, ignoring interface " "number: %d\n" , cfgno, inum);
@@ -688,7 +688,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, }if (inum >= nintf_orig) -dev_warn (ddev,"config %d has an invalid " +dev_notice (ddev,"config %d has an invalid " "interface number: %d but max is %d\n" , cfgno, inum, nintf_orig -1 );
@@ -713,14 +713,14 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, d = (struct usb_interface_assoc_descriptor *)header;if (d->bLength <USB_DT_INTERFACE_ASSOCIATION_SIZE ) { -dev_warn (ddev, +dev_notice (ddev,"config %d has an invalid interface association descriptor of length %d, skipping\n" , cfgno, d->bLength);continue ; }if (iad_num ==USB_MAXIADS ) { -dev_warn (ddev,"found more Interface " +dev_notice (ddev,"found more Interface " "Association Descriptors " "than allocated for in " "configuration %d\n" , cfgno);
@@ -731,7 +731,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, }else if (header->bDescriptorType ==USB_DT_DEVICE || header->bDescriptorType ==USB_DT_CONFIG ) -dev_warn (ddev,"config %d contains an unexpected " +dev_notice (ddev,"config %d contains an unexpected " "descriptor of type 0x%X, skipping\n" , cfgno, header->bDescriptorType);
@@ -740,11 +740,11 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx, config->desc.wTotalLength =cpu_to_le16 (buffer2 - buffer0);if (n != nintf) -dev_warn (ddev,"config %d has %d interface%s, different from " +dev_notice (ddev,"config %d has %d interface%s, different from " "the descriptor's value: %d\n" , cfgno, n,plural (n), nintf_orig);else if (n ==0 ) -dev_warn (ddev,"config %d has no interfaces?\n" , cfgno); +dev_notice (ddev,"config %d has no interfaces?\n" , cfgno); config->desc.bNumInterfaces = nintf = n;/* Check for missing interface numbers */
@@ -754,7 +754,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx,break ; }if (j >= nintf) -dev_warn (ddev,"config %d has no interface number " +dev_notice (ddev,"config %d has no interface number " "%d\n" , cfgno, i); }
@@ -762,7 +762,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx,for (i =0 ; i < nintf; ++i) { j = nalts[i];if (j >USB_MAXALTSETTING ) { -dev_warn (ddev,"too many alternate settings for " +dev_notice (ddev,"too many alternate settings for " "config %d interface %d: %d, " "using maximum allowed: %d\n" , cfgno, inums[i], j,USB_MAXALTSETTING );
@@ -811,7 +811,7 @@ static int usb_parse_configuration(struct usb_device *dev, int cfgidx,break ; }if (n >= intfc->num_altsetting) -dev_warn (ddev,"config %d interface %d has no " +dev_notice (ddev,"config %d interface %d has no " "altsetting %d\n" , cfgno, inums[i], j); } }
@@ -868,7 +868,7 @@ int usb_get_configuration(struct usb_device *dev)int result;if (ncfg >USB_MAXCONFIG ) { -dev_warn (ddev,"too many configurations: %d, " +dev_notice (ddev,"too many configurations: %d, " "using maximum allowed: %d\n" , ncfg,USB_MAXCONFIG ); dev->descriptor.bNumConfigurations = ncfg =USB_MAXCONFIG ; }
@@ -902,7 +902,7 @@ int usb_get_configuration(struct usb_device *dev) "descriptor/%s: %d\n", cfgno, "start", result);if (result != -EPIPE ) goto err; -dev_err (ddev,"chopping to %d config(s)\n" , cfgno); +dev_notice (ddev,"chopping to %d config(s)\n" , cfgno); dev->descriptor.bNumConfigurations = cfgno;break ; }else if (result <4 ) {
@@ -934,7 +934,7 @@ int usb_get_configuration(struct usb_device *dev) goto err; }if (result < length) { -dev_warn (ddev,"config index %d descriptor too short " +dev_notice (ddev,"config index %d descriptor too short " "(expected %i, got %i)\n" , cfgno, length, result); length = result; }
@@ -993,7 +993,7 @@ int usb_get_bos_descriptor(struct usb_device *dev)/* Get BOS descriptor */ ret =usb_get_descriptor (dev,USB_DT_BOS ,0 , bos,USB_DT_BOS_SIZE );if (ret <USB_DT_BOS_SIZE || bos->bLength <USB_DT_BOS_SIZE ) { -dev_err (ddev,"unable to get BOS descriptor or descriptor too short\n" ); +dev_notice (ddev,"unable to get BOS descriptor or descriptor too short\n" );if (ret >=0 ) ret = -ENOMSG ;kfree (bos);
@@ -1021,7 +1021,7 @@ int usb_get_bos_descriptor(struct usb_device *dev) ret =usb_get_descriptor (dev,USB_DT_BOS ,0 , buffer, total_len);if (ret < total_len) { -dev_err (ddev,"unable to get BOS descriptor set\n" ); +dev_notice (ddev,"unable to get BOS descriptor set\n" );if (ret >=0 ) ret = -ENOMSG ; goto err;
@@ -1046,7 +1046,7 @@ int usb_get_bos_descriptor(struct usb_device *dev) }if (cap->bDescriptorType !=USB_DT_DEVICE_CAPABILITY ) { -dev_warn (ddev,"descriptor type invalid, skip\n" ); +dev_notice (ddev,"descriptor type invalid, skip\n" );continue ; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 57/107 usb: config: fix iteration issue in usb_get_bos_descriptor()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Niklas Neronin <[email protected]>
[ Upstream commit 974bba5c118f4c2baf00de0356e3e4f7928b4cbc ]
The BOS descriptor defines a root descriptor and is the base descriptor for accessing a family of related descriptors.
Function 'usb_get_bos_descriptor()' encounters an iteration issue when skipping the 'USB_DT_DEVICE_CAPABILITY' descriptor type. This results in the same descriptor being read repeatedly.
To address this issue, a 'goto' statement is introduced to ensure that the pointer and the amount read is updated correctly. This ensures that the function iterates to the next descriptor instead of reading the same descriptor repeatedly.
--- drivers/usb/core/config.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/usb/core/config.c +2 -1
@@ -1047,7 +1047,7 @@ int usb_get_bos_descriptor(struct usb_device *dev)if (cap->bDescriptorType !=USB_DT_DEVICE_CAPABILITY ) {dev_notice (ddev,"descriptor type invalid, skip\n" ); -continue ; + goto skip_to_next_descriptor; }switch (cap_type) {
@@ -1081,6 +1081,7 @@ int usb_get_bos_descriptor(struct usb_device *dev)break ; } +skip_to_next_descriptor: total_len -= length; buffer += length; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 58/107 ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zhengchao Shao <[email protected]>
[ Upstream commit e2b706c691905fe78468c361aaabc719d0a496f1 ]
When I perform the following test operations:
1.ip link add br0 type bridge
2.brctl addif br0 eth0
3.ip addr add 239.0.0.1/32 dev eth0
4.ip addr add 239.0.0.1/32 dev br0
5.ip addr add 224.0.0.1/32 dev br0
6.while ((1))
do
ifconfig br0 up
ifconfig br0 down
done
7.send IGMPv2 query packets to port eth0 continuously. For example, ./mausezahn ethX -c 0 "01 00 5e 00 00 01 00 72 19 88 aa 02 08 00 45 00 00 1c 00 01 00 00 01 02 0e 7f c0 a8 0a b7 e0 00 00 01 11 64 ee 9b 00 00 00 00"
The preceding tests may trigger the refcnt uaf issue of the mc list. The stack is as follows:
refcount_t: addition on 0; use-after-free. WARNING: CPU: 21 PID: 144 at lib/refcount.c:25 refcount_warn_saturate (lib/refcount.c:25) CPU: 21 PID: 144 Comm: ksoftirqd/21 Kdump: loaded Not tainted 6.7.0-rc1-next-20231117-dirty #80 Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 RIP: 0010:refcount_warn_saturate (lib/refcount.c:25) RSP: 0018:ffffb68f00657910 EFLAGS: 00010286 RAX: 0000000000000000 RBX: ffff8a00c3bf96c0 RCX: ffff8a07b6160908 RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff8a07b6160900 RBP: ffff8a00cba36862 R08: 0000000000000000 R09: 00000000ffff7fff R10: ffffb68f006577c0 R11: ffffffffb0fdcdc8 R12: ffff8a00c3bf9680 R13: ffff8a00c3bf96f0 R14: 0000000000000000 R15: ffff8a00d8766e00 FS: 0000000000000000(0000) GS:ffff8a07b6140000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055f10b520b28 CR3: 000000039741a000 CR4: 00000000000006f0 Call Trace: <TASK> igmp_heard_query (net/ipv4/igmp.c:1068) igmp_rcv (net/ipv4/igmp.c:1132) ip_protocol_deliver_rcu (net/ipv4/ip_input.c:205) ip_local_deliver_finish (net/ipv4/ip_input.c:234) __netif_receive_skb_one_core (net/core/dev.c:5529) netif_receive_skb_internal (net/core/dev.c:5729) netif_receive_skb (net/core/dev.c:5788) br_handle_frame_finish (net/bridge/br_input.c:216) nf_hook_bridge_pre (net/bridge/br_input.c:294) __netif_receive_skb_core (net/core/dev.c:5423) __netif_receive_skb_list_core (net/core/dev.c:5606) __netif_receive_skb_list (net/core/dev.c:5674) netif_receive_skb_list_internal (net/core/dev.c:5764) napi_gro_receive (net/core/gro.c:609) e1000_clean_rx_irq (drivers/net/ethernet/intel/e1000/e1000_main.c:4467) e1000_clean (drivers/net/ethernet/intel/e1000/e1000_main.c:3805) __napi_poll (net/core/dev.c:6533) net_rx_action (net/core/dev.c:6735) __do_softirq (kernel/softirq.c:554) run_ksoftirqd (kernel/softirq.c:913) smpboot_thread_fn (kernel/smpboot.c:164) kthread (kernel/kthread.c:388) ret_from_fork (arch/x86/kernel/process.c:153) ret_from_fork_asm (arch/x86/entry/entry_64.S:250) </TASK>
The root causes are as follows:
Thread A Thread B
... netif_receive_skbbr_dev_stop ...
br_multicast_leave_snoopers ...
__ip_mc_dec_group ...
__igmp_group_dropped igmp_rcv
igmp_stop_timer igmp_heard_query //ref = 1
ip_ma_put igmp_mod_timer
refcount_dec_and_test igmp_start_timer //ref = 0
... refcount_inc //ref increases from 0
When the device receives an IGMPv2 Query message, it starts the timer immediately, regardless of whether the device is running. If the device is down and has left the multicast group, it will cause the mc list refcount uaf issue.
--- net/ipv4/igmp.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
net/ipv4/igmp.c +4 -2
@@ -216,8 +216,10 @@ static void igmp_start_timer(struct ip_mc_list *im, int max_delay)int tv =prandom_u32_max (max_delay); im->tm_running =1 ; -if (!mod_timer (&im->timer, jiffies+tv+2 )) -refcount_inc (&im->refcnt); +if (refcount_inc_not_zero (&im->refcnt)) { +if (mod_timer (&im->timer, jiffies + tv +2 )) +ip_ma_put (im); + } }static void igmp_gq_start_timer (struct in_device *in_dev)
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 59/107 dpaa2-eth: increase the needed headroom to account for alignment
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ioana Ciornei <[email protected]>
[ Upstream commit f422abe3f23d483cf01f386819f26fb3fe0dbb2b ]
Increase the needed headroom to account for a 64 byte alignment restriction which, with this patch, we make mandatory on the Tx path. The case in which the amount of headroom needed is not available is already handled by the driver which instead sends a S/G frame with the first buffer only holding the SW and HW annotation areas.
Without this patch, we can empirically see data corruption happening between Tx and Tx confirmation which sometimes leads to the SW annotation area being overwritten.
Since this is an old IP where the hardware team cannot help to understand the underlying behavior, we make the Tx alignment mandatory for all frames to avoid the crash on Tx conf. Also, remove the comment that suggested that this is just an optimization.
This patch also sets the needed_headroom net device field to the usual value that the driver would need on the Tx path:
- 64 bytes for the software annotation area
- 64 bytes to account for a 64 byte aligned buffer address
--- drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c | 8 ++++---- drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.h | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-)
drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c +4 -4
@@ -1043,14 +1043,12 @@ static int dpaa2_eth_build_single_fd(struct dpaa2_eth_priv *priv,dma_addr_t addr; buffer_start = skb->data -dpaa2_eth_needed_headroom (skb); - -/* If there's enough room to align the FD address, do it. -* It will help hardware optimize accesses. -*/ aligned_start =PTR_ALIGN (buffer_start -DPAA2_ETH_TX_BUF_ALIGN ,DPAA2_ETH_TX_BUF_ALIGN );if (aligned_start >= skb->head) buffer_start = aligned_start; +else +return -ENOMEM ;/* Store a backpointer to the skb at the beginning of the buffer * (in the private data area) such that we can release it
@@ -4738,6 +4736,8 @@ static int dpaa2_eth_probe(struct fsl_mc_device *dpni_dev)if (err) goto err_dl_port_add; + net_dev->needed_headroom =DPAA2_ETH_SWA_SIZE +DPAA2_ETH_TX_BUF_ALIGN ; + err =register_netdev (net_dev);if (err <0 ) {dev_err (dev,"register_netdev() failed\n" );
drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.h +1 -1
@@ -702,7 +702,7 @@ static inline bool dpaa2_eth_rx_pause_enabled(u64 link_options)static inline unsigned int dpaa2_eth_needed_headroom (struct sk_buff *skb) { -unsigned int headroom =DPAA2_ETH_SWA_SIZE ; +unsigned int headroom =DPAA2_ETH_SWA_SIZE +DPAA2_ETH_TX_BUF_ALIGN ;/* If we don't have an skb (e.g. XDP buffer), we only need space for * the software annotation area
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 60/107 uapi: propagate __struct_group() attributes to the container union
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Antipov <[email protected]>
[ Upstream commit 4e86f32a13af1970d21be94f659cae56bbe487ee ]
Recently the kernel test robot has reported an ARM-specific BUILD_BUG_ON() in an old and unmaintained wil6210 wireless driver. The problem comes from the structure packing rules of old ARM ABI ('-mabi=apcs-gnu'). For example, the following structure is packed to 18 bytes instead of 16:
struct poorly_packed {
unsigned int a;
unsigned int b;
unsigned short c;
union {
struct {
unsigned short d;
unsigned int e;
} __attribute__((packed));
struct {
unsigned short d;
unsigned int e;
} __attribute__((packed)) inner;
};
} __attribute__((packed));To fit it into 16 bytes, it's required to add packed attribute to the container union as well:
struct poorly_packed {
unsigned int a;
unsigned int b;
unsigned short c;
union {
struct {
unsigned short d;
unsigned int e;
} __attribute__((packed));
struct {
unsigned short d;
unsigned int e;
} __attribute__((packed)) inner;
} __attribute__((packed));
} __attribute__((packed));Thanks to Andrew Pinski of GCC team for sorting the things out at
https://gcc.gnu.org/pipermail/gcc/2023-November/242888.html.
--- include/uapi/linux/stddef.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/uapi/linux/stddef.h +1 -1
@@ -27,7 +27,7 @@ union { \ struct { MEMBERS } ATTRS; \ struct TAG { MEMBERS } ATTRS NAME; \ - } + } ATTRS /** * __DECLARE_FLEX_ARRAY() - Declare a flexible array usable in a union
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 61/107 selftests/net: ipsec: fix constant out of range
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Willem de Bruijn <[email protected]>
[ Upstream commit 088559815477c6f623a5db5993491ddd7facbec7 ]
Fix a small compiler warning.
nr_process must be a signed long: it is assigned a signed long by strtol() and is compared against LONG_MIN and LONG_MAX.
ipsec.c:2280:65:
error: result of comparison of constant -9223372036854775808 with expression of type 'unsigned int' is always false [-Werror,-Wtautological-constant-out-of-range-compare]
if ((errno == ERANGE && (nr_process == LONG_MAX || nr_process == LONG_MIN))
--- tools/testing/selftests/net/ipsec.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
tools/testing/selftests/net/ipsec.c +2 -2
@@ -2263,7 +2263,7 @@ static int check_results(void)int main (int argc,char **argv) { -unsigned int nr_process =1 ; +long nr_process =1 ;int route_sock =-1 , ret =KSFT_SKIP ;int test_desc_fd[2 ];uint32_t route_seq;
@@ -2284,7 +2284,7 @@ int main(int argc, char **argv)exit_usage (argv); } -if (nr_process >MAX_PROCESSES || !nr_process) { +if (nr_process >MAX_PROCESSES || nr_process <1 ) {printk ("nr_process should be between [1; %u]" ,MAX_PROCESSES );exit_usage (argv);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 62/107 selftests/net: fix a char signedness issue
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Willem de Bruijn <[email protected]>
[ Upstream commit 7b29828c5af6841bdeb9fafa32fdfeff7ab9c407 ]
Signedness of char is signed on x86_64, but unsigned on arm64.
Fix the warning building cmsg_sender.c on signed platforms or forced with -fsigned-char:
msg_sender.c:455:12:
error: implicit conversion from 'int' to 'char' changes value from 128 to -128 [-Werror,-Wconstant-conversion]
buf[0] = ICMPV6_ECHO_REQUEST;
constant ICMPV6_ECHO_REQUEST is 128.
--- tools/testing/selftests/net/cmsg_sender.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/net/cmsg_sender.c +1 -1
@@ -416,9 +416,9 @@ int main(int argc, char *argv[]) {struct addrinfo hints, *ai;struct iovec iov[1 ]; +unsigned char *buf;struct msghdr msg;char cbuf[1024 ]; -char *buf;int err;int fd;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 63/107 selftests/net: unix: fix unused variable compiler warning
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Willem de Bruijn <[email protected]>
[ Upstream commit 59fef379d453781f0dabfa1f1a1e86e78aee919a ]
Remove an unused variable.
diag_uid.c:151:24:
error: unused variable 'udr'
[-Werror,-Wunused-variable]
--- tools/testing/selftests/net/af_unix/diag_uid.c | 1 - 1 file changed, 1 deletion(-)
tools/testing/selftests/net/af_unix/diag_uid.c +0 -1
@@ -148,7 +148,6 @@ void receive_response(struct __test_metadata *_metadata, .msg_iov = &iov, .msg_iovlen = 1 }; -struct unix_diag_req *udr;struct nlmsghdr *nlh;int ret;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 64/107 selftests/net: mptcp: fix uninitialized variable warnings
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Willem de Bruijn <[email protected]>
[ Upstream commit 00a4f8fd9c750f20d8fd4535c71c9caa7ef5ff2f ]
Same init_rng() in both tests. The function reads /dev/urandom to initialize srand(). In case of failure, it falls back onto the entropy in the uninitialized variable. Not sure if this is on purpose. But failure reading urandom should be rare, so just fail hard. While at it, convert to getrandom(). Which man 4 random suggests is simpler and more robust.
mptcp_inq.c:525:6:
mptcp_connect.c:1131:6:
error: variable 'foo' is used uninitialized
whenever 'if' condition is false
[-Werror,-Wsometimes-uninitialized]
----
When input is randomized because this is expected to meaningfully explore edge cases, should we also add
1. logging the random seed to stdout and
2. adding a command line argument to replay from a specific seed I can do this in net-next, if authors find it useful in this case.
--- tools/testing/selftests/net/mptcp/mptcp_connect.c | 11 ++++------- tools/testing/selftests/net/mptcp/mptcp_inq.c | 11 ++++------- 2 files changed, 8 insertions(+), 14 deletions(-)
tools/testing/selftests/net/mptcp/mptcp_connect.c +4 -7
@@ -18,6 +18,7 @@#include <sys/ioctl.h> #include <sys/poll.h> +#include <sys/random.h> #include <sys/sendfile.h> #include <sys/stat.h> #include <sys/socket.h>
@@ -1050,15 +1051,11 @@ int main_loop_s(int listensock)static void init_rng (void ) { -int fd =open ("/dev/urandom" ,O_RDONLY );unsigned int foo; -if (fd >0 ) { -int ret =read (fd, &foo,sizeof (foo)); - -if (ret <0 ) -srand (fd + foo); -close (fd); +if (getrandom (&foo,sizeof (foo),0 ) ==-1 ) { +perror ("getrandom" ); +exit (1 ); }srand (foo);
tools/testing/selftests/net/mptcp/mptcp_inq.c +4 -7
@@ -18,6 +18,7 @@#include <time.h> #include <sys/ioctl.h> +#include <sys/random.h> #include <sys/socket.h> #include <sys/types.h> #include <sys/wait.h>
@@ -519,15 +520,11 @@ static int client(int unixfd)static void init_rng (void ) { -int fd =open ("/dev/urandom" ,O_RDONLY );unsigned int foo; -if (fd >0 ) { -int ret =read (fd, &foo,sizeof (foo)); - -if (ret <0 ) -srand (fd + foo); -close (fd); +if (getrandom (&foo,sizeof (foo),0 ) ==-1 ) { +perror ("getrandom" ); +exit (1 ); }srand (foo);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 65/107 octeontx2-af: Fix possible buffer overflow
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Elena Salomatkina <[email protected]>
[ Upstream commit ad31c629ca3c87f6d557488c1f9faaebfbcd203c ]
A loop in rvu_mbox_handler_nix_bandprof_free() contains
a break if (idx == MAX_BANDPROF_PER_PFFUNC),
but if idx may reach MAX_BANDPROF_PER_PFFUNC
buffer '(*req->prof_idx)[layer]' overflow happens before that check.
The patch moves the break to the
beginning of the loop.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
--- drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/marvell/octeontx2/af/rvu_nix.c +2 -2
@@ -5236,6 +5236,8 @@ int rvu_mbox_handler_nix_bandprof_free(struct rvu *rvu, ipolicer = &nix_hw->ipolicer[layer];for (idx =0 ; idx < req->prof_count[layer]; idx++) { +if (idx ==MAX_BANDPROF_PER_PFFUNC ) +break ; prof_idx = req->prof_idx[layer][idx];if (prof_idx >= ipolicer->band_prof.max || ipolicer->pfvf_map[prof_idx] != pcifunc)
@@ -5249,8 +5251,6 @@ int rvu_mbox_handler_nix_bandprof_free(struct rvu *rvu, ipolicer->pfvf_map[prof_idx] =0x00 ; ipolicer->match_id[prof_idx] =0 ;rvu_free_rsrc (&ipolicer->band_prof, prof_idx); -if (idx ==MAX_BANDPROF_PER_PFFUNC ) -break ; } }mutex_unlock (&rvu->rsrc_lock);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 66/107 net: stmmac: xgmac: Disable FPE MMC interrupts
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Furong Xu <[email protected]>
[ Upstream commit e54d628a2721bfbb002c19f6e8ca6746cec7640f ]
Commit aeb18dd07692 ("net: stmmac: xgmac: Disable MMC interrupts by default") tries to disable MMC interrupts to avoid a storm of unhandled interrupts, but leaves the FPE(Frame Preemption) MMC interrupts enabled, FPE MMC interrupts can cause the same problem. Now we mask FPE TX and RX interrupts to disable all MMC interrupts.
--- drivers/net/ethernet/stmicro/stmmac/mmc_core.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/net/ethernet/stmicro/stmmac/mmc_core.c +4 -0
@@ -177,8 +177,10 @@#define MMC_XGMAC_RX_DISCARD_OCT_GB 0x1b4#define MMC_XGMAC_RX_ALIGN_ERR_PKT 0x1bc +#define MMC_XGMAC_TX_FPE_INTR_MASK 0x204#define MMC_XGMAC_TX_FPE_FRAG 0x208#define MMC_XGMAC_TX_HOLD_REQ 0x20c +#define MMC_XGMAC_RX_FPE_INTR_MASK 0x224#define MMC_XGMAC_RX_PKT_ASSEMBLY_ERR 0x228#define MMC_XGMAC_RX_PKT_SMD_ERR 0x22c#define MMC_XGMAC_RX_PKT_ASSEMBLY_OK 0x230
@@ -352,6 +354,8 @@ static void dwxgmac_mmc_intr_all_mask(void __iomem *mmcaddr) {writel (0x0 , mmcaddr +MMC_RX_INTR_MASK );writel (0x0 , mmcaddr +MMC_TX_INTR_MASK ); +writel (MMC_DEFAULT_MASK , mmcaddr +MMC_XGMAC_TX_FPE_INTR_MASK ); +writel (MMC_DEFAULT_MASK , mmcaddr +MMC_XGMAC_RX_FPE_INTR_MASK );writel (MMC_DEFAULT_MASK , mmcaddr +MMC_XGMAC_RX_IPC_INTR_MASK ); }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 67/107 octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Geetha sowjanya <[email protected]>
[ Upstream commit 51597219e0cd5157401d4d0ccb5daa4d9961676f ]
When more than 64 VFs are enabled for a PF then mbox communication between VF and PF is not working as mbox work queueing for few VFs are skipped due to wrong calculation of VF numbers.
--- drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c +5 -2
@@ -566,7 +566,9 @@ static irqreturn_t otx2_pfvf_mbox_intr_handler(int irq, void *pf_irq)otx2_write64 (pf,RVU_PF_VFPF_MBOX_INTX (1 ), intr);otx2_queue_work (mbox, pf->mbox_pfvf_wq,64 , vfs, intr,TYPE_PFVF ); - vfs -=64 ; +if (intr) +trace_otx2_msg_interrupt (mbox->mbox.pdev,"VF(s) to PF" , intr); + vfs =64 ; } intr =otx2_read64 (pf,RVU_PF_VFPF_MBOX_INTX (0 ));
@@ -574,7 +576,8 @@ static irqreturn_t otx2_pfvf_mbox_intr_handler(int irq, void *pf_irq)otx2_queue_work (mbox, pf->mbox_pfvf_wq,0 , vfs, intr,TYPE_PFVF ); -trace_otx2_msg_interrupt (mbox->mbox.pdev,"VF(s) to PF" , intr); +if (intr) +trace_otx2_msg_interrupt (mbox->mbox.pdev,"VF(s) to PF" , intr);return IRQ_HANDLED ; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 68/107 octeontx2-af: Install TC filter rules in hardware based on priority
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Suman Ghosh <[email protected]>
[ Upstream commit ec87f05402f592d27507e1aa6b2fd21c486f2cc0 ]
As of today, hardware does not support installing tc filter rules based on priority. This patch adds support to install the hardware rules based on priority. The final hardware rules will not be dependent on rule installation order, it will be strictly priority based, same as software.
Stable-dep-of: fd7f98b2e12a ("octeontx2-pf: Restore TC ingress police rules when interface is up")
--- .../net/ethernet/marvell/octeontx2/af/mbox.h | 9 +- .../marvell/octeontx2/af/rvu_npc_fs.c | 9 +- .../marvell/octeontx2/af/rvu_switch.c | 6 +- .../marvell/octeontx2/nic/otx2_common.h | 11 +- .../marvell/octeontx2/nic/otx2_devlink.c | 1 - .../marvell/octeontx2/nic/otx2_ethtool.c | 1 + .../marvell/octeontx2/nic/otx2_flows.c | 2 + .../ethernet/marvell/octeontx2/nic/otx2_tc.c | 320 +++++++++++++----- 8 files changed, 255 insertions(+), 104 deletions(-)
drivers/net/ethernet/marvell/octeontx2/af/mbox.h +8 -1
@@ -232,7 +232,7 @@ M(NPC_GET_KEX_CFG, 0x600c, npc_get_kex_cfg, \M (NPC_INSTALL_FLOW ,0x600d , npc_install_flow, \ npc_install_flow_req, npc_install_flow_rsp) \M (NPC_DELETE_FLOW ,0x600e , npc_delete_flow, \ - npc_delete_flow_req, msg_rsp) \ + npc_delete_flow_req, npc_delete_flow_rsp) \M (NPC_MCAM_READ_ENTRY ,0x600f , npc_mcam_read_entry, \ npc_mcam_read_entry_req, \ npc_mcam_read_entry_rsp) \
@@ -1471,6 +1471,8 @@ struct npc_install_flow_req {u8 vtag0_op;u16 vtag1_def;u8 vtag1_op; +/* old counter value */ +u16 cntr_val; };struct npc_install_flow_rsp {
@@ -1486,6 +1488,11 @@ struct npc_delete_flow_req {u8 all;/* PF + VFs */ }; +struct npc_delete_flow_rsp { +struct mbox_msghdr hdr; +u16 cntr_val; +}; +struct npc_mcam_read_entry_req {struct mbox_msghdr hdr;u16 entry;/* MCAM entry to read */
drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c +7 -2
@@ -1184,7 +1184,7 @@ static int npc_install_flow(struct rvu *rvu, int blkaddr, u16 target, write_req.enable_entry = (u8 )enable;/* if counter is available then clear and use it */ if (req->set_cntr && rule->has_cntr) { -rvu_write64 (rvu, blkaddr,NPC_AF_MATCH_STATX (rule->cntr),0x00 ); +rvu_write64 (rvu, blkaddr,NPC_AF_MATCH_STATX (rule->cntr), req->cntr_val); write_req.set_cntr =1 ; write_req.cntr = rule->cntr; }
@@ -1399,12 +1399,13 @@ static int npc_delete_flow(struct rvu *rvu, struct rvu_npc_mcam_rule *rule,int rvu_mbox_handler_npc_delete_flow (struct rvu *rvu,struct npc_delete_flow_req *req, -struct msg_rsp *rsp) +struct npc_delete_flow_rsp *rsp) {struct npc_mcam *mcam = &rvu->hw->mcam;struct rvu_npc_mcam_rule *iter, *tmp;u16 pcifunc = req->hdr.pcifunc;struct list_head del_list; +int blkaddr;INIT_LIST_HEAD (&del_list);
@@ -1420,6 +1421,10 @@ int rvu_mbox_handler_npc_delete_flow(struct rvu *rvu,list_move_tail (&iter->list, &del_list);/* single rule */ }else if (req->entry == iter->entry) { + blkaddr =rvu_get_blkaddr (rvu,BLKTYPE_NPC ,0 ); +if (blkaddr) + rsp->cntr_val =rvu_read64 (rvu, blkaddr, +NPC_AF_MATCH_STATX (iter->cntr));list_move_tail (&iter->list, &del_list);break ; }
drivers/net/ethernet/marvell/octeontx2/af/rvu_switch.c +4 -2
@@ -145,6 +145,7 @@ void rvu_switch_enable(struct rvu *rvu)struct npc_mcam_alloc_entry_req alloc_req = {0 };struct npc_mcam_alloc_entry_rsp alloc_rsp = {0 };struct npc_delete_flow_req uninstall_req = {0 }; +struct npc_delete_flow_rsp uninstall_rsp = {0 };struct npc_mcam_free_entry_req free_req = {0 };struct rvu_switch *rswitch = &rvu->rswitch;struct msg_rsp rsp;
@@ -184,7 +185,7 @@ void rvu_switch_enable(struct rvu *rvu) uninstall_rules: uninstall_req.start = rswitch->start_entry; uninstall_req.end = rswitch->start_entry + rswitch->used_entries -1 ; -rvu_mbox_handler_npc_delete_flow (rvu, &uninstall_req, &rsp); +rvu_mbox_handler_npc_delete_flow (rvu, &uninstall_req, &uninstall_rsp);kfree (rswitch->entry2pcifunc); free_entries: free_req.all =1 ;
@@ -196,6 +197,7 @@ void rvu_switch_enable(struct rvu *rvu)void rvu_switch_disable (struct rvu *rvu) {struct npc_delete_flow_req uninstall_req = {0 }; +struct npc_delete_flow_rsp uninstall_rsp = {0 };struct npc_mcam_free_entry_req free_req = {0 };struct rvu_switch *rswitch = &rvu->rswitch;struct rvu_hwinfo *hw = rvu->hw;
@@ -232,7 +234,7 @@ void rvu_switch_disable(struct rvu *rvu) uninstall_req.start = rswitch->start_entry; uninstall_req.end = rswitch->start_entry + rswitch->used_entries -1 ; free_req.all =1 ; -rvu_mbox_handler_npc_delete_flow (rvu, &uninstall_req, &rsp); +rvu_mbox_handler_npc_delete_flow (rvu, &uninstall_req, &uninstall_rsp);rvu_mbox_handler_npc_mcam_free_entry (rvu, &free_req, &rsp); rswitch->used_entries =0 ;kfree (rswitch->entry2pcifunc);
drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h +2 -9
@@ -339,13 +339,8 @@ struct otx2_flow_config {struct list_head flow_list;u32 dmacflt_max_flows;u16 max_flows; -}; - -struct otx2_tc_info { -/* hash table to store TC offloaded flows */ -struct rhashtable flow_table; -struct rhashtable_params flow_ht_params; -unsigned long *tc_entries_bitmap; +struct list_head flow_list_tc; +bool ntuple; };struct dev_hw_ops {
@@ -465,7 +460,6 @@ struct otx2_nic {/* NPC MCAM */ struct otx2_flow_config *flow_cfg;struct otx2_mac_table *mac_table; -struct otx2_tc_info tc_info;u64 reset_count;struct work_struct reset_task;
@@ -1024,7 +1018,6 @@ int otx2_init_tc(struct otx2_nic *nic);void otx2_shutdown_tc (struct otx2_nic *nic);int otx2_setup_tc (struct net_device *netdev,enum tc_setup_type type,void *type_data); -int otx2_tc_alloc_ent_bitmap (struct otx2_nic *nic);/* CGX/RPM DMAC filters support */ int otx2_dmacflt_get_max_cnt (struct otx2_nic *pf);int otx2_dmacflt_add (struct otx2_nic *pf,const u8 *mac,u32 bit_pos);
drivers/net/ethernet/marvell/octeontx2/nic/otx2_devlink.c +0 -1
@@ -41,7 +41,6 @@ static int otx2_dl_mcam_count_set(struct devlink *devlink, u32 id,return 0 ;otx2_alloc_mcam_entries (pfvf, ctx->val.vu16); -otx2_tc_alloc_ent_bitmap (pfvf);return 0 ; }
drivers/net/ethernet/marvell/octeontx2/nic/otx2_ethtool.c +1 -0
@@ -753,6 +753,7 @@ static int otx2_set_rxnfc(struct net_device *dev, struct ethtool_rxnfc *nfc)struct otx2_nic *pfvf =netdev_priv (dev);int ret = -EOPNOTSUPP ; + pfvf->flow_cfg->ntuple = ntuple;switch (nfc->cmd) {case ETHTOOL_SRXFH : ret =otx2_set_rss_hash_opts (pfvf, nfc);
drivers/net/ethernet/marvell/octeontx2/nic/otx2_flows.c +2 -0
@@ -276,6 +276,7 @@ int otx2vf_mcam_flow_init(struct otx2_nic *pfvf) flow_cfg = pfvf->flow_cfg;INIT_LIST_HEAD (&flow_cfg->flow_list); +INIT_LIST_HEAD (&flow_cfg->flow_list_tc); flow_cfg->max_flows =0 ;return 0 ;
@@ -298,6 +299,7 @@ int otx2_mcam_flow_init(struct otx2_nic *pf)return -ENOMEM ;INIT_LIST_HEAD (&pf->flow_cfg->flow_list); +INIT_LIST_HEAD (&pf->flow_cfg->flow_list_tc);/* Allocate bare minimum number of MCAM entries needed for * unicast and ntuple filters.
drivers/net/ethernet/marvell/octeontx2/nic/otx2_tc.c +231 -89
458 lines not on this page · raw message
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 69/107 octeontx2-pf: Restore TC ingress police rules when interface is up
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Subbaraya Sundeep <[email protected]>
[ Upstream commit fd7f98b2e12a3d96a92bde6640657ec7116f4372 ]
TC ingress policer rules depends on interface receive queue contexts since the bandwidth profiles are attached to RQ contexts. When an interface is brought down all the queue contexts are freed. This in turn frees bandwidth profiles in hardware causing ingress police rules non-functional after the interface is brought up. Fix this by applying all the ingress police rules config to hardware in otx2_open. Also allow adding ingress rules only when interface is running since no contexts exist for the interface when it is down.
--- .../ethernet/marvell/octeontx2/nic/cn10k.c | 3 + .../marvell/octeontx2/nic/otx2_common.h | 2 + .../ethernet/marvell/octeontx2/nic/otx2_pf.c | 2 + .../ethernet/marvell/octeontx2/nic/otx2_tc.c | 120 ++++++++++++++---- 4 files changed, 102 insertions(+), 25 deletions(-)
drivers/net/ethernet/marvell/octeontx2/nic/cn10k.c +3 -0
@@ -448,6 +448,9 @@ int cn10k_set_ipolicer_rate(struct otx2_nic *pfvf, u16 profile, aq->prof.pebs_mantissa =0 ; aq->prof_mask.pebs_mantissa =0xFF ; + aq->prof.hl_en =0 ; + aq->prof_mask.hl_en =1 ; +/* Fill AQ info */ aq->qidx = profile; aq->ctype =NIX_AQ_CTYPE_BANDPROF ;
drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.h +2 -0
@@ -1018,6 +1018,8 @@ int otx2_init_tc(struct otx2_nic *nic);void otx2_shutdown_tc (struct otx2_nic *nic);int otx2_setup_tc (struct net_device *netdev,enum tc_setup_type type,void *type_data); +void otx2_tc_apply_ingress_police_rules (struct otx2_nic *nic); +/* CGX/RPM DMAC filters support */ int otx2_dmacflt_get_max_cnt (struct otx2_nic *pf);int otx2_dmacflt_add (struct otx2_nic *pf,const u8 *mac,u32 bit_pos);
drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c +2 -0
@@ -1858,6 +1858,8 @@ int otx2_open(struct net_device *netdev)if (pf->flags &OTX2_FLAG_DMACFLTR_SUPPORT )otx2_dmacflt_reinstall_flows (pf); +otx2_tc_apply_ingress_police_rules (pf); + err =otx2_rxtx_enable (pf, true);/* If a mbox communication error happens at this point then interface * will end up in a state such that it is in down state but hardware
drivers/net/ethernet/marvell/octeontx2/nic/otx2_tc.c +95 -25
177 lines not on this page · raw message
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 70/107 r8169: prevent potential deadlock in rtl8169_close
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Heiner Kallweit <[email protected]>
[ Upstream commit 91d3d149978ba7b238198dd80e4b823756aa7cfa ]
ndo_stop() is RTNL-protected by net core, and the worker function takes RTNL as well. Therefore we will deadlock when trying to execute a pending work synchronously. To fix this execute any pending work asynchronously. This will do no harm because netif_running() is false in ndo_stop(), and therefore the work function is effectively a no-op. However we have to ensure that no task is running or pending after rtl_remove_one(), therefore add a call to cancel_work_sync().
--- drivers/net/ethernet/realtek/r8169_main.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/net/ethernet/realtek/r8169_main.c +3 -1
@@ -4656,7 +4656,7 @@ static int rtl8169_close(struct net_device *dev)rtl8169_down (tp);rtl8169_rx_clear (tp); -cancel_work_sync (&tp->wk.work); +cancel_work (&tp->wk.work);free_irq (tp->irq, tp);
@@ -4890,6 +4890,8 @@ static void rtl_remove_one(struct pci_dev *pdev)if (pci_dev_run_wake (pdev))pm_runtime_get_noresume (&pdev->dev); +cancel_work_sync (&tp->wk.work); +unregister_netdev (tp->dev);if (tp->dash_type !=RTL_DASH_NONE )
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 71/107 ravb: Fix races between ravb_tx_timeout_work() and net related ops
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yoshihiro Shimoda <[email protected]>
[ Upstream commit 9870257a0a338cd8d6c1cddab74e703f490f6779 ]
Fix races between ravb_tx_timeout_work() and functions of net_device_ops and ethtool_ops by using rtnl_trylock() and rtnl_unlock(). Note that since ravb_close() is under the rtnl lock and calls cancel_work_sync(), ravb_tx_timeout_work() should calls rtnl_trylock(). Otherwise, a deadlock may happen in ravb_tx_timeout_work() like below:
CPU0 CPU1
ravb_tx_timeout()
schedule_work()
...__dev_close_many()
// Under rtnl lockravb_close()cancel_work_sync()
// Waiting
ravb_tx_timeout_work() rtnl_lock() // This is possible to cause a deadlock
If rtnl_trylock() fails, rescheduling the work with sleep for 1 msec.
--- drivers/net/ethernet/renesas/ravb_main.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
drivers/net/ethernet/renesas/ravb_main.c +10 -1
@@ -1890,6 +1890,12 @@ static void ravb_tx_timeout_work(struct work_struct *work)struct net_device *ndev = priv->ndev;int error; +if (!rtnl_trylock ()) { +usleep_range (1000 ,2000 ); +schedule_work (&priv->work); +return ; + } +netif_tx_stop_all_queues (ndev);/* Stop PTP Clock driver */
@@ -1923,7 +1929,7 @@ static void ravb_tx_timeout_work(struct work_struct *work)*/ netdev_err (ndev,"%s: ravb_dmac_init() failed, error %d\n" , __func__, error); -return ; + goto out_unlock; }ravb_emac_init (ndev);
@@ -1933,6 +1939,9 @@ static void ravb_tx_timeout_work(struct work_struct *work)ravb_ptp_init (ndev, priv->pdev);netif_tx_start_all_queues (ndev); + +out_unlock: +rtnl_unlock (); }/* Packet transmit function for Ethernet AVB */
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 72/107 net: ravb: Check return value of reset_control_deassert()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
[ Upstream commit d8eb6ea4b302e7ff78535c205510e359ac10a0bd ]
reset_control_deassert() could return an error. Some devices cannot work if reset signal de-assert operation fails. To avoid this check the return code of reset_control_deassert() in ravb_probe() and take proper action.
Along with it, the free_netdev() call from the error path was moved after reset_control_assert() on its own label (out_free_netdev) to free netdev in case reset_control_deassert() fails.
--- drivers/net/ethernet/renesas/ravb_main.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
drivers/net/ethernet/renesas/ravb_main.c +6 -3
@@ -2670,7 +2670,10 @@ static int ravb_probe(struct platform_device *pdev) ndev->features = info->net_features; ndev->hw_features = info->net_hw_features; -reset_control_deassert (rstc); + error =reset_control_deassert (rstc); +if (error) + goto out_free_netdev; +pm_runtime_enable (&pdev->dev);pm_runtime_get_sync (&pdev->dev);
@@ -2897,11 +2900,11 @@ static int ravb_probe(struct platform_device *pdev) out_disable_refclk:clk_disable_unprepare (priv->refclk); out_release: -free_netdev (ndev); -pm_runtime_put (&pdev->dev);pm_runtime_disable (&pdev->dev);reset_control_assert (rstc); +out_free_netdev: +free_netdev (ndev);return error; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 73/107 net: ravb: Use pm_runtime_resume_and_get()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
[ Upstream commit 88b74831faaee455c2af380382d979fc38e79270 ]
pm_runtime_get_sync() may return an error. In case it returns with an error dev->power.usage_count needs to be decremented. pm_runtime_resume_and_get() takes care of this. Thus use it.
--- drivers/net/ethernet/renesas/ravb_main.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/net/ethernet/renesas/ravb_main.c +4 -1
@@ -2675,7 +2675,9 @@ static int ravb_probe(struct platform_device *pdev) goto out_free_netdev;pm_runtime_enable (&pdev->dev); -pm_runtime_get_sync (&pdev->dev); + error =pm_runtime_resume_and_get (&pdev->dev); +if (error <0 ) + goto out_rpm_disable;if (info->multi_irqs) {if (info->err_mgmt_irqs)
@@ -2901,6 +2903,7 @@ static int ravb_probe(struct platform_device *pdev)clk_disable_unprepare (priv->refclk); out_release:pm_runtime_put (&pdev->dev); +out_rpm_disable:pm_runtime_disable (&pdev->dev);reset_control_assert (rstc); out_free_netdev:
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 74/107 net: ravb: Make write access to CXR35 first before accessing other EMAC registers
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
[ Upstream commit d78c0ced60d5e2f8b5a4a0468a5c400b24aeadf2 ]
Hardware manual of RZ/G3S (and RZ/G2L) specifies the following on the description of CXR35 register (chapter "PHY interface select register (CXR35)"): "After release reset, make write-access to this register before making write-access to other registers (except MDIOMOD). Even if not need to change the value of this register, make write-access to this register at least one time. Because RGMII/MII MODE is recognized by accessing this register".
The setup procedure for EMAC module (chapter "Setup procedure" of RZ/G3S, RZ/G2L manuals) specifies the E-MAC.CXR35 register is the first EMAC register that is to be configured.
Note [A] from chapter "PHY interface select register (CXR35)" specifies the following:
[A] The case which CXR35 SEL_XMII is used for the selection of RGMII/MII in APB Clock 100 MHz.
(1) To use RGMII interface, Set ‘H’03E8_0000’ to this register.
(2) To use MII interface, Set ‘H’03E8_0002’ to this register.
Take into account these indication.
--- drivers/net/ethernet/renesas/ravb_main.c | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-)
drivers/net/ethernet/renesas/ravb_main.c +9 -8
@@ -517,6 +517,15 @@ static void ravb_emac_init_gbeth(struct net_device *ndev) {struct ravb_private *priv =netdev_priv (ndev); +if (priv->phy_interface ==PHY_INTERFACE_MODE_MII ) { +ravb_write (ndev, (1000 <<16 ) |CXR35_SEL_XMII_MII ,CXR35 ); +ravb_modify (ndev,CXR31 ,CXR31_SEL_LINK0 |CXR31_SEL_LINK1 ,0 ); + }else { +ravb_write (ndev, (1000 <<16 ) |CXR35_SEL_XMII_RGMII ,CXR35 ); +ravb_modify (ndev,CXR31 ,CXR31_SEL_LINK0 |CXR31_SEL_LINK1 , +CXR31_SEL_LINK0 ); + } +/* Receive frame limit set register */ ravb_write (ndev,GBETH_RX_BUFF_MAX +ETH_FCS_LEN ,RFLR );
@@ -539,14 +548,6 @@ static void ravb_emac_init_gbeth(struct net_device *ndev)/* E-MAC interrupt enable register */ ravb_write (ndev,ECSIPR_ICDIP ,ECSIPR ); - -if (priv->phy_interface ==PHY_INTERFACE_MODE_MII ) { -ravb_modify (ndev,CXR31 ,CXR31_SEL_LINK0 |CXR31_SEL_LINK1 ,0 ); -ravb_write (ndev, (1000 <<16 ) |CXR35_SEL_XMII_MII ,CXR35 ); - }else { -ravb_modify (ndev,CXR31 ,CXR31_SEL_LINK0 |CXR31_SEL_LINK1 , -CXR31_SEL_LINK0 ); - } }static void ravb_emac_init_rcar (struct net_device *ndev)
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 75/107 net: ravb: Start TX queues after HW initialization succeeded
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
[ Upstream commit 6f32c086602050fc11157adeafaa1c1eb393f0af ]
ravb_phy_start() may fail. If that happens, the TX queues will remain started. Thus, move the netif_tx_start_all_queues() after PHY is successfully initialized.
--- drivers/net/ethernet/renesas/ravb_main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/renesas/ravb_main.c +2 -2
@@ -1828,13 +1828,13 @@ static int ravb_open(struct net_device *ndev)if (info->gptp)ravb_ptp_init (ndev, priv->pdev); -netif_tx_start_all_queues (ndev); -/* PHY control start */ error =ravb_phy_start (ndev);if (error) goto out_ptp_stop; +netif_tx_start_all_queues (ndev); +return 0 ; out_ptp_stop:
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 76/107 net: ravb: Stop DMA in case of failures on ravb_open()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
[ Upstream commit eac16a733427ba0de2449ffc7bd3da32ddb65cb7 ]
In case ravb_phy_start() returns with error the settings applied in ravb_dmac_init() are not reverted (e.g. config mode). For this call ravb_stop_dma() on failure path of ravb_open().
--- drivers/net/ethernet/renesas/ravb_main.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/ethernet/renesas/ravb_main.c +1 -0
@@ -1841,6 +1841,7 @@ static int ravb_open(struct net_device *ndev)/* Stop PTP Clock driver */ if (info->gptp)ravb_ptp_stop (ndev); +ravb_stop_dma (ndev); out_free_irq_mgmta:if (!info->multi_irqs) goto out_free_irq;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 77/107 net: ravb: Keep reverse order of operations in ravb_remove()
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Claudiu Beznea <[email protected]>
[ Upstream commit edf9bc396e05081ca281ffb0cd41e44db478ff26 ]
On RZ/G3S SMARC Carrier II board having RGMII connections b/w Ethernet MACs and PHYs it has been discovered that doing unbind/bind for ravb driver in a loop leads to wrong speed and duplex for Ethernet links and broken connectivity (the connectivity cannot be restored even with bringing interface down/up). Before doing unbind/bind the Ethernet interfaces were configured though systemd. The sh instructions used to do unbind/bind were:
$ cd /sys/bus/platform/drivers/ravb/ $ while :; do echo 11c30000.ethernet > unbind ; \ echo 11c30000.ethernet > bind; done
It has been discovered that there is a race b/w IOCTLs initialized by systemd at the response of success binding and the "ravb_write(ndev, CCC_OPC_RESET, CCC)" call in ravb_remove() as follows:
1/ as a result of bind success the user space open/configures the
interfaces tough an IOCTL; the following stack trace has been identified on RZ/G3S:
Call trace: dump_backtrace+0x9c/0x100 show_stack+0x20/0x38 dump_stack_lvl+0x48/0x60 dump_stack+0x18/0x28 ravb_open+0x70/0xa58 __dev_open+0xf4/0x1e8 __dev_change_flags+0x198/0x218 dev_change_flags+0x2c/0x80 devinet_ioctl+0x640/0x708 inet_ioctl+0x1e4/0x200 sock_do_ioctl+0x50/0x108 sock_ioctl+0x240/0x358 __arm64_sys_ioctl+0xb0/0x100 invoke_syscall+0x50/0x128 el0_svc_common.constprop.0+0xc8/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x34/0xb8 el0t_64_sync_handler+0xc0/0xc8 el0t_64_sync+0x190/0x198
2/ this call may execute concurrently with ravb_remove() as the
unbind/bind operation was executed in a loop
3/ if the operation mode is changed to RESET (through
ravb_write(ndev, CCC_OPC_RESET, CCC) call in ravb_remove()) while the above ravb_open() is in progress it may lead to MAC (or PHY, or MAC-PHY connection, the right point hasn't been identified at the moment) to be broken, thus the Ethernet connectivity fails to restore.
The simple fix for this is to move ravb_write(ndev, CCC_OPC_RESET, CCC)) after unregister_netdev() to avoid resetting the controller while the netdev interface is still registered.
To avoid future issues in ravb_remove(), the patch follows the proper order of operations in ravb_remove(): reverse order compared with ravb_probe(). This avoids described races as the IOCTLs as well as unregister_netdev() (called now at the beginning of ravb_remove()) calls rtnl_lock() before continuing and IOCTLs check (though devinet_ioctl()) if device is still registered just after taking the lock:
int devinet_ioctl(struct net *net, unsigned int cmd, struct ifreq *ifr)
{
// ...
rtnl_lock();
ret = -ENODEV;
dev = __dev_get_by_name(net, ifr->ifr_name);
if (!dev)
goto done;
// ...
done:
rtnl_unlock();
out:
return ret;
}--- drivers/net/ethernet/renesas/ravb_main.c | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-)
drivers/net/ethernet/renesas/ravb_main.c +13 -9
@@ -2919,22 +2919,26 @@ static int ravb_remove(struct platform_device *pdev)struct ravb_private *priv =netdev_priv (ndev);const struct ravb_hw_info *info = priv->info; -/* Stop PTP Clock driver */ -if (info->ccc_gac) -ravb_ptp_stop (ndev); - -clk_disable_unprepare (priv->gptp_clk); -clk_disable_unprepare (priv->refclk); - -/* Set reset mode */ -ravb_write (ndev,CCC_OPC_RESET ,CCC );unregister_netdev (ndev);if (info->nc_queues)netif_napi_del (&priv->napi[RAVB_NC ]);netif_napi_del (&priv->napi[RAVB_BE ]); +ravb_mdio_release (priv); + +/* Stop PTP Clock driver */ +if (info->ccc_gac) +ravb_ptp_stop (ndev); +dma_free_coherent (ndev->dev.parent, priv->desc_bat_size, priv->desc_bat, priv->desc_bat_dma); + +/* Set reset mode */ +ravb_write (ndev,CCC_OPC_RESET ,CCC ); + +clk_disable_unprepare (priv->gptp_clk); +clk_disable_unprepare (priv->refclk); +pm_runtime_put_sync (&pdev->dev);pm_runtime_disable (&pdev->dev);reset_control_assert (priv->rstc);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 78/107 KVM: x86: Fix lapic timer interrupt lost after loading a snapshot.
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Haitao Shan <[email protected]>
[ Upstream commit 9cfec6d097c607e36199cf0cfbb8cf5acbd8e9b2 ]
When running android emulator (which is based on QEMU 2.12) on certain Intel hosts with kernel version 6.3-rc1 or above, guest will freeze after loading a snapshot. This is almost 100% reproducible. By default, the android emulator will use snapshot to speed up the next launching of the same android guest. So this breaks the android emulator badly.
I tested QEMU 8.0.4 from Debian 12 with an Ubuntu 22.04 guest by running command "loadvm" after "savevm". The same issue is observed. At the same time, none of our AMD platforms is impacted. More experiments show that loading the KVM module with "enable_apicv=false" can workaround it.
The issue started to show up after commit 8e6ed96cdd50 ("KVM: x86:
fire timer when it is migrated and expired, and in oneshot mode"). However, as is pointed out by Sean Christopherson, it is introduced by commit 967235d32032 ("KVM: vmx: clear pending interrupts on KVM_SET_LAPIC"). commit 8e6ed96cdd50 ("KVM: x86: fire timer when it is migrated and expired, and in oneshot mode") just makes it easier to hit the issue.
Having both commits, the oneshot lapic timer gets fired immediately inside the KVM_SET_LAPIC call when loading the snapshot. On Intel platforms with APIC virtualization and posted interrupt processing, this eventually leads to setting the corresponding PIR bit. However, the whole PIR bits get cleared later in the same KVM_SET_LAPIC call by apicv_post_state_restore. This leads to timer interrupt lost.
The fix is to move vmx_apicv_post_state_restore to the beginning of the KVM_SET_LAPIC call and rename to vmx_apicv_pre_state_restore. What vmx_apicv_post_state_restore does is actually clearing any former apicv state and this behavior is more suitable to carry out in the beginning.
--- arch/x86/include/asm/kvm-x86-ops.h | 1 + arch/x86/include/asm/kvm_host.h | 1 + arch/x86/kvm/lapic.c | 4 ++++ arch/x86/kvm/vmx/vmx.c | 4 ++-- 4 files changed, 8 insertions(+), 2 deletions(-)
arch/x86/include/asm/kvm-x86-ops.h +1 -0
@@ -106,6 +106,7 @@ KVM_X86_OP_OPTIONAL(vcpu_blocking) KVM_X86_OP_OPTIONAL(vcpu_unblocking) KVM_X86_OP_OPTIONAL(pi_update_irte) KVM_X86_OP_OPTIONAL(pi_start_assignment) +KVM_X86_OP_OPTIONAL(apicv_pre_state_restore) KVM_X86_OP_OPTIONAL(apicv_post_state_restore) KVM_X86_OP_OPTIONAL_RET0(dy_apicv_has_pending_interrupt) KVM_X86_OP_OPTIONAL(set_hv_timer)
arch/x86/include/asm/kvm_host.h +1 -0
@@ -1603,6 +1603,7 @@ struct kvm_x86_ops {int (*pi_update_irte)(struct kvm *kvm,unsigned int host_irq,uint32_t guest_irq,bool set);void (*pi_start_assignment)(struct kvm *kvm); +void (*apicv_pre_state_restore)(struct kvm_vcpu *vcpu);void (*apicv_post_state_restore)(struct kvm_vcpu *vcpu);bool (*dy_apicv_has_pending_interrupt)(struct kvm_vcpu *vcpu);
arch/x86/kvm/lapic.c +4 -0
@@ -2446,6 +2446,8 @@ void kvm_lapic_reset(struct kvm_vcpu *vcpu, bool init_event)u64 msr_val;int i; +static_call_cond (kvm_x86_apicv_pre_state_restore)(vcpu); +if (!init_event) { msr_val =APIC_DEFAULT_PHYS_BASE |MSR_IA32_APICBASE_ENABLE ;if (kvm_vcpu_is_reset_bsp (vcpu))
@@ -2757,6 +2759,8 @@ int kvm_apic_set_state(struct kvm_vcpu *vcpu, struct kvm_lapic_state *s)struct kvm_lapic *apic = vcpu->arch.apic;int r; +static_call_cond (kvm_x86_apicv_pre_state_restore)(vcpu); +kvm_lapic_set_base (vcpu, vcpu->arch.apic_base);/* set SPIV separately to get count of SW disabled APICs right */ apic_set_spiv (apic, *((u32 *)(s->regs +APIC_SPIV )));
arch/x86/kvm/vmx/vmx.c +2 -2
@@ -6799,7 +6799,7 @@ static void vmx_load_eoi_exitmap(struct kvm_vcpu *vcpu, u64 *eoi_exit_bitmap)vmcs_write64 (EOI_EXIT_BITMAP3 , eoi_exit_bitmap[3 ]); } -static void vmx_apicv_post_state_restore (struct kvm_vcpu *vcpu) +static void vmx_apicv_pre_state_restore (struct kvm_vcpu *vcpu) {struct vcpu_vmx *vmx =to_vmx (vcpu);
@@ -8172,7 +8172,7 @@ static struct kvm_x86_ops vmx_x86_ops __initdata = { .set_apic_access_page_addr = vmx_set_apic_access_page_addr, .refresh_apicv_exec_ctrl = vmx_refresh_apicv_exec_ctrl, .load_eoi_exitmap = vmx_load_eoi_exitmap, - .apicv_post_state_restore = vmx_apicv_post_state_restore, + .apicv_pre_state_restore = vmx_apicv_pre_state_restore, .check_apicv_inhibit_reasons = vmx_check_apicv_inhibit_reasons, .hwapic_irr_update = vmx_hwapic_irr_update, .hwapic_isr_update = vmx_hwapic_isr_update,
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 79/107 PCI: Lengthen reset delay for VideoPropulsion Torrent QN16e card
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lukas Wunner <[email protected]>
[ Upstream commit c9260693aa0c1e029ed23693cfd4d7814eee6624 ]
Commit ac91e6980563 ("PCI: Unify delay handling for reset and resume") shortened an unconditional 1 sec delay after a Secondary Bus Reset to 100 msec for PCIe (per PCIe r6.1 sec 6.6.1). The 1 sec delay is only required for Conventional PCI.
But it turns out that there are PCIe devices which require a longer delay than prescribed before first config space access after reset recovery or resume from D3cold:
Chad reports that a "VideoPropulsion Torrent QN16e" MPEG QAM Modulator "raises a PCI system error (PERR), as reported by the IPMI event log, and the hardware itself would suffer a catastrophic event, cycling the server" unless the longer delay is observed.
The card is specified to conform to PCIe r1.0 and indeed only supports Gen1 speed (2.5 GT/s) according to lspci. PCIe r1.0 sec 7.6 prescribes the same 100 msec delay as PCIe r6.1 sec 6.6.1:
To allow components to perform internal initialization, system software must wait for at least 100 ms from the end of a reset (cold/warm/hot) before it is permitted to issue Configuration Requests
The behavior of the Torrent QN16e card thus appears to be a quirk. Treat it as such and lengthen the reset delay for this specific device.
--- drivers/pci/quirks.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/pci/quirks.c +12 -0
@@ -6058,3 +6058,15 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x9a2d, dpc_log_size);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x9a2f , dpc_log_size);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x9a31 , dpc_log_size);#endif + +/* +* Devices known to require a longer delay before first config space access +* after reset recovery or resume from D3cold: +* +* VideoPropulsion (aka Genroco) Torrent QN16e MPEG QAM Modulator +*/ +static void pci_fixup_d3cold_delay_1sec (struct pci_dev *pdev) +{ + pdev->d3cold_delay =1000 ; +} +DECLARE_PCI_FIXUP_FINAL (0x5555 ,0x0004 , pci_fixup_d3cold_delay_1sec);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 80/107 powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gaurav Batra <[email protected]>
[ Upstream commit 3bf983e4e93ce8e6d69e9d63f52a66ec0856672e ]
When a device is initialized, the driver invokes dma_supported() twice - first for streaming mappings followed by coherent mappings. For an SR-IOV device, default window is deleted and DDW created. With vPMEM enabled, TCE mappings are dynamically created for both vPMEM and SR-IOV device. There are no direct mappings.
First time when dma_supported() is called with 64 bit mask, DDW is created and marked as dynamic window. The second time dma_supported() is called, enable_ddw() finds existing window for the device and incorrectly returns it as "direct mapping".
This only happens when size of DDW is big enough to map max LPAR memory.
This results in streaming TCEs to not get dynamically mapped, since code incorrently assumes these are already pre-mapped. The adapter initially comes up but goes down due to EEH.
--- arch/powerpc/platforms/pseries/iommu.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
arch/powerpc/platforms/pseries/iommu.c +4 -4
@@ -909,7 +909,8 @@ static int remove_ddw(struct device_node *np, bool remove_prop, const char *win_return 0 ; } -static bool find_existing_ddw (struct device_node *pdn,u64 *dma_addr,int *window_shift) +static bool find_existing_ddw (struct device_node *pdn,u64 *dma_addr,int *window_shift, +bool *direct_mapping) {struct dma_win *window;const struct dynamic_dma_window_prop *dma64;
@@ -922,6 +923,7 @@ static bool find_existing_ddw(struct device_node *pdn, u64 *dma_addr, int *windo dma64 = window->prop; *dma_addr =be64_to_cpu (dma64->dma_base); *window_shift =be32_to_cpu (dma64->window_shift); + *direct_mapping = window->direct; found = true;break ; }
@@ -1275,10 +1277,8 @@ static bool enable_ddw(struct pci_dev *dev, struct device_node *pdn)mutex_lock (&dma_win_init_mutex); -if (find_existing_ddw (pdn, &dev->dev.archdata.dma_offset, &len)) { - direct_mapping = (len >= max_ram_len); +if (find_existing_ddw (pdn, &dev->dev.archdata.dma_offset, &len, &direct_mapping)) goto out_unlock; - }/* * If we already went through this for a previous function of
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 81/107 s390/cmma: fix handling of swapper_pg_dir and invalid_pg_dir
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Heiko Carstens <[email protected]>
[ Upstream commit 84bb41d5df48868055d159d9247b80927f1f70f9 ]
If the cmma no-dat feature is available the kernel page tables are walked to identify and mark all pages which are used for address translation (all region, segment, and page tables). In a subsequent loop all other pages are marked as "no-dat" pages with the ESSA instruction.
This information is visible to the hypervisor, so that the hypervisor can optimize purging of guest TLB entries. All pages used for swapper_pg_dir and invalid_pg_dir are incorrectly marked as no-dat, which in turn can result in incorrect guest TLB flushes.
Fix this by marking those pages correctly as being used for DAT.
--- arch/s390/mm/page-states.c | 6 ++++++ 1 file changed, 6 insertions(+)
arch/s390/mm/page-states.c +6 -0
@@ -192,6 +192,12 @@ void __init cmma_init_nodat(void)return ;/* Mark pages used in kernel page tables */ mark_kernel_pgd (); + page =virt_to_page (&swapper_pg_dir); +for (i =0 ; i <4 ; i++) +set_bit (PG_arch_1, &page[i].flags); + page =virt_to_page (&invalid_pg_dir); +for (i =0 ; i <4 ; i++) +set_bit (PG_arch_1, &page[i].flags);/* Set all kernel pages not used for page tables to stable/no-dat */ for_each_mem_pfn_range (i,MAX_NUMNODES , &start, &end,NULL ) {
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 82/107 PCI: qcom-ep: Add dedicated callback for writing to DBI2 registers
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Manivannan Sadhasivam <[email protected]>
[ Upstream commit a07d2497ed657eb2efeb967af47e22f573dcd1d6 ]
The DWC core driver exposes the write_dbi2() callback for writing to the DBI2 registers in a vendor-specific way.
On the Qcom EP platforms, the DBI_CS2 bit in the ELBI region needs to be asserted before writing to any DBI2 registers and deasserted once done.
So, let's implement the callback for the Qcom PCIe EP driver so that the DBI2 writes are correctly handled in the hardware.
Without this callback, the DBI2 register writes like BAR size won't go through and as a result, the default BAR size is set for all BARs.
--- drivers/pci/controller/dwc/pcie-qcom-ep.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
drivers/pci/controller/dwc/pcie-qcom-ep.c +17 -0
@@ -120,6 +120,7 @@/* ELBI registers */ #define ELBI_SYS_STTS 0x08 +#define ELBI_CS2_ENABLE 0xa4/* DBI registers */ #define DBI_CON_STATUS 0x44
@@ -252,6 +253,21 @@ static void qcom_pcie_dw_stop_link(struct dw_pcie *pci)disable_irq (pcie_ep->perst_irq); } +static void qcom_pcie_dw_write_dbi2 (struct dw_pcie *pci,void __iomem *base, +u32 reg,size_t size,u32 val) +{ +struct qcom_pcie_ep *pcie_ep =to_pcie_ep (pci); +int ret; + +writel (1 , pcie_ep->elbi +ELBI_CS2_ENABLE ); + + ret =dw_pcie_write (pci->dbi_base2 + reg, size, val); +if (ret) +dev_err (pci->dev,"Failed to write DBI2 register (0x%x): %d\n" , reg, ret); + +writel (0 , pcie_ep->elbi +ELBI_CS2_ENABLE ); +} +static int qcom_pcie_enable_resources (struct qcom_pcie_ep *pcie_ep) {int ret;
@@ -446,6 +462,7 @@ static const struct dw_pcie_ops pci_ops = { .link_up = qcom_pcie_dw_link_up, .start_link = qcom_pcie_dw_start_link, .stop_link = qcom_pcie_dw_stop_link, + .write_dbi2 = qcom_pcie_dw_write_dbi2, }; static int qcom_pcie_ep_get_io_resources(struct platform_device *pdev,
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 83/107 fbdev: stifb: Make the STI next font pointer a 32-bit signed offset
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Helge Deller <[email protected]>
[ Upstream commit 8a32aa17c1cd48df1ddaa78e45abcb8c7a2220d6 ]
The pointer to the next STI font is actually a signed 32-bit offset. With this change the 64-bit kernel will correctly subract the (signed 32-bit) offset instead of adding a (unsigned 32-bit) offset. It has no effect on 32-bit kernels.
This fixes the stifb driver with a 64-bit kernel on qemu.
--- drivers/video/fbdev/sticore.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/video/fbdev/sticore.h +1 -1
@@ -231,7 +231,7 @@ struct sti_rom_font {u8 height;u8 font_type;/* language type */ u8 bytes_per_char; -u32 next_font; +s32 next_font;/* note: signed int */ u8 underline_height;u8 underline_pos;u8 res008[2 ];
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 84/107 drivers: perf: Check find_first_bit() return value
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexandre Ghiti <[email protected]>
[ Upstream commit c6e316ac05532febb0c966fa9b55f5258ed037be ]
We must check the return value of find_first_bit() before using the return value as an index array since it happens to overflow the array and then panic:
[ 107.318430] Kernel BUG [#1] [ 107.319434] CPU: 3 PID: 1238 Comm: kill Tainted: G E 6.6.0-rc6ubuntu-defconfig #2 [ 107.319465] Hardware name: riscv-virtio,qemu (DT) [ 107.319551] epc : pmu_sbi_ovf_handler+0x3a4/0x3ae [ 107.319840] ra : pmu_sbi_ovf_handler+0x52/0x3ae [ 107.319868] epc : ffffffff80a0a77c ra : ffffffff80a0a42a sp : ffffaf83fecda350 [ 107.319884] gp : ffffffff823961a8 tp : ffffaf8083db1dc0 t0 : ffffaf83fecda480 [ 107.319899] t1 : ffffffff80cafe62 t2 : 000000000000ff00 s0 : ffffaf83fecda520 [ 107.319921] s1 : ffffaf83fecda380 a0 : 00000018fca29df0 a1 : ffffffffffffffff [ 107.319936] a2 : 0000000001073734 a3 : 0000000000000004 a4 : 0000000000000000 [ 107.319951] a5 : 0000000000000040 a6 : 000000001d1c8774 a7 : 0000000000504d55 [ 107.319965] s2 : ffffffff82451f10 s3 : ffffffff82724e70 s4 : 000000000000003f [ 107.319980] s5 : 0000000000000011 s6 : ffffaf8083db27c0 s7 : 0000000000000000 [ 107.319995] s8 : 0000000000000001 s9 : 00007fffb45d6558 s10: 00007fffb45d81a0 [ 107.320009] s11: ffffaf7ffff60000 t3 : 0000000000000004 t4 : 0000000000000000 [ 107.320023] t5 : ffffaf7f80000000 t6 : ffffaf8000000000 [ 107.320037] status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003 [ 107.320081] [<ffffffff80a0a77c>] pmu_sbi_ovf_handler+0x3a4/0x3ae [ 107.320112] [<ffffffff800b42d0>] handle_percpu_devid_irq+0x9e/0x1a0 [ 107.320131] [<ffffffff800ad92c>] generic_handle_domain_irq+0x28/0x36 [ 107.320148] [<ffffffff8065f9f8>] riscv_intc_irq+0x36/0x4e [ 107.320166] [<ffffffff80caf4a0>] handle_riscv_irq+0x54/0x86 [ 107.320189] [<ffffffff80cb0036>] do_irq+0x64/0x96 [ 107.320271] Code: 85a6 855e b097 ff7f 80e7 9220 b709 9002 4501 bbd9 (9002) 6097 [ 107.320585] ---[ end trace 0000000000000000 ]--- [ 107.320704] Kernel panic - not syncing: Fatal exception in interrupt [ 107.320775] SMP: stopping secondary CPUs [ 107.321219] Kernel Offset: 0x0 from 0xffffffff80000000 [ 107.333051] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---
--- drivers/perf/riscv_pmu_sbi.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/perf/riscv_pmu_sbi.c +5 -0
@@ -578,6 +578,11 @@ static irqreturn_t pmu_sbi_ovf_handler(int irq, void *dev)/* Firmware counter don't support overflow yet */ fidx =find_first_bit (cpu_hw_evt->used_hw_ctrs,RISCV_MAX_COUNTERS ); +if (fidx ==RISCV_MAX_COUNTERS ) { +csr_clear (CSR_SIP ,BIT (riscv_pmu_irq_num)); +return IRQ_NONE ; + } + event = cpu_hw_evt->events[fidx];if (!event) {csr_clear (CSR_SIP ,SIP_LCOFIP );
Signature · 1 line
2.42.0
Re: [PATCH 6.1 084/107] drivers: perf: Check find_first_bit() return value
Quoted 57 lines · Greg Kroah-Hartman
6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexandre Ghiti <[email protected]>
[ Upstream commit
c6e316ac05532febb0c966fa9b55f5258ed037be]We must check the return value of
find_first_bit()before using the return value as an index array since it happens to overflow the array and then panic:[ 107.318430] Kernel BUG [#1] [ 107.319434] CPU: 3 PID: 1238 Comm: kill Tainted: G E 6.6.0-rc6ubuntu-defconfig #2 [ 107.319465] Hardware name: riscv-virtio,qemu (DT) [ 107.319551] epc : pmu_sbi_ovf_handler+0x3a4/0x3ae [ 107.319840] ra : pmu_sbi_ovf_handler+0x52/0x3ae [ 107.319868] epc : ffffffff80a0a77c ra : ffffffff80a0a42a sp : ffffaf83fecda350 [ 107.319884] gp : ffffffff823961a8 tp : ffffaf8083db1dc0 t0 : ffffaf83fecda480 [ 107.319899] t1 : ffffffff80cafe62 t2 : 000000000000ff00 s0 : ffffaf83fecda520 [ 107.319921] s1 : ffffaf83fecda380 a0 : 00000018fca29df0 a1 : ffffffffffffffff [ 107.319936] a2 : 0000000001073734 a3 : 0000000000000004 a4 : 0000000000000000 [ 107.319951] a5 : 0000000000000040 a6 : 000000001d1c8774 a7 : 0000000000504d55 [ 107.319965] s2 : ffffffff82451f10 s3 : ffffffff82724e70 s4 : 000000000000003f [ 107.319980] s5 : 0000000000000011 s6 : ffffaf8083db27c0 s7 : 0000000000000000 [ 107.319995] s8 : 0000000000000001 s9 : 00007fffb45d6558 s10: 00007fffb45d81a0 [ 107.320009] s11: ffffaf7ffff60000 t3 : 0000000000000004 t4 : 0000000000000000 [ 107.320023] t5 : ffffaf7f80000000 t6 : ffffaf8000000000 [ 107.320037] status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003 [ 107.320081] [<ffffffff80a0a77c>] pmu_sbi_ovf_handler+0x3a4/0x3ae [ 107.320112] [<ffffffff800b42d0>] handle_percpu_devid_irq+0x9e/0x1a0 [ 107.320131] [<ffffffff800ad92c>] generic_handle_domain_irq+0x28/0x36 [ 107.320148] [<ffffffff8065f9f8>] riscv_intc_irq+0x36/0x4e [ 107.320166] [<ffffffff80caf4a0>] handle_riscv_irq+0x54/0x86 [ 107.320189] [<ffffffff80cb0036>] do_irq+0x64/0x96 [ 107.320271] Code: 85a6 855e b097 ff7f 80e7 9220 b709 9002 4501 bbd9 (9002) 6097 [ 107.320585] ---[ end trace 0000000000000000 ]--- [ 107.320704] Kernel panic - not syncing: Fatal exception in interrupt [ 107.320775] SMP: stopping secondary CPUs [ 107.321219] Kernel Offset: 0x0 from 0xffffffff80000000 [ 107.333051] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---Fixes 4905ec2fb7e6 ("RISC-V: Add sscofpmf extension support")Signed-off-by Alexandre Ghiti <[email protected]>Signed-off-by Palmer Dabbelt <[email protected]>Signed-off-by Sasha Levin <[email protected]>--- drivers/perf/riscv_pmu_sbi.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/perf/riscv_pmu_sbi.c +0
-0
drivers/perf/riscv_pmu_sbi.c static irqreturn_t pmu_sbi_ovf_handler(int irq, void *dev) · line 582
Quoted 5 lines
drivers/perf/riscv_pmu_sbi.c +2
-0@@ -578,6 +578,11 @@ static irqreturn_t pmu_sbi_ovf_handler(int irq, void *dev)/* Firmware counter don't support overflow yet */ fidx =find_first_bit (cpu_hw_evt->used_hw_ctrs,RISCV_MAX_COUNTERS ); +if (fidx ==RISCV_MAX_COUNTERS ) { +csr_clear (CSR_SIP ,BIT (riscv_pmu_irq_num));
This breaks the build, "riscv_pmu_irq_num" does not exist in 6.1, perhaps "riscv_pmu_irq" is the right choice, but it needs a deeper look.
Quoted 11 lines
drivers/perf/riscv_pmu_sbi.c +3
-0+return IRQ_NONE ; + } + event = cpu_hw_evt->events[fidx];if (!event) {csr_clear (CSR_SIP ,SIP_LCOFIP );Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerRe: [PATCH 6.1 084/107] drivers: perf: Check find_first_bit() return value
Quoted 59 lines · Conor Dooley
Quoted 58 lines · Greg Kroah-Hartman
6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexandre Ghiti <[email protected]>
[ Upstream commit
c6e316ac05532febb0c966fa9b55f5258ed037be]We must check the return value of
find_first_bit()before using the return value as an index array since it happens to overflow the array and then panic:[ 107.318430] Kernel BUG [#1] [ 107.319434] CPU: 3 PID: 1238 Comm: kill Tainted: G E 6.6.0-rc6ubuntu-defconfig #2 [ 107.319465] Hardware name: riscv-virtio,qemu (DT) [ 107.319551] epc : pmu_sbi_ovf_handler+0x3a4/0x3ae [ 107.319840] ra : pmu_sbi_ovf_handler+0x52/0x3ae [ 107.319868] epc : ffffffff80a0a77c ra : ffffffff80a0a42a sp : ffffaf83fecda350 [ 107.319884] gp : ffffffff823961a8 tp : ffffaf8083db1dc0 t0 : ffffaf83fecda480 [ 107.319899] t1 : ffffffff80cafe62 t2 : 000000000000ff00 s0 : ffffaf83fecda520 [ 107.319921] s1 : ffffaf83fecda380 a0 : 00000018fca29df0 a1 : ffffffffffffffff [ 107.319936] a2 : 0000000001073734 a3 : 0000000000000004 a4 : 0000000000000000 [ 107.319951] a5 : 0000000000000040 a6 : 000000001d1c8774 a7 : 0000000000504d55 [ 107.319965] s2 : ffffffff82451f10 s3 : ffffffff82724e70 s4 : 000000000000003f [ 107.319980] s5 : 0000000000000011 s6 : ffffaf8083db27c0 s7 : 0000000000000000 [ 107.319995] s8 : 0000000000000001 s9 : 00007fffb45d6558 s10: 00007fffb45d81a0 [ 107.320009] s11: ffffaf7ffff60000 t3 : 0000000000000004 t4 : 0000000000000000 [ 107.320023] t5 : ffffaf7f80000000 t6 : ffffaf8000000000 [ 107.320037] status: 0000000200000100 badaddr: 0000000000000000 cause: 0000000000000003 [ 107.320081] [<ffffffff80a0a77c>] pmu_sbi_ovf_handler+0x3a4/0x3ae [ 107.320112] [<ffffffff800b42d0>] handle_percpu_devid_irq+0x9e/0x1a0 [ 107.320131] [<ffffffff800ad92c>] generic_handle_domain_irq+0x28/0x36 [ 107.320148] [<ffffffff8065f9f8>] riscv_intc_irq+0x36/0x4e [ 107.320166] [<ffffffff80caf4a0>] handle_riscv_irq+0x54/0x86 [ 107.320189] [<ffffffff80cb0036>] do_irq+0x64/0x96 [ 107.320271] Code: 85a6 855e b097 ff7f 80e7 9220 b709 9002 4501 bbd9 (9002) 6097 [ 107.320585] ---[ end trace 0000000000000000 ]--- [ 107.320704] Kernel panic - not syncing: Fatal exception in interrupt [ 107.320775] SMP: stopping secondary CPUs [ 107.321219] Kernel Offset: 0x0 from 0xffffffff80000000 [ 107.333051] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---Fixes 4905ec2fb7e6 ("RISC-V: Add sscofpmf extension support")Signed-off-by Alexandre Ghiti <[email protected]>Signed-off-by Palmer Dabbelt <[email protected]>Signed-off-by Sasha Levin <[email protected]>--- drivers/perf/riscv_pmu_sbi.c | 5 +++++ 1 file changed, 5 insertions(+)drivers/perf/riscv_pmu_sbi.c +0
-0@@ -578,6 +578,11 @@ static irqreturn_t pmu_sbi_ovf_handler(int irq, void *dev)
Quoted 7 lines
drivers/perf/riscv_pmu_sbi.c static irqreturn_t pmu_sbi_ovf_handler(int irq, void *dev) · line 582
Quoted 4 lines
drivers/perf/riscv_pmu_sbi.c +2
-0/* Firmware counter don't support overflow yet */ fidx =find_first_bit (cpu_hw_evt->used_hw_ctrs,RISCV_MAX_COUNTERS ); +if (fidx ==RISCV_MAX_COUNTERS ) { +csr_clear (CSR_SIP ,BIT (riscv_pmu_irq_num));This breaks the build, "
riscv_pmu_irq_num" does not exist in 6.1, perhaps "riscv_pmu_irq" is the right choice, but it needs a deeper look.
Thanks, now dropped.
greg k-h
Greg Kroah-Hartman
maintainerPATCH 85/107 spi: Fix null dereference on suspend
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mark Hasemeyer <[email protected]>
[ Upstream commit bef4a48f4ef798c4feddf045d49e53c8a97d5e37 ]
A race condition exists where a synchronous (noqueue) transfer can be active during a system suspend. This can cause a null pointer dereference exception to occur when the system resumes.
Example order of events leading to the exception:
1. spi_sync() calls __spi_transfer_message_noqueue() which sets ctlr->cur_msg
2. Spi transfer begins via spi_transfer_one_message()
3. System is suspended interrupting the transfer context
4. System is resumed
6. spi_controller_resume() calls spi_start_queue() which resets cur_msg to NULL
7. Spi transfer context resumes and spi_finalize_current_message() is called which dereferences cur_msg (which is now NULL)
Wait for synchronous transfers to complete before suspending by acquiring the bus mutex and setting/checking a suspend flag.
--- drivers/spi/spi.c | 56 ++++++++++++++++++++++++++++------------- include/linux/spi/spi.h | 1 + 2 files changed, 40 insertions(+), 17 deletions(-)
drivers/spi/spi.c +39 -17
@@ -3299,33 +3299,52 @@ void spi_unregister_controller(struct spi_controller *ctlr) }EXPORT_SYMBOL_GPL (spi_unregister_controller); +static inline int __spi_check_suspended (const struct spi_controller *ctlr) +{ +return ctlr->flags &SPI_CONTROLLER_SUSPENDED ? -ESHUTDOWN :0 ; +} + +static inline void __spi_mark_suspended (struct spi_controller *ctlr) +{ +mutex_lock (&ctlr->bus_lock_mutex); + ctlr->flags |=SPI_CONTROLLER_SUSPENDED ; +mutex_unlock (&ctlr->bus_lock_mutex); +} + +static inline void __spi_mark_resumed (struct spi_controller *ctlr) +{ +mutex_lock (&ctlr->bus_lock_mutex); + ctlr->flags &= ~SPI_CONTROLLER_SUSPENDED ; +mutex_unlock (&ctlr->bus_lock_mutex); +} +int spi_controller_suspend (struct spi_controller *ctlr) { -int ret; +int ret =0 ;/* Basically no-ops for non-queued controllers */ -if (!ctlr->queued) -return 0 ; - - ret =spi_stop_queue (ctlr); -if (ret) -dev_err (&ctlr->dev,"queue stop failed\n" ); +if (ctlr->queued) { + ret =spi_stop_queue (ctlr); +if (ret) +dev_err (&ctlr->dev,"queue stop failed\n" ); + } +__spi_mark_suspended (ctlr);return ret; }EXPORT_SYMBOL_GPL (spi_controller_suspend);int spi_controller_resume (struct spi_controller *ctlr) { -int ret; - -if (!ctlr->queued) -return 0 ; +int ret =0 ; - ret =spi_start_queue (ctlr); -if (ret) -dev_err (&ctlr->dev,"queue restart failed\n" ); +__spi_mark_resumed (ctlr); +if (ctlr->queued) { + ret =spi_start_queue (ctlr); +if (ret) +dev_err (&ctlr->dev,"queue restart failed\n" ); + }return ret; }EXPORT_SYMBOL_GPL (spi_controller_resume);
@@ -4050,8 +4069,7 @@ static void __spi_transfer_message_noqueue(struct spi_controller *ctlr, struct s ctlr->cur_msg = msg; ret =__spi_pump_transfer_message (ctlr, msg, was_busy);if (ret) - goto out; - +dev_err (&ctlr->dev,"noqueue transfer failed\n" ); ctlr->cur_msg =NULL ; ctlr->fallback = false;
@@ -4067,7 +4085,6 @@ static void __spi_transfer_message_noqueue(struct spi_controller *ctlr, struct sspi_idle_runtime_pm (ctlr); } -out:mutex_unlock (&ctlr->io_mutex); }
@@ -4090,6 +4107,11 @@ static int __spi_sync(struct spi_device *spi, struct spi_message *message)int status;struct spi_controller *ctlr = spi->controller; +if (__spi_check_suspended (ctlr)) { +dev_warn_once (&spi->dev,"Attempted to sync while suspend\n" ); +return -ESHUTDOWN ; + } + status =__spi_validate (spi, message);if (status !=0 )return status;
include/linux/spi/spi.h +1 -0
@@ -531,6 +531,7 @@ struct spi_controller {#define SPI_CONTROLLER_MUST_TX BIT(4)/* Requires tx */ #define SPI_MASTER_GPIO_SS BIT(5)/* GPIO CS must select slave */ +#define SPI_CONTROLLER_SUSPENDED BIT(6)/* Currently suspended */ /* Flag indicating if the allocation of this struct is devres-managed */ bool devm_allocated;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 86/107 drm/amd/display: Restore rptr/wptr for DMCUB as workaround
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: JinZe.Xu <[email protected]>
[ Upstream commit 8f3589bb6fcea397775398cba4fbcc46829a60ed ]
[Why]
States may be desync after resume.
[How]
Sync sw state with hw state.
Stable-dep-of: 1ffa8602e39b ("drm/amd/display: Guard against invalid RPTR/WPTR being set")
--- drivers/gpu/drm/amd/display/dmub/dmub_srv.h | 14 ++++++++++++++ .../gpu/drm/amd/display/dmub/src/dmub_dcn20.c | 5 +++++ .../gpu/drm/amd/display/dmub/src/dmub_dcn20.h | 2 ++ .../gpu/drm/amd/display/dmub/src/dmub_dcn31.c | 5 +++++ .../gpu/drm/amd/display/dmub/src/dmub_dcn31.h | 2 ++ .../gpu/drm/amd/display/dmub/src/dmub_dcn32.c | 5 +++++ .../gpu/drm/amd/display/dmub/src/dmub_dcn32.h | 2 ++ drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c | 17 +++++++++++++++++ 8 files changed, 52 insertions(+)
drivers/gpu/drm/amd/display/dmub/dmub_srv.h +14 -0
@@ -332,6 +332,8 @@ struct dmub_srv_hw_funcs {void (*setup_mailbox)(struct dmub_srv *dmub,const struct dmub_region *inbox1); +uint32_t (*get_inbox1_wptr)(struct dmub_srv *dmub); +uint32_t (*get_inbox1_rptr)(struct dmub_srv *dmub);void (*set_inbox1_wptr)(struct dmub_srv *dmub,uint32_t wptr_offset);
@@ -590,6 +592,18 @@ enum dmub_status dmub_srv_hw_init(struct dmub_srv *dmub,*/ enum dmub_status dmub_srv_hw_reset (struct dmub_srv *dmub); +/** +* dmub_srv_sync_inbox1() - sync sw state with hw state +* @dmub: the dmub service +* +* Sync sw state with hw state when resume from S0i3 +* +* Return: +* DMUB_STATUS_OK - success +* DMUB_STATUS_INVALID - unspecified error +*/ +enum dmub_status dmub_srv_sync_inbox1 (struct dmub_srv *dmub); +/** * dmub_srv_cmd_queue() - queues a command to the DMUB * @dmub: the dmub service
drivers/gpu/drm/amd/display/dmub/src/dmub_dcn20.c +5 -0
@@ -282,6 +282,11 @@ void dmub_dcn20_setup_mailbox(struct dmub_srv *dmub,REG_WRITE (DMCUB_INBOX1_SIZE , inbox1->top - inbox1->base); } +uint32_t dmub_dcn20_get_inbox1_wptr (struct dmub_srv *dmub) +{ +return REG_READ (DMCUB_INBOX1_WPTR ); +} +uint32_t dmub_dcn20_get_inbox1_rptr (struct dmub_srv *dmub) {return REG_READ (DMCUB_INBOX1_RPTR );
drivers/gpu/drm/amd/display/dmub/src/dmub_dcn20.h +2 -0
@@ -202,6 +202,8 @@ void dmub_dcn20_setup_windows(struct dmub_srv *dmub,void dmub_dcn20_setup_mailbox (struct dmub_srv *dmub,const struct dmub_region *inbox1); +uint32_t dmub_dcn20_get_inbox1_wptr (struct dmub_srv *dmub); +uint32_t dmub_dcn20_get_inbox1_rptr (struct dmub_srv *dmub);void dmub_dcn20_set_inbox1_wptr (struct dmub_srv *dmub,uint32_t wptr_offset);
drivers/gpu/drm/amd/display/dmub/src/dmub_dcn31.c +5 -0
@@ -242,6 +242,11 @@ void dmub_dcn31_setup_mailbox(struct dmub_srv *dmub,REG_WRITE (DMCUB_INBOX1_SIZE , inbox1->top - inbox1->base); } +uint32_t dmub_dcn31_get_inbox1_wptr (struct dmub_srv *dmub) +{ +return REG_READ (DMCUB_INBOX1_WPTR ); +} +uint32_t dmub_dcn31_get_inbox1_rptr (struct dmub_srv *dmub) {return REG_READ (DMCUB_INBOX1_RPTR );
drivers/gpu/drm/amd/display/dmub/src/dmub_dcn31.h +2 -0
@@ -204,6 +204,8 @@ void dmub_dcn31_setup_windows(struct dmub_srv *dmub,void dmub_dcn31_setup_mailbox (struct dmub_srv *dmub,const struct dmub_region *inbox1); +uint32_t dmub_dcn31_get_inbox1_wptr (struct dmub_srv *dmub); +uint32_t dmub_dcn31_get_inbox1_rptr (struct dmub_srv *dmub);void dmub_dcn31_set_inbox1_wptr (struct dmub_srv *dmub,uint32_t wptr_offset);
drivers/gpu/drm/amd/display/dmub/src/dmub_dcn32.c +5 -0
@@ -266,6 +266,11 @@ void dmub_dcn32_setup_mailbox(struct dmub_srv *dmub,REG_WRITE (DMCUB_INBOX1_SIZE , inbox1->top - inbox1->base); } +uint32_t dmub_dcn32_get_inbox1_wptr (struct dmub_srv *dmub) +{ +return REG_READ (DMCUB_INBOX1_WPTR ); +} +uint32_t dmub_dcn32_get_inbox1_rptr (struct dmub_srv *dmub) {return REG_READ (DMCUB_INBOX1_RPTR );
drivers/gpu/drm/amd/display/dmub/src/dmub_dcn32.h +2 -0
@@ -206,6 +206,8 @@ void dmub_dcn32_setup_windows(struct dmub_srv *dmub,void dmub_dcn32_setup_mailbox (struct dmub_srv *dmub,const struct dmub_region *inbox1); +uint32_t dmub_dcn32_get_inbox1_wptr (struct dmub_srv *dmub); +uint32_t dmub_dcn32_get_inbox1_rptr (struct dmub_srv *dmub);void dmub_dcn32_set_inbox1_wptr (struct dmub_srv *dmub,uint32_t wptr_offset);
drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c +17 -0
@@ -167,6 +167,7 @@ static bool dmub_srv_hw_setup(struct dmub_srv *dmub, enum dmub_asic asic) funcs->backdoor_load = dmub_dcn20_backdoor_load; funcs->setup_windows = dmub_dcn20_setup_windows; funcs->setup_mailbox = dmub_dcn20_setup_mailbox; + funcs->get_inbox1_wptr = dmub_dcn20_get_inbox1_wptr; funcs->get_inbox1_rptr = dmub_dcn20_get_inbox1_rptr; funcs->set_inbox1_wptr = dmub_dcn20_set_inbox1_wptr; funcs->is_supported = dmub_dcn20_is_supported;
@@ -243,6 +244,7 @@ static bool dmub_srv_hw_setup(struct dmub_srv *dmub, enum dmub_asic asic) funcs->backdoor_load = dmub_dcn31_backdoor_load; funcs->setup_windows = dmub_dcn31_setup_windows; funcs->setup_mailbox = dmub_dcn31_setup_mailbox; + funcs->get_inbox1_wptr = dmub_dcn31_get_inbox1_wptr; funcs->get_inbox1_rptr = dmub_dcn31_get_inbox1_rptr; funcs->set_inbox1_wptr = dmub_dcn31_set_inbox1_wptr; funcs->setup_out_mailbox = dmub_dcn31_setup_out_mailbox;
@@ -281,6 +283,7 @@ static bool dmub_srv_hw_setup(struct dmub_srv *dmub, enum dmub_asic asic) funcs->backdoor_load_zfb_mode = dmub_dcn32_backdoor_load_zfb_mode; funcs->setup_windows = dmub_dcn32_setup_windows; funcs->setup_mailbox = dmub_dcn32_setup_mailbox; + funcs->get_inbox1_wptr = dmub_dcn32_get_inbox1_wptr; funcs->get_inbox1_rptr = dmub_dcn32_get_inbox1_rptr; funcs->set_inbox1_wptr = dmub_dcn32_set_inbox1_wptr; funcs->setup_out_mailbox = dmub_dcn32_setup_out_mailbox;
@@ -666,6 +669,20 @@ enum dmub_status dmub_srv_hw_init(struct dmub_srv *dmub,return DMUB_STATUS_OK ; } +enum dmub_status dmub_srv_sync_inbox1 (struct dmub_srv *dmub) +{ +if (!dmub->sw_init) +return DMUB_STATUS_INVALID ; + +if (dmub->hw_funcs.get_inbox1_rptr && dmub->hw_funcs.get_inbox1_wptr) { + dmub->inbox1_rb.rptr = dmub->hw_funcs.get_inbox1_rptr (dmub); + dmub->inbox1_rb.wrpt = dmub->hw_funcs.get_inbox1_wptr (dmub); + dmub->inbox1_last_wptr = dmub->inbox1_rb.wrpt; + } + +return DMUB_STATUS_OK ; +} +enum dmub_status dmub_srv_hw_reset (struct dmub_srv *dmub) {if (!dmub->sw_init)
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 87/107 drm/amd/display: Guard against invalid RPTR/WPTR being set
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Kazlauskas <[email protected]>
[ Upstream commit 1ffa8602e39b89469dc703ebab7a7e44c33da0f7 ]
[WHY]
HW can return invalid values on register read, guard against these being set and causing us to access memory out of range and page fault.
[HOW]
Guard at sync_inbox1 and guard at pushing commands.
--- .../gpu/drm/amd/display/dmub/src/dmub_srv.c | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/display/dmub/src/dmub_srv.c +15 -3
@@ -675,9 +675,16 @@ enum dmub_status dmub_srv_sync_inbox1(struct dmub_srv *dmub)return DMUB_STATUS_INVALID ;if (dmub->hw_funcs.get_inbox1_rptr && dmub->hw_funcs.get_inbox1_wptr) { - dmub->inbox1_rb.rptr = dmub->hw_funcs.get_inbox1_rptr (dmub); - dmub->inbox1_rb.wrpt = dmub->hw_funcs.get_inbox1_wptr (dmub); - dmub->inbox1_last_wptr = dmub->inbox1_rb.wrpt; +uint32_t rptr = dmub->hw_funcs.get_inbox1_rptr (dmub); +uint32_t wptr = dmub->hw_funcs.get_inbox1_wptr (dmub); + +if (rptr > dmub->inbox1_rb.capacity || wptr > dmub->inbox1_rb.capacity) { +return DMUB_STATUS_HW_FAILURE ; + }else { + dmub->inbox1_rb.rptr = rptr; + dmub->inbox1_rb.wrpt = wptr; + dmub->inbox1_last_wptr = dmub->inbox1_rb.wrpt; + } }return DMUB_STATUS_OK ;
@@ -711,6 +718,11 @@ enum dmub_status dmub_srv_cmd_queue(struct dmub_srv *dmub,if (!dmub->hw_init)return DMUB_STATUS_INVALID ; +if (dmub->inbox1_rb.rptr > dmub->inbox1_rb.capacity || + dmub->inbox1_rb.wrpt > dmub->inbox1_rb.capacity) { +return DMUB_STATUS_HW_FAILURE ; + } +if (dmub_rb_push_front (&dmub->inbox1_rb, cmd))return DMUB_STATUS_OK ;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 88/107 cpufreq: imx6q: dont warn for disabling a non-existing frequency
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Niedermaier <[email protected]>
[ Upstream commit 11a3b0ac33d95aa84be426e801f800997262a225 ]
It is confusing if a warning is given for disabling a non-existent frequency of the operating performance points (OPP). In this case the function dev_pm_opp_disable() returns -ENODEV. Check the return value and avoid the output of a warning in this case. Avoid code duplication by using a separate function.
Stable-dep-of: 2e4e0984c7d6 ("cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily")
--- drivers/cpufreq/imx6q-cpufreq.c | 30 ++++++++++++++++-------------- 1 file changed, 16 insertions(+), 14 deletions(-)
drivers/cpufreq/imx6q-cpufreq.c +16 -14
@@ -209,6 +209,14 @@ static struct cpufreq_driver imx6q_cpufreq_driver = { .suspend = cpufreq_generic_suspend, }; +static void imx6x_disable_freq_in_opp (struct device *dev,unsigned long freq) +{ +int ret =dev_pm_opp_disable (dev, freq); + +if (ret <0 && ret != -ENODEV ) +dev_warn (dev,"failed to disable %ldMHz OPP\n" , freq /1000000 ); +} +#define OCOTP_CFG3 0x440#define OCOTP_CFG3_SPEED_SHIFT 16#define OCOTP_CFG3_SPEED_1P2GHZ 0x3
@@ -254,17 +262,15 @@ static int imx6q_opp_check_speed_grading(struct device *dev) val &=0x3 ;if (val <OCOTP_CFG3_SPEED_996MHZ ) -if (dev_pm_opp_disable (dev,996000000 )) -dev_warn (dev,"failed to disable 996MHz OPP\n" ); +imx6x_disable_freq_in_opp (dev,996000000 );if (of_machine_is_compatible ("fsl,imx6q" ) ||of_machine_is_compatible ("fsl,imx6qp" )) {if (val !=OCOTP_CFG3_SPEED_852MHZ ) -if (dev_pm_opp_disable (dev,852000000 )) -dev_warn (dev,"failed to disable 852MHz OPP\n" ); +imx6x_disable_freq_in_opp (dev,852000000 ); +if (val !=OCOTP_CFG3_SPEED_1P2GHZ ) -if (dev_pm_opp_disable (dev,1200000000 )) -dev_warn (dev,"failed to disable 1.2GHz OPP\n" ); +imx6x_disable_freq_in_opp (dev,1200000000 ); }return 0 ;
@@ -316,20 +322,16 @@ static int imx6ul_opp_check_speed_grading(struct device *dev) val >>=OCOTP_CFG3_SPEED_SHIFT ; val &=0x3 ; -if (of_machine_is_compatible ("fsl,imx6ul" )) { +if (of_machine_is_compatible ("fsl,imx6ul" ))if (val !=OCOTP_CFG3_6UL_SPEED_696MHZ ) -if (dev_pm_opp_disable (dev,696000000 )) -dev_warn (dev,"failed to disable 696MHz OPP\n" ); - } +imx6x_disable_freq_in_opp (dev,696000000 );if (of_machine_is_compatible ("fsl,imx6ull" )) {if (val !=OCOTP_CFG3_6ULL_SPEED_792MHZ ) -if (dev_pm_opp_disable (dev,792000000 )) -dev_warn (dev,"failed to disable 792MHz OPP\n" ); +imx6x_disable_freq_in_opp (dev,792000000 );if (val !=OCOTP_CFG3_6ULL_SPEED_900MHZ ) -if (dev_pm_opp_disable (dev,900000000 )) -dev_warn (dev,"failed to disable 900MHz OPP\n" ); +imx6x_disable_freq_in_opp (dev,900000000 ); }return ret;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 89/107 cpufreq: imx6q: Dont disable 792 Mhz OPP unnecessarily
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Niedermaier <[email protected]>
[ Upstream commit 2e4e0984c7d696cc74cf2fd7e7f62997f0e9ebe6 ]
For a 900MHz i.MX6ULL CPU the 792MHz OPP is disabled. There is no convincing reason to disable this OPP. If a CPU can run at 900MHz, it should also be able to cope with 792MHz. Looking at the voltage level of 792MHz in [1] (page 24, table 10. "Operating Ranges") the current defined OPP is above the minimum. So the voltage level shouldn't be a problem. However in [2] (page 24, table 10. "Operating Ranges"), it is not mentioned that 792MHz OPP isn't allowed. Change it to only disable 792MHz OPP for i.MX6ULL types below 792 MHz.
[1] https://www.nxp.com/docs/en/data-sheet/IMX6ULLIEC.pdf
[2] https://www.nxp.com/docs/en/data-sheet/IMX6ULLCEC.pdf
--- drivers/cpufreq/imx6q-cpufreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/cpufreq/imx6q-cpufreq.c +1 -1
@@ -327,7 +327,7 @@ static int imx6ul_opp_check_speed_grading(struct device *dev)imx6x_disable_freq_in_opp (dev,696000000 );if (of_machine_is_compatible ("fsl,imx6ull" )) { -if (val !=OCOTP_CFG3_6ULL_SPEED_792MHZ ) +if (val <OCOTP_CFG3_6ULL_SPEED_792MHZ )imx6x_disable_freq_in_opp (dev,792000000 );if (val !=OCOTP_CFG3_6ULL_SPEED_900MHZ )
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 90/107 iommu/vt-d: Omit devTLB invalidation requests when TES=0
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lu Baolu <[email protected]>
[ Upstream commit 0f5432a9b839847dcfe9fa369d72e3d646102ddf ]
The latest VT-d spec indicates that when remapping hardware is disabled (TES=0 in Global Status Register), upstream ATS Invalidation Completion requests are treated as UR (Unsupported Request).
Consequently, the spec recommends in section 4.3 Handling of Device-TLB Invalidations that software refrain from submitting any Device-TLB invalidation requests when address remapping hardware is disabled.
Verify address remapping hardware is enabled prior to submitting Device- TLB invalidation requests.
--- drivers/iommu/intel/dmar.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
drivers/iommu/intel/dmar.c +18 -0
@@ -1495,6 +1495,15 @@ void qi_flush_dev_iotlb(struct intel_iommu *iommu, u16 sid, u16 pfsid, {struct qi_desc desc; +/* +* VT-d spec, section 4.3: +* +* Software is recommended to not submit any Device-TLB invalidation +* requests while address remapping hardware is disabled. +*/ +if (!(iommu->gcmd &DMA_GCMD_TE )) +return ; +if (mask) { addr |= (1ULL << (VTD_PAGE_SHIFT + mask -1 )) -1 ; desc.qw1 =QI_DEV_IOTLB_ADDR (addr) |QI_DEV_IOTLB_SIZE ;
@@ -1560,6 +1569,15 @@ void qi_flush_dev_iotlb_pasid(struct intel_iommu *iommu, u16 sid, u16 pfsid,unsigned long mask =1UL << (VTD_PAGE_SHIFT + size_order -1 );struct qi_desc desc = {.qw1 =0 , .qw2 =0 , .qw3 =0 }; +/* +* VT-d spec, section 4.3: +* +* Software is recommended to not submit any Device-TLB invalidation +* requests while address remapping hardware is disabled. +*/ +if (!(iommu->gcmd &DMA_GCMD_TE )) +return ; + desc.qw0 =QI_DEV_EIOTLB_PASID (pasid) |QI_DEV_EIOTLB_SID (sid) |QI_DEV_EIOTLB_QDEP (qdep) |QI_DEIOTLB_TYPE |QI_DEV_IOTLB_PFSID (pfsid);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 91/107 iommu/vt-d: Allocate pasid table in device probe path
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lu Baolu <[email protected]>
[ Upstream commit ec62b4424174f41bdcedd08d12d7bed80088453d ]
Whether or not a domain is attached to the device, the pasid table should always be valid as long as it has been probed. This moves the pasid table allocation from the domain attaching device path to device probe path and frees it in the device release path.
Stable-dep-of: da37dddcf4ca ("iommu/vt-d: Disable PCI ATS in legacy passthrough mode")
--- drivers/iommu/intel/iommu.c | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-)
drivers/iommu/intel/iommu.c +12 -8
@@ -2494,13 +2494,6 @@ static int domain_add_dev_info(struct dmar_domain *domain, struct device *dev)/* PASID table is mandatory for a PCI device in scalable mode. */ if (sm_supported (iommu) && !dev_is_real_dma_subdevice (dev)) { - ret =intel_pasid_alloc_table (dev); -if (ret) { -dev_err (dev,"PASID table allocation failed\n" ); -dmar_remove_one_dev_info (dev); -return ret; - } -/* Setup the PASID entry for requests without PASID: */ if (hw_pass_through &&domain_type_is_si (domain)) ret = intel_pasid_setup_pass_through(iommu, domain,
@@ -4112,7 +4105,6 @@ static void dmar_remove_one_dev_info(struct device *dev)iommu_disable_dev_iotlb (info);domain_context_clear (info); -intel_pasid_free_table (info->dev); }spin_lock_irqsave (&domain->lock, flags);
@@ -4477,6 +4469,7 @@ static struct iommu_device *intel_iommu_probe_device(struct device *dev)struct device_domain_info *info;struct intel_iommu *iommu;u8 bus, devfn; +int ret; iommu =device_to_iommu (dev, &bus, &devfn);if (!iommu || !iommu->iommu.ops)
@@ -4521,6 +4514,16 @@ static struct iommu_device *intel_iommu_probe_device(struct device *dev)dev_iommu_priv_set (dev, info); +if (sm_supported (iommu) && !dev_is_real_dma_subdevice (dev)) { + ret =intel_pasid_alloc_table (dev); +if (ret) { +dev_err (dev,"PASID table allocation failed\n" ); +dev_iommu_priv_set (dev,NULL ); +kfree (info); +return ERR_PTR (ret); + } + } +return &iommu->iommu; }
@@ -4529,6 +4532,7 @@ static void intel_iommu_release_device(struct device *dev)struct device_domain_info *info =dev_iommu_priv_get (dev);dmar_remove_one_dev_info (dev); +intel_pasid_free_table (dev);dev_iommu_priv_set (dev,NULL );kfree (info);set_dma_ops (dev,NULL );
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 92/107 iommu/vt-d: Add device_block_translation() helper
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lu Baolu <[email protected]>
[ Upstream commit c7be17c2903d4acbf9aa372bfb6e2a418387fce0 ]
If domain attaching to device fails, the IOMMU driver should bring the device to blocking DMA state. The upper layer is expected to recover it by attaching a new domain. Use device_block_translation() in the error path of dev_attach to make the behavior specific.
The difference between device_block_translation() and the previous dmar_remove_one_dev_info() is that, in the scalable mode, it is the RID2PASID entry instead of context entry being cleared. As a result, enabling PCI capabilities is moved up.
Stable-dep-of: da37dddcf4ca ("iommu/vt-d: Disable PCI ATS in legacy passthrough mode")
--- drivers/iommu/intel/iommu.c | 44 ++++++++++++++++++++++++++++++++----- 1 file changed, 38 insertions(+), 6 deletions(-)
drivers/iommu/intel/iommu.c +38 -6
@@ -277,7 +277,7 @@ static LIST_HEAD(dmar_satc_units);#define for_each_rmrr_units (rmrr) \ list_for_each_entry(rmrr, &dmar_rmrr_units, list) -static void dmar_remove_one_dev_info (struct device *dev); +static void device_block_translation (struct device *dev);int dmar_disabled = !IS_ENABLED (CONFIG_INTEL_IOMMU_DEFAULT_ON );int intel_iommu_sm =IS_ENABLED (CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON );
@@ -1418,7 +1418,7 @@ static void iommu_enable_pci_caps(struct device_domain_info *info) {struct pci_dev *pdev; -if (!info || !dev_is_pci (info->dev)) +if (!dev_is_pci (info->dev))return ; pdev =to_pci_dev (info->dev);
@@ -2064,7 +2064,6 @@ static int domain_context_mapping_one(struct dmar_domain *domain, }else {iommu_flush_write_buffer (iommu); } -iommu_enable_pci_caps (info); ret =0 ;
@@ -2506,7 +2505,7 @@ static int domain_add_dev_info(struct dmar_domain *domain, struct device *dev) dev, PASID_RID2PASID);if (ret) {dev_err (dev,"Setup RID2PASID failed\n" ); -dmar_remove_one_dev_info (dev); +device_block_translation (dev);return ret; } }
@@ -2514,10 +2513,12 @@ static int domain_add_dev_info(struct dmar_domain *domain, struct device *dev) ret =domain_context_mapping (domain, dev);if (ret) {dev_err (dev,"Domain context map failed\n" ); -dmar_remove_one_dev_info (dev); +device_block_translation (dev);return ret; } +iommu_enable_pci_caps (info); +return 0 ; }
@@ -4115,6 +4116,37 @@ static void dmar_remove_one_dev_info(struct device *dev) info->domain =NULL ; } +/* +* Clear the page table pointer in context or pasid table entries so that +* all DMA requests without PASID from the device are blocked. If the page +* table has been set, clean up the data structures. +*/ +static void device_block_translation (struct device *dev) +{ +struct device_domain_info *info =dev_iommu_priv_get (dev); +struct intel_iommu *iommu = info->iommu; +unsigned long flags; + +iommu_disable_dev_iotlb (info); +if (!dev_is_real_dma_subdevice (dev)) { +if (sm_supported (iommu)) +intel_pasid_tear_down_entry (iommu, dev, +PASID_RID2PASID , false); +else +domain_context_clear (info); + } + +if (!info->domain) +return ; + +spin_lock_irqsave (&info->domain->lock, flags); +list_del (&info->link); +spin_unlock_irqrestore (&info->domain->lock, flags); + +domain_detach_iommu (info->domain, iommu); + info->domain =NULL ; +} +static int md_domain_init (struct dmar_domain *domain,int guest_width) {int adjust_width;
@@ -4238,7 +4270,7 @@ static int intel_iommu_attach_device(struct iommu_domain *domain,struct device_domain_info *info =dev_iommu_priv_get (dev);if (info->domain) -dmar_remove_one_dev_info (dev); +device_block_translation (dev); } ret =prepare_domain_attach_device (domain, dev);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 93/107 iommu/vt-d: Disable PCI ATS in legacy passthrough mode
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lu Baolu <[email protected]>
[ Upstream commit da37dddcf4caf015c400a930301d2ee27a7a15fb ]
When IOMMU hardware operates in legacy mode, the TT field of the context entry determines the translation type, with three supported types (Section 9.3 Context Entry):
- DMA translation without device TLB support
- DMA translation with device TLB support
- Passthrough mode with translated and translation requests blocked
Device TLB support is absent when hardware is configured in passthrough mode.
Disable the PCI ATS feature when IOMMU is configured for passthrough translation type in legacy (non-scalable) mode.
--- drivers/iommu/intel/iommu.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/iommu/intel/iommu.c +2 -1
@@ -2517,7 +2517,8 @@ static int domain_add_dev_info(struct dmar_domain *domain, struct device *dev)return ret; } -iommu_enable_pci_caps (info); +if (sm_supported (info->iommu) || !domain_type_is_si (info->domain)) +iommu_enable_pci_caps (info);return 0 ; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 94/107 iommu/vt-d: Make context clearing consistent with context mapping
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lu Baolu <[email protected]>
[ Upstream commit 9a16ab9d640274b20813d2d17475e18d3e99d834 ]
In the iommu probe_device path, domain_context_mapping() allows setting up the context entry for a non-PCI device. However, in the iommu release_device path, domain_context_clear() only clears context entries for PCI devices.
Make domain_context_clear() behave consistently with domain_context_mapping() by clearing context entries for both PCI and non-PCI devices.
--- drivers/iommu/intel/iommu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/iommu/intel/iommu.c +2 -2
@@ -4086,8 +4086,8 @@ static int domain_context_clear_one_cb(struct pci_dev *pdev, u16 alias, void *op*/ static void domain_context_clear (struct device_domain_info *info) { -if (!info->iommu || !info->dev || !dev_is_pci (info->dev)) -return ; +if (!dev_is_pci (info->dev)) +domain_context_clear_one (info, info->bus, info->devfn);pci_for_each_dma_alias (to_pci_dev (info->dev), &domain_context_clear_one_cb, info);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 95/107 drm/amd/pm: fix a memleak in aldebaran_tables_init
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dinghao Liu <[email protected]>
[ Upstream commit 7a88f23e768491bae653b444a96091d2aaeb0818 ]
When kzalloc() for smu_table->ecc_table fails, we should free the previously allocated resources to prevent memleak.
--- drivers/gpu/drm/amd/pm/swsmu/smu13/aldebaran_ppt.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/gpu/drm/amd/pm/swsmu/smu13/aldebaran_ppt.c +4 -1
@@ -258,8 +258,11 @@ static int aldebaran_tables_init(struct smu_context *smu) } smu_table->ecc_table =kzalloc (tables[SMU_TABLE_ECCINFO ].size,GFP_KERNEL ); -if (!smu_table->ecc_table) +if (!smu_table->ecc_table) { +kfree (smu_table->metrics_table); +kfree (smu_table->gpu_metrics_table);return -ENOMEM ; + }return 0 ; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 96/107 mmc: core: add helpers mmc_regulator_enable/disable_vqmmc
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Heiner Kallweit <[email protected]>
[ Upstream commit 8d91f3f8ae57e6292142ca89f322e90fa0d6ac02 ]
There's a number of drivers (e.g. dw_mmc, meson-gx, mmci, sunxi) using the same mechanism and a private flag vqmmc_enabled to deal with enabling/disabling the vqmmc regulator.
Move this to the core and create new helpers mmc_regulator_enable_vqmmc and mmc_regulator_disable_vqmmc.
Stable-dep-of: 477865af60b2 ("mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled")
--- drivers/mmc/core/regulator.c | 41 ++++++++++++++++++++++++++++++++++++ include/linux/mmc/host.h | 3 +++ 2 files changed, 44 insertions(+)
drivers/mmc/core/regulator.c +41 -0
@@ -271,3 +271,44 @@ int mmc_regulator_get_supply(struct mmc_host *mmc)return 0 ; }EXPORT_SYMBOL_GPL (mmc_regulator_get_supply); + +/** +* mmc_regulator_enable_vqmmc - enable VQMMC regulator for a host +* @mmc: the host to regulate +* +* Returns 0 or errno. Enables the regulator for vqmmc. +* Keeps track of the enable status for ensuring that calls to +* regulator_enable/disable are balanced. +*/ +int mmc_regulator_enable_vqmmc (struct mmc_host *mmc) +{ +int ret =0 ; + +if (!IS_ERR (mmc->supply.vqmmc) && !mmc->vqmmc_enabled) { + ret =regulator_enable (mmc->supply.vqmmc); +if (ret <0 ) +dev_err (mmc_dev (mmc),"enabling vqmmc regulator failed\n" ); +else + mmc->vqmmc_enabled = true; + } + +return ret; +} +EXPORT_SYMBOL_GPL (mmc_regulator_enable_vqmmc); + +/** +* mmc_regulator_disable_vqmmc - disable VQMMC regulator for a host +* @mmc: the host to regulate +* +* Returns 0 or errno. Disables the regulator for vqmmc. +* Keeps track of the enable status for ensuring that calls to +* regulator_enable/disable are balanced. +*/ +void mmc_regulator_disable_vqmmc (struct mmc_host *mmc) +{ +if (!IS_ERR (mmc->supply.vqmmc) && mmc->vqmmc_enabled) { +regulator_disable (mmc->supply.vqmmc); + mmc->vqmmc_enabled = false; + } +} +EXPORT_SYMBOL_GPL (mmc_regulator_disable_vqmmc);
include/linux/mmc/host.h +3 -0
@@ -450,6 +450,7 @@ struct mmc_host { unsigned int retune_paused:1; /* re-tuning is temporarily disabled */ unsigned int retune_crc_disable:1; /* don't trigger retune upon crc */ unsigned int can_dma_map_merge:1; /* merging can be used */ + unsigned int vqmmc_enabled:1; /* vqmmc regulator is enabled */int rescan_disable;/* disable card detection */ int rescan_entered;/* used with nonremovable devices */
@@ -597,6 +598,8 @@ static inline int mmc_regulator_set_vqmmc(struct mmc_host *mmc,#endif int mmc_regulator_get_supply (struct mmc_host *mmc); +int mmc_regulator_enable_vqmmc (struct mmc_host *mmc); +void mmc_regulator_disable_vqmmc (struct mmc_host *mmc);static inline int mmc_card_is_removable (struct mmc_host *host) {
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 97/107 mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wenchao Chen <[email protected]>
[ Upstream commit 477865af60b2117ceaa1d558e03559108c15c78c ]
With cat regulator_summary, we found that vqmmc was not shutting down after the card was pulled.
cat /sys/kernel/debug/regulator/regulator_summary
1.before fix
1)Insert SD card
vddsdio 1 1 0 unknown 3500mV 0mA 1200mV 3750mV
71100000.mmc-vqmmc 1 0mA 3500mV 3600mV
2)Pull out the SD card
vddsdio 1 1 0 unknown 3500mV 0mA 1200mV 3750mV
71100000.mmc-vqmmc 1 0mA 3500mV 3600mV2.after fix
1)Insert SD cardt
vddsdio 1 1 0 unknown 3500mV 0mA 1200mV 3750mV
71100000.mmc-vqmmc 1 0mA 3500mV 3600mV2)Pull out the SD card
vddsdio 0 1 0 unknown 3500mV 0mA 1200mV 3750mV
71100000.mmc-vqmmc 0 0mA 3500mV 3600mV
--- drivers/mmc/host/sdhci-sprd.c | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+)
drivers/mmc/host/sdhci-sprd.c +25 -0
@@ -405,12 +405,33 @@ static void sdhci_sprd_request_done(struct sdhci_host *host,mmc_request_done (host->mmc, mrq); } +static void sdhci_sprd_set_power (struct sdhci_host *host,unsigned char mode, +unsigned short vdd) +{ +struct mmc_host *mmc = host->mmc; + +switch (mode) { +case MMC_POWER_OFF : +mmc_regulator_set_ocr (host->mmc, mmc->supply.vmmc,0 ); + +mmc_regulator_disable_vqmmc (mmc); +break ; +case MMC_POWER_ON : +mmc_regulator_enable_vqmmc (mmc); +break ; +case MMC_POWER_UP : +mmc_regulator_set_ocr (host->mmc, mmc->supply.vmmc, vdd); +break ; + } +} +static struct sdhci_ops sdhci_sprd_ops = { .read_l = sdhci_sprd_readl, .write_l = sdhci_sprd_writel, .write_w = sdhci_sprd_writew, .write_b = sdhci_sprd_writeb, .set_clock = sdhci_sprd_set_clock, + .set_power = sdhci_sprd_set_power, .get_max_clock = sdhci_sprd_get_max_clock, .get_min_clock = sdhci_sprd_get_min_clock, .set_bus_width = sdhci_set_bus_width,
@@ -676,6 +697,10 @@ static int sdhci_sprd_probe(struct platform_device *pdev) host->caps1 &= ~(SDHCI_SUPPORT_SDR50 |SDHCI_SUPPORT_SDR104 |SDHCI_SUPPORT_DDR50 ); + ret =mmc_regulator_get_supply (host->mmc); +if (ret) + goto pm_runtime_disable; + ret =sdhci_setup_host (host);if (ret) goto pm_runtime_disable;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 98/107 drm/amd/display: Expand kernel doc for DC
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rodrigo Siqueira <[email protected]>
[ Upstream commit 1682bd1a6b5fb094e914d9b73b711821fd84dcbd ]
This commit adds extra documentation for elements related to FAMs.
Stable-dep-of: 67e38874b85b ("drm/amd/display: Increase num voltage states to 40")
--- drivers/gpu/drm/amd/display/dc/dc.h | 19 +++++++++++--- drivers/gpu/drm/amd/display/dc/dc_stream.h | 11 ++++++++ .../gpu/drm/amd/display/dc/dml/dc_features.h | 7 ++++++ .../amd/display/dc/dml/display_mode_enums.h | 25 +++++++++++++++++++ .../drm/amd/display/dc/dml/display_mode_vba.h | 9 +++++++ .../gpu/drm/amd/display/dc/inc/core_types.h | 7 ++++++ .../gpu/drm/amd/display/dc/inc/hw/hw_shared.h | 7 ++++++ 7 files changed, 82 insertions(+), 3 deletions(-)
drivers/gpu/drm/amd/display/dc/dc.h +16 -3
@@ -499,9 +499,12 @@ enum dcn_zstate_support_state { DCN_ZSTATE_SUPPORT_ALLOW_Z10_ONLY, DCN_ZSTATE_SUPPORT_DISALLOW, }; -/* -* For any clocks that may differ per pipe -* only the max is stored in this structure + +/** +* dc_clocks - DC pipe clocks +* +* For any clocks that may differ per pipe only the max is stored in this +* structure */ struct dc_clocks {int dispclk_khz;
@@ -528,6 +531,16 @@ struct dc_clocks {bool prev_p_state_change_support;bool fclk_prev_p_state_change_support;int num_ways; + +/** +* @fw_based_mclk_switching +* +* DC has a mechanism that leverage the variable refresh rate to switch +* memory clock in cases that we have a large latency to achieve the +* memory clock change and a short vblank window. DC has some +* requirements to enable this feature, and this field describes if the +* system support or not such a feature. +*/ bool fw_based_mclk_switching;bool fw_based_mclk_switching_shut_down;int prev_num_ways;
drivers/gpu/drm/amd/display/dc/dc_stream.h +11 -0
@@ -202,7 +202,18 @@ struct dc_stream_state {bool use_vsc_sdp_for_colorimetry;bool ignore_msa_timing_param; +/** +* @allow_freesync: +* +* It say if Freesync is enabled or not. +*/ bool allow_freesync; + +/** +* @vrr_active_variable: +* +* It describes if VRR is in use. +*/ bool vrr_active_variable;bool freesync_on_desktop;
drivers/gpu/drm/amd/display/dc/dml/dc_features.h +7 -0
@@ -29,6 +29,13 @@#define DC__PRESENT 1#define DC__PRESENT__1 1#define DC__NUM_DPP 4 + +/** +* @DC__VOLTAGE_STATES: +* +* Define the maximum amount of states supported by the ASIC. Every ASIC has a +* specific number of states; this macro defines the maximum number of states. +*/ #define DC__VOLTAGE_STATES 20#define DC__NUM_DPP__4 1#define DC__NUM_DPP__0_PRESENT 1
drivers/gpu/drm/amd/display/dc/dml/display_mode_enums.h +25 -0
@@ -105,14 +105,39 @@ enum source_macro_tile_size {enum cursor_bpp { dm_cur_2bit =0 , dm_cur_32bit =1 , dm_cur_64bit =2 }; + +/** +* @enum clock_change_support - It represents possible reasons to change the DRAM clock. +* +* DC may change the DRAM clock during its execution, and this enum tracks all +* the available methods. Note that every ASIC has their specific way to deal +* with these clock switch. +*/ enum clock_change_support { +/** +* @dm_dram_clock_change_uninitialized: If you see this, we might have +* a code initialization issue +*/ dm_dram_clock_change_uninitialized =0 , + +/** +* @dm_dram_clock_change_vactive: Support DRAM switch in VActive +*/ dm_dram_clock_change_vactive, + +/** +* @dm_dram_clock_change_vblank: Support DRAM switch in VBlank +*/ dm_dram_clock_change_vblank, + dm_dram_clock_change_vactive_w_mall_full_frame, dm_dram_clock_change_vactive_w_mall_sub_vp, dm_dram_clock_change_vblank_w_mall_full_frame, dm_dram_clock_change_vblank_w_mall_sub_vp, + +/** +* @dm_dram_clock_change_unsupported: Do not support DRAM switch +*/ dm_dram_clock_change_unsupported };
drivers/gpu/drm/amd/display/dc/dml/display_mode_vba.h +9 -0
@@ -419,6 +419,15 @@ struct vba_vars_st {double MinPixelChunkSizeBytes;unsigned int DCCMetaBufferSizeBytes;// Pipe/Plane Parameters + +/** @VoltageLevel: +* Every ASIC has a fixed number of DPM states, and some devices might +* have some particular voltage configuration that does not map +* directly to the DPM states. This field tells how many states the +* target device supports; even though this field combines the DPM and +* special SOC voltages, it mostly matches the total number of DPM +* states. +*/ int VoltageLevel;double FabricClock;double DRAMSpeed;
drivers/gpu/drm/amd/display/dc/inc/core_types.h +7 -0
@@ -115,6 +115,13 @@ struct resource_funcs { int vlevel);void (*update_soc_for_wm_a)(struct dc *dc,struct dc_state *context); + +/** +* @populate_dml_pipes - Populate pipe data struct +* +* Returns: +* Total of pipes available in the specific ASIC. +*/ int (*populate_dml_pipes)( struct dc *dc, struct dc_state *context,
drivers/gpu/drm/amd/display/dc/inc/hw/hw_shared.h +7 -0
@@ -35,6 +35,13 @@******************************************************************************/ #define MAX_AUDIOS 7 + +/** +* @MAX_PIPES: +* +* Every ASIC support a fixed number of pipes; MAX_PIPES defines a large number +* to be used inside loops and for determining array sizes. +*/ #define MAX_PIPES 6#define MAX_DIG_LINK_ENCODERS 7#define MAX_DWB_PIPES 1
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 99/107 drm/amd/display: clean code-style issues in dcn30_set_mpc_shaper_3dlut
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Melissa Wen <[email protected]>
[ Upstream commit 94369589e4ec13c762fe10a1fdc4463bdfee5d5f ]
This function has many conditions and all code style issues (identation, missing braces, etc.) make reading it really annoying.
Stable-dep-of: 6f395cebdd89 ("drm/amd/display: Fix MPCC 1DLUT programming")
--- .../drm/amd/display/dc/dcn30/dcn30_hwseq.c | 37 ++++++++++--------- 1 file changed, 19 insertions(+), 18 deletions(-)
drivers/gpu/drm/amd/display/dc/dcn30/dcn30_hwseq.c +19 -18
@@ -91,8 +91,8 @@ bool dcn30_set_blend_lut(return result; } -static bool dcn30_set_mpc_shaper_3dlut ( -struct pipe_ctx *pipe_ctx,const struct dc_stream_state *stream) +static bool dcn30_set_mpc_shaper_3dlut (struct pipe_ctx *pipe_ctx, +const struct dc_stream_state *stream) {struct dpp *dpp_base = pipe_ctx->plane_res.dpp;int mpcc_id = pipe_ctx->plane_res.hubp->inst;
@@ -104,19 +104,18 @@ static bool dcn30_set_mpc_shaper_3dlut(const struct pwl_params *shaper_lut =NULL ;//get the shaper lut params if (stream->func_shaper) { -if (stream->func_shaper->type ==TF_TYPE_HWPWL ) +if (stream->func_shaper->type ==TF_TYPE_HWPWL ) { shaper_lut = &stream->func_shaper->pwl; -else if (stream->func_shaper->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format ( - stream->func_shaper, - &dpp_base->shaper_params, true); + }else if (stream->func_shaper->type ==TF_TYPE_DISTRIBUTED_POINTS ) { +cm_helper_translate_curve_to_hw_format (stream->func_shaper, + &dpp_base->shaper_params, true); shaper_lut = &dpp_base->shaper_params; } }if (stream->lut3d_func && - stream->lut3d_func->state.bits.initialized ==1 && - stream->lut3d_func->state.bits.rmu_idx_valid ==1 ) { + stream->lut3d_func->state.bits.initialized ==1 && + stream->lut3d_func->state.bits.rmu_idx_valid ==1 ) {if (stream->lut3d_func->state.bits.rmu_mux_num ==0 ) mpcc_id_projected = stream->lut3d_func->state.bits.mpc_rmu0_mux;else if (stream->lut3d_func->state.bits.rmu_mux_num ==1 )
@@ -125,20 +124,22 @@ static bool dcn30_set_mpc_shaper_3dlut( mpcc_id_projected = stream->lut3d_func->state.bits.mpc_rmu2_mux;if (mpcc_id_projected != mpcc_id)BREAK_TO_DEBUGGER (); -/*find the reason why logical layer assigned a differant mpcc_id into acquire_post_bldn_3dlut*/ +/* find the reason why logical layer assigned a different +* mpcc_id into acquire_post_bldn_3dlut +*/ acquired_rmu = mpc->funcs->acquire_rmu (mpc, mpcc_id, - stream->lut3d_func->state.bits.rmu_mux_num); + stream->lut3d_func->state.bits.rmu_mux_num);if (acquired_rmu != stream->lut3d_func->state.bits.rmu_mux_num)BREAK_TO_DEBUGGER (); - result = mpc->funcs->program_3dlut (mpc, - &stream->lut3d_func->lut_3d, - stream->lut3d_func->state.bits.rmu_mux_num); + + result = mpc->funcs->program_3dlut (mpc, &stream->lut3d_func->lut_3d, + stream->lut3d_func->state.bits.rmu_mux_num); result = mpc->funcs->program_shaper (mpc, shaper_lut, - stream->lut3d_func->state.bits.rmu_mux_num); - }else -/*loop through the available mux and release the requested mpcc_id*/ + stream->lut3d_func->state.bits.rmu_mux_num); + }else { +// loop through the available mux and release the requested mpcc_id mpc->funcs->release_rmu (mpc, mpcc_id); - + }return result; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 100/107 drm/amd/display: Fix the delta clamping for shaper LUT
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Harry Wentland <[email protected]>
[ Upstream commit 27fc10d1095f7a7de7c917638d7134033a190dd8 ]
The shaper LUT requires a 10-bit value of the delta between segments. We were using dc_fixpt_clamp_u0d10() to do that but it doesn't do what we want it to do. It will preserve 10-bit precision after the decimal point, but that's not quite what we want. We want 14-bit precision and discard the 4 most-significant bytes.
To do that we'll do dc_fixpt_clamp_u0d14() & 0x3ff instead.
Stable-dep-of: 6f395cebdd89 ("drm/amd/display: Fix MPCC 1DLUT programming")
--- .../amd/display/dc/dcn10/dcn10_cm_common.c | 19 +++++++++++++++---- .../amd/display/dc/dcn10/dcn10_cm_common.h | 1 + .../amd/display/dc/dcn10/dcn10_hw_sequencer.c | 2 +- .../drm/amd/display/dc/dcn20/dcn20_hwseq.c | 6 +++--- .../drm/amd/display/dc/dcn30/dcn30_dwb_cm.c | 2 +- .../drm/amd/display/dc/dcn30/dcn30_hwseq.c | 2 +- .../drm/amd/display/dc/dcn32/dcn32_hwseq.c | 6 +++--- 7 files changed, 25 insertions(+), 13 deletions(-)
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_cm_common.c +15 -4
@@ -308,7 +308,10 @@ bool cm_helper_convert_to_custom_float(#define NUMBER_REGIONS 32#define NUMBER_SW_SEGMENTS 16 -bool cm_helper_translate_curve_to_hw_format ( +#define DC_LOGGER \ + ctx->logger + +bool cm_helper_translate_curve_to_hw_format (struct dc_context *ctx,const struct dc_transfer_func *output_tf,struct pwl_params *lut_params,bool fixpoint) {
@@ -482,10 +485,18 @@ bool cm_helper_translate_curve_to_hw_format( rgb->delta_green =dc_fixpt_sub (rgb_plus_1->green, rgb->green); rgb->delta_blue =dc_fixpt_sub (rgb_plus_1->blue, rgb->blue); +if (fixpoint == true) { - rgb->delta_red_reg =dc_fixpt_clamp_u0d10 (rgb->delta_red); - rgb->delta_green_reg =dc_fixpt_clamp_u0d10 (rgb->delta_green); - rgb->delta_blue_reg =dc_fixpt_clamp_u0d10 (rgb->delta_blue); +uint32_t red_clamp =dc_fixpt_clamp_u0d14 (rgb->delta_red); +uint32_t green_clamp =dc_fixpt_clamp_u0d14 (rgb->delta_green); +uint32_t blue_clamp =dc_fixpt_clamp_u0d14 (rgb->delta_blue); + +if (red_clamp >>10 || green_clamp >>10 || blue_clamp >>10 ) +DC_LOG_WARNING ("Losing delta precision while programming shaper LUT." ); + + rgb->delta_red_reg = red_clamp &0x3ff ; + rgb->delta_green_reg = green_clamp &0x3ff ; + rgb->delta_blue_reg = blue_clamp &0x3ff ; rgb->red_reg =dc_fixpt_clamp_u0d14 (rgb->red); rgb->green_reg =dc_fixpt_clamp_u0d14 (rgb->green); rgb->blue_reg =dc_fixpt_clamp_u0d14 (rgb->blue);
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_cm_common.h +1 -0
@@ -106,6 +106,7 @@ bool cm_helper_convert_to_custom_float( bool fixpoint);bool cm_helper_translate_curve_to_hw_format ( +struct dc_context *ctx,const struct dc_transfer_func *output_tf,struct pwl_params *lut_params,bool fixpoint);
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hw_sequencer.c +1 -1
@@ -1867,7 +1867,7 @@ bool dcn10_set_output_transfer_func(struct dc *dc, struct pipe_ctx *pipe_ctx,/* dcn10_translate_regamma_to_hw_format takes 750us, only do it when full * update. */ - else if (cm_helper_translate_curve_to_hw_format( + else if (cm_helper_translate_curve_to_hw_format(dc->ctx, stream->out_transfer_func, &dpp->regamma_params, false)) { dpp->funcs->dpp_program_regamma_pwl(
drivers/gpu/drm/amd/display/dc/dcn20/dcn20_hwseq.c +3 -3
@@ -843,7 +843,7 @@ bool dcn20_set_output_transfer_func(struct dc *dc, struct pipe_ctx *pipe_ctx, params = &stream->out_transfer_func->pwl; else if (pipe_ctx->stream->out_transfer_func->type == TF_TYPE_DISTRIBUTED_POINTS && -cm_helper_translate_curve_to_hw_format ( + cm_helper_translate_curve_to_hw_format(dc->ctx, stream->out_transfer_func, &mpc->blender_params, false)) params = &mpc->blender_params;
@@ -872,7 +872,7 @@ bool dcn20_set_blend_lut(if (plane_state->blend_tf->type ==TF_TYPE_HWPWL ) blend_lut = &plane_state->blend_tf->pwl;else if (plane_state->blend_tf->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format ( +cm_helper_translate_curve_to_hw_format (plane_state->ctx, plane_state->blend_tf, &dpp_base->regamma_params, false); blend_lut = &dpp_base->regamma_params;
@@ -894,7 +894,7 @@ bool dcn20_set_shaper_3dlut(if (plane_state->in_shaper_func->type ==TF_TYPE_HWPWL ) shaper_lut = &plane_state->in_shaper_func->pwl;else if (plane_state->in_shaper_func->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format ( +cm_helper_translate_curve_to_hw_format (plane_state->ctx, plane_state->in_shaper_func, &dpp_base->shaper_params, true); shaper_lut = &dpp_base->shaper_params;
drivers/gpu/drm/amd/display/dc/dcn30/dcn30_dwb_cm.c +1 -1
@@ -280,7 +280,7 @@ bool dwb3_ogam_set_input_transfer_func( dwb_ogam_lut =kzalloc (sizeof (*dwb_ogam_lut),GFP_KERNEL );if (dwb_ogam_lut) { -cm_helper_translate_curve_to_hw_format ( +cm_helper_translate_curve_to_hw_format (dwbc->ctx, in_transfer_func_dwb_ogam, dwb_ogam_lut, false);
drivers/gpu/drm/amd/display/dc/dcn30/dcn30_hwseq.c +1 -1
@@ -107,7 +107,7 @@ static bool dcn30_set_mpc_shaper_3dlut(struct pipe_ctx *pipe_ctx,if (stream->func_shaper->type ==TF_TYPE_HWPWL ) { shaper_lut = &stream->func_shaper->pwl; }else if (stream->func_shaper->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format (stream->func_shaper, +cm_helper_translate_curve_to_hw_format (stream->ctx, stream->func_shaper, &dpp_base->shaper_params, true); shaper_lut = &dpp_base->shaper_params; }
drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c +3 -3
@@ -530,7 +530,7 @@ static bool dcn32_set_mpc_shaper_3dlut(if (stream->func_shaper->type ==TF_TYPE_HWPWL ) shaper_lut = &stream->func_shaper->pwl;else if (stream->func_shaper->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format ( +cm_helper_translate_curve_to_hw_format (stream->ctx, stream->func_shaper, &dpp_base->shaper_params, true); shaper_lut = &dpp_base->shaper_params;
@@ -566,7 +566,7 @@ bool dcn32_set_mcm_luts(if (plane_state->blend_tf->type ==TF_TYPE_HWPWL ) lut_params = &plane_state->blend_tf->pwl;else if (plane_state->blend_tf->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format ( +cm_helper_translate_curve_to_hw_format (plane_state->ctx, plane_state->blend_tf, &dpp_base->regamma_params, false); lut_params = &dpp_base->regamma_params;
@@ -581,7 +581,7 @@ bool dcn32_set_mcm_luts(else if (plane_state->in_shaper_func->type ==TF_TYPE_DISTRIBUTED_POINTS ) {// TODO: dpp_base replace ASSERT (false); -cm_helper_translate_curve_to_hw_format ( +cm_helper_translate_curve_to_hw_format (plane_state->ctx, plane_state->in_shaper_func, &dpp_base->shaper_params, true); lut_params = &dpp_base->shaper_params;
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 101/107 drm/amd/display: Fix MPCC 1DLUT programming
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ilya Bakoulin <[email protected]>
[ Upstream commit 6f395cebdd8927fbffdc3a55a14fcacf93634359 ]
[Why]
Wrong function is used to translate LUT values to HW format, leading to visible artifacting in some cases.
[How]
Use the correct cm3_helper function.
--- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c +2 -4
@@ -566,8 +566,7 @@ bool dcn32_set_mcm_luts(if (plane_state->blend_tf->type ==TF_TYPE_HWPWL ) lut_params = &plane_state->blend_tf->pwl;else if (plane_state->blend_tf->type ==TF_TYPE_DISTRIBUTED_POINTS ) { -cm_helper_translate_curve_to_hw_format (plane_state->ctx, - plane_state->blend_tf, +cm3_helper_translate_curve_to_hw_format (plane_state->blend_tf, &dpp_base->regamma_params, false); lut_params = &dpp_base->regamma_params; }
@@ -581,8 +580,7 @@ bool dcn32_set_mcm_luts(else if (plane_state->in_shaper_func->type ==TF_TYPE_DISTRIBUTED_POINTS ) {// TODO: dpp_base replace ASSERT (false); -cm_helper_translate_curve_to_hw_format (plane_state->ctx, - plane_state->in_shaper_func, +cm3_helper_translate_curve_to_hw_format (plane_state->in_shaper_func, &dpp_base->shaper_params, true); lut_params = &dpp_base->shaper_params; }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 102/107 r8169: disable ASPM in case of tx timeout
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Heiner Kallweit <[email protected]>
[ Upstream commit 80c0576ef179311f624bc450fede30a89afe9792 ]
There are still single reports of systems where ASPM incompatibilities cause tx timeouts. It's not clear whom to blame, so let's disable ASPM in case of a tx timeout.
v2:
- add one-time warning for informing the user
Stable-dep-of: 59d395ed606d ("r8169: fix deadlock on RTL8125 in jumbo mtu mode")
--- drivers/net/ethernet/realtek/r8169_main.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
drivers/net/ethernet/realtek/r8169_main.c +13 -1
@@ -576,6 +576,7 @@ struct rtl8169_tc_offsets {enum rtl_flag {RTL_FLAG_TASK_ENABLED =0 ,RTL_FLAG_TASK_RESET_PENDING , +RTL_FLAG_TASK_TX_TIMEOUT ,RTL_FLAG_MAX };
@@ -3943,7 +3944,7 @@ static void rtl8169_tx_timeout(struct net_device *dev, unsigned int txqueue) {struct rtl8169_private *tp =netdev_priv (dev); -rtl_schedule_task (tp,RTL_FLAG_TASK_RESET_PENDING ); +rtl_schedule_task (tp,RTL_FLAG_TASK_TX_TIMEOUT ); } static int rtl8169_tx_map(struct rtl8169_private *tp, const u32 *opts, u32 len,
@@ -4537,6 +4538,7 @@ static void rtl_task(struct work_struct *work) {struct rtl8169_private *tp = container_of(work, struct rtl8169_private, wk.work); +int ret;rtnl_lock ();
@@ -4544,7 +4546,17 @@ static void rtl_task(struct work_struct *work) !test_bit(RTL_FLAG_TASK_ENABLED, tp->wk.flags)) goto out_unlock; +if (test_and_clear_bit (RTL_FLAG_TASK_TX_TIMEOUT , tp->wk.flags)) { +/* ASPM compatibility issues are a typical reason for tx timeouts */ + ret =pci_disable_link_state (tp->pci_dev,PCIE_LINK_STATE_L1 | +PCIE_LINK_STATE_L0S ); +if (!ret) +netdev_warn_once (tp->dev,"ASPM disabled on Tx timeout\n" ); + goto reset; + } +if (test_and_clear_bit (RTL_FLAG_TASK_RESET_PENDING , tp->wk.flags)) { +reset:rtl_reset_work (tp);netif_wake_queue (tp->dev); }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 103/107 r8169: fix deadlock on RTL8125 in jumbo mtu mode
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Heiner Kallweit <[email protected]>
[ Upstream commit 59d395ed606d8df14615712b0cdcdadb2d962175 ]
The original change results in a deadlock if jumbo mtu mode is used. Reason is that the phydev lock is held when rtl_reset_work() is called here, and rtl_jumbo_config() calls phy_start_aneg() which also tries to acquire the phydev lock. Fix this by calling rtl_reset_work() asynchronously.
--- drivers/net/ethernet/realtek/r8169_main.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/net/ethernet/realtek/r8169_main.c +4 -1
@@ -576,6 +576,7 @@ struct rtl8169_tc_offsets {enum rtl_flag {RTL_FLAG_TASK_ENABLED =0 ,RTL_FLAG_TASK_RESET_PENDING , +RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE ,RTL_FLAG_TASK_TX_TIMEOUT ,RTL_FLAG_MAX };
@@ -4559,6 +4560,8 @@ static void rtl_task(struct work_struct *work) reset:rtl_reset_work (tp);netif_wake_queue (tp->dev); + }else if (test_and_clear_bit (RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE , tp->wk.flags)) { +rtl_reset_work (tp); } out_unlock:rtnl_unlock ();
@@ -4592,7 +4595,7 @@ static void r8169_phylink_handler(struct net_device *ndev) }else {/* In few cases rx is broken after link-down otherwise */ if (rtl_is_8125 (tp)) -rtl_reset_work (tp); +rtl_schedule_task (tp,RTL_FLAG_TASK_RESET_NO_QUEUE_WAKE );pm_runtime_idle (d); }
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 104/107 xen: Allow platform PCI interrupt to be shared
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Woodhouse <[email protected]>
[ Upstream commit 3e8cd711c3da6c3d724076048038cd666bdbb2b5 ]
When we don't use the per-CPU vector callback, we ask Xen to deliver event channel interrupts as INTx on the PCI platform device. As such, it can be shared with INTx on other PCI devices.
Set IRQF_SHARED, and make it return IRQ_HANDLED or IRQ_NONE according to whether the evtchn_upcall_pending flag was actually set. Now I can share the interrupt:
11: 82 0 IO-APIC 11-fasteoi xen-platform-pci, ens4
Drop the IRQF_TRIGGER_RISING. It has no effect when the IRQ is shared, and besides, the only effect it was having even beforehand was to trigger a debug message in both I/OAPIC and legacy PIC cases:
[ 0.915441] genirq: No set_type function for IRQ 11 (IO-APIC) [ 0.951939] genirq: No set_type function for IRQ 11 (XT-PIC)
Stable-dep-of: db2832309a82 ("x86/xen: fix percpu vcpu_info allocation")
--- drivers/xen/events/events_base.c | 9 ++++++--- drivers/xen/platform-pci.c | 5 ++--- include/xen/events.h | 2 +- 3 files changed, 9 insertions(+), 7 deletions(-)
drivers/xen/events/events_base.c +6 -3
@@ -1710,9 +1710,10 @@ void handle_irq_for_port(evtchn_port_t port, struct evtchn_loop_ctrl *ctrl)generic_handle_irq (irq); } -static void __xen_evtchn_do_upcall (void ) +static int __xen_evtchn_do_upcall (void ) {struct vcpu_info *vcpu_info =__this_cpu_read (xen_vcpu); +int ret = vcpu_info->evtchn_upcall_pending ?IRQ_HANDLED :IRQ_NONE ;int cpu =smp_processor_id ();struct evtchn_loop_ctrl ctrl = {0 };
@@ -1744,6 +1745,8 @@ static void __xen_evtchn_do_upcall(void)* above. */ __this_cpu_inc (irq_epoch); + +return ret; }void xen_evtchn_do_upcall (struct pt_regs *regs)
@@ -1758,9 +1761,9 @@ void xen_evtchn_do_upcall(struct pt_regs *regs)set_irq_regs (old_regs); } -void xen_hvm_evtchn_do_upcall (void ) +int xen_hvm_evtchn_do_upcall (void ) { -__xen_evtchn_do_upcall (); +return __xen_evtchn_do_upcall (); }EXPORT_SYMBOL_GPL (xen_hvm_evtchn_do_upcall);
drivers/xen/platform-pci.c +2 -3
@@ -64,14 +64,13 @@ static uint64_t get_callback_via(struct pci_dev *pdev)static irqreturn_t do_hvm_evtchn_intr (int irq,void *dev_id) { -xen_hvm_evtchn_do_upcall (); -return IRQ_HANDLED ; +return xen_hvm_evtchn_do_upcall (); }static int xen_allocate_irq (struct pci_dev *pdev) {return request_irq (pdev->irq, do_hvm_evtchn_intr, -IRQF_NOBALANCING |IRQF_TRIGGER_RISING , +IRQF_NOBALANCING |IRQF_SHARED ,"xen-platform-pci" , pdev); }
include/xen/events.h +1 -1
@@ -107,7 +107,7 @@ evtchn_port_t evtchn_from_irq(unsigned irq);int xen_set_callback_via (uint64_t via);void xen_evtchn_do_upcall (struct pt_regs *regs); -void xen_hvm_evtchn_do_upcall (void ); +int xen_hvm_evtchn_do_upcall (void );/* Bind a pirq for a physical interrupt to an irq. */ int xen_bind_pirq_gsi_to_irq(unsigned gsi,
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 105/107 xen: simplify evtchn_do_upcall() call maze
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Juergen Gross <[email protected]>
[ Upstream commit 37510dd566bdbff31a769cde2fa6654bccdb8b24 ]
There are several functions involved for performing the functionality of evtchn_do_upcall():
- __xen_evtchn_do_upcall() doing the real work
- xen_hvm_evtchn_do_upcall() just being a wrapper for __xen_evtchn_do_upcall(), exposed for external callers
- xen_evtchn_do_upcall() calling __xen_evtchn_do_upcall(), too, but without any user
Simplify this maze by:
- removing the unused xen_evtchn_do_upcall()
- removing xen_hvm_evtchn_do_upcall() as the only left caller of __xen_evtchn_do_upcall(), while renaming __xen_evtchn_do_upcall() to xen_evtchn_do_upcall()
Stable-dep-of: db2832309a82 ("x86/xen: fix percpu vcpu_info allocation")
--- arch/arm/xen/enlighten.c | 2 +- arch/x86/entry/common.c | 2 +- arch/x86/xen/enlighten.c | 2 +- arch/x86/xen/enlighten_hvm.c | 2 +- drivers/xen/events/events_base.c | 21 ++------------------- drivers/xen/platform-pci.c | 2 +- include/xen/events.h | 3 +-- 7 files changed, 8 insertions(+), 26 deletions(-)
arch/arm/xen/enlighten.c +1 -1
@@ -204,7 +204,7 @@ static void xen_power_off(void)static irqreturn_t xen_arm_callback (int irq,void *arg) { -xen_hvm_evtchn_do_upcall (); +xen_evtchn_do_upcall ();return IRQ_HANDLED ; }
arch/x86/entry/common.c +1 -1
@@ -294,7 +294,7 @@ static void __xen_pv_evtchn_do_upcall(struct pt_regs *regs)inc_irq_stat (irq_hv_callback_count); -xen_hvm_evtchn_do_upcall (); +xen_evtchn_do_upcall ();set_irq_regs (old_regs); }
arch/x86/xen/enlighten.c +1 -1
@@ -32,7 +32,7 @@ EXPORT_SYMBOL_GPL(hypercall_page);* &HYPERVISOR_shared_info->vcpu_info[cpu]. See xen_hvm_init_shared_info * and xen_vcpu_setup for details. By default it points to share_info->vcpu_info * but during boot it is switched to point to xen_vcpu_info. -* The pointer is used in __xen_evtchn_do_upcall to acknowledge pending events. +* The pointer is used in xen_evtchn_do_upcall to acknowledge pending events. */ DEFINE_PER_CPU(struct vcpu_info *, xen_vcpu); DEFINE_PER_CPU(struct vcpu_info, xen_vcpu_info);
arch/x86/xen/enlighten_hvm.c +1 -1
@@ -136,7 +136,7 @@ DEFINE_IDTENTRY_SYSVEC(sysvec_xen_hvm_callback)inc_irq_stat (irq_hv_callback_count); -xen_hvm_evtchn_do_upcall (); +xen_evtchn_do_upcall ();set_irq_regs (old_regs); }
drivers/xen/events/events_base.c +2 -19
@@ -1710,7 +1710,7 @@ void handle_irq_for_port(evtchn_port_t port, struct evtchn_loop_ctrl *ctrl)generic_handle_irq (irq); } -static int __xen_evtchn_do_upcall (void ) +int xen_evtchn_do_upcall (void ) {struct vcpu_info *vcpu_info =__this_cpu_read (xen_vcpu);int ret = vcpu_info->evtchn_upcall_pending ?IRQ_HANDLED :IRQ_NONE ;
@@ -1748,24 +1748,7 @@ static int __xen_evtchn_do_upcall(void)return ret; } - -void xen_evtchn_do_upcall (struct pt_regs *regs) -{ -struct pt_regs *old_regs =set_irq_regs (regs); - -irq_enter (); - -__xen_evtchn_do_upcall (); - -irq_exit (); -set_irq_regs (old_regs); -} - -int xen_hvm_evtchn_do_upcall (void ) -{ -return __xen_evtchn_do_upcall (); -} -EXPORT_SYMBOL_GPL (xen_hvm_evtchn_do_upcall); +EXPORT_SYMBOL_GPL (xen_evtchn_do_upcall);/* Rebind a new event channel to an existing irq. */ void rebind_evtchn_irq (evtchn_port_t evtchn,int irq)
drivers/xen/platform-pci.c +1 -1
@@ -64,7 +64,7 @@ static uint64_t get_callback_via(struct pci_dev *pdev)static irqreturn_t do_hvm_evtchn_intr (int irq,void *dev_id) { -return xen_hvm_evtchn_do_upcall (); +return xen_evtchn_do_upcall (); }static int xen_allocate_irq (struct pci_dev *pdev)
include/xen/events.h +1 -2
@@ -106,8 +106,7 @@ int irq_from_virq(unsigned int cpu, unsigned int virq);evtchn_port_t evtchn_from_irq (unsigned irq);int xen_set_callback_via (uint64_t via); -void xen_evtchn_do_upcall (struct pt_regs *regs); -int xen_hvm_evtchn_do_upcall (void ); +int xen_evtchn_do_upcall (void );/* Bind a pirq for a physical interrupt to an irq. */ int xen_bind_pirq_gsi_to_irq(unsigned gsi,
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 106/107 x86/xen: fix percpu vcpu_info allocation
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Juergen Gross <[email protected]>
[ Upstream commit db2832309a82b9acc4b8cc33a1831d36507ec13e ]
Today the percpu struct vcpu_info is allocated via DEFINE_PER_CPU(), meaning that it could cross a page boundary. In this case registering it with the hypervisor will fail, resulting in a panic().
This can easily be fixed by using DEFINE_PER_CPU_ALIGNED() instead, as struct vcpu_info is guaranteed to have a size of 64 bytes, matching the cache line size of x86 64-bit processors (Xen doesn't support 32-bit processors).
--- arch/x86/xen/enlighten.c | 6 +++++- arch/x86/xen/xen-ops.h | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-)
arch/x86/xen/enlighten.c +5 -1
@@ -33,9 +33,12 @@ EXPORT_SYMBOL_GPL(hypercall_page);* and xen_vcpu_setup for details. By default it points to share_info->vcpu_info * but during boot it is switched to point to xen_vcpu_info. * The pointer is used in xen_evtchn_do_upcall to acknowledge pending events. +* Make sure that xen_vcpu_info doesn't cross a page boundary by making it +* cache-line aligned (the struct is guaranteed to have a size of 64 bytes, +* which matches the cache line size of 64-bit x86 processors). */ DEFINE_PER_CPU(struct vcpu_info *, xen_vcpu); -DEFINE_PER_CPU(struct vcpu_info, xen_vcpu_info); +DEFINE_PER_CPU_ALIGNED(struct vcpu_info, xen_vcpu_info);/* Linux <-> Xen vCPU id mapping */ DEFINE_PER_CPU (uint32_t, xen_vcpu_id);
@@ -160,6 +163,7 @@ void xen_vcpu_setup(int cpu)int err;struct vcpu_info *vcpup; +BUILD_BUG_ON (sizeof (*vcpup) >SMP_CACHE_BYTES );BUG_ON (HYPERVISOR_shared_info == &xen_dummy_shared_info);/*
arch/x86/xen/xen-ops.h +1 -1
@@ -21,7 +21,7 @@ extern void *xen_initial_gdt;struct trap_info ;void xen_copy_trap_info (struct trap_info *traps); -DECLARE_PER_CPU(struct vcpu_info, xen_vcpu_info); +DECLARE_PER_CPU_ALIGNED(struct vcpu_info, xen_vcpu_info); DECLARE_PER_CPU(unsigned long, xen_cr3); DECLARE_PER_CPU(unsigned long, xen_current_cr3);
Signature · 1 line
2.42.0
Greg Kroah-Hartman
maintainerPATCH 107/107 x86/apic/msi: Fix misconfigured non-maskable MSI quirk
In reply to Greg Kroah-Hartman6.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Koichiro Den <[email protected]>
commit b56ebe7c896dc78b5865ec2c4b1dae3c93537517 upstream.
commit ef8dd01538ea ("genirq/msi: Make interrupt allocation less convoluted"), reworked the code so that the x86 specific quirk for affinity setting of non-maskable PCI/MSI interrupts is not longer activated if necessary.
This could be solved by restoring the original logic in the core MSI code, but after a deeper analysis it turned out that the quirk flag is not required at all.
The quirk is only required when the PCI/MSI device cannot mask the MSI interrupts, which in turn also prevents reservation mode from being enabled for the affected interrupt.
This allows ot remove the NOMASK quirk bit completely as msi_set_affinity() can instead check whether reservation mode is enabled for the interrupt, which gives exactly the same answer.
Even in the momentary non-existing case that the reservation mode would be not set for a maskable MSI interrupt this would not cause any harm as it just would cause msi_set_affinity() to go needlessly through the functionaly equivalent slow path, which works perfectly fine with maskable interrupts as well.
Rework msi_set_affinity() to query the reservation mode and remove all NOMASK quirk logic from the core code.
[ tglx: Massaged changelog ]
--- arch/x86/kernel/apic/msi.c | 8 +++----- include/linux/irq.h | 24 +++--------------------- kernel/irq/debugfs.c | 1 - kernel/irq/msi.c | 12 +----------- 4 files changed, 7 insertions(+), 38 deletions(-)
arch/x86/kernel/apic/msi.c +3 -5
@@ -55,14 +55,14 @@ msi_set_affinity(struct irq_data *irqd,* caused by the non-atomic update of the address/data pair. * * Direct update is possible when: -* - The MSI is maskable (remapped MSI does not use this code path)). -* The quirk bit is not set in this case. +* - The MSI is maskable (remapped MSI does not use this code path). +* The reservation mode bit is set in this case. * - The new vector is the same as the old vector * - The old vector is MANAGED_IRQ_SHUTDOWN_VECTOR (interrupt starts up) * - The interrupt is not yet started up * - The new destination CPU is the same as the old destination CPU */ - if (!irqd_msi_nomask_quirk(irqd) || + if (!irqd_can_reserve(irqd) || cfg->vector == old_cfg.vector || old_cfg.vector == MANAGED_IRQ_SHUTDOWN_VECTOR || !irqd_is_started(irqd) ||
@@ -202,8 +202,6 @@ struct irq_domain * __init native_createif (!d) {irq_domain_free_fwnode (fn);pr_warn ("Failed to initialize PCI-MSI irqdomain.\n" ); - }else { - d->flags |=IRQ_DOMAIN_MSI_NOMASK_QUIRK ; }return d; }
include/linux/irq.h +3 -21
@@ -215,8 +215,6 @@ struct irq_data {* IRQD_SINGLE_TARGET - IRQ allows only a single affinity target * IRQD_DEFAULT_TRIGGER_SET - Expected trigger already been set * IRQD_CAN_RESERVE - Can use reservation mode -* IRQD_MSI_NOMASK_QUIRK - Non-maskable MSI quirk for affinity change -* required * IRQD_HANDLE_ENFORCE_IRQCTX - Enforce that handle_irq_*() is only invoked * from actual interrupt context. * IRQD_AFFINITY_ON_ACTIVATE - Affinity is set on activation. Don't call
@@ -245,10 +243,9 @@ enum {IRQD_SINGLE_TARGET = (1 <<24 ),IRQD_DEFAULT_TRIGGER_SET = (1 <<25 ),IRQD_CAN_RESERVE = (1 <<26 ), -IRQD_MSI_NOMASK_QUIRK = (1 <<27 ), -IRQD_HANDLE_ENFORCE_IRQCTX = (1 <<28 ), -IRQD_AFFINITY_ON_ACTIVATE = (1 <<29 ), - IRQD_IRQ_ENABLED_ON_SUSPEND = (1 << 30), +IRQD_HANDLE_ENFORCE_IRQCTX = (1 <<27 ), +IRQD_AFFINITY_ON_ACTIVATE = (1 <<28 ), + IRQD_IRQ_ENABLED_ON_SUSPEND = (1 << 29), };#define __irqd_to_state (d) ACCESS_PRIVATE((d)->common, state_use_accessors)
@@ -423,21 +420,6 @@ static inline bool irqd_can_reserve(strureturn __irqd_to_state (d) &IRQD_CAN_RESERVE ; } -static inline void irqd_set_msi_nomask_quirk (struct irq_data *d) -{ -__irqd_to_state (d) |=IRQD_MSI_NOMASK_QUIRK ; -} - -static inline void irqd_clr_msi_nomask_quirk (struct irq_data *d) -{ -__irqd_to_state (d) &= ~IRQD_MSI_NOMASK_QUIRK ; -} - -static inline bool irqd_msi_nomask_quirk (struct irq_data *d) -{ -return __irqd_to_state (d) &IRQD_MSI_NOMASK_QUIRK ; -} -static inline void irqd_set_affinity_on_activate (struct irq_data *d) {__irqd_to_state (d) |=IRQD_AFFINITY_ON_ACTIVATE ;
kernel/irq/debugfs.c +0 -1
@@ -121,7 +121,6 @@ static const struct irq_bit_descr irqdatBIT_MASK_DESCR (IRQD_AFFINITY_ON_ACTIVATE ),BIT_MASK_DESCR (IRQD_MANAGED_SHUTDOWN ),BIT_MASK_DESCR (IRQD_CAN_RESERVE ), -BIT_MASK_DESCR (IRQD_MSI_NOMASK_QUIRK ), BIT_MASK_DESCR(IRQD_FORWARDED_TO_VCPU),
kernel/irq/msi.c +1 -11
@@ -807,7 +807,6 @@ static int msi_handle_pci_fail(struct ir#define VIRQ_CAN_RESERVE 0x01#define VIRQ_ACTIVATE 0x02 -#define VIRQ_NOMASK_QUIRK 0x04static int msi_init_virq (struct irq_domain *domain,int virq,unsigned int vflags) {
@@ -816,8 +815,6 @@ static int msi_init_virq(struct irq_domaif (!(vflags &VIRQ_CAN_RESERVE )) {irqd_clr_can_reserve (irqd); -if (vflags &VIRQ_NOMASK_QUIRK ) -irqd_set_msi_nomask_quirk (irqd);/* * If the interrupt is managed but no CPU is available to
@@ -877,15 +874,8 @@ int __msi_domain_alloc_irqs(struct irq_d* Interrupt can use a reserved vector and will not occupy * a real device vector until the interrupt is requested. */ -if (msi_check_reservation_mode (domain, info, dev)) { +if (msi_check_reservation_mode (domain, info, dev)) vflags |=VIRQ_CAN_RESERVE ; -/* -* MSI affinity setting requires a special quirk (X86) when -* reservation mode is active. -*/ -if (domain->flags &IRQ_DOMAIN_MSI_NOMASK_QUIRK ) - vflags |=VIRQ_NOMASK_QUIRK ; - }msi_for_each_desc (desc, dev,MSI_DESC_NOTASSOCIATED ) { ops->set_desc (&arg, desc);
Hi!
Quoted 4 lines
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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.
We see build failure on risc-v:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/5680050135
AR drivers/nvmem/built-in.a
2686In file included from ./arch/riscv/include/asm/ptrace.h:10,
2687 from ./arch/riscv/include/uapi/asm/bpf_perf_event.h:5, 2688 from ./include/uapi/linux/bpf_perf_event.h:11, 2689 from ./include/linux/perf_event.h:18, 2690 from ./include/linux/perf/riscv_pmu.h:12, 2691 from drivers/perf/riscv_pmu_sbi.c:14:
2692drivers/perf/riscv_pmu_sbi.c: In function 'pmu_sbi_ovf_handler':2693drivers/perf/riscv_pmu_sbi.c:582:40: error: 'riscv_pmu_irq_num' undeclared (first use in this function); did you mean 'riscv_pmu_irq'?
2694 582 | csr_clear(CSR_SIP, BIT(riscv_pmu_irq_num));
2695 | ^~~~~~~~~~~~~~~~~2696./arch/riscv/include/asm/csr.h:400:45: note: in definition of macro 'csr_clear'
2697 400 | unsigned long __v = (unsigned long)(val); \
2698 | ^~~2699drivers/perf/riscv_pmu_sbi.c:582:36: note: in expansion of macro 'BIT'
2700 582 | csr_clear(CSR_SIP, BIT(riscv_pmu_irq_num));
2701 | ^~~2702drivers/perf/riscv_pmu_sbi.c:582:40: note: each undeclared identifier is reported only once for each function it appears in
2703 582 | csr_clear(CSR_SIP, BIT(riscv_pmu_irq_num));
2704 | ^~~~~~~~~~~~~~~~~2705./arch/riscv/include/asm/csr.h:400:45: note: in definition of macro 'csr_clear'
2706 400 | unsigned long __v = (unsigned long)(val); \
2707 | ^~~2708drivers/perf/riscv_pmu_sbi.c:582:36: note: in expansion of macro 'BIT'
2709 582 | csr_clear(CSR_SIP, BIT(riscv_pmu_irq_num));
2710 | ^~~
2711make[3]: *** [scripts/Makefile.build:250: drivers/perf/riscv_pmu_sbi.o] Error 1
2712make[2]: *** [scripts/Makefile.build:500: drivers/perf] Error 2
2713make[2]: *** Waiting for unfinished jobs....
2714 CC drivers/firmware/efi/earlycon.o
2715
Best regards,
Pavel
Signature · 2 lines
DENX Software Engineering GmbH, Managing Director: Erika Unter HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Quoted 4 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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.
The perf patch I pointed out breaks the build in all my configs on riscv.
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.66-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1:
10 builds: 10 pass, 0 fail
26 boots: 26 pass, 0 fail
116 tests: 116 pass, 0 failLinux version: 6.1.66-rc1-gc1e513337d8b
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra20-ventana, tegra210-p2371-2180,
tegra210-p3450-0000, tegra30-cardhu-a04Jon
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.66-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
Powerpc, s390 and riscv allmodconfig failed on stable-rc linux-6.1.y
- s390: gcc-13-allmodconfig: FAILED
- Powerpc: gcc-13-allmodconfig: FAILED
- riscv: gcc-13-allmodconfig: FAILED
S390 build error:arch/s390/mm/page-states.c:198:23: error: 'invalid_pg_dir' undeclared (first use in this function); did you mean 'is_valid_bugaddr'?
page = virt_to_page(&invalid_pg_dir);
^~~~~~~~~~~~~~s390/cmma: fix handling of swapper_pg_dir and invalid_pg_dir
[ Upstream commit 84bb41d5df48868055d159d9247b80927f1f70f9 ]
Powerpc build error:arch/powerpc/platforms/pseries/iommu.c:926:28: error: 'struct dma_win' has no member named 'direct'
*direct_mapping = window->direct;
^~powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
[ Upstream commit 3bf983e4e93ce8e6d69e9d63f52a66ec0856672e ]
riscv: gcc-13-allmodconfig: FAILED
drivers/perf/riscv_pmu_sbi.c: In function 'pmu_sbi_ovf_handler':drivers/perf/riscv_pmu_sbi.c:582:40: error: 'riscv_pmu_irq_num' undeclared (first use in this function); did you mean 'riscv_pmu_irq'?
582 | csr_clear(CSR_SIP, BIT(riscv_pmu_irq_num));
| ^~~~~~~~~~~~~~~~~drivers: perf: Check find_first_bit() return value
[ Upstream commit c6e316ac05532febb0c966fa9b55f5258ed037be ]
Links:
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2Z6hXBQ5SQY07zKJyG6c3B1W9M0/
- https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/2Z6hXGJFTdSPKZSutAt0vOOcDd1
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.65-108-gc1e513337d8b/testrun/21509082/suite/build/test/gcc-13-allmodconfig/details/
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.65-108-gc1e513337d8b/testrun/21509040/suite/build/test/gcc-13-allmodconfig/details/
- https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.65-108-gc1e513337d8b/testrun/21509172/suite/build/test/gcc-13-allmodconfig/history/
--
Linaro LKFT
https://lkft.linaro.org
Greg Kroah-Hartman
maintainerQuoted 51 lines · Naresh Kamboju
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.66-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
Powerpc, s390 and riscv allmodconfig failed on stable-rc linux-6.1.y
- s390: gcc-13-allmodconfig: FAILED
- Powerpc: gcc-13-allmodconfig: FAILED
- riscv: gcc-13-allmodconfig: FAILEDS390 build error:
arch/s390/mm/page-states.c:198:23: error: 'invalid_pg_dir' undeclared (first use in this function); did you mean 'is_valid_bugaddr'?page = virt_to_page(&invalid_pg_dir); ^~~~~~~~~~~~~~s390/cmma: fix handling of
swapper_pg_dirandinvalid_pg_dir
[ Upstream commit84bb41d5df48868055d159d9247b80927f1f70f9]Powerpc build error:
arch/powerpc/platforms/pseries/iommu.c:926:28: error: 'structdma_win' has no member named 'direct'*direct_mapping = window->direct; ^~powerpc/pseries/iommu:
enable_ddwincorrectly returns direct mapping for SR-IOV device
[ Upstream commit3bf983e4e93ce8e6d69e9d63f52a66ec0856672e]riscv: gcc-13-allmodconfig: FAILED
Quoted 8 lines
drivers/perf/riscv_pmu_sbi.c: In function 'pmu_sbi_ovf_handler':drivers/perf/riscv_pmu_sbi.c:582:40: error: 'riscv_pmu_irq_num' undeclared (first use in this function); did you mean 'riscv_pmu_irq'?582 | csr_clear(CSR_SIP, BIT(riscv_pmu_irq_num)); | ^~~~~~~~~~~~~~~~~drivers: perf: Check
find_first_bit()return value
[ Upstream commitc6e316ac05532febb0c966fa9b55f5258ed037be]
Thanks, all should now be dropped. I'll push out new -rc releases in a bit...
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +0000. Anything received after that time might be too late.
Build results:
total: 157 pass: 146 fail: 11 Failed builds: powerpc:defconfig powerpc:allmodconfig riscv32:defconfig riscv32:allmodconfig riscv:defconfig riscv:allmodconfig s390:defconfig s390:allmodconfig s390:allnoconfig s390:tinyconfig s390:debug_defconfig Qemu test results: total: 537 pass: 467 fail: 70 Failed tests: <most ppc64> <all riscv32/riscv64> <all s390>
powerpc:
arch/powerpc/platforms/pseries/iommu.c: In function 'find_existing_ddw':arch/powerpc/platforms/pseries/iommu.c:926:49: error: 'struct dma_win' has no member named 'direct'
riscv:
drivers/perf/riscv_pmu_sbi.c: In function 'pmu_sbi_ovf_handler':drivers/perf/riscv_pmu_sbi.c:582:40: error: 'riscv_pmu_irq_num' undeclared
s390:
arch/s390/mm/page-states.c: In function 'cmma_init_nodat':arch/s390/mm/page-states.c:198:30: error: 'invalid_pg_dir' undeclared
Guenter
Hello,
Quoted 5 lines · On 2023-12-05T12:15:35+09:00 Greg Kroah-Hartman <[email protected]>…
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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.
Quoted 8 lines
Responses should be made by Thu, 07 Dec 2023 03:14:57 +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/v6.x/stable-review/patch-6.1.66-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.
This rc kernel passes DAMON functionality test[1] on my test machine. Attaching the test results summary below. Please note that I retrieved the kernel from linux-stable-rc tree[2].
[1] https://github.com/awslabs/damon-tests/tree/next/corr
[2] c1e513337d8b ("Linux 6.1.66-rc1")
Thanks,
SJ
[...]
---
ok 1 selftests: damon: debugfs_attrs.sh
ok 2 selftests: damon: debugfs_schemes.sh
ok 3 selftests: damon: debugfs_target_ids.sh
ok 4 selftests: damon: debugfs_empty_targets.sh
ok 5 selftests: damon: debugfs_huge_count_read_write.sh
ok 6 selftests: damon: debugfs_duplicate_context_creation.sh
ok 7 selftests: damon: sysfs.sh
ok 1 selftests: damon-tests: kunit.sh
ok 2 selftests: damon-tests: huge_count_read_write.sh
ok 3 selftests: damon-tests: buffer_overflow.sh
ok 4 selftests: damon-tests: rm_contexts.sh
ok 5 selftests: damon-tests: record_null_deref.sh
ok 6 selftests: damon-tests: dbgfs_target_ids_read_before_terminate_race.sh ok 7 selftests: damon-tests: dbgfs_target_ids_pid_leak.sh
ok 8 selftests: damon-tests: damo_tests.sh
ok 9 selftests: damon-tests: masim-record.sh
ok 10 selftests: damon-tests: build_i386.sh
ok 11 selftests: damon-tests: build_arm64.sh
ok 12 selftests: damon-tests: build_i386_idle_flag.sh
ok 13 selftests: damon-tests: build_i386_highpte.sh
ok 14 selftests: damon-tests: build_nomemcg.sh
[33m
[92mPASS [39m
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.66-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on BMIPS_GENERIC:
Signature · 1 line
Florian
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 6.1.66 release. There are 107 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 Thu, 07 Dec 2023 03:14:57 +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/v6.x/stable-review/patch-6.1.66-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-6.1.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah