This is the start of the stable review cycle for the 6.0.19 release.
There are 148 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.
NOTE, this will probably be the LAST 6.0.y release. If there is
anything preventing you from moving to 6.1.y right now, please let me
know.
Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 6.0.19-rc1
Jocelyn Falempe <[email protected]>
drm/mgag200: Fix PLL setup for G200_SE_A rev >=4
Ard Biesheuvel <[email protected]>
efi: random: combine bootloader provided RNG seed with RNG protocol output
Qu Wenruo <[email protected]>
btrfs: make thaw time super block check to also verify checksum
William Liu <[email protected]>
ksmbd: check nt_len to be at least CIFS_ENCPWD_SIZE in ksmbd_decode_ntlmssp_auth_blob
Marios Makassikis <[email protected]>
ksmbd: send proper error response in smb2_tree_connect()
Namjae Jeon <[email protected]>
ksmbd: fix infinite loop in ksmbd_conn_handler_loop()
Qu Wenruo <[email protected]>
btrfs: handle case when repair happens with dev-replace
Rafael Mendonca <[email protected]>
virtio_blk: Fix signedness bug in virtblk_prep_rq()
Dmitry Fomichev <[email protected]>
virtio-blk: use a helper to handle request queuing errors
Zhenyu Wang <[email protected]>
drm/i915/gvt: fix vgpu debugfs clean in remove
Zhenyu Wang <[email protected]>
drm/i915/gvt: fix gvt debugfs destroy
Mukul Joshi <[email protected]>
drm/amdkfd: Fix kernel warning during topology setup
Andreas Rammhold <[email protected]>
of/fdt: run soc memory setup when early_init_dt_scan_memory fails
Björn Töpel <[email protected]>
riscv, kprobes: Stricter c.jr/c.jalr decoding
Ben Dooks <[email protected]>
riscv: uaccess: fix type of 0 variable on error in get_user()
Srinivas Pandruvada <[email protected]>
thermal: int340x: Add missing attribute for data rate base
Cindy Lu <[email protected]>
vhost_vdpa: fix the crash in unmap a large memory
Pavel Begunkov <[email protected]>
io_uring: fix CQ waiting timeout handling
Jens Axboe <[email protected]>
block: don't allow splitting of a REQ_NOWAIT bio
Christian Marangi <[email protected]>
net: dsa: tag_qca: fix wrong MGMT_DATA2 size
Christian Marangi <[email protected]>
net: dsa: qca8k: fix wrong length value for mgmt eth packet
Christian Marangi <[email protected]>
Revert "net: dsa: qca8k: cache lo and hi for mdio write"
Michel Dänzer <[email protected]>
Revert "drm/amd/display: Enable Freesync Video Mode by default"
Chuang Wang <[email protected]>
bpf: Fix panic due to wrong pageattr of im->image
Paul Menzel <[email protected]>
fbdev: matroxfb: G200eW: Increase max memory from 1 MB to 16 MB
Jeff Layton <[email protected]>
nfsd: fix handling of readdir in v4root vs. mount upcall timeout
Rodrigo Branco <[email protected]>
x86/bugs: Flush IBP in ib_prctl_set()
Takashi Iwai <[email protected]>
x86/kexec: Fix double-free of elf header buffer
Qu Wenruo <[email protected]>
btrfs: fix compat_ro checks against remount
Qu Wenruo <[email protected]>
btrfs: relax block-group-tree feature dependency checks
Qu Wenruo <[email protected]>
btrfs: separate BLOCK_GROUP_TREE compat RO flag from EXTENT_TREE_V2
Qu Wenruo <[email protected]>
btrfs: don't save block group root into super block
Qu Wenruo <[email protected]>
btrfs: check superblock to ensure the fs was not modified at thaw time
Kai Vehmanen <[email protected]>
ASoC: SOF: Intel: pci-tgl: unblock S5 entry if DMA stop has failed"
Christoph Hellwig <[email protected]>
nvme: also return I/O command effects from nvme_command_effects
Christoph Hellwig <[email protected]>
nvmet: use NVME_CMD_EFFECTS_CSUPP instead of open coding it
Jens Axboe <[email protected]>
io_uring: check for valid register opcode earlier
Yanjun Zhang <[email protected]>
nvme: fix multipath crash caused by flush request when blktrace is enabled
Philip Yang <[email protected]>
drm/amdkfd: Fix double release compute pasid
Philip Yang <[email protected]>
drm/amdkfd: Fix kfd_process_device_init_vm error handling
Luben Tuikov <[email protected]>
drm/amdgpu: Fix size validation for non-exclusive domains (v4)
YC Hung <[email protected]>
ASoC: SOF: mediatek: initialize panic_info to zero
Hans de Goede <[email protected]>
ASoC: Intel: bytcr_rt5640: Add quirk for the Advantech MICA-071 tablet
Dominique Martinet <[email protected]>
9p/client: fix data race on req->status
Kai Vehmanen <[email protected]>
ASoC: SOF: Revert: "core: unregister clients and machine drivers in .shutdown"
Linus Torvalds <[email protected]>
hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling
Arnd Bergmann <[email protected]>
usb: dwc3: xilinx: include linux/gpio/consumer.h
Jan Kara <[email protected]>
udf: Fix extension of the last extent in the file
Zhengchao Shao <[email protected]>
caif: fix memory leak in cfctrl_linkup_request()
Paolo Abeni <[email protected]>
net/ulp: prevent ULP without clone op from entering the LISTEN status
Caleb Sander <[email protected]>
qed: allow sleep in qed_mcp_trace_dump()
Ming Lei <[email protected]>
ublk: honor IO_URING_F_NONBLOCK for handling control command
Zheng Wang <[email protected]>
drm/i915/gvt: fix double free bug in split_2MB_gtt_entry
Dan Carpenter <[email protected]>
drm/i915: unpin on error in intel_vgpu_shadow_mm_pin()
Namhyung Kim <[email protected]>
perf stat: Fix handling of --for-each-cgroup with --bpf-counters to match non BPF mode
Namhyung Kim <[email protected]>
perf stat: Fix handling of unsupported cgroup events when using BPF counters
Thomas Richter <[email protected]>
perf lock contention: Fix core dump related to not finding the "__sched_text_end" symbol on s/390
Szymon Heidrich <[email protected]>
usb: rndis_host: Secure rndis_query check against int overflow
Geetha sowjanya <[email protected]>
octeontx2-pf: Fix lmtst ID used in aura free
Daniil Tatianin <[email protected]>
drivers/net/bonding/bond_3ad: return when there's no aggregator
Tetsuo Handa <[email protected]>
fs/ntfs3: don't hold ni_lock when calling truncate_setsize()
Philipp Zabel <[email protected]>
drm/imx: ipuv3-plane: Fix overlay plane width
Miaoqian Lin <[email protected]>
perf tools: Fix resources leak in perf_data__open_dir()
Jozsef Kadlecsik <[email protected]>
netfilter: ipset: Rework long task execution when adding/deleting entries
Jozsef Kadlecsik <[email protected]>
netfilter: ipset: fix hash:net,port,net hang with /0 subnet
Horatiu Vultur <[email protected]>
net: sparx5: Fix reading of the MAC address
Ido Schimmel <[email protected]>
vxlan: Fix memory leaks in error path
Jamal Hadi Salim <[email protected]>
net: sched: cbq: dont intepret cls results when asked to drop
Jamal Hadi Salim <[email protected]>
net: sched: atm: dont intepret cls results when asked to drop
Miaoqian Lin <[email protected]>
gpio: sifive: Fix refcount leak in sifive_gpio_probe
Xiubo Li <[email protected]>
ceph: switch to vfs_inode_has_locks() to fix file lock bug
Jeff Layton <[email protected]>
filelock: new helper: vfs_inode_has_locks
Carlo Caione <[email protected]>
drm/meson: Reduce the FIFO lines held when AFBC is not used
Po-Hsu Lin <[email protected]>
selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier
Po-Hsu Lin <[email protected]>
selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier
Maor Gottlieb <[email protected]>
RDMA/mlx5: Fix validation of max_rd_atomic caps for DC
Shay Drory <[email protected]>
RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device
Miaoqian Lin <[email protected]>
net: phy: xgmiitorgmii: Fix refcount leak in xgmiitorgmii_probe
David Arinzon <[email protected]>
net: ena: Update NUMA TPH hint register upon NUMA node update
David Arinzon <[email protected]>
net: ena: Set default value for RX interrupt moderation
David Arinzon <[email protected]>
net: ena: Fix rx_copybreak value update
David Arinzon <[email protected]>
net: ena: Use bitmask to indicate packet redirection
David Arinzon <[email protected]>
net: ena: Account for the number of processed bytes in XDP
David Arinzon <[email protected]>
net: ena: Don't register memory info on XDP exchange
David Arinzon <[email protected]>
net: ena: Fix toeplitz initial hash value
Jiguang Xiao <[email protected]>
net: amd-xgbe: add missed tasklet_kill
Jian Shen <[email protected]>
net: hns3: refine the handling for VF heartbeat
Hao Lan <[email protected]>
net: hns3: refactor function hclge_mbx_handler()
Eli Cohen <[email protected]>
net/mlx5: Lag, fix failure to cancel delayed bond work
Maor Dickman <[email protected]>
net/mlx5e: Set geneve_tlv_option_0_exist when matching on geneve option
Adham Faris <[email protected]>
net/mlx5e: Fix hw mtu initializing at XDP SQ allocation
Chris Mi <[email protected]>
net/mlx5e: Always clear dest encap in neigh-update-del
Chris Mi <[email protected]>
net/mlx5e: CT: Fix ct debugfs folder name
Dragos Tatulea <[email protected]>
net/mlx5e: IPoIB, Don't allow CQE compression to be turned on by default
Shay Drory <[email protected]>
net/mlx5: Fix RoCE setting at HCA level
Shay Drory <[email protected]>
net/mlx5: Avoid recovery in probe flows
Shay Drory <[email protected]>
net/mlx5: Fix io_eq_size and event_eq_size params validation
Jiri Pirko <[email protected]>
net/mlx5: Add forgotten cleanup calls into mlx5_init_once() error path
Moshe Shemesh <[email protected]>
net/mlx5: E-Switch, properly handle ingress tagged packets on VST
Jason Wang <[email protected]>
vdpasim: fix memory leak when freeing IOTLBs
Rong Wang <[email protected]>
vdpa/vp_vdpa: fix kfree a wrong pointer in vp_vdpa_remove
Wei Yongjun <[email protected]>
virtio-crypto: fix memory leak in virtio_crypto_alg_skcipher_close_session()
Stefano Garzarella <[email protected]>
vdpa_sim: fix vringh initialization in vdpasim_queue_ready()
Stefano Garzarella <[email protected]>
vhost-vdpa: fix an iotlb memory leak
Stefano Garzarella <[email protected]>
vhost: fix range used in translate_desc()
Stefano Garzarella <[email protected]>
vringh: fix range used in iotlb_translate()
Yuan Can <[email protected]>
vhost/vsock: Fix error handling in vhost_vsock_init()
ruanjinjie <[email protected]>
vdpa_sim: fix possible memory leak in vdpasim_net_init() and vdpasim_blk_init()
Eli Cohen <[email protected]>
vdpa/mlx5: Fix wrong mac address deletion
Eli Cohen <[email protected]>
vdpa/mlx5: Fix rule forwarding VLAN to TIR
Michael Chan <[email protected]>
bnxt_en: Fix HDS and jumbo thresholds for RX packets
Michael Chan <[email protected]>
bnxt_en: Fix first buffer size calculations for XDP multi-buffer
Michael Chan <[email protected]>
bnxt_en: Fix XDP RX path
Michael Chan <[email protected]>
bnxt_en: Simplify bnxt_xdp_buff_init()
Miaoqian Lin <[email protected]>
nfc: Fix potential resource leaks
Johnny S. Lee <[email protected]>
net: dsa: mv88e6xxx: depend on PTP conditionally
Daniil Tatianin <[email protected]>
qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure
Hawkins Jiawei <[email protected]>
net: sched: fix memory leak in tcindex_set_parms
Jian Shen <[email protected]>
net: hns3: fix VF promisc mode not update when mac table full
Jian Shen <[email protected]>
net: hns3: fix miss L3E checking for rx packet
Jie Wang <[email protected]>
net: hns3: add interrupts re-initialization while doing VF FLR
Jeff Layton <[email protected]>
nfsd: shut down the NFSv4 state objects before the filecache
Shawn Bohrer <[email protected]>
veth: Fix race with AF_XDP exposing old or uninitialized descriptors
Horatiu Vultur <[email protected]>
net: lan966x: Fix configuration of the PCS
Eric Dumazet <[email protected]>
bonding: fix lockdep splat in bond_miimon_commit()
Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables: honor set timeout and garbage collection updates
Paolo Abeni <[email protected]>
mptcp: fix lockdep false positive
Ronak Doshi <[email protected]>
vmxnet3: correctly report csum_level for encapsulated packet
Antoine Tenart <[email protected]>
net: vrf: determine the dst using the original ifindex for multicast
Maciej Fijalkowski <[email protected]>
ice: xsk: do not use xdp_return_frame() on tx_buf->raw_buf
Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables: perform type checking for existing sets
Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables: add function to create set stateful expressions
Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables: consolidate set description
Steven Price <[email protected]>
drm/panfrost: Fix GEM handle creation ref-counting
Jakub Kicinski <[email protected]>
bpf: pull before calling skb_postpull_rcsum()
Arnd Bergmann <[email protected]>
wifi: ath9k: use proper statements in conditionals
Sasha Levin <[email protected]>
btrfs: fix an error handling path in btrfs_defrag_leaves()
minoura makoto <[email protected]>
SUNRPC: ensure the matching upcall is in-flight upon downcall
Baokun Li <[email protected]>
ext4: correct inconsistent error msg in nojournal mode
Jason Yan <[email protected]>
ext4: goto right label 'failed_mount3a'
Johan Hovold <[email protected]>
phy: qcom-qmp-combo: fix broken power on
Masami Hiramatsu (Google) <[email protected]>
perf probe: Fix to get the DW_AT_decl_file and DW_AT_call_file as unsinged data
Masami Hiramatsu (Google) <[email protected]>
perf probe: Use dwarf_attr_integrate as generic DWARF attr accessor
Thinh Nguyen <[email protected]>
usb: dwc3: gadget: Ignore End Transfer delay on teardown
Shyam Prasad N <[email protected]>
cifs: refcount only the selected iface during interface update
Shyam Prasad N <[email protected]>
cifs: fix interface count calculation during refresh
Sasha Levin <[email protected]>
btrfs: replace strncpy() with strscpy()
Jens Axboe <[email protected]>
ARM: renumber bits related to _TIF_WORK_MASK
-------------
Diffstat:
Makefile | 4 +-
arch/arm/include/asm/thread_info.h | 13 +-
arch/mips/ralink/of.c | 2 +-
arch/riscv/include/asm/uaccess.h | 2 +-
arch/riscv/kernel/probes/simulate-insn.h | 4 +-
arch/x86/kernel/cpu/bugs.c | 2 +
arch/x86/kernel/crash.c | 4 +-
block/blk-merge.c | 10 +
drivers/block/ublk_drv.c | 3 +
drivers/block/virtio_blk.c | 33 +-
.../crypto/virtio/virtio_crypto_skcipher_algs.c | 3 +-
drivers/firmware/efi/efi.c | 4 +-
drivers/firmware/efi/libstub/efistub.h | 2 +
drivers/firmware/efi/libstub/random.c | 42 +-
drivers/gpio/gpio-sifive.c | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 39 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 27 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 19 +-
drivers/gpu/drm/amd/amdkfd/kfd_process.c | 24 +-
drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 2 +-
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 12 +-
drivers/gpu/drm/i915/gvt/debugfs.c | 17 +-
drivers/gpu/drm/i915/gvt/gtt.c | 17 +-
drivers/gpu/drm/i915/gvt/scheduler.c | 1 +
drivers/gpu/drm/imx/ipuv3-plane.c | 14 +-
drivers/gpu/drm/meson/meson_viu.c | 5 +-
drivers/gpu/drm/mgag200/mgag200_pll.c | 3 +-
drivers/gpu/drm/panfrost/panfrost_drv.c | 27 +-
drivers/gpu/drm/panfrost/panfrost_gem.c | 16 +-
drivers/gpu/drm/panfrost/panfrost_gem.h | 5 +-
drivers/infiniband/hw/mlx5/counters.c | 6 +-
drivers/infiniband/hw/mlx5/qp.c | 49 ++-
drivers/net/bonding/bond_3ad.c | 1 +
drivers/net/bonding/bond_main.c | 8 +-
drivers/net/dsa/mv88e6xxx/Kconfig | 4 +-
drivers/net/dsa/qca/qca8k-8xxx.c | 106 ++---
drivers/net/dsa/qca/qca8k.h | 5 -
drivers/net/ethernet/amazon/ena/ena_com.c | 29 +-
drivers/net/ethernet/amazon/ena/ena_ethtool.c | 6 +-
drivers/net/ethernet/amazon/ena/ena_netdev.c | 83 +++-
drivers/net/ethernet/amazon/ena/ena_netdev.h | 17 +-
drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 3 +
drivers/net/ethernet/amd/xgbe/xgbe-i2c.c | 4 +-
drivers/net/ethernet/amd/xgbe/xgbe-mdio.c | 4 +-
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 22 +-
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 15 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.c | 20 +-
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.h | 6 +-
drivers/net/ethernet/hisilicon/hns3/hclge_mbx.h | 11 +
drivers/net/ethernet/hisilicon/hns3/hns3_enet.c | 10 +-
.../ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 132 ++++--
.../ethernet/hisilicon/hns3/hns3pf/hclge_main.h | 7 +
.../net/ethernet/hisilicon/hns3/hns3pf/hclge_mbx.c | 486 ++++++++++++++-------
.../ethernet/hisilicon/hns3/hns3vf/hclgevf_main.c | 3 +-
drivers/net/ethernet/intel/ice/ice_xsk.c | 2 +-
.../ethernet/marvell/octeontx2/nic/otx2_common.c | 30 +-
drivers/net/ethernet/mellanox/mlx5/core/devlink.c | 4 +-
drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c | 7 +-
.../ethernet/mellanox/mlx5/core/en/tc_tun_encap.c | 9 +-
.../ethernet/mellanox/mlx5/core/en/tc_tun_geneve.c | 5 +
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 2 +-
.../mellanox/mlx5/core/esw/acl/egress_lgcy.c | 7 +-
.../mellanox/mlx5/core/esw/acl/ingress_lgcy.c | 33 +-
drivers/net/ethernet/mellanox/mlx5/core/eswitch.c | 30 +-
drivers/net/ethernet/mellanox/mlx5/core/eswitch.h | 6 +
drivers/net/ethernet/mellanox/mlx5/core/health.c | 6 +
.../net/ethernet/mellanox/mlx5/core/ipoib/ipoib.c | 4 +
drivers/net/ethernet/mellanox/mlx5/core/lag/lag.c | 1 +
drivers/net/ethernet/mellanox/mlx5/core/main.c | 4 +-
.../net/ethernet/microchip/lan966x/lan966x_port.c | 2 +-
.../net/ethernet/microchip/sparx5/sparx5_main.c | 2 +-
drivers/net/ethernet/qlogic/qed/qed_debug.c | 28 +-
.../net/ethernet/qlogic/qlcnic/qlcnic_83xx_init.c | 8 +-
drivers/net/ethernet/qlogic/qlcnic/qlcnic_dcb.h | 10 +-
drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c | 8 +-
drivers/net/phy/xilinx_gmii2rgmii.c | 1 +
drivers/net/usb/rndis_host.c | 3 +-
drivers/net/veth.c | 5 +-
drivers/net/vmxnet3/vmxnet3_drv.c | 8 +
drivers/net/vrf.c | 6 +-
drivers/net/vxlan/vxlan_core.c | 19 +-
drivers/net/wireless/ath/ath9k/htc.h | 14 +-
drivers/nvme/host/core.c | 32 +-
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/target/admin-cmd.c | 35 +-
drivers/of/fdt.c | 6 +-
drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 20 +-
.../intel/int340x_thermal/processor_thermal_rfim.c | 4 +
drivers/usb/dwc3/dwc3-xilinx.c | 1 +
drivers/usb/dwc3/gadget.c | 5 +-
drivers/vdpa/mlx5/net/mlx5_vnet.c | 10 +-
drivers/vdpa/vdpa_sim/vdpa_sim.c | 7 +-
drivers/vdpa/vdpa_sim/vdpa_sim_blk.c | 4 +-
drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 4 +-
drivers/vdpa/virtio_pci/vp_vdpa.c | 2 +-
drivers/vhost/vdpa.c | 52 ++-
drivers/vhost/vhost.c | 4 +-
drivers/vhost/vringh.c | 5 +-
drivers/vhost/vsock.c | 9 +-
drivers/video/fbdev/matrox/matroxfb_base.c | 4 +-
fs/btrfs/block-rsv.c | 1 +
fs/btrfs/ctree.h | 30 +-
fs/btrfs/disk-io.c | 271 +++++++-----
fs/btrfs/disk-io.h | 9 +-
fs/btrfs/extent_io.c | 11 +-
fs/btrfs/ioctl.c | 9 +-
fs/btrfs/rcu-string.h | 6 +-
fs/btrfs/super.c | 95 +++-
fs/btrfs/sysfs.c | 2 +
fs/btrfs/transaction.c | 8 -
fs/btrfs/tree-defrag.c | 6 +-
fs/btrfs/volumes.c | 2 +-
fs/ceph/caps.c | 2 +-
fs/ceph/locks.c | 4 -
fs/ceph/super.h | 1 -
fs/cifs/sess.c | 3 +-
fs/cifs/smb2ops.c | 3 +-
fs/ext4/super.c | 19 +-
fs/hfs/inode.c | 15 +-
fs/ksmbd/auth.c | 3 +-
fs/ksmbd/connection.c | 7 +-
fs/ksmbd/smb2pdu.c | 7 +-
fs/ksmbd/transport_tcp.c | 5 +-
fs/locks.c | 23 +
fs/nfsd/nfs4xdr.c | 11 +
fs/nfsd/nfssvc.c | 2 +-
fs/ntfs3/file.c | 4 +-
fs/udf/inode.c | 2 +-
include/linux/dsa/tag_qca.h | 4 +-
include/linux/efi.h | 2 -
include/linux/fs.h | 6 +
include/linux/mlx5/device.h | 5 +
include/linux/mlx5/mlx5_ifc.h | 3 +-
include/linux/netfilter/ipset/ip_set.h | 2 +-
include/linux/sunrpc/rpc_pipe_fs.h | 5 +
include/net/netfilter/nf_tables.h | 25 +-
include/uapi/linux/btrfs.h | 6 +
io_uring/io_uring.c | 11 +-
kernel/bpf/trampoline.c | 4 +
net/9p/client.c | 15 +-
net/9p/trans_fd.c | 12 +-
net/9p/trans_rdma.c | 4 +-
net/9p/trans_virtio.c | 9 +-
net/9p/trans_xen.c | 4 +-
net/caif/cfctrl.c | 6 +-
net/core/filter.c | 7 +-
net/ipv4/inet_connection_sock.c | 14 +
net/ipv4/tcp_ulp.c | 4 +
net/mptcp/protocol.c | 2 +-
net/mptcp/protocol.h | 2 +-
net/mptcp/subflow.c | 19 +-
net/netfilter/ipset/ip_set_core.c | 7 +-
net/netfilter/ipset/ip_set_hash_ip.c | 14 +-
net/netfilter/ipset/ip_set_hash_ipmark.c | 13 +-
net/netfilter/ipset/ip_set_hash_ipport.c | 13 +-
net/netfilter/ipset/ip_set_hash_ipportip.c | 13 +-
net/netfilter/ipset/ip_set_hash_ipportnet.c | 13 +-
net/netfilter/ipset/ip_set_hash_net.c | 17 +-
net/netfilter/ipset/ip_set_hash_netiface.c | 15 +-
net/netfilter/ipset/ip_set_hash_netnet.c | 23 +-
net/netfilter/ipset/ip_set_hash_netport.c | 19 +-
net/netfilter/ipset/ip_set_hash_netportnet.c | 40 +-
net/netfilter/nf_tables_api.c | 261 +++++++----
net/nfc/netlink.c | 52 ++-
net/sched/cls_tcindex.c | 12 +-
net/sched/sch_atm.c | 5 +-
net/sched/sch_cbq.c | 4 +-
net/sunrpc/auth_gss/auth_gss.c | 19 +-
sound/soc/intel/boards/bytcr_rt5640.c | 15 +
sound/soc/sof/core.c | 9 -
sound/soc/sof/intel/hda-dsp.c | 72 +++
sound/soc/sof/intel/hda.h | 1 +
sound/soc/sof/intel/tgl.c | 2 +-
sound/soc/sof/mediatek/mtk-adsp-common.c | 2 +-
tools/perf/builtin-lock.c | 2 +
tools/perf/util/bpf_counter_cgroup.c | 14 +-
tools/perf/util/cgroup.c | 23 +-
tools/perf/util/data.c | 2 +
tools/perf/util/dwarf-aux.c | 23 +-
.../selftests/net/arp_ndisc_evict_nocarrier.sh | 15 +-
182 files changed, 2179 insertions(+), 1142 deletions(-)
On 1/10/23 10:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.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
On 1/10/23 11:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.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
+ attachment failed resending with trim version of log file.
On Wed, 11 Jan 2023 at 11:46, Naresh Kamboju <[email protected]> wrote:
>
> On Tue, 10 Jan 2023 at 23:36, Greg Kroah-Hartman
> <[email protected]> wrote:
> >
> > This is the start of the stable review cycle for the 6.0.19 release.
> > There are 148 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.
> >
> > NOTE, this will probably be the LAST 6.0.y release. If there is
> > anything preventing you from moving to 6.1.y right now, please let me
> > know.
> >
> > Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Results from Linaro’s test farm.
> Regressions on arm64 Raspberry Pi 4 Model B.
>
> Reported-by: Linux Kernel Functional Testing <[email protected]>
>
> While running LTP controllers cgroup_fj_stress_blkio test cases
> the Insufficient stack space to handle exception! occurred and
> followed by kernel panic on arm64 Raspberry Pi 4 Model B with
> clang-15 built kernel Image.
>
> The full boot and test log attached to this email and build and
> Kconfig links provided in the bottom of this email.
>
> I will try to reproduce this reported issue and get back to you.
>
> test log:
> --------
> [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
> [ 0.000000] Linux version 6.0.19-rc1 (tuxmake@tuxmake) (Debian
> clang version 15.0.6, Debian LLD 15.0.6) #1 SMP PREEMPT @1673381411
> [ 0.000000] Machine model: Raspberry Pi 4 Model B
> ...
> cgroup_fj_stress_blkio_2_9_one 1 TINFO: Attaching task 315404 to
> /sys/fs/cgroup/blkio/ltp/1/1/1/2/2/2/1/1/2
> cgroup_fj_stress_blkio_2_9_one 1 TINFO: Attaching task 315404 to
> /sys/fs/cgroup/blkio/ltp/1/1/1/2/2/2/1/1
> cgroup_fj_stress_blkio_2_9_one 1 TINFO: Attaching task 315404 to
> /sys/fs/cgroup/blkio/ltp/1/1/1/2/2/2/1/2
> [ 2893.044339] Insufficient stack space to handle exception!
> [ 2893.044351] ESR: 0x0000000096000047 -- DABT (current EL)
> [ 2893.044360] FAR: 0xffff8000128180d0
> [ 2893.044364] Task stack: [0xffff800012a18000..0xffff800012a1c000]
> [ 2893.044370] IRQ stack: [0xffff80000a798000..0xffff80000a79c000]
> [ 2893.044375] Overflow stack: [0xffff0000f77c4310..0xffff0000f77c5310]
> [ 2893.044383] CPU: 2 PID: 315758 Comm: cgroup_fj_stres Not tainted
> 6.0.19-rc1 #1
> [ 2893.044396] Hardware name: Raspberry Pi 4 Model B (DT)
> [ 2893.044401] pstate: 400003c5 (nZcv DAIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2893.044413] pc : el1h_64_sync+0x0/0x68
> [ 2893.044430] lr : wp_page_copy+0xf8/0x90c
> [ 2893.044445] sp : ffff8000128180d0
> [ 2893.044450] x29: ffff800012a1bc30 x28: ffff800009e25000 x27: 0000000000000a55
> [ 2893.044468] x26: ffff000066a5f000 x25: ffff000066a5f000 x24: 00000000342f5000
> [ 2893.044481] x23: ffff00005033d2c0 x22: ffff000066a5f000 x21: fffffc00012a0d00
> [ 2893.044494] x20: ffff800012a1bcf0 x19: fffffc00016402c0 x18: 0000000000000000
> [ 2893.044506] x17: 72705f6a665f7075 x16: 6f72676320202020 x15: 0a292022656e6f22
> [ 2893.044519] x14: 0a6e69206e6f6974 x13: 617265706f5f6863 x12: 6174746124206573
> [ 2893.044531] x11: 61630a0a2273656d x10: 697420746e756f63 x9 : ffff800008304b84
> [ 2893.044544] x8 : 0000000000000000 x7 : 464e4954206d7365 x6 : 725f7473740a0a30
> [ 2893.044556] x5 : 2022687461705f74 x4 : 7261747324222073 x3 : 70756f7267627573
> [ 2893.044568] x2 : 0000000000000cc0 x1 : ffff00005033d2c0 x0 : fffffc00012a0d00
> [ 2893.044584] Kernel panic - not syncing: kernel stack overflow
> [ 2893.044590] CPU: 2 PID: 315758 Comm: cgroup_fj_stres Not tainted
> 6.0.19-rc1 #1
> [ 2893.044600] Hardware name: Raspberry Pi 4 Model B (DT)
> [ 2893.044605] Call trace:
> [ 2893.044608] dump_backtrace+0xf4/0x144
> [ 2893.044619] show_stack+0x24/0x58
> [ 2893.044627] dump_stack_lvl+0x7c/0xa0
> [ 2893.044638] dump_stack+0x18/0x44
> [ 2893.044646] panic+0x168/0x374
> [ 2893.044658] test_taint+0x0/0x38
> [ 2893.044667] panic_bad_stack+0x110/0x124
> [ 2893.044675] handle_bad_stack+0x34/0x48
> [ 2893.044685] __bad_stack+0x78/0x7c
> [ 2893.044692] el1h_64_sync+0x0/0x68
> [ 2893.044700] do_wp_page+0x4a0/0x5c8
> [ 2893.044708] handle_mm_fault+0x7fc/0x14dc
> [ 2893.044718] do_page_fault+0x29c/0x450
> [ 2893.044727] do_mem_abort+0x4c/0xf8
> [ 2893.044741] el0_da+0x48/0xa8
> [ 2893.044750] el0t_64_sync_handler+0xcc/0xf0
> [ 2893.044759] el0t_64_sync+0x18c/0x190
> [ 2893.044769] SMP: stopping secondary CPUs
> [ 2893.044780] Kernel Offset: disabled
> [ 2893.044783] CPU features: 0x4000,0800f020,00001086
> [ 2893.044790] Memory Limit: none
> [ 2893.278874] ---[ end Kernel panic - not syncing: kernel stack overflow ]---
> [ 2893.285971] ------------[ cut here ]------------
> [ 2893.285975] WARNING: CPU: 2 PID: 315758 at kernel/sched/core.c:3119
> set_task_cpu+0x14c/0x208
> [ 2893.285996] Modules linked in: btrfs xor xor_neon raid6_pq
> zstd_compress libcrc32c algif_hash aes_neon_bs aes_neon_blk xhci_pci
> raspberrypi_cpufreq xhci_pci_renesas brcmfmac hci_uart brcmutil btqca
> btbcm cfg80211 bluetooth clk_raspberrypi raspberrypi_hwmon
> reset_raspberrypi pwm_bcm2835 rfkill vc4 crct10dif_ce bcm2711_thermal
> snd_soc_hdmi_codec i2c_bcm2835 iproc_rng200 rng_core cec v3d
> drm_display_helper pcie_brcmstb gpu_sched drm_cma_helper
> drm_shmem_helper drm_kms_helper fuse drm
> [ 2893.286117] CPU: 2 PID: 315758 Comm: cgroup_fj_stres Not tainted
> 6.0.19-rc1 #1
> [ 2893.286127] Hardware name: Raspberry Pi 4 Model B (DT)
> [ 2893.286131] pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 2893.286142] pc : set_task_cpu+0x14c/0x208
> [ 2893.286151] lr : try_to_wake_up+0x230/0x5b8
> [ 2893.286160] sp : ffff0000f77c4af0
> [ 2893.286164] x29: ffff0000f77c4af0 x28: ffff00004106b7a8 x27: ffff80000a1d29c8
> [ 2893.286177] x26: 0000000000000000 x25: ffff80000a1b3248 x24: ffff000063d16300
> [ 2893.286190] x23: 0000000000000001 x22: 00000000000000c0 x21: 0000000000000001
> [ 2893.286202] x20: 0000000000000001 x19: ffff000041d70000 x18: 00007fffffffffff
> [ 2893.286214] x17: 0000000000000011 x16: ffffffffffffffff x15: 0000000000000004
> [ 2893.286227] x14: 0000000000000fff x13: ffff80000a1eaad8 x12: 000000000000000f
> [ 2893.286239] x11: 0000000000000917 x10: 0000000000000001 x9 : 0000000000000002
> [ 2893.286251] x8 : ffff80000a1aea80 x7 : 205d343738383732 x6 : 322e33393832205b
> [ 2893.286263] x5 : ffff80000a6c752f x4 : 0000000000000008 x3 : 0000000000000000
> [ 2893.286275] x2 : 0000000000000008 x1 : 0000000000000001 x0 : ffff000041d70000
> [ 2893.286287] Call trace:
> [ 2893.286290] set_task_cpu+0x14c/0x208
> [ 2893.286300] try_to_wake_up+0x230/0x5b8
> [ 2893.286309] default_wake_function+0x28/0x3c
> [ 2893.286321] autoremove_wake_function+0x24/0x4c
> [ 2893.286332] __wake_up_common_lock+0x108/0x18c
> [ 2893.286341] __wake_up+0x24/0x30
> [ 2893.286350] wake_up_klogd_work_func+0x94/0x23c
> [ 2893.286364] irq_work_tick+0x98/0xfc
> [ 2893.286378] update_process_times+0x8c/0xa8
> [ 2893.286387] tick_sched_timer+0xd0/0x14c
> [ 2893.286399] __hrtimer_run_queues+0x158/0x378
> [ 2893.286408] hrtimer_interrupt+0xe8/0x3a8
> [ 2893.286416] arch_timer_handler_phys+0x44/0x54
> [ 2893.286427] handle_percpu_devid_irq+0x90/0x220
> [ 2893.286439] generic_handle_domain_irq+0x38/0x50
> [ 2893.286447] gic_handle_irq+0x68/0xe8
> [ 2893.286455] el1_interrupt+0x88/0xc8
> [ 2893.286464] el1h_64_irq_handler+0x18/0x24
> [ 2893.286474] el1h_64_irq+0x64/0x68
> [ 2893.286482] panic+0x2d8/0x374
> [ 2893.286494] test_taint+0x0/0x38
> [ 2893.286502] panic_bad_stack+0x110/0x124
> [ 2893.286509] handle_bad_stack+0x34/0x48
> [ 2893.286519] __bad_stack+0x78/0x7c
> [ 2893.286526] el1h_64_sync+0x0/0x68
> [ 2893.286533] do_wp_page+0x4a0/0x5c8
> [ 2893.286542] handle_mm_fault+0x7fc/0x14dc
> [ 2893.286551] do_page_fault+0x29c/0x450
> [ 2893.286560] do_mem_abort+0x4c/0xf8
> [ 2893.286572] el0_da+0x48/0xa8
> [ 2893.286581] el0t_64_sync_handler+0xcc/0xf0
> [ 2893.286590] el0t_64_sync+0x18c/0x190
> [ 2893.286598] ---[ end trace 0000000000000000 ]---
>
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.0.y/build/v6.0.18-149-ga7ffaeeaf9bb/testrun/14092161/suite/log-parser-test/tests/
> https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.0.y/build/v6.0.18-149-ga7ffaeeaf9bb/testrun/14092161/suite/log-parser-test/test/check-kernel-panic/log
>
> metadata:
> git_ref: linux-6.0.y
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
> git_sha: a7ffaeeaf9bb7ab13e00a589d0910efb9119479c
> git_describe: v6.0.18-149-ga7ffaeeaf9bb
> kernel_version: 6.0.19-rc1
> kernel-config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT/config
> build-url: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/pipelines/743516145
> artifact-location:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT
> toolchain: clang-15
>
> --
> Linaro LKFT
> https://lkft.linaro.org
On Wed, Jan 11, 2023, at 07:16, Naresh Kamboju wrote:
> On Tue, 10 Jan 2023 at 23:36, Greg Kroah-Hartman <[email protected]> wrote:
>>
>
> Results from Linaro’s test farm.
> Regressions on arm64 Raspberry Pi 4 Model B.
>
> Reported-by: Linux Kernel Functional Testing <[email protected]>
>
> While running LTP controllers cgroup_fj_stress_blkio test cases
> the Insufficient stack space to handle exception! occurred and
> followed by kernel panic on arm64 Raspberry Pi 4 Model B with
> clang-15 built kernel Image.
>
> The full boot and test log attached to this email and build and
> Kconfig links provided in the bottom of this email.
>
> I will try to reproduce this reported issue and get back to you.
I looked at the log between 6.0.18 and 6.0.19-rc1, but don't see
any arm64 or memory management patches that could result in this.
Do you know if 6.0.18 ran successfull
> [ 2893.044339] Insufficient stack space to handle exception!
> [ 2893.044351] ESR: 0x0000000096000047 -- DABT (current EL)
> [ 2893.044360] FAR: 0xffff8000128180d0
> [ 2893.044364] Task stack: [0xffff800012a18000..0xffff800012a1c000]
> [ 2893.044370] IRQ stack: [0xffff80000a798000..0xffff80000a79c000]
> [ 2893.044375] Overflow stack: [0xffff0000f77c4310..0xffff0000f77c5310]
...
> [ 2893.044413] pc : el1h_64_sync+0x0/0x68
> [ 2893.044430] lr : wp_page_copy+0xf8/0x90c
> [ 2893.044445] sp : ffff8000128180d0
...
> [ 2893.044692] el1h_64_sync+0x0/0x68
> [ 2893.044700] do_wp_page+0x4a0/0x5c8
> [ 2893.044708] handle_mm_fault+0x7fc/0x14dc
> [ 2893.044718] do_page_fault+0x29c/0x450
> [ 2893.044727] do_mem_abort+0x4c/0xf8
> [ 2893.044741] el0_da+0x48/0xa8
> [ 2893.044750] el0t_64_sync_handler+0xcc/0xf0
> [ 2893.044759] el0t_64_sync+0x18c/0x190
It claims that the stack overflow happened in do_wp_page(),
but that has a really short call chain. It would be good
to have the source line for do_wp_page+0x4a0/0x5c8 and
wp_page_copy+0xf8/0x90c to see where exactly it was.
> [ 2893.285975] WARNING: CPU: 2 PID: 315758 at kernel/sched/core.c:3119
> set_task_cpu+0x14c/0x208
....
> [ 2893.286117] CPU: 2 PID: 315758 Comm: cgroup_fj_stres Not tainted
> [ 2893.286416] arch_timer_handler_phys+0x44/0x54
> [ 2893.286427] handle_percpu_devid_irq+0x90/0x220
> [ 2893.286439] generic_handle_domain_irq+0x38/0x50
> [ 2893.286447] gic_handle_irq+0x68/0xe8
> [ 2893.286455] el1_interrupt+0x88/0xc8
> [ 2893.286464] el1h_64_irq_handler+0x18/0x24
> [ 2893.286474] el1h_64_irq+0x64/0x68
> [ 2893.286482] panic+0x2d8/0x374
This is apparently a second unrelated bug -- it still processes timer
interrupts after calling panic() and this apparently fails because
the system is already unusable.
> artifact-location:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT
file not found. I tried to get the vmlinux file to look at the disassembly
but the artifacts appear to be gone already.
Arnd
On Wed, 11 Jan 2023 at 13:48, Arnd Bergmann <[email protected]> wrote:
>
> On Wed, Jan 11, 2023, at 07:16, Naresh Kamboju wrote:
> > On Tue, 10 Jan 2023 at 23:36, Greg Kroah-Hartman <[email protected]> wrote:
> >>
> >
> > Results from Linaro’s test farm.
> > Regressions on arm64 Raspberry Pi 4 Model B.
> >
> > Reported-by: Linux Kernel Functional Testing <[email protected]>
> >
> > While running LTP controllers cgroup_fj_stress_blkio test cases
> > the Insufficient stack space to handle exception! occurred and
> > followed by kernel panic on arm64 Raspberry Pi 4 Model B with
> > clang-15 built kernel Image.
> >
> > The full boot and test log attached to this email and build and
> > Kconfig links provided in the bottom of this email.
> >
> > I will try to reproduce this reported issue and get back to you.
>
> I looked at the log between 6.0.18 and 6.0.19-rc1, but don't see
> any arm64 or memory management patches that could result in this.
> Do you know if 6.0.18 ran successful
Yes, it ran successfully on 6.0.18.
On the same kernel 6.0.19-rc1 built with gcc-12 did not find this panic.
The reported issue is specific to clang-15 build.
> > [ 2893.044339] Insufficient stack space to handle exception!
> > [ 2893.044351] ESR: 0x0000000096000047 -- DABT (current EL)
> > [ 2893.044360] FAR: 0xffff8000128180d0
> > [ 2893.044364] Task stack: [0xffff800012a18000..0xffff800012a1c000]
> > [ 2893.044370] IRQ stack: [0xffff80000a798000..0xffff80000a79c000]
> > [ 2893.044375] Overflow stack: [0xffff0000f77c4310..0xffff0000f77c5310]
> ...
> > [ 2893.044413] pc : el1h_64_sync+0x0/0x68
> > [ 2893.044430] lr : wp_page_copy+0xf8/0x90c
> > [ 2893.044445] sp : ffff8000128180d0
> ...
> > [ 2893.044692] el1h_64_sync+0x0/0x68
> > [ 2893.044700] do_wp_page+0x4a0/0x5c8
> > [ 2893.044708] handle_mm_fault+0x7fc/0x14dc
> > [ 2893.044718] do_page_fault+0x29c/0x450
> > [ 2893.044727] do_mem_abort+0x4c/0xf8
> > [ 2893.044741] el0_da+0x48/0xa8
> > [ 2893.044750] el0t_64_sync_handler+0xcc/0xf0
> > [ 2893.044759] el0t_64_sync+0x18c/0x190
>
> It claims that the stack overflow happened in do_wp_page(),
> but that has a really short call chain. It would be good
> to have the source line for do_wp_page+0x4a0/0x5c8 and
> wp_page_copy+0xf8/0x90c to see where exactly it was.
>
>
> > [ 2893.285975] WARNING: CPU: 2 PID: 315758 at kernel/sched/core.c:3119
> > set_task_cpu+0x14c/0x208
> ....
> > [ 2893.286117] CPU: 2 PID: 315758 Comm: cgroup_fj_stres Not tainted
> > [ 2893.286416] arch_timer_handler_phys+0x44/0x54
> > [ 2893.286427] handle_percpu_devid_irq+0x90/0x220
> > [ 2893.286439] generic_handle_domain_irq+0x38/0x50
> > [ 2893.286447] gic_handle_irq+0x68/0xe8
> > [ 2893.286455] el1_interrupt+0x88/0xc8
> > [ 2893.286464] el1h_64_irq_handler+0x18/0x24
> > [ 2893.286474] el1h_64_irq+0x64/0x68
> > [ 2893.286482] panic+0x2d8/0x374
>
> This is apparently a second unrelated bug -- it still processes timer
> interrupts after calling panic() and this apparently fails because
> the system is already unusable.
>
> > artifact-location:
> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT
>
Adding " / " at end works.
https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT/
> file not found. I tried to get the vmlinux file to look at the disassembly
> but the artifacts appear to be gone already.
System.map:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT/System.map
vmlinux:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT/vmlinux.xz
Sorry for the trouble.
- Naresh
>
> Arnd
On Wed, Jan 11, 2023, at 10:31, Naresh Kamboju wrote:
> On Wed, 11 Jan 2023 at 13:48, Arnd Bergmann <[email protected]> wrote:
>> On Wed, Jan 11, 2023, at 07:16, Naresh Kamboju wrote:
>> > On Tue, 10 Jan 2023 at 23:36, Greg Kroah-Hartman <[email protected]> wrote:
>
> Yes, it ran successfully on 6.0.18.
>
> On the same kernel 6.0.19-rc1 built with gcc-12 did not find this panic.
> The reported issue is specific to clang-15 build.
Ok, and was the 6.0.18 build using the exact same clang-15 toolchain,
or could there have been an update to any of the tools?
Have you seen results with older clang releases?
>> > [ 2893.044339] Insufficient stack space to handle exception!
>> > [ 2893.044351] ESR: 0x0000000096000047 -- DABT (current EL)
>> > [ 2893.044360] FAR: 0xffff8000128180d0
>> > [ 2893.044364] Task stack: [0xffff800012a18000..0xffff800012a1c000]
>> > [ 2893.044370] IRQ stack: [0xffff80000a798000..0xffff80000a79c000]
>> > [ 2893.044375] Overflow stack: [0xffff0000f77c4310..0xffff0000f77c5310]
>> ...
>> > [ 2893.044413] pc : el1h_64_sync+0x0/0x68
>> > [ 2893.044430] lr : wp_page_copy+0xf8/0x90c
>> > [ 2893.044445] sp : ffff8000128180d0
>> ...
>> > [ 2893.044646] panic+0x168/0x374
>> > [ 2893.044658] test_taint+0x0/0x38
>> > [ 2893.044667] panic_bad_stack+0x110/0x124
>> > [ 2893.044675] handle_bad_stack+0x34/0x48
>> > [ 2893.044685] __bad_stack+0x78/0x7c
>> > [ 2893.044692] el1h_64_sync+0x0/0x68
>> > [ 2893.044700] do_wp_page+0x4a0/0x5c8
>> > [ 2893.044708] handle_mm_fault+0x7fc/0x14dc
>> > [ 2893.044718] do_page_fault+0x29c/0x450
>> > [ 2893.044727] do_mem_abort+0x4c/0xf8
>> > [ 2893.044741] el0_da+0x48/0xa8
>> > [ 2893.044750] el0t_64_sync_handler+0xcc/0xf0
>> > [ 2893.044759] el0t_64_sync+0x18c/0x190
>>
>> It claims that the stack overflow happened in do_wp_page(),
>> but that has a really short call chain. It would be good
>> to have the source line for do_wp_page+0x4a0/0x5c8 and
>> wp_page_copy+0xf8/0x90c to see where exactly it was.
>>
>> > artifact-location:
>> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT
>>
>
> Adding " / " at end works.
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT/
Ok, I disassembled the image to see what happened.
do_wp_page+0x4a0/0x5c8 is the call to wp_page_copy(), so I would
guess the el1h_64_sync fault actually happened in that function.
lr : wp_page_copy+0xf8/0x90c the return address from
__mem_cgroup_charge(), but I suspect it's not where the fault
happened either, just the last address that was in the
link register.
el1h_64_sync+0x0/0x68 is a "paciasp" pointer authentication
instruction.
__bad_stack is actually called from 'vectors', which has this
code for calling el1h_64_sync, from kernel_ventry:
ffff800008011200: d10543ff sub sp, sp, #0x150
ffff800008011204: 8b2063ff add sp, sp, x0
ffff800008011208: cb2063e0 sub x0, sp, x0
ffff80000801120c: 37700080 tbnz w0, #14, ffff80000801121c <vectors+0x21c>
ffff800008011210: cb2063e0 sub x0, sp, x0
ffff800008011214: cb2063ff sub sp, sp, x0
ffff800008011218: 14000201 b ffff800008011a1c <el1h_64_sync>
ffff80000801121c: d51bd040 msr tpidr_el0, x0
ffff800008011220: cb2063e0 sub x0, sp, x0
ffff800008011224: d51bd060 msr tpidrro_el0, x0
ffff800008011228: f0010a80 adrp x0, ffff80000a164000 <overflow_stack+0xcf0>
ffff80000801122c: 910c401f add sp, x0, #0x310
ffff800008011230: d538d080 mrs x0, tpidr_el1
ffff800008011234: 8b2063ff add sp, sp, x0
ffff800008011238: d53bd040 mrs x0, tpidr_el0
ffff80000801123c: cb2063e0 sub x0, sp, x0
ffff800008011240: f274cc1f tst x0, #0xfffffffffffff000
ffff800008011244: 54002de1 b.ne ffff800008011800 <__bad_stack> // b.any
ffff800008011248: cb2063ff sub sp, sp, x0
ffff80000801124c: d53bd060 mrs x0, tpidrro_el0
ffff800008011250: 140001f3 b ffff800008011a1c <el1h_64_sync>
and here I'm lost now.
Arnd
On Tue, 10 Jan 2023 19:01:44 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.0:
11 builds: 11 pass, 0 fail
28 boots: 28 pass, 0 fail
130 tests: 130 pass, 0 fail
Linux version: 6.0.19-rc1-ga7ffaeeaf9bb
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
On Wed, 11 Jan 2023 at 16:48, Arnd Bergmann <[email protected]> wrote:
>
> On Wed, Jan 11, 2023, at 10:31, Naresh Kamboju wrote:
> > On Wed, 11 Jan 2023 at 13:48, Arnd Bergmann <[email protected]> wrote:
> >> On Wed, Jan 11, 2023, at 07:16, Naresh Kamboju wrote:
> >> > On Tue, 10 Jan 2023 at 23:36, Greg Kroah-Hartman <[email protected]> wrote:
> >
> > Yes, it ran successfully on 6.0.18.
> >
> > On the same kernel 6.0.19-rc1 built with gcc-12 did not find this panic.
> > The reported issue is specific to clang-15 build.
After retesting a couple of times it is confirmed that it is not reproducible.
> Ok, and was the 6.0.18 build using the exact same clang-15 toolchain,
> or could there have been an update to any of the tools?
it is same Clang version 15.0.6
> Have you seen results with older clang releases?
We are not testing with older clang versions.
>
> >> > [ 2893.044339] Insufficient stack space to handle exception!
> >> > [ 2893.044351] ESR: 0x0000000096000047 -- DABT (current EL)
> >> > [ 2893.044360] FAR: 0xffff8000128180d0
> >> > [ 2893.044364] Task stack: [0xffff800012a18000..0xffff800012a1c000]
> >> > [ 2893.044370] IRQ stack: [0xffff80000a798000..0xffff80000a79c000]
> >> > [ 2893.044375] Overflow stack: [0xffff0000f77c4310..0xffff0000f77c5310]
> >> ...
> >> > [ 2893.044413] pc : el1h_64_sync+0x0/0x68
> >> > [ 2893.044430] lr : wp_page_copy+0xf8/0x90c
> >> > [ 2893.044445] sp : ffff8000128180d0
> >> ...
> >> > [ 2893.044646] panic+0x168/0x374
> >> > [ 2893.044658] test_taint+0x0/0x38
> >> > [ 2893.044667] panic_bad_stack+0x110/0x124
> >> > [ 2893.044675] handle_bad_stack+0x34/0x48
> >> > [ 2893.044685] __bad_stack+0x78/0x7c
> >> > [ 2893.044692] el1h_64_sync+0x0/0x68
> >> > [ 2893.044700] do_wp_page+0x4a0/0x5c8
> >> > [ 2893.044708] handle_mm_fault+0x7fc/0x14dc
> >> > [ 2893.044718] do_page_fault+0x29c/0x450
> >> > [ 2893.044727] do_mem_abort+0x4c/0xf8
> >> > [ 2893.044741] el0_da+0x48/0xa8
> >> > [ 2893.044750] el0t_64_sync_handler+0xcc/0xf0
> >> > [ 2893.044759] el0t_64_sync+0x18c/0x190
> >>
> >> It claims that the stack overflow happened in do_wp_page(),
> >> but that has a really short call chain. It would be good
> >> to have the source line for do_wp_page+0x4a0/0x5c8 and
> >> wp_page_copy+0xf8/0x90c to see where exactly it was.
> >>
> >> > artifact-location:
> >> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT
> >>
> >
> > Adding " / " at end works.
> > https://storage.tuxsuite.com/public/linaro/lkft/builds/2K9JDtix2mHMoYRjNkBef3oR5JT/
>
> Ok, I disassembled the image to see what happened.
>
> do_wp_page+0x4a0/0x5c8 is the call to wp_page_copy(), so I would
> guess the el1h_64_sync fault actually happened in that function.
>
> lr : wp_page_copy+0xf8/0x90c the return address from
> __mem_cgroup_charge(), but I suspect it's not where the fault
> happened either, just the last address that was in the
> link register.
>
> el1h_64_sync+0x0/0x68 is a "paciasp" pointer authentication
> instruction.
>
> __bad_stack is actually called from 'vectors', which has this
> code for calling el1h_64_sync, from kernel_ventry:
>
> ffff800008011200: d10543ff sub sp, sp, #0x150
> ffff800008011204: 8b2063ff add sp, sp, x0
> ffff800008011208: cb2063e0 sub x0, sp, x0
> ffff80000801120c: 37700080 tbnz w0, #14, ffff80000801121c <vectors+0x21c>
> ffff800008011210: cb2063e0 sub x0, sp, x0
> ffff800008011214: cb2063ff sub sp, sp, x0
> ffff800008011218: 14000201 b ffff800008011a1c <el1h_64_sync>
> ffff80000801121c: d51bd040 msr tpidr_el0, x0
> ffff800008011220: cb2063e0 sub x0, sp, x0
> ffff800008011224: d51bd060 msr tpidrro_el0, x0
> ffff800008011228: f0010a80 adrp x0, ffff80000a164000 <overflow_stack+0xcf0>
> ffff80000801122c: 910c401f add sp, x0, #0x310
> ffff800008011230: d538d080 mrs x0, tpidr_el1
> ffff800008011234: 8b2063ff add sp, sp, x0
> ffff800008011238: d53bd040 mrs x0, tpidr_el0
> ffff80000801123c: cb2063e0 sub x0, sp, x0
> ffff800008011240: f274cc1f tst x0, #0xfffffffffffff000
> ffff800008011244: 54002de1 b.ne ffff800008011800 <__bad_stack> // b.any
> ffff800008011248: cb2063ff sub sp, sp, x0
> ffff80000801124c: d53bd060 mrs x0, tpidrro_el0
> ffff800008011250: 140001f3 b ffff800008011a1c <el1h_64_sync>
>
> and here I'm lost now.
>
> Arnd
Hi Greg,
On Tue, Jan 10, 2023 at 07:01:44PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +0000.
> Anything received after that time might be too late.
Build test (gcc version 12.2.1 20221127):
mips: 52 configs -> no failure
arm: 100 configs -> no failure
arm64: 3 configs -> no failure
x86_64: 4 configs -> no failure
alpha allmodconfig -> no failure
csky allmodconfig -> no failure
powerpc allmodconfig -> no failure
riscv allmodconfig -> no failure
s390 allmodconfig -> no failure
xtensa allmodconfig -> no failure
Boot test:
x86_64: Booted on my test laptop. No regression.
x86_64: Booted on qemu. No regression. [1]
arm64: Booted on rpi4b (4GB model). No regression. [2]
mips: Booted on ci20 board.
Known issue - VNC server fails to start.
[1]. https://openqa.qa.codethink.co.uk/tests/2608
[2]. https://openqa.qa.codethink.co.uk/tests/2611
Tested-by: Sudip Mukherjee <[email protected]>
--
Regards
Sudip
On Tue, Jan 10, 2023 at 07:01:44PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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 cross-compiled for arm64 (bcm2711_defconfig, GCC 10.2.0) and
powerpc (ps3_defconfig, GCC 12.2.0).
Tested-by: Bagas Sanjaya <[email protected]>
--
An old man doll... just what I always wanted! - Clara
On Tue, 10 Jan 2023 at 23:36, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.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]>
NOTE:
Regression reported on arm64 Raspberry Pi 4 Model B with clang-15
built kernel Image.
Insufficient stack space to handle exception!
end Kernel panic - not syncing: kernel stack overflow
https://lore.kernel.org/stable/CA+G9fYt42ntYZhhzqAYKf8J3TdNZ+fRYwNgQP=TgCLODcpNrfg@mail.gmail.com/
## Build
* kernel: 6.0.19-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-6.0.y
* git commit: a7ffaeeaf9bb7ab13e00a589d0910efb9119479c
* git describe: v6.0.18-149-ga7ffaeeaf9bb
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.0.y/build/v6.0.18-149-ga7ffaeeaf9bb
## Test Regressions (compared to v6.0.18)
## Metric Regressions (compared to v6.0.18)
## Test Fixes (compared to v6.0.18)
## Metric Fixes (compared to v6.0.18)
## Test result summary
total: 167741, pass: 139653, fail: 4441, skip: 23296, xfail: 351
## Build Summary
* arc: 5 total, 5 passed, 0 failed
* arm: 151 total, 148 passed, 3 failed
* arm64: 49 total, 49 passed, 0 failed
* i386: 39 total, 36 passed, 3 failed
* mips: 30 total, 28 passed, 2 failed
* parisc: 8 total, 8 passed, 0 failed
* powerpc: 38 total, 32 passed, 6 failed
* riscv: 16 total, 16 passed, 0 failed
* s390: 16 total, 16 passed, 0 failed
* sh: 14 total, 12 passed, 2 failed
* sparc: 8 total, 8 passed, 0 failed
* x86_64: 42 total, 41 passed, 1 failed
## Test suites summary
* boot
* fwts
* igt-gpu-tools
* 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-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-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-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libgpiod
* libhugetlbfs
* 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-math++
* ltp-mm
* ltp-nptl
* ltp-open-posix-tests
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* packetdrill
* perf
* rcutorture
* v4l2-compliance
* vdso
--
Linaro LKFT
https://lkft.linaro.org
On Tue, Jan 10, 2023 at 07:01:44PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Tested rc1 against the Fedora build system (aarch64, armv7, ppc64le,
s390x, x86_64), and boot tested x86_64. No regressions noted.
Tested-by: Justin M. Forbes <[email protected]>
On Tue, Jan 10, 2023 at 07:01:44PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +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.0.19-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.0.y
> and the diffstat can be found below.
Tested-by: Conor Dooley <[email protected]>
Thanks,
Conor.
On Tue, Jan 10, 2023 at 07:01:44PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.19 release.
> There are 148 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.
>
> NOTE, this will probably be the LAST 6.0.y release. If there is
> anything preventing you from moving to 6.1.y right now, please let me
> know.
>
> Responses should be made by Thu, 12 Jan 2023 17:59:42 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 155 pass: 155 fail: 0
Qemu test results:
total: 500 pass: 500 fail: 0
Tested-by: Guenter Roeck <[email protected]>
Guenter
Hi!
> Results from Linaro’s test farm.
> Regressions on arm64 Raspberry Pi 4 Model B.
>
> Reported-by: Linux Kernel Functional Testing <[email protected]>
>
> While running LTP controllers cgroup_fj_stress_blkio test cases
> the Insufficient stack space to handle exception! occurred and
> followed by kernel panic on arm64 Raspberry Pi 4 Model B with
> clang-15 built kernel Image.
>
> The full boot and test log attached to this email and build and
> Kconfig links provided in the bottom of this email.
Full log is 11MB. That's rather... big for an email. Please post such
stuff as a link or at least compress them...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Hi Pavel,
On Fri, 13 Jan 2023 at 15:03, Pavel Machek <[email protected]> wrote:
>
> Hi!
> Full log is 11MB. That's rather... big for an email. Please post such
> stuff as a link or at least compress them...
Thanks for the comments,
And i did in the next email with a trimmed version of log files.
[ + attachment failed resending with trim version of log file. ]
In general practice, I do share links to log files, kconfigs and artifacts.
Thank you.
Naresh Kamboju