2023-03-20 14:58:52

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.10 00/99] 5.10.176-rc1 review

This is the start of the stable review cycle for the 5.10.176 release.
There are 99 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.

Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.176-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <[email protected]>
Linux 5.10.176-rc1

Lee Jones <[email protected]>
HID: uhid: Over-ride the default maximum data buffer value with our own

Lee Jones <[email protected]>
HID: core: Provide new max_buffer_size attribute to over-ride the default

Gaosheng Cui <[email protected]>
xfs: remove xfs_setattr_time() declaration

Christian Brauner <[email protected]>
fs: use consistent setgid checks in is_sxid()

Amir Goldstein <[email protected]>
attr: use consistent sgid stripping checks

Amir Goldstein <[email protected]>
attr: add setattr_should_drop_sgid()

Amir Goldstein <[email protected]>
fs: move should_remove_suid()

Amir Goldstein <[email protected]>
attr: add in_group_or_capable()

Yang Xu <[email protected]>
fs: move S_ISGID stripping into the vfs_*() helpers

Yang Xu <[email protected]>
fs: add mode_strip_sgid() helper

Darrick J. Wong <[email protected]>
xfs: use setattr_copy to set vfs inode attributes

Dave Chinner <[email protected]>
xfs: set prealloc flag in xfs_alloc_file_space()

Dave Chinner <[email protected]>
xfs: fallocate() should call file_modified()

Dave Chinner <[email protected]>
xfs: remove XFS_PREALLOC_SYNC

Darrick J. Wong <[email protected]>
xfs: don't leak btree cursor when insrec fails after a split

Darrick J. Wong <[email protected]>
xfs: purge dquots after inode walk fails during quotacheck

Dave Chinner <[email protected]>
xfs: don't assert fail on perag references on teardown

Lukas Wunner <[email protected]>
PCI/DPC: Await readiness of secondary bus after reset

Lukas Wunner <[email protected]>
PCI: Unify delay handling for reset and resume

Sven Schnelle <[email protected]>
s390/ipl: add missing intersection check to ipl_report handling

Fedor Pchelkin <[email protected]>
io_uring: avoid null-ptr-deref in io_arm_poll_handler

Janusz Krzysztofik <[email protected]>
drm/i915/active: Fix misuse of non-idle barriers as fence trackers

John Harrison <[email protected]>
drm/i915: Don't use stolen memory for ring buffers with LLC

Nikita Zhandarovich <[email protected]>
x86/mm: Fix use of uninitialized buffer in sme_enable()

Yazen Ghannam <[email protected]>
x86/mce: Make sure logged MCEs are processed after sysfs update

Shawn Guo <[email protected]>
cpuidle: psci: Iterate backwards over list in psci_pd_remove()

Helge Deller <[email protected]>
fbdev: stifb: Provide valid pixelclock and add fb_check_var() checks

Francesco Dolcini <[email protected]>
mmc: sdhci_am654: lower power-on failed message severity

David Hildenbrand <[email protected]>
mm/userfaultfd: propagate uffd-wp bit when PTE-mapping the huge zeropage

Chen Zhongjin <[email protected]>
ftrace: Fix invalid address access in lookup_rec() when index is 0

Matthieu Baerts <[email protected]>
mptcp: avoid setting TCP_CLOSE state twice

Dmitry Osipenko <[email protected]>
drm/shmem-helper: Remove another errant put in error path

Hamidreza H. Fard <[email protected]>
ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book2 Pro

Bard Liao <[email protected]>
ALSA: hda: intel-dsp-config: add MTL PCI id

Paolo Bonzini <[email protected]>
KVM: nVMX: add missing consistency checks for CR0 and CR4

Volker Lendecke <[email protected]>
cifs: Fix smb2_set_path_size()

Steven Rostedt (Google) <[email protected]>
tracing: Make tracepoint lockdep check actually test something

Steven Rostedt (Google) <[email protected]>
tracing: Check field value in hist_field_name()

