2023-10-09 13:16:28

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 6.1 000/162] 6.1.57-rc1 review

This is the start of the stable review cycle for the 6.1.57 release.
There are 162 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, 11 Oct 2023 13:00:55 +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.57-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.57-rc1

Jakub Kicinski <[email protected]>
netlink: remove the flex array from struct nlmsghdr

Filipe Manana <[email protected]>
btrfs: fix fscrypt name leak after failure to join log transaction

Christophe JAILLET <[email protected]>
btrfs: fix an error handling path in btrfs_rename()

Ido Schimmel <[email protected]>
vrf: Fix lockdep splat in output path

Eric Dumazet <[email protected]>
ipv6: remove nexthop_fib6_nh_bh()

John David Anglin <[email protected]>
parisc: Restore __ldcw_align for PA-RISC 2.0 processors

luosili <[email protected]>
ksmbd: fix uaf in smb20_oplock_break_ack

Namjae Jeon <[email protected]>
ksmbd: fix race condition between session lookup and expire

Tom Lendacky <[email protected]>
x86/sev: Use the GHCB protocol when available for SNP CPUID requests

Kailang Yang <[email protected]>
ALSA: hda/realtek - Fixed two speaker platform

Colin Ian King <[email protected]>
ALSA: hda/realtek: Fix spelling mistake "powe" -> "power"

Shay Drory <[email protected]>
RDMA/mlx5: Fix NULL string error

Hamdan Igbaria <[email protected]>
RDMA/mlx5: Fix mutex unlocking on error flow for steering anchor creation

Bernard Metzler <[email protected]>
RDMA/siw: Fix connection failure handling

Bart Van Assche <[email protected]>
RDMA/srp: Do not call scsi_done() from srp_abort()

Konstantin Meskhidze <[email protected]>
RDMA/uverbs: Fix typo of sizeof argument

Leon Romanovsky <[email protected]>
RDMA/cma: Fix truncation compilation warning in make_cma_ports

Mark Zhang <[email protected]>
RDMA/cma: Initialize ib_sa_multicast structure to 0 when join

Duje Mihanović <[email protected]>
gpio: pxa: disable pinctrl calls for MMP_GPIO

Bartosz Golaszewski <[email protected]>
gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config()

Christophe JAILLET <[email protected]>
IB/mlx4: Fix the size of a buffer in add_port_entries()

Dan Carpenter <[email protected]>
of: dynamic: Fix potential memory leak in of_changeset_action()

Leon Romanovsky <[email protected]>
RDMA/core: Require admin capabilities to set system parameters

Fedor Pchelkin <[email protected]>
dm zoned: free dmz->ddev array in dmz_put_zoned_devices

Helge Deller <[email protected]>
parisc: Fix crash with nr_cpus=1 option

Jordan Rife <[email protected]>
smb: use kernel_connect() and kernel_bind()

Artem Bityutskiy <[email protected]>
intel_idle: add Emerald Rapids Xeon support

Srinivas Pandruvada <[email protected]>
HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit

Jiri Kosina <[email protected]>
HID: sony: remove duplicate NULL check before calling usb_free_urb()

Eric Dumazet <[email protected]>
netlink: annotate data-races around sk->sk_err

Tao Chen <[email protected]>
netlink: Fix potential skb memleak in netlink_ack

Jakub Kicinski <[email protected]>
netlink: split up copies in the ack construction

Xin Long <[email protected]>
sctp: update hb timer immediately after users change hb_interval

Xin Long <[email protected]>
sctp: update transport state when processing a dupcook packet

Neal Cardwell <[email protected]>
tcp: fix delayed ACKs for MSS boundary condition

Neal Cardwell <[email protected]>
tcp: fix quick-ack counting to count actual ACKs of new data

Chengfeng Ye <[email protected]>
tipc: fix a potential deadlock on &tx->lock

Ben Wolsieffer <[email protected]>
net: stmmac: dwmac-stm32: fix resume on STM32 MCU

Benjamin Poirier <[email protected]>
ipv4: Set offload_failed flag in fibmatch results

Florian Westphal <[email protected]>
netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure

Phil Sutter <[email protected]>
netfilter: nf_tables: Deduplicate nft_register_obj audit logs

Phil Sutter <[email protected]>
selftests: netfilter: Extend nft_audit.sh

Phil Sutter <[email protected]>
selftests: netfilter: Test nf_tables audit logging

Xin Long <[email protected]>
netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp

David Wilder <[email protected]>
ibmveth: Remove condition to recompute TCP header checksum.

Dan Carpenter <[email protected]>
net: ethernet: ti: am65-cpsw: Fix error code in am65_cpsw_nuss_init_tx_chns()

Jeremy Cline <[email protected]>
net: nfc: llcp: Add lock when modifying device list

Shigeru Yoshida <[email protected]>
net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg

Ilya Maximets <[email protected]>
ipv6: tcp: add a missing nf_reset_ct() in 3WHS handling

Fabio Estevam <[email protected]>
net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent

Dinghao Liu <[email protected]>
ptp: ocp: Fix error handling in ptp_ocp_device_init

David Howells <[email protected]>
ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()

Eric Dumazet <[email protected]>
neighbour: fix data-races around n->output

Eric Dumazet <[email protected]>
neighbour: switch to standard rcu, instead of rcu_bh

Eric Dumazet <[email protected]>
neighbour: annotate lockless accesses to n->nud_state

Martin KaFai Lau <[email protected]>
bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup

Eric Dumazet <[email protected]>
net: fix possible store tearing in neigh_periodic_work()

Mauricio Faria de Oliveira <[email protected]>
modpost: add missing else to the "of" check

Jakub Sitnicki <[email protected]>
bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets

John Fastabend <[email protected]>
bpf, sockmap: Do not inc copied_seq when PEEK flag set

John Fastabend <[email protected]>
bpf: tcp_read_skb needs to pop skb regardless of seq

Trond Myklebust <[email protected]>
NFSv4: Fix a nfs4_state_manager() race

Arnd Bergmann <[email protected]>
ima: rework CONFIG_IMA dependency block

Junxiao Bi <[email protected]>
scsi: target: core: Fix deadlock due to recursive locking

Oleksandr Tymoshenko <[email protected]>
ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig

Michał Mirosław <[email protected]>
regulator/core: regulator_register: set device->class earlier

Yong Wu <[email protected]>
iommu/mediatek: Fix share pgtable for iova over 4GB

Breno Leitao <[email protected]>
perf/x86/amd: Do not WARN() on every IRQ

Johannes Berg <[email protected]>
wifi: mac80211: fix potential key use-after-free

Richard Fitzgerald <[email protected]>
regmap: rbtree: Fix wrong register marked as in-cache when creating new node

Sandipan Das <[email protected]>
perf/x86/amd/core: Fix overflow reset on hotplug

Felix Fietkau <[email protected]>
wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling

Alexandra Diupina <[email protected]>
drivers/net: process the result of hdlc_open() and add call of hdlc_close() in uhdlc_close()

Luiz Augusto von Dentz <[email protected]>
Bluetooth: ISO: Fix handling of listen for unicast

Yao Xiao <[email protected]>
Bluetooth: Delete unused hci_req_prepare_suspend() declaration