Sung-hun Kim <[email protected]>
tracing: Make splice_read available again

Johan Hovold <[email protected]>
interconnect: fix mem leak when freeing nodes

Roman Gushchin <[email protected]>
firmware: xilinx: don't make a sleepable memory allocation from an atomic context

Biju Das <[email protected]>
serial: 8250_em: Fix UART port type

Sherry Sun <[email protected]>
tty: serial: fsl_lpuart: skip waiting for transmission complete when UARTCTRL_SBK is asserted

Theodore Ts'o <[email protected]>
ext4: fix possible double unlock when moving a directory

Alex Hung <[email protected]>
drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes

Michael Karcher <[email protected]>
sh: intc: Avoid spurious sizeof-pointer-div warning

Qu Huang <[email protected]>
drm/amdkfd: Fix an illegal memory access

Baokun Li <[email protected]>
ext4: fix task hung in ext4_xattr_delete_inode

Baokun Li <[email protected]>
ext4: fail ext4_iget if special inode unallocated

David Gow <[email protected]>
rust: arch/um: Disable FP/SIMD instruction to match x86

Yifei Liu <[email protected]>
jffs2: correct logic when creating a hole in jffs2_write_begin

Tobias Schramm <[email protected]>
mmc: atmel-mci: fix race between stop command and start of next command

Linus Torvalds <[email protected]>
media: m5mols: fix off-by-one loop termination error

Lars-Peter Clausen <[email protected]>
hwmon: (adm1266) Set `can_sleep` flag for GPIO chip

Krzysztof Kozlowski <[email protected]>
hwmon: tmp512: drop of_match_ptr for ID table

Lars-Peter Clausen <[email protected]>
hwmon: (ucd90320) Add minimum delay between bus accesses

Marcus Folkesson <[email protected]>
hwmon: (ina3221) return prober error code

Zheng Wang <[email protected]>
hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to race condition

Tony O'Brien <[email protected]>
hwmon: (adt7475) Fix masking of hysteresis registers

Tony O'Brien <[email protected]>
hwmon: (adt7475) Display smoothing attributes in correct order

Liang He <[email protected]>
ethernet: sun: add check for the mdesc_grab()

Daniil Tatianin <[email protected]>
qed/qed_mng_tlv: correctly zero out ->min instead of ->hour

Po-Hsu Lin <[email protected]>
selftests: net: devlink_port_split.py: skip test if no suitable device available

Alexandra Winter <[email protected]>
net/iucv: Fix size of interrupt data

Szymon Heidrich <[email protected]>
net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull

Ido Schimmel <[email protected]>
ipv4: Fix incorrect table ID in IOCTL path

Vladimir Oltean <[email protected]>
net: dsa: mv88e6xxx: fix max_mtu of 1492 on 6165, 6191, 6220, 6250, 6290

Maciej Fijalkowski <[email protected]>
ice: xsk: disable txq irq before flushing hw

Liang He <[email protected]>
block: sunvdc: add check for mdesc_grab() returning NULL

Damien Le Moal <[email protected]>
nvmet: avoid potential UAF in nvmet_req_complete()

Ming Lei <[email protected]>
nvme: fix handling single range discard request

Damien Le Moal <[email protected]>
block: null_blk: Fix handling of fake timeout request

Damien Le Moal <[email protected]>
null_blk: Move driver into its own directory

Liu Ying <[email protected]>
drm/bridge: Fix returned array size name for atomic_get_input_bus_fmts kdoc

Szymon Heidrich <[email protected]>
net: usb: smsc75xx: Limit packet length to skb->len

Wenjia Zhang <[email protected]>
net/smc: fix deadlock triggered by cancel_delayed_work_syn()

Zheng Wang <[email protected]>
nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition

Heiner Kallweit <[email protected]>
net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails

Eric Dumazet <[email protected]>
net: tunnels: annotate lockless accesses to dev->needed_headroom

Daniil Tatianin <[email protected]>
qed/qed_dev: guard against a possible division by zero

D. Wythe <[email protected]>
net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()

Ivan Vecera <[email protected]>
i40e: Fix kernel crash during reboot when adapter is in recovery mode

Jianguo Wu <[email protected]>
ipvlan: Make skb->skb_iif track skb->dev for l3s mode

Fedor Pchelkin <[email protected]>
nfc: pn533: initialize struct pn533_out_arg properly

Breno Leitao <[email protected]>
tcp: tcp_make_synack() can be called from process context

Bart Van Assche <[email protected]>
scsi: core: Fix a procfs host directory removal regression

Xiang Chen <[email protected]>
scsi: core: Fix a comment in function scsi_host_dev_release()

Jeremy Sowden <[email protected]>
netfilter: nft_redir: correct value of inet type `.maxattrs`

Jeremy Sowden <[email protected]>
netfilter: nft_redir: correct length for loading protocol registers

Jeremy Sowden <[email protected]>
netfilter: nft_masq: correct length for loading protocol registers

Jeremy Sowden <[email protected]>
netfilter: nft_nat: correct length for loading protocol registers

Bjorn Helgaas <[email protected]>
ALSA: hda: Match only Intel devices with CONTROLLER_IN_GPU()

Wenchao Hao <[email protected]>
scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add()

Glenn Washburn <[email protected]>
docs: Correct missing "d_" prefix for dentry_operations member d_weak_revalidate

Randy Dunlap <[email protected]>
clk: HI655X: select REGMAP instead of depending on it

Christian Hewitt <[email protected]>
drm/meson: fix 1px pink line on GXM when scaling video overlay

Zhang Xiaoxu <[email protected]>
cifs: Move the in_send statistic to __smb_send_rqst()

Dmitry Osipenko <[email protected]>
drm/panfrost: Don't sync rpm suspension after mmu flushing

Herbert Xu <[email protected]>
xfrm: Allow transport-mode states with AF_UNSPEC selector


-------------

Diffstat:

Documentation/filesystems/vfs.rst | 2 +-
Documentation/trace/ftrace.rst | 2 +-
Makefile | 4 +-
arch/s390/boot/ipl_report.c | 8 +++
arch/x86/Makefile.um | 6 ++
arch/x86/kernel/cpu/mce/core.c | 1 +
arch/x86/kvm/vmx/nested.c | 10 ++-
arch/x86/mm/mem_encrypt_identity.c | 3 +-
drivers/block/Kconfig | 8 +--
drivers/block/Makefile | 7 +-
drivers/block/null_blk/Kconfig | 12 ++++
drivers/block/null_blk/Makefile | 11 +++
drivers/block/{null_blk_main.c => null_blk/main.c} | 6 +-
drivers/block/{ => null_blk}/null_blk.h | 0
.../block/{null_blk_trace.c => null_blk/trace.c} | 2 +-
.../block/{null_blk_trace.h => null_blk/trace.h} | 2 +-
.../block/{null_blk_zoned.c => null_blk/zoned.c} | 2 +-
drivers/block/sunvdc.c | 2 +
drivers/clk/Kconfig | 2 +-
drivers/cpuidle/cpuidle-psci-domain.c | 3 +-
drivers/firmware/xilinx/zynqmp.c | 2 +-
drivers/gpu/drm/amd/amdkfd/kfd_events.c | 9 +--
.../amd/display/dc/dml/dcn30/display_mode_vba_30.c | 5 +-
drivers/gpu/drm/drm_gem_shmem_helper.c | 9 ++-
drivers/gpu/drm/i915/gt/intel_ring.c | 2 +-
drivers/gpu/drm/i915/i915_active.c | 24 ++++---
drivers/gpu/drm/meson/meson_vpp.c | 2 +
drivers/gpu/drm/panfrost/panfrost_mmu.c | 2 +-
drivers/hid/hid-core.c | 18 +++--
drivers/hid/uhid.c | 1 +
drivers/hwmon/adt7475.c | 8 +--
drivers/hwmon/ina3221.c | 2 +-
drivers/hwmon/pmbus/adm1266.c | 1 +
drivers/hwmon/pmbus/ucd9000.c | 75 ++++++++++++++++++++
drivers/hwmon/tmp513.c | 2 +-
drivers/hwmon/xgene-hwmon.c | 1 +
drivers/interconnect/core.c | 4 ++
drivers/media/i2c/m5mols/m5mols_core.c | 2 +-
drivers/mmc/host/atmel-mci.c | 3 -
drivers/mmc/host/sdhci_am654.c | 2 +-
drivers/net/dsa/mv88e6xxx/chip.c | 16 +++--
drivers/net/ethernet/intel/i40e/i40e_main.c | 1 +
drivers/net/ethernet/intel/ice/ice_xsk.c | 4 +-
drivers/net/ethernet/qlogic/qed/qed_dev.c | 5 ++
drivers/net/ethernet/qlogic/qed/qed_mng_tlv.c | 2 +-
drivers/net/ethernet/sun/ldmvsw.c | 3 +
drivers/net/ethernet/sun/sunvnet.c | 3 +
drivers/net/ipvlan/ipvlan_l3s.c | 1 +
drivers/net/phy/smsc.c | 5 +-
drivers/net/usb/smsc75xx.c | 7 ++
drivers/nfc/pn533/usb.c | 1 +
drivers/nfc/st-nci/ndlc.c | 6 +-
drivers/nvme/host/core.c | 28 +++++---
drivers/nvme/target/core.c | 4 +-
drivers/pci/pci-driver.c | 4 +-
drivers/pci/pci.c | 57 +++++++--------
drivers/pci/pci.h | 16 ++++-
drivers/pci/pcie/dpc.c | 4 +-
drivers/scsi/hosts.c | 5 +-
drivers/scsi/mpt3sas/mpt3sas_transport.c | 14 +++-
drivers/tty/serial/8250/8250_em.c | 4 +-
drivers/tty/serial/fsl_lpuart.c | 12 +++-
drivers/video/fbdev/stifb.c | 27 ++++++++
fs/attr.c | 70 +++++++++++++++++--
fs/cifs/smb2inode.c | 31 +++++++--
fs/cifs/transport.c | 21 +++---
fs/ext4/inode.c | 18 +++--
fs/ext4/namei.c | 4 +-
fs/ext4/xattr.c | 11 +++
fs/inode.c | 80 +++++++++++++---------
fs/internal.h | 6 ++
fs/jffs2/file.c | 15 ++--
fs/namei.c | 80 ++++++++++++++++++----
fs/ocfs2/file.c | 4 +-
fs/ocfs2/namei.c | 1 +
fs/open.c | 6 +-
fs/xfs/libxfs/xfs_btree.c | 8 ++-
fs/xfs/xfs_bmap_util.c | 9 +--
fs/xfs/xfs_file.c | 24 +++----
fs/xfs/xfs_iops.c | 56 +--------------
fs/xfs/xfs_iops.h | 1 -
fs/xfs/xfs_mount.c | 3 +-
fs/xfs/xfs_pnfs.c | 9 ++-
fs/xfs/xfs_qm.c | 9 ++-
include/drm/drm_bridge.h | 4 +-
include/linux/fs.h | 5 +-
include/linux/hid.h | 3 +
include/linux/netdevice.h | 6 +-
include/linux/sh_intc.h | 5 +-
include/linux/tracepoint.h | 15 ++--
io_uring/io_uring.c | 4 +-
kernel/trace/ftrace.c | 3 +-
kernel/trace/trace.c | 2 +
kernel/trace/trace_events_hist.c | 3 +
mm/huge_memory.c | 6 +-
net/ipv4/fib_frontend.c | 3 +
net/ipv4/ip_tunnel.c | 12 ++--
net/ipv4/tcp_output.c | 2 +-
net/ipv6/ip6_tunnel.c | 4 +-
net/iucv/iucv.c | 2 +-
net/mptcp/subflow.c | 1 -
net/netfilter/nft_masq.c | 2 +-
net/netfilter/nft_nat.c | 2 +-
net/netfilter/nft_redir.c | 4 +-
net/smc/smc_cdc.c | 3 +
net/smc/smc_core.c | 2 +-
net/xfrm/xfrm_state.c | 3 -
sound/hda/intel-dsp-config.c | 9 +++
sound/pci/hda/hda_intel.c | 5 +-
sound/pci/hda/patch_realtek.c | 1 +
tools/testing/selftests/net/devlink_port_split.py | 30 ++++++++
111 files changed, 743 insertions(+), 360 deletions(-)