Chen-Yu Tsai <[email protected]>
regulator: mt6358: split ops for buck and linear range LDO regulators

Chen-Yu Tsai <[email protected]>
regulator: mt6358: Use linear voltage helpers for single range regulators

Chen-Yu Tsai <[email protected]>
regulator: mt6358: Drop *_SSHUB regulators

Leon Hwang <[email protected]>
bpf: Fix tr dereferencing

Marek Behún <[email protected]>
leds: Drop BUG_ON check for LED_COLOR_ID_MULTI

Pin-yen Lin <[email protected]>
wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet

Johannes Berg <[email protected]>
wifi: cfg80211: add missing kernel-doc for cqm_rssi_work

Johannes Berg <[email protected]>
wifi: cfg80211: fix cqm_config access race

Johannes Berg <[email protected]>
wifi: cfg80211: add a work abstraction with special semantics

Johannes Berg <[email protected]>
wifi: cfg80211: move wowlan disable under locks

Johannes Berg <[email protected]>
wifi: cfg80211: hold wiphy lock in auto-disconnect

Christophe JAILLET <[email protected]>
wifi: iwlwifi: mvm: Fix a memory corruption issue

Arnd Bergmann <[email protected]>
wifi: iwlwifi: dbg_ini: fix structure packing

Gao Xiang <[email protected]>
erofs: fix memory leak of LZMA global compressed deduplication

Zhihao Cheng <[email protected]>
ubi: Refuse attaching if mtd's erasesize is 0

Christophe JAILLET <[email protected]>
HID: sony: Fix a potential memory leak in sony_probe()

Rob Herring <[email protected]>
arm64: errata: Add Cortex-A520 speculative unprivileged load workaround

Rob Herring <[email protected]>
arm64: Add Cortex-A520 CPU part definition

Mario Limonciello <[email protected]>
drm/amd: Fix logic error in sienna_cichlid_update_pcie_parameters()

Mario Limonciello <[email protected]>
drm/amd: Fix detection of _PR3 on the PCIe root port

Jordan Rife <[email protected]>
net: prevent rewrite of msg_name in sock_sendmsg()

Qu Wenruo <[email protected]>
btrfs: reject unknown mount options early

Jordan Rife <[email protected]>
net: replace calls to sock->ops->connect() with kernel_connect()

Sricharan Ramabadhran <[email protected]>
PCI: qcom: Fix IPQ8074 enumeration

David Jeffery <[email protected]>
md/raid5: release batch_last before waiting for another stripe_head

Gustavo A. R. Silva <[email protected]>
wifi: mwifiex: Fix tlv_buf_left calculation

Luiz Augusto von Dentz <[email protected]>
Bluetooth: hci_sync: Fix handling of HCI_QUIRK_STRICT_DUPLICATE_FILTER

Luiz Augusto von Dentz <[email protected]>
Bluetooth: hci_codec: Fix leaking content of local_codecs

Gustavo A. R. Silva <[email protected]>
qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info

Geliang Tang <[email protected]>
mptcp: userspace pm allow creating id 0 subflow

Christian Marangi <[email protected]>
net: ethernet: mediatek: disable irq before schedule napi

Stefano Garzarella <[email protected]>
vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()

Zhang Rui <[email protected]>
iommu/vt-d: Avoid memory allocation in iommu_suspend()

Dinghao Liu <[email protected]>
scsi: zfcp: Fix a double put in zfcp_port_enqueue()

Yajun Deng <[email protected]>
i40e: fix the wrong PTP frequency calculation

Aleksandr Mezin <[email protected]>
hwmon: (nzxt-smart2) add another USB ID

Herman Fries <[email protected]>
hwmon: (nzxt-smart2) Add device id

Ming Lei <[email protected]>
block: fix use-after-free of q->q_usage_counter

Ilya Dryomov <[email protected]>
rbd: take header_rwsem in rbd_dev_refresh() only when updating

Ilya Dryomov <[email protected]>
rbd: decouple parent info read-in from updating rbd_dev

Ilya Dryomov <[email protected]>
rbd: decouple header read-in from updating rbd_dev->header

Ilya Dryomov <[email protected]>
rbd: move rbd_dev_refresh() definition

Robin Murphy <[email protected]>
iommu/arm-smmu-v3: Avoid constructing invalid range commands

Robin Murphy <[email protected]>
iommu/arm-smmu-v3: Set TTL invalidation hint better

Wayne Lin <[email protected]>
drm/amd/display: Adjust the MST resume flow

Kristina Martsenko <[email protected]>
arm64: cpufeature: Fix CLRBHB and BC detection

Patrick Rohr <[email protected]>
net: release reference to inet6_dev pointer

Patrick Rohr <[email protected]>
net: change accept_ra_min_rtr_lft to affect all RA lifetimes

Patrick Rohr <[email protected]>
net: add sysctl accept_ra_min_rtr_lft

Gabriel Krisman Bertazi <[email protected]>
arm64: Avoid repeated AA64MMFR1_EL1 register read on pagefault path

Benjamin Coddington <[email protected]>
Revert "NFSv4: Retry LOCK on OLD_STATEID during delegation return"

Sweet Tea Dorminy <[email protected]>
btrfs: use struct fscrypt_str instead of struct qstr

Sweet Tea Dorminy <[email protected]>
btrfs: setup qstr from dentrys using fscrypt helper

Sweet Tea Dorminy <[email protected]>
btrfs: use struct qstr instead of name and namelen pairs

Zheng Yejian <[email protected]>
ring-buffer: Fix bytes info in per_cpu buffer stats

Vlastimil Babka <[email protected]>
ring-buffer: remove obsolete comment for free_buffer_page()

Johannes Weiner <[email protected]>
mm: page_alloc: fix CMA and HIGHATOMIC landing on the wrong buddy list

Mel Gorman <[email protected]>
mm/page_alloc: leave IRQs enabled for per-cpu page allocations

Mel Gorman <[email protected]>
mm/page_alloc: always remove pages from temporary list

Yang Shi <[email protected]>
mm: mempolicy: keep VMA walk if both MPOL_MF_STRICT and MPOL_MF_MOVE are specified

Vishal Moola (Oracle) <[email protected]>
mm/mempolicy: convert migrate_page_add() to migrate_folio_add()

Vishal Moola (Oracle) <[email protected]>
mm/mempolicy: convert queue_pages_pte_range() to queue_folios_pte_range()

Vishal Moola (Oracle) <[email protected]>
mm/mempolicy: convert queue_pages_pmd() to queue_folios_pmd()

Vishal Moola (Oracle) <[email protected]>
mm/memory: add vm_normal_folio()

Trond Myklebust <[email protected]>
NFSv4: Fix a state manager thread deadlock regression

Benjamin Coddington <[email protected]>
NFS: rename nfs_client_kset to nfs_kset

Benjamin Coddington <[email protected]>
NFS: Cleanup unused rpc_clnt variable

Damien Le Moal <[email protected]>
ata: libata-scsi: Fix delayed scsi_rescan_device() execution

Damien Le Moal <[email protected]>
scsi: Do not attempt to rescan suspended devices

Bart Van Assche <[email protected]>
scsi: core: Improve type safety of scsi_rescan_device()

Damien Le Moal <[email protected]>
scsi: sd: Do not issue commands to suspended disks on shutdown

Damien Le Moal <[email protected]>
scsi: sd: Differentiate system and runtime start/stop management

Damien Le Moal <[email protected]>
ata,scsi: do not issue START STOP UNIT on resume

Paolo Abeni <[email protected]>
mptcp: process pending subflow error on close

Paolo Abeni <[email protected]>
mptcp: move __mptcp_error_report in protocol.c

Eric Dumazet <[email protected]>
mptcp: annotate lockless accesses to sk->sk_err

Paolo Abeni <[email protected]>
mptcp: fix dangling connection hang-up

Paolo Abeni <[email protected]>
mptcp: rename timer related helper to less confusing names

Sameer Pujar <[email protected]>
ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates

Sameer Pujar <[email protected]>
ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol

Kailang Yang <[email protected]>
ALSA: hda/realtek - ALC287 Realtek I2S speaker platform support

Kailang Yang <[email protected]>
ALSA: hda/realtek - ALC287 I2S speaker platform support

Fabian Vogt <[email protected]>
ALSA: hda/realtek: Add quirk for mute LEDs on HP ENVY x360 15-eu0xxx

SungHwan Jung <[email protected]>
ALSA: hda/realtek: Add quirk for HP Victus 16-d1xxx to enable mute LED

Shenghao Ding <[email protected]>
ALSA: hda/tas2781: Add tas2781 HDA driver

Johan Hovold <[email protected]>
spi: zynqmp-gqspi: fix clock imbalance on probe failure

Uwe Kleine-König <[email protected]>
spi: zynqmp-gqspi: Convert to platform remove callback returning void


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

Diffstat:

Documentation/arm64/silicon-errata.rst | 2 +
Documentation/networking/ip-sysctl.rst | 8 +
Makefile | 4 +-
arch/arm64/Kconfig | 13 +
arch/arm64/include/asm/cpufeature.h | 8 +-
arch/arm64/include/asm/cputype.h | 2 +
arch/arm64/kernel/cpu_errata.c | 8 +
arch/arm64/kernel/cpufeature.c | 3 +-
arch/arm64/kernel/entry.S | 4 +
arch/arm64/tools/cpucaps | 1 +
arch/arm64/tools/sysreg | 6 +-
arch/parisc/include/asm/ldcw.h | 36 +-
arch/parisc/include/asm/spinlock_types.h | 5 -
arch/parisc/kernel/smp.c | 4 +-
arch/x86/events/amd/core.c | 24 +-
arch/x86/kernel/sev-shared.c | 69 +++-
block/blk-sysfs.c | 3 +-
drivers/ata/libata-core.c | 16 +
drivers/ata/libata-scsi.c | 43 ++-
drivers/base/regmap/regcache-rbtree.c | 3 +-
drivers/block/rbd.c | 412 +++++++++++----------
drivers/firewire/sbp2.c | 9 +-
drivers/gpio/gpio-aspeed.c | 2 +-
drivers/gpio/gpio-pxa.c | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 +-
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 93 ++++-
.../drm/amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 41 +-
drivers/hid/hid-sony.c | 2 +
drivers/hid/intel-ish-hid/ipc/pci-ish.c | 8 +
drivers/hwmon/nzxt-smart2.c | 2 +
drivers/idle/intel_idle.c | 2 +
drivers/infiniband/core/cma.c | 2 +-
drivers/infiniband/core/cma_configfs.c | 2 +-
drivers/infiniband/core/nldev.c | 1 +
drivers/infiniband/core/uverbs_main.c | 2 +-
drivers/infiniband/hw/mlx4/sysfs.c | 2 +-
drivers/infiniband/hw/mlx5/fs.c | 2 +-
drivers/infiniband/hw/mlx5/main.c | 2 +-
drivers/infiniband/sw/siw/siw_cm.c | 16 +-
drivers/infiniband/ulp/srp/ib_srp.c | 16 +-
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 18 +-
drivers/iommu/intel/iommu.c | 16 -
drivers/iommu/intel/iommu.h | 2 +-
drivers/iommu/mtk_iommu.c | 9 +-
drivers/leds/led-core.c | 4 -
drivers/md/dm-zoned-target.c | 15 +-
drivers/md/raid5.c | 7 +
drivers/mtd/ubi/build.c | 7 +
drivers/net/dsa/mv88e6xxx/chip.c | 6 +-
drivers/net/dsa/mv88e6xxx/global1.c | 31 --
drivers/net/dsa/mv88e6xxx/global1.h | 1 -
drivers/net/dsa/mv88e6xxx/global2.c | 2 +-
drivers/net/dsa/mv88e6xxx/global2.h | 1 +
drivers/net/ethernet/ibm/ibmveth.c | 25 +-
drivers/net/ethernet/intel/i40e/i40e_ptp.c | 4 +-
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 4 +-
drivers/net/ethernet/qlogic/qed/qed_ll2.h | 2 +-
drivers/net/ethernet/stmicro/stmmac/dwmac-stm32.c | 7 +-
drivers/net/ethernet/ti/am65-cpsw-nuss.c | 1 +
drivers/net/usb/smsc75xx.c | 4 +-
drivers/net/vrf.c | 12 +-
drivers/net/vxlan/vxlan_core.c | 4 +-
drivers/net/wan/fsl_ucc_hdlc.c | 12 +-
drivers/net/wireless/intel/iwlwifi/fw/error-dump.h | 6 +-
drivers/net/wireless/intel/iwlwifi/mvm/fw.c | 2 +-
.../net/wireless/marvell/mwifiex/11n_rxreorder.c | 4 +-
drivers/net/wireless/marvell/mwifiex/sta_rx.c | 16 +-
.../net/wireless/mediatek/mt76/mt76x02_eeprom.c | 7 -
drivers/net/wireless/mediatek/mt76/mt76x2/eeprom.c | 13 +-
drivers/of/dynamic.c | 6 +-
drivers/pci/controller/dwc/pcie-qcom.c | 4 +-
drivers/ptp/ptp_ocp.c | 1 -
drivers/regulator/core.c | 4 +-
drivers/regulator/mt6358-regulator.c | 153 +++-----
drivers/s390/scsi/zfcp_aux.c | 9 +-
drivers/scsi/aacraid/commsup.c | 2 +-
drivers/scsi/mvumi.c | 2 +-
drivers/scsi/scsi_lib.c | 2 +-
drivers/scsi/scsi_priv.h | 1 -
drivers/scsi/scsi_scan.c | 20 +-
drivers/scsi/scsi_sysfs.c | 4 +-
drivers/scsi/sd.c | 110 ++++--
drivers/scsi/sd.h | 1 +
drivers/scsi/smartpqi/smartpqi_init.c | 2 +-
drivers/scsi/storvsc_drv.c | 2 +-
drivers/scsi/virtio_scsi.c | 2 +-
drivers/spi/spi-zynqmp-gqspi.c | 18 +-
drivers/target/target_core_device.c | 11 +-
drivers/vhost/vringh.c | 12 +-
fs/btrfs/ctree.h | 28 +-
fs/btrfs/dir-item.c | 50 ++-
fs/btrfs/inode-item.c | 73 ++--
fs/btrfs/inode-item.h | 20 +-
fs/btrfs/inode.c | 267 ++++++++-----
fs/btrfs/ioctl.c | 7 +-
fs/btrfs/root-tree.c | 19 +-
fs/btrfs/send.c | 12 +-
fs/btrfs/super.c | 7 +-
fs/btrfs/transaction.c | 40 +-
fs/btrfs/tree-log.c | 279 +++++++-------
fs/btrfs/tree-log.h | 4 +-
fs/erofs/decompressor_lzma.c | 5 +-
fs/nfs/nfs4proc.c | 10 +-
fs/nfs/nfs4state.c | 47 ++-
fs/nfs/sysfs.c | 16 +-
fs/smb/client/connect.c | 10 +-
fs/smb/server/connection.c | 2 +
fs/smb/server/connection.h | 1 +
fs/smb/server/mgmt/user_session.c | 10 +-
fs/smb/server/smb2pdu.c | 4 +-
include/linux/bpf.h | 2 +-
include/linux/ipv6.h | 1 +
include/linux/mm.h | 2 +
include/linux/netfilter/nf_conntrack_sctp.h | 1 +
include/linux/regulator/mt6358-regulator.h | 4 -
include/net/arp.h | 8 +-
include/net/cfg80211.h | 99 ++++-
include/net/ndisc.h | 12 +-
include/net/neighbour.h | 10 +-
include/net/netlink.h | 21 ++
include/net/nexthop.h | 23 --
include/net/tcp.h | 6 +-
include/scsi/scsi_device.h | 6 +-
include/scsi/scsi_host.h | 2 +-
include/uapi/linux/bpf.h | 6 +
include/uapi/linux/ipv6.h | 1 +
kernel/trace/ring_buffer.c | 32 +-
mm/memory.c | 10 +
mm/mempolicy.c | 122 +++---
mm/page_alloc.c | 138 ++++---
net/bluetooth/hci_core.c | 1 +
net/bluetooth/hci_event.c | 1 +
net/bluetooth/hci_request.h | 2 -
net/bluetooth/hci_sync.c | 14 +-
net/bluetooth/iso.c | 9 +-
net/bridge/br_arp_nd_proxy.c | 4 +-
net/bridge/br_netfilter_hooks.c | 5 +-
net/core/filter.c | 59 +--
net/core/neighbour.c | 106 +++---
net/core/sock_map.c | 4 +
net/ipv4/arp.c | 8 +-
net/ipv4/fib_semantics.c | 8 +-
net/ipv4/ip_output.c | 6 +-
net/ipv4/nexthop.c | 12 +-
net/ipv4/route.c | 8 +-
net/ipv4/tcp.c | 10 +-
net/ipv4/tcp_bpf.c | 4 +-
net/ipv4/tcp_input.c | 13 +
net/ipv4/tcp_output.c | 7 +-
net/ipv6/addrconf.c | 27 +-
net/ipv6/ip6_fib.c | 16 +-
net/ipv6/ip6_output.c | 12 +-
net/ipv6/ndisc.c | 17 +-
net/ipv6/route.c | 14 +-
net/ipv6/tcp_ipv6.c | 10 +-
net/l2tp/l2tp_ip6.c | 2 +-
net/mac80211/cfg.c | 3 +
net/mac80211/key.c | 2 +-
net/mptcp/pm_netlink.c | 2 +-
net/mptcp/pm_userspace.c | 6 -
net/mptcp/protocol.c | 177 +++++----
net/mptcp/protocol.h | 24 +-
net/mptcp/subflow.c | 41 +-
net/netfilter/ipvs/ip_vs_sync.c | 4 +-
net/netfilter/nf_conntrack_proto_sctp.c | 43 ++-
net/netfilter/nf_tables_api.c | 44 ++-
net/netfilter/nft_set_rbtree.c | 46 ++-
net/netlink/af_netlink.c | 37 +-
net/nfc/llcp_core.c | 2 +
net/rds/tcp_connect.c | 2 +-
net/sctp/associola.c | 3 +-
net/sctp/socket.c | 1 +
net/socket.c | 29 +-
net/tipc/crypto.c | 4 +-
net/wireless/core.c | 150 +++++++-
net/wireless/core.h | 14 +-
net/wireless/nl80211.c | 93 +++--
net/wireless/sme.c | 4 +-
net/wireless/sysfs.c | 8 +-
scripts/mod/file2alias.c | 2 +-
security/integrity/ima/Kconfig | 22 +-
sound/pci/hda/patch_realtek.c | 154 +++++++-
sound/soc/soc-utils.c | 1 +
sound/soc/tegra/tegra_audio_graph_card.c | 30 +-
tools/include/uapi/linux/bpf.h | 6 +
tools/testing/selftests/netfilter/.gitignore | 1 +
tools/testing/selftests/netfilter/Makefile | 4 +-
tools/testing/selftests/netfilter/audit_logread.c | 165 +++++++++
tools/testing/selftests/netfilter/config | 1 +
tools/testing/selftests/netfilter/nft_audit.sh | 193 ++++++++++
190 files changed, 2961 insertions(+), 1642 deletions(-)