2023-03-20 15:12:09

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.10 59/99] firmware: xilinx: dont make a sleepable memory allocation from an atomic context

From: Roman Gushchin <[email protected]>

commit 38ed310c22e7a0fc978b1f8292136a4a4a8b3051 upstream.

The following issue was discovered using lockdep:
[ 6.691371] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:209
[ 6.694602] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0
[ 6.702431] 2 locks held by swapper/0/1:
[ 6.706300] #0: ffffff8800f6f188 (&dev->mutex){....}-{3:3}, at: __device_driver_lock+0x4c/0x90
[ 6.714900] #1: ffffffc009a2abb8 (enable_lock){....}-{2:2}, at: clk_enable_lock+0x4c/0x140
[ 6.723156] irq event stamp: 304030
[ 6.726596] hardirqs last enabled at (304029): [<ffffffc008d17ee0>] _raw_spin_unlock_irqrestore+0xc0/0xd0
[ 6.736142] hardirqs last disabled at (304030): [<ffffffc00876bc5c>] clk_enable_lock+0xfc/0x140
[ 6.744742] softirqs last enabled at (303958): [<ffffffc0080904f0>] _stext+0x4f0/0x894
[ 6.752655] softirqs last disabled at (303951): [<ffffffc0080e53b8>] irq_exit+0x238/0x280
[ 6.760744] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G U 5.15.36 #2
[ 6.768048] Hardware name: xlnx,zynqmp (DT)
[ 6.772179] Call trace:
[ 6.774584] dump_backtrace+0x0/0x300
[ 6.778197] show_stack+0x18/0x30
[ 6.781465] dump_stack_lvl+0xb8/0xec
[ 6.785077] dump_stack+0x1c/0x38
[ 6.788345] ___might_sleep+0x1a8/0x2a0
[ 6.792129] __might_sleep+0x6c/0xd0
[ 6.795655] kmem_cache_alloc_trace+0x270/0x3d0
[ 6.800127] do_feature_check_call+0x100/0x220
[ 6.804513] zynqmp_pm_invoke_fn+0x8c/0xb0
[ 6.808555] zynqmp_pm_clock_getstate+0x90/0xe0
[ 6.813027] zynqmp_pll_is_enabled+0x8c/0x120
[ 6.817327] zynqmp_pll_enable+0x38/0xc0
[ 6.821197] clk_core_enable+0x144/0x400
[ 6.825067] clk_core_enable+0xd4/0x400
[ 6.828851] clk_core_enable+0xd4/0x400
[ 6.832635] clk_core_enable+0xd4/0x400
[ 6.836419] clk_core_enable+0xd4/0x400
[ 6.840203] clk_core_enable+0xd4/0x400
[ 6.843987] clk_core_enable+0xd4/0x400
[ 6.847771] clk_core_enable+0xd4/0x400
[ 6.851555] clk_core_enable_lock+0x24/0x50
[ 6.855683] clk_enable+0x24/0x40
[ 6.858952] fclk_probe+0x84/0xf0
[ 6.862220] platform_probe+0x8c/0x110
[ 6.865918] really_probe+0x110/0x5f0
[ 6.869530] __driver_probe_device+0xcc/0x210
[ 6.873830] driver_probe_device+0x64/0x140
[ 6.877958] __driver_attach+0x114/0x1f0
[ 6.881828] bus_for_each_dev+0xe8/0x160
[ 6.885698] driver_attach+0x34/0x50
[ 6.889224] bus_add_driver+0x228/0x300
[ 6.893008] driver_register+0xc0/0x1e0
[ 6.896792] __platform_driver_register+0x44/0x60
[ 6.901436] fclk_driver_init+0x1c/0x28
[ 6.905220] do_one_initcall+0x104/0x590
[ 6.909091] kernel_init_freeable+0x254/0x2bc
[ 6.913390] kernel_init+0x24/0x130
[ 6.916831] ret_from_fork+0x10/0x20