2023-10-09 18:44:48

by SeongJae Park

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hello,

On Mon, 9 Oct 2023 14:59:41 +0200 Greg Kroah-Hartman <[email protected]> wrote:

> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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.

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].

Tested-by: SeongJae Park <[email protected]>

[1] https://github.com/awslabs/damon-tests/tree/next/corr
[2] 282079f8e407 ("Linux 6.1.57-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
_remote_run_corr.sh SUCCESS

2023-10-09 20:44:11

by Naresh Kamboju

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Mon, 9 Oct 2023 at 18:46, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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


The following kernel warnings were noticed several times on arm x15 devices
running stable-rc 6.1.57-rc1 while running selftests: net: mptcp_connect.sh
and netfilter: nft_fib.sh.

The possible unsafe locking scenario detected.

FYI,
Stable-rc/ linux.6.1.y kernel running stable/ linux.6.5.y selftest in this case.

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

kselftest: Running tests in net/mptcp
TAP version 13
1..7
# timeout set to 1200
# selftests: net/mptcp: mptcp_connect.sh
[ 80.093261] IPv6: ADDRCONF(NETDEV_CHANGE): ns1eth2: link becomes ready
[ 80.449707] IPv6: ADDRCONF(NETDEV_CHANGE): ns2eth3: link becomes ready
[ 80.770538] IPv6: ADDRCONF(NETDEV_CHANGE): ns2eth1: link becomes ready
[ 80.826141] IPv6: ADDRCONF(NETDEV_CHANGE): ns4eth3: link becomes ready
[ 80.833465] IPv6: ADDRCONF(NETDEV_CHANGE): ns3eth4: link becomes ready
# INFO: set ns4-64ac7c08-UbLqmM dev ns4eth3: ethtool -K gso off
# Created /tmp/tmp.de3ILrgEEm (size 375836 /tmp/tmp.de3ILrgEEm)
containing data sent by client
# Created /tmp/tmp.YGH83JN29o (size 8315932 /tmp/tmp.YGH83JN29o)
containing data sent by server
# New MPTCP socket can be blocked via sysctl [ OK ]
# INFO: validating network environment with pings
[ 82.468353]
[ 82.469848] ================================
[ 82.474151] WARNING: inconsistent lock state
[ 82.478454] 6.1.57-rc1 #1 Not tainted
[ 82.482116] --------------------------------
[ 82.486419] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-R} usage.
[ 82.492431] ping/1924 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 82.497436] c9a58224 (&n->lock){++-?}-{2:2}, at: rt6_score_route+0xd8/0x1e0
[ 82.504455] {IN-SOFTIRQ-W} state was registered at:
[ 82.509368] _raw_write_lock_bh+0x48/0x58
[ 82.513488] __neigh_update+0x74/0xe48
[ 82.517333] neigh_update+0x24/0x2c
[ 82.520935] ndisc_rcv+0x4c4/0x1440
[ 82.524536] icmpv6_rcv+0x604/0x810
[ 82.528137] ip6_protocol_deliver_rcu+0x9c/0x9ac
[ 82.532867] ip6_input_finish+0xa0/0x18c
[ 82.536895] ip6_mc_input+0x148/0x3d0
[ 82.540679] __netif_receive_skb_one_core+0x58/0x74
[ 82.545654] process_backlog+0x138/0x300
[ 82.549713] __napi_poll+0x34/0x258
[ 82.553283] net_rx_action+0x160/0x350
[ 82.557159] __do_softirq+0x1b8/0x4dc
[ 82.560913] call_with_stack+0x18/0x20
[ 82.564788] do_softirq+0xb0/0xb4
[ 82.568206] __local_bh_enable_ip+0x180/0x1b8
[ 82.572662] __dev_queue_xmit+0x3bc/0x12d0
[ 82.576873] ip6_finish_output2+0x178/0xb80
[ 82.581176] ip6_finish_output+0x1c8/0x48c
[ 82.585388] ndisc_send_skb+0x4d8/0x8c0
[ 82.589324] addrconf_dad_completed+0xd8/0x3b0
[ 82.593872] addrconf_dad_work+0x208/0x56c
[ 82.598083] process_one_work+0x26c/0x6a0
[ 82.602203] worker_thread+0x60/0x4e8
[ 82.605987] kthread+0xfc/0x11c
[ 82.609222] ret_from_fork+0x14/0x28
[ 82.612915] irq event stamp: 18041
[ 82.616333] hardirqs last enabled at (18041): [<c035a990>]
__local_bh_enable_ip+0xcc/0x1b8
[ 82.624725] hardirqs last disabled at (18039): [<c035aa0c>]
__local_bh_enable_ip+0x148/0x1b8
[ 82.633178] softirqs last enabled at (18040): [<c14fc510>]
ip6_datagram_connect+0x20/0x44
[ 82.641510] softirqs last disabled at (18038): [<c1306cc8>]
lock_sock_nested+0x4c/0x7c
[ 82.649475]
[ 82.649475] other info that might help us debug this:
[ 82.656036] Possible unsafe locking scenario:
[ 82.656036]
[ 82.661956] CPU0
[ 82.664428] ----
[ 82.666870] lock(&n->lock);
[ 82.669860] <Interrupt>
[ 82.672485] lock(&n->lock);
[ 82.675659]
[ 82.675659] *** DEADLOCK ***
[ 82.675659]
[ 82.681610] 4 locks held by ping/1924:
[ 82.685363] #0: c9ab0110 (sk_lock-AF_INET6){+.+.}-{0:0}, at:
ip6_datagram_connect+0x20/0x44
[ 82.693878] #1: c24a62f8 (rcu_read_lock){....}-{1:2}, at:
ip6_route_output_flags+0x0/0x1f4
[ 82.702301] #2: c24a62f8 (rcu_read_lock){....}-{1:2}, at:
ip6_pol_route+0x60/0x718
[ 82.709991] #3: c24a62f8 (rcu_read_lock){....}-{1:2}, at:
rt6_score_route+0x78/0x1e0
[ 82.717895]
[ 82.717895] stack backtrace:
[ 82.722259] CPU: 1 PID: 1924 Comm: ping Not tainted 6.1.57-rc1 #1
[ 82.728393] Hardware name: Generic DRA74X (Flattened Device Tree)
[ 82.734527] unwind_backtrace from show_stack+0x18/0x1c
[ 82.739776] show_stack from dump_stack_lvl+0x58/0x70
[ 82.744873] dump_stack_lvl from mark_lock.part.0+0xb74/0x128c
[ 82.750732] mark_lock.part.0 from __lock_acquire+0x3d8/0x2aa4
[ 82.756591] __lock_acquire from lock_acquire+0x110/0x334
[ 82.762023] lock_acquire from _raw_read_lock+0x64/0x74
[ 82.767272] _raw_read_lock from rt6_score_route+0xd8/0x1e0
[ 82.772888] rt6_score_route from find_match.part.0+0x6c/0x4d4
[ 82.778747] find_match.part.0 from __find_rr_leaf+0xb8/0x430
[ 82.784515] __find_rr_leaf from fib6_table_lookup+0x234/0x46c
[ 82.790405] fib6_table_lookup from ip6_pol_route+0xd0/0x718
[ 82.796081] ip6_pol_route from ip6_pol_route_output+0x2c/0x34
[ 82.801940] ip6_pol_route_output from fib6_rule_lookup+0xb4/0x1e4
[ 82.808166] fib6_rule_lookup from ip6_route_output_flags_noref+0xbc/0x110
[ 82.815063] ip6_route_output_flags_noref from
ip6_route_output_flags+0x78/0x1f4
[ 82.822509] ip6_route_output_flags from ip6_dst_lookup_tail+0xa8/0x7b0
[ 82.829162] ip6_dst_lookup_tail from ip6_dst_lookup_flow+0x40/0x90
[ 82.835479] ip6_dst_lookup_flow from ip6_datagram_dst_update+0x18c/0x3d4
[ 82.842315] ip6_datagram_dst_update from __ip6_datagram_connect+0x234/0x4b0
[ 82.849395] __ip6_datagram_connect from ip6_datagram_connect+0x30/0x44
[ 82.856048] ip6_datagram_connect from __sys_connect+0xc4/0xd8
[ 82.861907] __sys_connect from ret_fast_syscall+0x0/0x1c
[ 82.867340] Exception stack(0xf0441fa8 to 0xf0441ff0)
[ 82.872436] 1fa0: 004e2208 004e0208 00000006
004e2524 0000001c 00000001
[ 82.880645] 1fc0: 004e2208 004e0208 bec08828 0000011b 004e3544
00000000 00000006 00000000
[ 82.888854] 1fe0: 0000011b bec08778 b6efe83b b6e67616
# INFO: Using loss of 0.16% delay 24 ms reorder 96% 19% with delay 6ms
on ns3eth4
...
# ns1 TCP -> ns1 (dead:beef:1::1:10053) MPTCP (duration 242ms) [ OK ]
# INFO: TFO not supported by the kernel: SKIP
# INFO: test tproxy ipv4
# ns1 MPTCP -> ns2 (10.0.3.1:20000 ) MPTCP (duration 412ms) [ OK ]
# PASS: tproxy ipv4
# INFO: test tproxy ipv6
# ns1 MPTCP -> ns2 (dead:beef:3::1:20000) MPTCP (duration 323ms) [ OK ]
# PASS: tproxy ipv6
# INFO: disconnect
# ns1 MPTCP -> ns1 (10.0.1.1:20001 ) MPTCP (duration 198ms) [ OK ]
# ns1 MPTCP -> ns1 (10.0.1.1:20002 ) TCP (duration 91ms) [ OK ]
# ns1 TCP -> ns1 (10.0.1.1:20003 ) MPTCP (duration 88ms) [ OK ]
# ns1 MPTCP -> ns1 (dead:beef:1::1:20004) MPTCP (duration 147ms) [ OK ]
# ns1 MPTCP -> ns1 (dead:beef:1::1:20005) TCP (duration 95ms) [ OK ]
# ns1 TCP -> ns1 (dead:beef:1::1:20006) MPTCP (duration 83ms) [ OK ]
# Time: 88 seconds
ok 1 selftests: net/mptcp: mptcp_connect.sh



And on other instance,

[ 77.366607] kselftest: Running tests in netfilter
TAP version 13
1..14
# timeout set to 120
# selftests: netfilter: nft_fib.sh
# /dev/stdin:4:10-28: Error: Could not process rule: No such file or directory
# fib saddr . iif oif missing counter log prefix
\"nsrouter-TgCmRmhz nft_rpfilter: \" drop
# ^^^^^^^^^^^^^^^^^^^
# /dev/stdin:4:10-28: Error: Could not process rule: No such file or directory
# fib saddr . iif oif missing counter log prefix
\"ns1-TgCmRmhz nft_rpfilter: \" drop
# ^^^^^^^^^^^^^^^^^^^
# /dev/stdin:4:10-28: Error: Could not process rule: No such file or directory
# fib saddr . iif oif missing counter log prefix
\"ns2-TgCmRmhz nft_rpfilter: \" drop
# ^^^^^^^^^^^^^^^^^^^
[ 79.492797] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
[ 79.567138] IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
[ 80.175903] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 84.184631]
[ 84.186157] ================================
[ 84.190429] WARNING: inconsistent lock state
[ 84.194732] 6.1.57-rc1 #1 Not tainted
[ 84.198425] --------------------------------
[ 84.202697] inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-R} usage.
[ 84.208740] ping/582 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 84.213653] c85b0e24 (&n->lock){++-?}-{2:2}, at: rt6_score_route+0xd8/0x1e0
[ 84.220703] {IN-SOFTIRQ-W} state was registered at:
[ 84.225616] _raw_write_lock_bh+0x48/0x58
[ 84.229736] __neigh_update+0x74/0xe48
[ 84.233612] neigh_update+0x24/0x2c
[ 84.237213] ndisc_rcv+0x4c4/0x1440
[ 84.240814] icmpv6_rcv+0x604/0x810
[ 84.244415] ip6_protocol_deliver_rcu+0x9c/0x9ac
[ 84.249145] ip6_input_finish+0xa0/0x18c
[ 84.253204] ip6_mc_input+0x148/0x3d0
[ 84.256958] __netif_receive_skb_one_core+0x58/0x74
[ 84.261962] process_backlog+0x138/0x300
[ 84.266021] __napi_poll+0x34/0x258
[ 84.269622] net_rx_action+0x160/0x350
[ 84.273468] __do_softirq+0x1b8/0x4dc
[ 84.277252] call_with_stack+0x18/0x20
[ 84.281127] do_softirq+0xb0/0xb4
[ 84.284545] __local_bh_enable_ip+0x180/0x1b8
[ 84.289001] __dev_queue_xmit+0x3bc/0x12d0
[ 84.293212] ip6_finish_output2+0x178/0xb80
[ 84.297515] ip6_finish_output+0x1c8/0x48c
[ 84.301727] ndisc_send_skb+0x4d8/0x8c0
[ 84.305694] addrconf_dad_completed+0xd8/0x3b0
[ 84.310241] addrconf_dad_work+0x208/0x56c
[ 84.314453] process_one_work+0x26c/0x6a0
[ 84.318572] worker_thread+0x60/0x4e8
[ 84.322357] kthread+0xfc/0x11c
[ 84.325622] ret_from_fork+0x14/0x28
[ 84.329315] irq event stamp: 18409
[ 84.332733] hardirqs last enabled at (18409): [<c0422f9c>]
ktime_get_real_ts64+0x208/0x22c
[ 84.341125] hardirqs last disabled at (18408): [<c0422f68>]
ktime_get_real_ts64+0x1d4/0x22c
[ 84.349517] softirqs last enabled at (18368): [<c14e08a8>]
rawv6_sendmsg+0x780/0x14cc
[ 84.357482] softirqs last disabled at (18366): [<c1306ea0>]
release_sock+0x20/0xa0
[ 84.365112]
[ 84.365112] other info that might help us debug this:
[ 84.371673] Possible unsafe locking scenario:
[ 84.371673]
[ 84.377624] CPU0
[ 84.380096] ----
[ 84.382537] lock(&n->lock);
[ 84.385528] <Interrupt>
[ 84.388183] lock(&n->lock);
[ 84.391326]
[ 84.391326] *** DEADLOCK ***
[ 84.391326]
[ 84.397277] 3 locks held by ping/582:
[ 84.400970] #0: c24a62f8 (rcu_read_lock){....}-{1:2}, at:
ip6_route_output_flags+0x0/0x1f4
[ 84.409393] #1: c24a62f8 (rcu_read_lock){....}-{1:2}, at:
ip6_pol_route+0x60/0x718
[ 84.417114] #2: c24a62f8 (rcu_read_lock){....}-{1:2}, at:
rt6_score_route+0x78/0x1e0
[ 84.425048]
[ 84.425048] stack backtrace:
[ 84.429412] CPU: 0 PID: 582 Comm: ping Not tainted 6.1.57-rc1 #1
[ 84.435455] Hardware name: Generic DRA74X (Flattened Device Tree)
[ 84.441589] unwind_backtrace from show_stack+0x18/0x1c
[ 84.446868] show_stack from dump_stack_lvl+0x58/0x70
[ 84.451965] dump_stack_lvl from mark_lock.part.0+0xb74/0x128c
[ 84.457824] mark_lock.part.0 from __lock_acquire+0x3d8/0x2aa4
[ 84.463684] __lock_acquire from lock_acquire+0x110/0x334
[ 84.469116] lock_acquire from _raw_read_lock+0x64/0x74
[ 84.474395] _raw_read_lock from rt6_score_route+0xd8/0x1e0
[ 84.480010] rt6_score_route from find_match.part.0+0x6c/0x4d4
[ 84.485900] find_match.part.0 from __find_rr_leaf+0xb8/0x430
[ 84.491668] __find_rr_leaf from fib6_table_lookup+0x234/0x46c
[ 84.497528] fib6_table_lookup from ip6_pol_route+0xd0/0x718
[ 84.503234] ip6_pol_route from ip6_pol_route_output+0x2c/0x34
[ 84.509094] ip6_pol_route_output from fib6_rule_lookup+0xb4/0x1e4
[ 84.515319] fib6_rule_lookup from ip6_route_output_flags_noref+0xbc/0x110
[ 84.522247] ip6_route_output_flags_noref from
ip6_route_output_flags+0x78/0x1f4
[ 84.529693] ip6_route_output_flags from ip6_dst_lookup_tail+0xa8/0x7b0
[ 84.536346] ip6_dst_lookup_tail from ip6_dst_lookup_flow+0x40/0x90
[ 84.542663] ip6_dst_lookup_flow from rawv6_sendmsg+0x3d0/0x14cc
[ 84.548736] rawv6_sendmsg from __sys_sendto+0xd8/0x128
[ 84.553985] __sys_sendto from ret_fast_syscall+0x0/0x1c
[ 84.559326] Exception stack(0xf03e1fa8 to 0xf03e1ff0)
[ 84.564422] 1fa0: 004b247c 0000001c 00000006
004b5220 00000040 00000800
[ 84.572662] 1fc0: 004b247c 0000001c 00000001 00000122 004b5220
004b3208 004b0208 beb36778
[ 84.580871] 1fe0: 00000122 beb36608 b6e8ed91 b6df7616
# PASS: fib expression did not cause unwanted packet drops