Fix it by passing the GFP_ATOMIC gfp flag for the corresponding
memory allocation.

Fixes: acfdd18591ea ("firmware: xilinx: Use hash-table for api feature check")
Cc: stable <[email protected]>
Signed-off-by: Roman Gushchin <[email protected]>
Cc: Amit Sunil Dhamne <[email protected]>
Cc: Michal Simek <[email protected]>
Cc: [email protected]
Cc: [email protected]
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/firmware/xilinx/zynqmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/firmware/xilinx/zynqmp.c
+++ b/drivers/firmware/xilinx/zynqmp.c
@@ -171,7 +171,7 @@ static int zynqmp_pm_feature(u32 api_id)
}

/* Add new entry if not present */
- feature_data = kmalloc(sizeof(*feature_data), GFP_KERNEL);
+ feature_data = kmalloc(sizeof(*feature_data), GFP_ATOMIC);
if (!feature_data)
return -ENOMEM;




2023-03-20 17:23:32

by Chris Paterson

[permalink] [raw]
Subject: RE: [PATCH 5.10 00/99] 5.10.176-rc1 review

Hello Greg,

> From: Greg Kroah-Hartman <[email protected]>
> Sent: 20 March 2023 14:54
>
> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
> Anything received after that time might be too late.

CIP configurations built and booted with Linux 5.10.176-rc1 (1686e1df6521):
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/812172029
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-5.10.y

Tested-by: Chris Paterson (CIP) <[email protected]>

Kind regards, Chris

2023-03-20 19:30:29

by Florian Fainelli

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

On 3/20/23 07:53, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.176-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on
BMIPS_GENERIC:

Tested-by: Florian Fainelli <[email protected]>
--
Florian


2023-03-20 19:44:48

by Pavel Machek

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

Hi!

> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>

> David Gow <[email protected]>
> rust: arch/um: Disable FP/SIMD instruction to match x86

Why is this patch here? It does not make sense for stable, it was only
in AUTOSEL for less than a week, and I already explained why it is
bad.

"git grep KBUILD_RUSTFLAGS" if in doubt.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Attachments:
(No filename) (698.00 B)
signature.asc (195.00 B)
Download all attachments

2023-03-20 20:30:14

by Naresh Kamboju

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

On Mon, 20 Mar 2023 at 20:26, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.176-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.

Tested-by: Linux Kernel Functional Testing <[email protected]>

## Build
* kernel: 5.10.176-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-5.10.y
* git commit: 1686e1df652191033a9fc46dc7cf43cd169baa1a
* git describe: v5.10.175-100-g1686e1df6521
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.175-100-g1686e1df6521

## Test Regressions (compared to v5.10.175)

## Metric Regressions (compared to v5.10.175)

## Test Fixes (compared to v5.10.175)

## Metric Fixes (compared to v5.10.175)

## Test result summary
total: 92521, pass: 75087, fail: 2264, skip: 14957, xfail: 213

## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 115 total, 114 passed, 1 failed
* arm64: 42 total, 39 passed, 3 failed
* i386: 33 total, 31 passed, 2 failed
* mips: 27 total, 26 passed, 1 failed
* parisc: 8 total, 8 passed, 0 failed
* powerpc: 26 total, 20 passed, 6 failed
* riscv: 12 total, 11 passed, 1 failed
* s390: 12 total, 12 passed, 0 failed
* sh: 14 total, 12 passed, 2 failed
* sparc: 8 total, 8 passed, 0 failed
* x86_64: 36 total, 34 passed, 2 failed

## Test suites summary
* boot
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers-dma-buf
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-net-forwarding
* kselftest-net-mptcp
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kunit
* libgpiod
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* packetdrill
* perf
* rcutorture
* v4l2-compliance

--
Linaro LKFT
https://lkft.linaro.org

2023-03-20 23:08:30

by Shuah Khan

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

On 3/20/23 08:53, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.176-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>

Compiled and booted on my test system. No dmesg regressions.

Tested-by: Shuah Khan <[email protected]>

thanks,
-- Shuah

2023-03-21 04:08:23

by David Gow

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

On Tue, 21 Mar 2023 at 03:41, Pavel Machek <[email protected]> wrote:
>
> Hi!
>
> > This is the start of the stable review cycle for the 5.10.176 release.
> > There are 99 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
>
> > David Gow <[email protected]>
> > rust: arch/um: Disable FP/SIMD instruction to match x86
>
> Why is this patch here? It does not make sense for stable, it was only
> in AUTOSEL for less than a week, and I already explained why it is
> bad.
>
> "git grep KBUILD_RUSTFLAGS" if in doubt.

I agree: let's exclude this patch from -stable.

While the CFLAGS part of it is still _technically_ valid without Rust,
it turns out it triggers a bug in gcc <11, so is probably best
avoided. See:
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99652
- https://lore.kernel.org/linux-um/[email protected]/

Cheers,
-- David



>
> Best regards,
> Pavel
> --
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Attachments:
smime.p7s (3.91 kB)
S/MIME Cryptographic Signature

2023-03-21 07:43:57

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

On Tue, Mar 21, 2023 at 12:02:30PM +0800, David Gow wrote:
> On Tue, 21 Mar 2023 at 03:41, Pavel Machek <[email protected]> wrote:
> >
> > Hi!
> >
> > > This is the start of the stable review cycle for the 5.10.176 release.
> > > There are 99 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> >
> > > David Gow <[email protected]>
> > > rust: arch/um: Disable FP/SIMD instruction to match x86
> >
> > Why is this patch here? It does not make sense for stable, it was only
> > in AUTOSEL for less than a week, and I already explained why it is
> > bad.
> >
> > "git grep KBUILD_RUSTFLAGS" if in doubt.
>
> I agree: let's exclude this patch from -stable.
>
> While the CFLAGS part of it is still _technically_ valid without Rust,
> it turns out it triggers a bug in gcc <11, so is probably best
> avoided. See:
> - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99652
> - https://lore.kernel.org/linux-um/[email protected]/

Thanks, I've now dropped this from kernels 5.15 and older.

greg k-h

2023-03-21 11:56:06

by Jon Hunter

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review


On 20/03/2023 14:53, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.176-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

All tests passing for Tegra.

Tested-by: Jon Hunter <[email protected]>

Due to infrastructure issues, no test report available, but all tests
are passing.

Jon

--
nvpublic

2023-03-21 23:40:14

by Guenter Roeck

[permalink] [raw]
Subject: Re: [PATCH 5.10 00/99] 5.10.176-rc1 review

On Mon, Mar 20, 2023 at 03:53:38PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.176 release.
> There are 99 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Wed, 22 Mar 2023 14:54:22 +0000.
> Anything received after that time might be too late.
>

Build results:
total: 162 pass: 162 fail: 0
Qemu test results:
total: 485 pass: 485 fail: 0

Tested-by: Guenter Roeck <[email protected]>

Guenter