Links,
- https://lkft.validation.linaro.org/scheduler/job/6858069#L4022
- https://lkft.validation.linaro.org/scheduler/job/6857530#L3070
- https://lkft.validation.linaro.org/scheduler/job/6856378#L3074

metadata:
git_ref: linux-6.1.y
git_repo: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
git_sha: 282079f8e40746cc342a7dd12654e3af7de01823
git_describe: v6.1.56-163-g282079f8e407
kernel_version: 6.1.57-rc1
kernel-config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2WWpUEO5ikJpR8NnchDG1NClaGf/config
artifact-location:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2WWpUEO5ikJpR8NnchDG1NClaGf/
toolchain: gcc-10


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

2023-10-09 22:49:24

by Shuah Khan

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On 10/9/23 06:59, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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
>

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

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

thanks,
-- Shuah

2023-10-09 23:24:25

by Florian Fainelli

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On 10/9/23 05:59, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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

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

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

2023-10-10 05:53:54

by Bagas Sanjaya

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Mon, Oct 09, 2023 at 02:59:41PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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.
>

Successfully compiled and installed bindeb-pkgs on my computer (Acer
Aspire E15, Intel Core i3 Haswell). No noticeable regressions.

Tested-by: Bagas Sanjaya <[email protected]>

--
An old man doll... just what I always wanted! - Clara


Attachments:
(No filename) (559.00 B)
signature.asc (235.00 B)
Download all attachments

2023-10-10 08:11:24

by Wang Yugui

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hi,

> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +0000.
> Anything received after that time might be too late.


drop this patch from 6.5/6.1/5.15/... please,
Qu Wenruo <[email protected]>
btrfs: reject unknown mount options early

becuase of this report.
https://lore.kernel.org/linux-btrfs/[email protected]/T/#t


Best Regards
Wang Yugui ([email protected])
2023/10/10



2023-10-10 09:52:03

by Pavel Machek

[permalink] [raw]
Subject: unneeded btrfs changes -- Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hi!
On Mon 2023-10-09 14:59:41, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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.
>

> Sweet Tea Dorminy <[email protected]>
> btrfs: use struct fscrypt_str instead of struct qstr
>
> Sweet Tea Dorminy <[email protected]>
> btrfs: setup qstr from dentrys using fscrypt helper
>
> Sweet Tea Dorminy <[email protected]>
> btrfs: use struct qstr instead of name and namelen pairs

These are rather intrusive, and marked with

Stable-dep-of: 9af86694fd5d ("btrfs: file_remove_privs needs an exclusive lock in direct io write")

but we don't have that one in 6.1, so we should not have these,
either.

Best regards,
Pavel

--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany


Attachments:
(No filename) (1.45 kB)
signature.asc (201.00 B)
Download all attachments

2023-10-10 10:00:52

by Jon Hunter

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Mon, 09 Oct 2023 14:59:41 +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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

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 fail

Linux version: 6.1.57-rc1-g32856ae49e9f
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-a04

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

Jon

2023-10-10 11:28:38

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Tue, Oct 10, 2023 at 04:10:48PM +0800, Wang Yugui wrote:
> Hi,
>
> > This is the start of the stable review cycle for the 6.1.57 release.
> > There are 162 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, 11 Oct 2023 13:00:55 +0000.
> > Anything received after that time might be too late.
>
>
> drop this patch from 6.5/6.1/5.15/... please,
> Qu Wenruo <[email protected]>
> btrfs: reject unknown mount options early
>
> becuase of this report.
> https://lore.kernel.org/linux-btrfs/[email protected]/T/#t

Is there a revert somewhere for this already?

thanks,

greg k-h

2023-10-10 11:42:46

by Wang Yugui

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hi,

> On Tue, Oct 10, 2023 at 04:10:48PM +0800, Wang Yugui wrote:
> > Hi,
> >
> > > This is the start of the stable review cycle for the 6.1.57 release.
> > > There are 162 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, 11 Oct 2023 13:00:55 +0000.
> > > Anything received after that time might be too late.
> >
> >
> > drop this patch from 6.5/6.1/5.15/... please,
> > Qu Wenruo <[email protected]>
> > btrfs: reject unknown mount options early
> >
> > becuase of this report.
> > https://lore.kernel.org/linux-btrfs/[email protected]/T/#t
>
> Is there a revert somewhere for this already?

Yet not.

but we can suspend to apply this patch(drop this patch) for stable.

Best Regards
Wang Yugui ([email protected])
2023/10/10

2023-10-10 13:22:19

by Takeshi Ogasawara

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hi Greg

On Mon, Oct 9, 2023 at 10:16 PM Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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
>


6.1.57-rc1 tested.

Build successfully completed.
Boot successfully completed.
No dmesg regressions.
Video output normal.
Sound output normal.

Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64) arch linux)

Thanks

Tested-by: Takeshi Ogasawara <[email protected]>

2023-10-10 16:16:50

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: unneeded btrfs changes -- Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Tue, Oct 10, 2023 at 11:51:42AM +0200, Pavel Machek wrote:
> Hi!
> On Mon 2023-10-09 14:59:41, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.57 release.
> > There are 162 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, 11 Oct 2023 13:00:55 +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.57-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.
> >
>
> > Sweet Tea Dorminy <[email protected]>
> > btrfs: use struct fscrypt_str instead of struct qstr
> >
> > Sweet Tea Dorminy <[email protected]>
> > btrfs: setup qstr from dentrys using fscrypt helper
> >
> > Sweet Tea Dorminy <[email protected]>
> > btrfs: use struct qstr instead of name and namelen pairs
>
> These are rather intrusive, and marked with
>
> Stable-dep-of: 9af86694fd5d ("btrfs: file_remove_privs needs an exclusive lock in direct io write")
>
> but we don't have that one in 6.1, so we should not have these,
> either.

Ah, seems we forgot that dep patch, so that's now added which makes more
sense why the prep patches were added.

thanks,

greg k-h

2023-10-10 16:51:37

by Matthieu Baerts (NGI0)

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hi Naresh,

On 09/10/2023 22:43, Naresh Kamboju wrote:
> On Mon, 9 Oct 2023 at 18:46, Greg Kroah-Hartman
> <[email protected]> wrote:
>>
>> This is the start of the stable review cycle for the 6.1.57 release.
>> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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
>
>
> The following kernel warnings were noticed several times on arm x15 devices
> running stable-rc 6.1.57-rc1 while running selftests: net: mptcp_connect.sh
> and netfilter: nft_fib.sh.
>
> The possible unsafe locking scenario detected.
>
> FYI,
> Stable-rc/ linux.6.1.y kernel running stable/ linux.6.5.y selftest in this case.
>
> Reported-by: Linux Kernel Functional Testing <[email protected]>
>
> kselftest: Running tests in net/mptcp

Thank you for having reported the issue and having added MPTCP ML in Cc!

Just to avoid confusions: the "WARNING" you shared when running
'mptcp_connect.sh' selftest appeared before creating the first MPTCP
connection. It looks like there is no reference to MPTCP in the
calltraces. Also, because you have the same issue with nft_fib.sh, I
would say that this issue is not linked to MPTCP but rather to a recent
modification in the IPv6 stack.

By chance, did you start a "git bisect" to identify the commit causing
this issue?

Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
http://www.tessares.net

2023-10-10 17:24:41

by Eric Dumazet

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Tue, Oct 10, 2023 at 6:51 PM Matthieu Baerts <[email protected]> wrote:
>
> Hi Naresh,
>
> On 09/10/2023 22:43, Naresh Kamboju wrote:
> > On Mon, 9 Oct 2023 at 18:46, Greg Kroah-Hartman
> > <[email protected]> wrote:
> >>
> >> This is the start of the stable review cycle for the 6.1.57 release.
> >> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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
> >
> >
> > The following kernel warnings were noticed several times on arm x15 devices
> > running stable-rc 6.1.57-rc1 while running selftests: net: mptcp_connect.sh
> > and netfilter: nft_fib.sh.
> >
> > The possible unsafe locking scenario detected.
> >
> > FYI,
> > Stable-rc/ linux.6.1.y kernel running stable/ linux.6.5.y selftest in this case.
> >
> > Reported-by: Linux Kernel Functional Testing <[email protected]>
> >
> > kselftest: Running tests in net/mptcp
>
> Thank you for having reported the issue and having added MPTCP ML in Cc!
>
> Just to avoid confusions: the "WARNING" you shared when running
> 'mptcp_connect.sh' selftest appeared before creating the first MPTCP
> connection. It looks like there is no reference to MPTCP in the
> calltraces. Also, because you have the same issue with nft_fib.sh, I
> would say that this issue is not linked to MPTCP but rather to a recent
> modification in the IPv6 stack.
>
> By chance, did you start a "git bisect" to identify the commit causing
> this issue?
>
>

I think stable teams missed to backport

commit c486640aa710ddd06c13a7f7162126e1552e8842
Author: Eric Dumazet <[email protected]>
Date: Mon Mar 13 20:17:32 2023 +0000

ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh()

rt6_check_neigh() uses read_lock() to protect n->nud_state reading.

This seems overkill and causes false sharing.

Signed-off-by: Eric Dumazet <[email protected]>
Reviewed-by: David Ahern <[email protected]>
Reviewed-by: Martin KaFai Lau <[email protected]>
Signed-off-by: Jakub Kicinski <[email protected]>

2023-10-10 18:19:57

by Guenter Roeck

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Mon, Oct 09, 2023 at 02:59:41PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +0000.
> Anything received after that time might be too late.
>

Build results:
total: 157 pass: 157 fail: 0
Qemu test results:
total: 529 pass: 529 fail: 0

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

Guenter

2023-10-10 18:43:13

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Tue, Oct 10, 2023 at 07:42:22PM +0800, Wang Yugui wrote:
> Hi,
>
> > On Tue, Oct 10, 2023 at 04:10:48PM +0800, Wang Yugui wrote:
> > > Hi,
> > >
> > > > This is the start of the stable review cycle for the 6.1.57 release.
> > > > There are 162 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, 11 Oct 2023 13:00:55 +0000.
> > > > Anything received after that time might be too late.
> > >
> > >
> > > drop this patch from 6.5/6.1/5.15/... please,
> > > Qu Wenruo <[email protected]>
> > > btrfs: reject unknown mount options early
> > >
> > > becuase of this report.
> > > https://lore.kernel.org/linux-btrfs/[email protected]/T/#t
> >
> > Is there a revert somewhere for this already?
>
> Yet not.
>
> but we can suspend to apply this patch(drop this patch) for stable.

Now dropped, thanks.

greg k-h

2023-10-10 19:00:04

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

On Tue, Oct 10, 2023 at 07:24:08PM +0200, Eric Dumazet wrote:
> On Tue, Oct 10, 2023 at 6:51 PM Matthieu Baerts <[email protected]> wrote:
> >
> > Hi Naresh,
> >
> > On 09/10/2023 22:43, Naresh Kamboju wrote:
> > > On Mon, 9 Oct 2023 at 18:46, Greg Kroah-Hartman
> > > <[email protected]> wrote:
> > >>
> > >> This is the start of the stable review cycle for the 6.1.57 release.
> > >> There are 162 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, 11 Oct 2023 13:00:55 +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.57-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
> > >
> > >
> > > The following kernel warnings were noticed several times on arm x15 devices
> > > running stable-rc 6.1.57-rc1 while running selftests: net: mptcp_connect.sh
> > > and netfilter: nft_fib.sh.
> > >
> > > The possible unsafe locking scenario detected.
> > >
> > > FYI,
> > > Stable-rc/ linux.6.1.y kernel running stable/ linux.6.5.y selftest in this case.
> > >
> > > Reported-by: Linux Kernel Functional Testing <[email protected]>
> > >
> > > kselftest: Running tests in net/mptcp
> >
> > Thank you for having reported the issue and having added MPTCP ML in Cc!
> >
> > Just to avoid confusions: the "WARNING" you shared when running
> > 'mptcp_connect.sh' selftest appeared before creating the first MPTCP
> > connection. It looks like there is no reference to MPTCP in the
> > calltraces. Also, because you have the same issue with nft_fib.sh, I
> > would say that this issue is not linked to MPTCP but rather to a recent
> > modification in the IPv6 stack.
> >
> > By chance, did you start a "git bisect" to identify the commit causing
> > this issue?
> >
> >
>
> I think stable teams missed to backport
>
> commit c486640aa710ddd06c13a7f7162126e1552e8842
> Author: Eric Dumazet <[email protected]>
> Date: Mon Mar 13 20:17:32 2023 +0000
>
> ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh()
>
> rt6_check_neigh() uses read_lock() to protect n->nud_state reading.
>
> This seems overkill and causes false sharing.
>
> Signed-off-by: Eric Dumazet <[email protected]>
> Reviewed-by: David Ahern <[email protected]>
> Reviewed-by: Martin KaFai Lau <[email protected]>
> Signed-off-by: Jakub Kicinski <[email protected]>

Ah, didn't know we needed that, now queued up, thanks!

greg k-h

2023-10-11 09:41:41

by Pavel Machek

[permalink] [raw]
Subject: Re: [PATCH 6.1 000/162] 6.1.57-rc1 review

Hi!

> This is the start of the stable review cycle for the 6.1.57 release.
> There are 162 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, 11 Oct 2023 13:00:55 +0000.
> Anything received after that time might be too late.

Released early?

Anyway, this seems to pass our testing.

CIP testing did not find any problems here:

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-6.1.y

Tested-by: Pavel Machek (CIP) <[email protected]>

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


Attachments:
(No filename) (845.00 B)
signature.asc (201.00 B)
Download all attachments