This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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 gregkh@linuxfoundation.org Linux 6.1.47-rc1
Yangtao Li frank.li@vivo.com mmc: f-sdh30: fix order of function calls in sdhci_f_sdh30_remove
Jason Xing kernelxing@tencent.com net: fix the RTO timer retransmitting skb every 1ms if linear option is enabled
Karol Herbst kherbst@redhat.com drm/nouveau/disp: fix use-after-free in error handling of nouveau_connector_create
Kuniyuki Iwashima kuniyu@amazon.com af_unix: Fix null-ptr-deref in unix_stream_sendpage().
Guchun Chen guchun.chen@amd.com drm/amdgpu: keep irq count in amdgpu_irq_disable_all
Tim Huang Tim.Huang@amd.com drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11
Mark Brown broonie@kernel.org arm64/ptrace: Ensure that SME is set up for target when writing SSVE state
Borislav Petkov (AMD) bp@alien8.de x86/srso: Correct the mitigation status when SMT is disabled
Peter Zijlstra peterz@infradead.org objtool/x86: Fixup frame-pointer vs rethunk
Petr Pavlu petr.pavlu@suse.com x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG
Borislav Petkov (AMD) bp@alien8.de x86/srso: Disable the mitigation on unaffected configurations
Borislav Petkov (AMD) bp@alien8.de x86/CPU/AMD: Fix the DIV(0) initial fix attempt
Sean Christopherson seanjc@google.com x86/retpoline: Don't clobber RFLAGS during srso_safe_ret()
Peter Zijlstra peterz@infradead.org x86/static_call: Fix __static_call_fixup()
Borislav Petkov (AMD) bp@alien8.de x86/srso: Explain the untraining sequences a bit more
Peter Zijlstra peterz@infradead.org x86/cpu: Cleanup the untrain mess
Peter Zijlstra peterz@infradead.org x86/cpu: Rename srso_(.*)_alias to srso_alias_\1
Peter Zijlstra peterz@infradead.org x86/cpu: Rename original retbleed methods
Peter Zijlstra peterz@infradead.org x86/cpu: Clean up SRSO return thunk mess
Peter Zijlstra peterz@infradead.org x86/alternative: Make custom return thunk unconditional
Peter Zijlstra peterz@infradead.org x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk()
Peter Zijlstra peterz@infradead.org x86/cpu: Fix __x86_return_thunk symbol type
Xin Long lucien.xin@gmail.com netfilter: set default timeout to 3 secs for sctp shutdown send and recv state
Mike Kravetz mike.kravetz@oracle.com hugetlb: do not clear hugetlb dtor until allocating vmemmap
Saaem Rizvi SyedSaaem.Rizvi@amd.com drm/amd/display: Implement workaround for writing to OTG_PIXEL_RATE_DIV register
Vincent Guittot vincent.guittot@linaro.org sched/fair: Remove capacity inversion detection
Vincent Guittot vincent.guittot@linaro.org sched/fair: unlink misfit task from cpu overutilized
Sergey Senozhatsky senozhatsky@chromium.org zsmalloc: allow only one active pool compaction context
Daniel Miess daniel.miess@amd.com drm/amd/display: disable RCO for DCN314
Arnd Bergmann arnd@arndb.de ASoC: amd: vangogh: select CONFIG_SND_AMD_ACP_CONFIG
Umio Yasuno coelacanth_dream@protonmail.com drm/amdgpu/pm: fix throttle_status for other than MP1 11.0.7
Tim Huang Tim.Huang@amd.com drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix
Mario Limonciello mario.limonciello@amd.com drm/amd: flush any delayed gfxoff on suspend entry
Jani Nikula jani.nikula@intel.com drm/i915/sdvo: fix panel_type initialization
Wander Lairson Costa wander@redhat.com drm/qxl: fix UAF on handle creation
Yibin Ding yibin.ding@unisoc.com mmc: block: Fix in_flight[issue_type] value error
Yang Yingliang yangyingliang@huawei.com mmc: wbsd: fix double mmc_free_host() in wbsd_init()
Sweet Tea Dorminy sweettea-kernel@dorminy.me blk-crypto: dynamically allocate fallback profile
Yogesh Hegde yogi.kernel@gmail.com arm64: dts: rockchip: Fix Wifi/Bluetooth on ROCK Pi 4 boards
Hawkins Jiawei yin31149@gmail.com virtio-net: Zero max_tx_vq field for VIRTIO_NET_CTRL_MQ_HASH_CONFIG case
Mingzheng Xing xingmingzheng@iscas.ac.cn riscv: Handle zicsr/zifencei issue between gcc and binutils
Russell Harmon via samba-technical samba-technical@lists.samba.org cifs: Release folio lock on fscache read hit.
dengxiang dengxiang@nfschina.com ALSA: usb-audio: Add support for Mythware XA001AU capture and playback interfaces.
Tony Lindgren tony@atomide.com serial: 8250: Fix oops for port->pm on uart_change_pm()
Alexandre Ghiti alexghiti@rivosinc.com riscv: uaccess: Return the number of bytes effectively not copied
Kailang Yang kailang@realtek.com ALSA: hda/realtek - Remodified 3k pull low procedure
Jiasheng Jiang jiasheng@iscas.ac.cn soc: aspeed: socinfo: Add kfree for kstrdup
Zev Weiss zev@bewilderbeest.net soc: aspeed: uart-routing: Use __sysfs_match_string
Stefan Binding sbinding@opensource.cirrus.com ALSA: hda/realtek: Add quirks for HP G11 Laptops
Jerome Brunet jbrunet@baylibre.com ASoC: meson: axg-tdm-formatter: fix channel slot allocation
Zhang Shurong zhang_shurong@foxmail.com ASoC: rt5665: add missed regulator_bulk_disable
Alexander Stein alexander.stein@ew.tq-group.com arm64: dts: imx93: Fix anatop node size
Xiaolei Wang xiaolei.wang@windriver.com ARM: dts: imx: Set default tuning step for imx6sx usdhc
Fabio Estevam festevam@denx.de arm64: dts: imx8mm: Drop CSI1 PHY reference clock configuration
Andrej Picej andrej.picej@norik.com ARM: dts: imx6: phytec: fix RTC interrupt level
Krzysztof Kozlowski krzysztof.kozlowski@linaro.org ARM: dts: imx: align LED node names with dtschema
Christopher Obbard chris.obbard@collabora.com arm64: dts: rockchip: Disable HS400 for eMMC on ROCK 4C+
Christopher Obbard chris.obbard@collabora.com arm64: dts: rockchip: Disable HS400 for eMMC on ROCK Pi 4
Dmitry Baryshkov dmitry.baryshkov@linaro.org arm64: dts: qcom: qrb5165-rb5: fix thermal zone conflict
Tony Lindgren tony@atomide.com bus: ti-sysc: Flush posted write on enable before reset
Marcin Szycik marcin.szycik@linux.intel.com ice: Block switchdev mode when ADQ is active and vice versa
Manish Chopra manishc@marvell.com qede: fix firmware halt over suspend and resume
Eric Dumazet edumazet@google.com net: do not allow gso_size to be set to GSO_BY_FRAGS
Abel Wu wuyun.abel@bytedance.com sock: Fix misuse of sk_under_memory_pressure()
Edward Cree ecree.xilinx@gmail.com sfc: don't unregister flow_indr if it was never registered
Alfred Lee l00g33k@gmail.com net: dsa: mv88e6xxx: Wait for EEPROM done before HW reset
Andrii Staikov andrii.staikov@intel.com i40e: fix misleading debug logs
Piotr Gardocki piotrx.gardocki@intel.com iavf: fix FDIR rule fields masks validation
Jakub Kicinski kuba@kernel.org net: openvswitch: reject negative ifindex
Ziyang Xuan william.xuanziyang@huawei.com team: Fix incorrect deletion of ETH_P_8021AD protocol vid from slaves
Justin Chen justin.chen@broadcom.com net: phy: broadcom: stub c45 read/write for 54810
Pablo Neira Ayuso pablo@netfilter.org netfilter: nft_dynset: disallow object maps
Sishuai Gong sishuai.system@gmail.com ipvs: fix racy memcpy in proc_do_sync_threshold
Florian Westphal fw@strlen.de netfilter: nf_tables: deactivate catchall elements in next generation
Florian Westphal fw@strlen.de netfilter: nf_tables: fix false-positive lockdep splat
Michal Schmidt mschmidt@redhat.com octeon_ep: cancel tx_timeout_task later in remove sequence
Radhey Shyam Pandey radhey.shyam.pandey@amd.com net: macb: In ZynqMP resume always configure PS GTR for non-wakeup source
Luca Ceresoli luca.ceresoli@bootlin.com drm/panel: simple: Fix AUO G121EAN01 panel timings according to the docs
Petr Machata petrm@nvidia.com selftests: mirror_gre_changes: Tighten up the TTL test match
Russell King (Oracle) rmk+kernel@armlinux.org.uk net: phy: fix IRQ-based wake-on-lan over hibernate / power off
Xiang Yang xiangyang3@huawei.com net: pcs: Add missing put_device call in miic_create
Jason Wang jasowang@redhat.com virtio-net: set queues after driver_ok
Laurent Vivier lvivier@redhat.com virtio_net: notify MAC address change on device initialization
Lin Ma linma@zju.edu.cn xfrm: add forgotten nla_policy for XFRMA_MTIMER_THRESH
Lin Ma linma@zju.edu.cn xfrm: add NULL check in xfrm_update_ae_params
Zhengchao Shao shaozhengchao@huawei.com ip_vti: fix potential slab-use-after-free in decode_session6
Zhengchao Shao shaozhengchao@huawei.com ip6_vti: fix slab-use-after-free in decode_session6
Zhengchao Shao shaozhengchao@huawei.com xfrm: fix slab-use-after-free in decode_session6
Lin Ma linma@zju.edu.cn net: xfrm: Amend XFRMA_SEC_CTX nla_policy structure
Lin Ma linma@zju.edu.cn net: af_key: fix sadb_x_filter validation
Lin Ma linma@zju.edu.cn net: xfrm: Fix xfrm_address_filter OOB read
Tam Nguyen tamnguyenchi@os.amperecomputing.com i2c: designware: Handle invalid SMBus block data response length value
Quan Nguyen quan@os.amperecomputing.com i2c: designware: Correct length byte validation logic
xiaoshoukui xiaoshoukui@gmail.com btrfs: fix BUG_ON condition in btrfs_cancel_balance
Josef Bacik josef@toxicpanda.com btrfs: fix incorrect splitting in btrfs_drop_extent_map_range
Sherry Sun sherry.sun@nxp.com tty: serial: fsl_lpuart: Clear the error flags by writing 1 for lpuart32 platforms
Yi Yang yiyang13@huawei.com tty: n_gsm: fix the UAF caused by race condition in gsm_cleanup_mux
Dragos Tatulea dtatulea@nvidia.com vdpa: Enable strict validation for netlinks ops
Lin Ma linma@zju.edu.cn vdpa: Add max vqp attr to vdpa_nl_policy for nlattr length check
Lin Ma linma@zju.edu.cn vdpa: Add queue index attr to vdpa_nl_policy for nlattr length check
Lin Ma linma@zju.edu.cn vdpa: Add features attr to vdpa_nl_policy for nlattr length check
Nathan Lynch nathanl@linux.ibm.com powerpc/rtas_flash: allow user copy to flash block cache objects
Yuanjun Gong ruc_gongyuanjun@163.com fbdev: mmp: fix value check in mmphw_probe()
Parker Newman pnewman@connecttech.com i2c: tegra: Fix i2c-tegra DMA config option processing
Yicong Yang yangyicong@hisilicon.com i2c: hisi: Only handle the interrupt of the driver's transfer
Chengfeng Ye dg573847474@gmail.com i2c: bcm-iproc: Fix bcm_iproc_i2c_isr deadlock issue
Steve French stfrench@microsoft.com cifs: fix potential oops in cifs_oplock_break
Eugenio Pérez eperezma@redhat.com vdpa/mlx5: Delete control vq iotlb in destroy_mr only when necessary
Dragos Tatulea dtatulea@nvidia.com vdpa/mlx5: Fix mr->initialized semantics
Maxime Coquelin maxime.coquelin@redhat.com vduse: Use proper spinlock for IRQ injection
Wolfram Sang wsa+renesas@sang-engineering.com virtio-mmio: don't break lifecycle of vm_dev
Filipe Manana fdmanana@suse.com btrfs: fix use-after-free of new block group that became unused
David Sterba dsterba@suse.com btrfs: convert btrfs_block_group::seq_zone to runtime flag
David Sterba dsterba@suse.com btrfs: convert btrfs_block_group::needs_free_space to runtime flag
Naohiro Aota naota@elisp.net btrfs: move out now unused BG from the reclaim list
Daniel Vetter daniel.vetter@ffwll.ch video/aperture: Only remove sysfb on the default vga pci device
Thomas Zimmermann tzimmermann@suse.de fbdev/hyperv-fb: Do not set struct fb_info.apertures
Xu Yang xu.yang_2@nxp.com ARM: dts: nxp/imx6sll: fix wrong property name in usbphy node
Marc Zyngier maz@kernel.org KVM: arm64: vgic-v4: Make the doorbell request robust w.r.t preemption
Hersen Wu hersenxs.wu@amd.com drm/amd/display: fix access hdcp_workqueue assert
hersen wu hersenxs.wu@amd.com drm/amd/display: phase3 mst hdcp for multiple displays
hersen wu hersenxs.wu@amd.com drm/amd/display: save restore hdcp state when display is unplugged from mst hub
Song Yoong Siang yoong.siang.song@intel.com igc: read before write to SRRCTL register
Chen Lin chen.lin5@zte.com.cn ring-buffer: Do not swap cpu_buffer during resize process
Andy Shevchenko andriy.shevchenko@linux.intel.com Bluetooth: MGMT: Use correct address for memcpy()
Benjamin Gray bgray@linux.ibm.com powerpc/kasan: Disable KCOV in KASAN code
Luke D. Jones luke@ljones.dev ALSA: hda/realtek: Add quirk for ASUS ROG GZ301V
Luke D. Jones luke@ljones.dev ALSA: hda/realtek: Add quirk for ASUS ROG GA402X
Luke D. Jones luke@ljones.dev ALSA: hda/realtek: Add quirk for ASUS ROG GX650P
Tuo Li islituo@gmail.com ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync()
dengxiang dengxiang@nfschina.com ALSA: hda/realtek: Add quirks for Unis H3C Desktop B760 & Q760
Konstantin Komarov almaz.alexandrovich@paragon-software.com fs/ntfs3: Mark ntfs dirty when on-disk struct is corrupted
Jia-Ju Bai baijiaju@buaa.edu.cn fs: ntfs3: Fix possible null-pointer dereferences in mi_read()
Edward Lo loyuantsung@gmail.com fs/ntfs3: Enhance sanity check while generating attr_list
shanzhulig shanzhulig@gmail.com drm/amdgpu: Fix potential fence use-after-free v2
Xiubo Li xiubli@redhat.com ceph: try to dump the msgs when decoding fails
Matthew Anderson ruinairas1992@gmail.com Bluetooth: btusb: Add MT7922 bluetooth ID for the Asus Ally
Zhengping Jiang jiangzp@google.com Bluetooth: L2CAP: Fix use-after-free
Yuechao Zhao yuechao.zhao@advantech.com.cn watchdog: sp5100_tco: support Hygon FCH/SCH (Server Controller Hub)
Zhang Shurong zhang_shurong@foxmail.com firewire: net: fix use after free in fwnet_finish_incoming_packet()
Mika Westerberg mika.westerberg@linux.intel.com thunderbolt: Limit Intel Barlow Ridge USB3 bandwidth
Mika Westerberg mika.westerberg@linux.intel.com thunderbolt: Add Intel Barlow Ridge PCI ID
Armin Wolf W_Armin@gmx.de pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()
Tuo Li islituo@gmail.com gfs2: Fix possible data races in gfs2_show_options()
Xu Yang xu.yang_2@nxp.com usb: chipidea: imx: add missing USB PHY DPDM wakeup setting
Xu Yang xu.yang_2@nxp.com usb: chipidea: imx: don't request QoS for imx8ulp
Mika Westerberg mika.westerberg@linux.intel.com thunderbolt: Read retimer NVM authentication status prior tb_retimer_set_inbound_sbtx()
Hans Verkuil hverkuil-cisco@xs4all.nl media: platform: mediatek: vpu: fix NULL ptr dereference
Avichal Rakesh arakesh@google.com usb: gadget: uvc: queue empty isoc requests if no video buffer is available
Prashanth K quic_prashk@quicinc.com usb: gadget: u_serial: Avoid spinlock recursion in __gs_console_push
Andrey Konovalov andrey.konovalov@linaro.org media: camss: set VFE bpl_alignment to 16 for sdm845 and sm8250
Yunfei Dong yunfei.dong@mediatek.com media: v4l2-mem2mem: add lock to protect parameter num_rdy
Lu Hongfei luhongfei@vivo.com led: qcom-lpg: Fix resource leaks in for_each_available_child_of_node() loops
Uwe Kleine-König u.kleine-koenig@pengutronix.de serial: stm32: Ignore return value of uart_remove_one_port() in .remove()
Winston Wen wentao@uniontech.com cifs: fix session state check in reconnect to avoid use-after-free issue
Paulo Alcantara pc@manguebit.com smb: client: fix warning in cifs_smb3_do_mount()
Matthew Anderson ruinairas1992@gmail.com ALSA: hda/realtek: Add quirks for ROG ALLY CS35l41 audio
Even Xu even.xu@intel.com HID: intel-ish-hid: ipc: Add Arrow Lake PCI device ID
Peter Ujfalusi peter.ujfalusi@linux.intel.com ASoC: SOF: core: Free the firmware trace before calling snd_sof_shutdown()
Daniel Miess daniel.miess@amd.com drm/amd/display: Enable dcn314 DPP RCO
Nicholas Kazlauskas nicholas.kazlauskas@amd.com drm/amd/display: Skip DPP DTO update if root clock is gated
Patrisious Haddad phaddad@nvidia.com RDMA/mlx5: Return the firmware result upon destroying QP/RQ
Alvin Lee alvin.lee2@amd.com drm/amd/display: Apply 60us prefetch for DCFCLK <= 300Mhz
Lang Yu Lang.Yu@amd.com drm/amdgpu: install stub fence into potential unused fence pointers
Suravee Suthikulpanit suravee.suthikulpanit@amd.com iommu/amd: Introduce Disable IRTE Caching Support
stuarthayhurst stuart.a.hayhurst@gmail.com HID: logitech-hidpp: Add USB and Bluetooth IDs for the Logitech G915 TKL Keyboard
Ofir Bitton obitton@habana.ai accel/habanalabs: add pci health check during heartbeat
gaoxu gaoxu2@hihonor.com dma-remap: use kvmalloc_array/kvfree for larger dma memory remap
Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com ASoC: SOF: Intel: fix SoundWire/HDaudio mutual exclusion
Geert Uytterhoeven geert+renesas@glider.be iopoll: Call cpu_relax() in busy loops
Uday M Bhat uday.m.bhat@intel.com ASoC: Intel: sof_sdw: Add support for Rex soundwire
Bard Liao yung-chuan.liao@linux.intel.com ASoC: Intel: sof_sdw_rt_sdca_jack_common: test SOF_JACK_JDSRC in _exit
Oleksij Rempel linux@rempel-privat.de ARM: dts: imx6dl: prtrvt, prtvt7, prti6q, prtwd2: fix USB related warnings
Venkata Prasad Potturu venkataprasad.potturu@amd.com ASoC: amd: vangogh: Add check for acp config flags in vangogh platform
Wolfram Sang wsa+renesas@sang-engineering.com drm: rcar-du: remove R-Car H3 ES1.* workarounds
Raphael Gallais-Pou raphael.gallais-pou@foss.st.com drm/stm: ltdc: fix late dereference check
Venkata Prasad Potturu venkataprasad.potturu@amd.com ASoC: SOF: amd: Add pci revision id check
Sumit Gupta sumitg@nvidia.com PCI: tegra194: Fix possible array out of bounds access
Peter Ujfalusi peter.ujfalusi@linux.intel.com ASoC: Intel: sof_sdw: add quirk for LNL RVP
Bard Liao yung-chuan.liao@linux.intel.com ASoC: Intel: sof_sdw: add quirk for MTL RVP
Jack Xiao Jack.Xiao@amd.com drm/amdgpu: fix memory leak in mes self test
hackyzh002 hackyzh002@gmail.com drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
Longlong Yao Longlong.Yao@amd.com drm/amdgpu: fix calltrace warning in amddrm_buddy_fini
Li Yang leoyang.li@nxp.com net: phy: at803x: fix the wol setting functions
Christophe JAILLET christophe.jaillet@wanadoo.fr net: phy: at803x: Use devm_regulator_get_enable_optional()
Gerd Bayer gbayer@linux.ibm.com net/smc: Fix setsockopt and sysctl to specify same buffer size again
D. Wythe alibuda@linux.alibaba.com net/smc: replace mutex rmbs_lock and sndbufs_lock with rw_semaphore
Ido Schimmel idosch@nvidia.com selftests: forwarding: tc_actions: Use ncat instead of nc
Davide Caratti dcaratti@redhat.com selftests: forwarding: tc_actions: cleanup temporary files when test is aborted
Andrew Yang andrew.yang@mediatek.com zsmalloc: fix races between modifications of fullness and isolated
Nhat Pham nphamcs@gmail.com zsmalloc: consolidate zs_pool's migrate_lock and size_class's locks
Maulik Shah quic_mkshah@quicinc.com cpuidle: psci: Move enabling OSI mode after power domains creation
Ulf Hansson ulf.hansson@linaro.org cpuidle: psci: Extend information in log about OSI/PC mode
Kunihiko Hayashi hayashi.kunihiko@socionext.com mmc: sdhci-f-sdh30: Replace with sdhci_pltfm
-------------
Diffstat:
Documentation/admin-guide/hw-vuln/srso.rst | 4 +- Documentation/admin-guide/kernel-parameters.txt | 1 + Makefile | 4 +- arch/arm/boot/dts/imx50-kobo-aura.dts | 2 +- arch/arm/boot/dts/imx53-cx9020.dts | 10 +- arch/arm/boot/dts/imx53-m53evk.dts | 4 +- arch/arm/boot/dts/imx53-m53menlo.dts | 6 +- arch/arm/boot/dts/imx53-tx53.dtsi | 2 +- arch/arm/boot/dts/imx53-usbarmory.dts | 2 +- arch/arm/boot/dts/imx6dl-b1x5pv2.dtsi | 6 +- arch/arm/boot/dts/imx6dl-prtrvt.dts | 4 + arch/arm/boot/dts/imx6dl-riotboard.dts | 4 +- arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 6 +- arch/arm/boot/dts/imx6q-gw5400-a.dts | 6 +- arch/arm/boot/dts/imx6q-h100.dts | 6 +- arch/arm/boot/dts/imx6q-kp.dtsi | 4 +- arch/arm/boot/dts/imx6q-marsboard.dts | 4 +- arch/arm/boot/dts/imx6q-tbs2910.dts | 2 +- arch/arm/boot/dts/imx6qdl-emcon.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw51xx.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw52xx.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw53xx.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw54xx.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw551x.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-gw552x.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw553x.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw560x.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5903.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-gw5904.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5907.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw5910.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5912.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5913.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi | 10 +- arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-phytec-mira.dtsi | 8 +- arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-prti6q.dtsi | 11 +- arch/arm/boot/dts/imx6qdl-rex.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-ts7970.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-tx6.dtsi | 2 +- arch/arm/boot/dts/imx6sl-evk.dts | 2 +- arch/arm/boot/dts/imx6sll-evk.dts | 2 +- arch/arm/boot/dts/imx6sll.dtsi | 2 +- arch/arm/boot/dts/imx6sx-sabreauto.dts | 2 +- arch/arm/boot/dts/imx6sx-udoo-neo.dtsi | 4 +- arch/arm/boot/dts/imx6sx.dtsi | 6 + arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi | 2 +- arch/arm/boot/dts/imx6ul-tx6ul.dtsi | 2 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 7 +- arch/arm64/boot/dts/freescale/imx93.dtsi | 2 +- arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 2 +- .../boot/dts/rockchip/rk3399-rock-4c-plus.dts | 3 +- arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 6 +- arch/arm64/include/asm/fpsimd.h | 4 +- arch/arm64/include/asm/kvm_host.h | 2 + arch/arm64/kernel/fpsimd.c | 6 +- arch/arm64/kernel/ptrace.c | 9 +- arch/arm64/kernel/signal.c | 2 +- arch/arm64/kvm/arm.c | 6 +- arch/arm64/kvm/vgic/vgic-v3.c | 2 +- arch/arm64/kvm/vgic/vgic-v4.c | 7 +- arch/powerpc/kernel/rtas_flash.c | 6 +- arch/powerpc/mm/kasan/Makefile | 1 + arch/riscv/Kconfig | 28 +-- arch/riscv/kernel/compat_vdso/Makefile | 8 +- arch/riscv/lib/uaccess.S | 11 +- arch/x86/include/asm/entry-common.h | 1 + arch/x86/include/asm/nospec-branch.h | 28 +-- arch/x86/kernel/cpu/amd.c | 1 + arch/x86/kernel/cpu/bugs.c | 28 ++- arch/x86/kernel/static_call.c | 13 ++ arch/x86/kernel/traps.c | 2 - arch/x86/kernel/vmlinux.lds.S | 20 +- arch/x86/kvm/svm/svm.c | 2 + arch/x86/lib/retpoline.S | 141 +++++++++----- block/blk-crypto-fallback.c | 36 ++-- drivers/bluetooth/btusb.c | 3 + drivers/bus/ti-sysc.c | 2 + drivers/cpuidle/cpuidle-psci-domain.c | 42 ++-- drivers/firewire/net.c | 6 +- drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 8 +- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 41 +++- drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c | 9 +- drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c | 1 - drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 6 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 211 +++++++++++++++++---- .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_hdcp.h | 14 ++ .../amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 30 +++ drivers/gpu/drm/amd/display/dc/dcn20/dcn20_dccg.h | 3 +- drivers/gpu/drm/amd/display/dc/dcn31/dcn31_dccg.c | 8 + .../gpu/drm/amd/display/dc/dcn314/dcn314_dccg.c | 5 + .../drm/amd/display/dc/dcn314/dcn314_resource.c | 20 ++ drivers/gpu/drm/amd/display/dc/dcn32/dcn32_dccg.c | 22 +++ drivers/gpu/drm/amd/display/dc/dcn32/dcn32_dccg.h | 3 +- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c | 2 +- .../gpu/drm/amd/display/dc/dcn32/dcn32_resource.h | 3 +- .../amd/display/dc/dml/dcn32/display_mode_vba_32.c | 4 +- .../amd/display/dc/dml/dcn32/display_mode_vba_32.h | 2 +- drivers/gpu/drm/amd/display/dc/inc/hw/dccg.h | 1 + drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c | 4 +- .../drm/amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 14 +- drivers/gpu/drm/i915/display/intel_sdvo.c | 2 +- drivers/gpu/drm/nouveau/nouveau_connector.c | 8 +- drivers/gpu/drm/panel/panel-simple.c | 24 +-- drivers/gpu/drm/qxl/qxl_drv.h | 2 +- drivers/gpu/drm/qxl/qxl_dumb.c | 5 +- drivers/gpu/drm/qxl/qxl_gem.c | 25 ++- drivers/gpu/drm/qxl/qxl_ioctl.c | 6 +- drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 37 +--- drivers/gpu/drm/rcar-du/rcar_du_drv.c | 48 ----- drivers/gpu/drm/rcar-du/rcar_du_drv.h | 2 - drivers/gpu/drm/rcar-du/rcar_du_regs.h | 3 +- drivers/gpu/drm/stm/ltdc.c | 4 +- drivers/hid/hid-logitech-hidpp.c | 4 + drivers/hid/intel-ish-hid/ipc/hw-ish.h | 1 + drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 + drivers/i2c/busses/i2c-bcm-iproc.c | 11 +- drivers/i2c/busses/i2c-designware-master.c | 16 +- drivers/i2c/busses/i2c-hisi.c | 8 + drivers/i2c/busses/i2c-tegra.c | 2 +- drivers/infiniband/hw/mlx5/qpc.c | 10 +- drivers/iommu/amd/amd_iommu_types.h | 4 + drivers/iommu/amd/init.c | 36 ++++ drivers/leds/rgb/leds-qcom-lpg.c | 8 +- drivers/media/platform/mediatek/vpu/mtk_vpu.c | 6 +- drivers/media/platform/qcom/camss/camss-vfe.c | 6 +- drivers/misc/habanalabs/common/device.c | 15 +- drivers/misc/habanalabs/common/habanalabs.h | 2 + drivers/misc/habanalabs/common/habanalabs_drv.c | 2 - drivers/mmc/core/block.c | 7 +- drivers/mmc/host/sdhci_f_sdh30.c | 66 +++---- drivers/mmc/host/wbsd.c | 2 - drivers/net/dsa/mv88e6xxx/chip.c | 8 + drivers/net/ethernet/cadence/macb_main.c | 9 +- drivers/net/ethernet/intel/i40e/i40e_nvm.c | 16 +- drivers/net/ethernet/intel/iavf/iavf_ethtool.c | 10 + drivers/net/ethernet/intel/iavf/iavf_fdir.c | 77 +++++++- drivers/net/ethernet/intel/iavf/iavf_fdir.h | 2 + drivers/net/ethernet/intel/ice/ice_eswitch.c | 6 + drivers/net/ethernet/intel/ice/ice_main.c | 5 + drivers/net/ethernet/intel/igc/igc_base.h | 11 +- drivers/net/ethernet/intel/igc/igc_main.c | 7 +- .../net/ethernet/marvell/octeon_ep/octep_main.c | 2 +- drivers/net/ethernet/qlogic/qede/qede_main.c | 10 + drivers/net/ethernet/sfc/tc.c | 2 +- drivers/net/pcs/pcs-rzn1-miic.c | 10 +- drivers/net/phy/at803x.c | 89 ++++----- drivers/net/phy/broadcom.c | 13 ++ drivers/net/phy/phy_device.c | 13 +- drivers/net/team/team.c | 4 +- drivers/net/virtio_net.c | 26 ++- drivers/pci/controller/dwc/pcie-tegra194.c | 13 +- drivers/pcmcia/rsrc_nonstatic.c | 2 + drivers/soc/aspeed/aspeed-socinfo.c | 1 + drivers/soc/aspeed/aspeed-uart-routing.c | 2 +- drivers/thunderbolt/nhi.c | 2 + drivers/thunderbolt/nhi.h | 4 + drivers/thunderbolt/quirks.c | 8 + drivers/thunderbolt/retimer.c | 29 ++- drivers/tty/n_gsm.c | 3 +- drivers/tty/serial/8250/8250_port.c | 1 + drivers/tty/serial/fsl_lpuart.c | 4 +- drivers/tty/serial/stm32-usart.c | 5 +- drivers/usb/chipidea/ci_hdrc_imx.c | 5 + drivers/usb/chipidea/usbmisc_imx.c | 2 +- drivers/usb/gadget/function/u_serial.c | 3 + drivers/usb/gadget/function/uvc_video.c | 32 +++- drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 + drivers/vdpa/mlx5/core/mr.c | 105 +++++++--- drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 +- drivers/vdpa/vdpa.c | 9 +- drivers/vdpa/vdpa_user/vduse_dev.c | 8 +- drivers/video/aperture.c | 7 +- drivers/video/fbdev/hyperv_fb.c | 17 +- drivers/video/fbdev/mmp/hw/mmp_ctrl.c | 4 +- drivers/virtio/virtio_mmio.c | 5 +- drivers/watchdog/sp5100_tco.c | 4 +- fs/btrfs/block-group.c | 14 +- fs/btrfs/block-group.h | 18 +- fs/btrfs/extent_map.c | 6 +- fs/btrfs/free-space-tree.c | 10 +- fs/btrfs/tests/free-space-tree-tests.c | 2 +- fs/btrfs/volumes.c | 3 +- fs/btrfs/zoned.c | 7 +- fs/ceph/mds_client.c | 4 + fs/gfs2/super.c | 26 +-- fs/ntfs3/frecord.c | 16 +- fs/ntfs3/fsntfs.c | 2 +- fs/ntfs3/index.c | 6 + fs/ntfs3/ntfs_fs.h | 2 + fs/ntfs3/record.c | 10 +- fs/smb/client/cifsfs.c | 28 +-- fs/smb/client/file.c | 25 ++- fs/smb/client/smb2pdu.c | 6 + include/kvm/arm_vgic.h | 2 +- include/linux/iopoll.h | 2 + include/linux/virtio_net.h | 4 + include/media/v4l2-mem2mem.h | 18 +- include/net/sock.h | 6 + kernel/dma/remap.c | 4 +- kernel/sched/fair.c | 193 +++++++++---------- kernel/sched/sched.h | 19 -- kernel/trace/ring_buffer.c | 14 +- kernel/trace/trace.c | 3 +- mm/hugetlb.c | 75 +++++--- mm/zsmalloc.c | 113 +++++------ net/bluetooth/l2cap_core.c | 5 + net/bluetooth/mgmt.c | 2 +- net/core/sock.c | 2 +- net/ipv4/ip_vti.c | 4 +- net/ipv4/tcp_timer.c | 4 +- net/ipv6/ip6_vti.c | 4 +- net/key/af_key.c | 4 +- net/netfilter/ipvs/ip_vs_ctl.c | 4 + net/netfilter/nf_conntrack_proto_sctp.c | 6 +- net/netfilter/nf_tables_api.c | 1 + net/netfilter/nft_dynset.c | 3 + net/netfilter/nft_set_pipapo.c | 13 +- net/openvswitch/datapath.c | 8 +- net/smc/af_smc.c | 4 +- net/smc/smc.h | 2 +- net/smc/smc_clc.c | 4 +- net/smc/smc_core.c | 80 ++++---- net/smc/smc_core.h | 4 +- net/smc/smc_llc.c | 16 +- net/smc/smc_sysctl.c | 10 +- net/unix/af_unix.c | 9 +- net/xfrm/xfrm_compat.c | 2 +- net/xfrm/xfrm_interface_core.c | 4 +- net/xfrm/xfrm_user.c | 14 +- sound/hda/hdac_regmap.c | 7 +- sound/pci/hda/patch_realtek.c | 91 ++++++++- sound/soc/amd/Kconfig | 1 + sound/soc/amd/vangogh/acp5x.h | 2 + sound/soc/amd/vangogh/pci-acp5x.c | 7 +- sound/soc/codecs/rt5665.c | 2 + sound/soc/intel/boards/sof_sdw.c | 25 +++ sound/soc/intel/boards/sof_sdw_rt711_sdca.c | 3 + sound/soc/meson/axg-tdm-formatter.c | 42 ++-- sound/soc/sof/amd/acp.h | 3 + sound/soc/sof/amd/pci-rmb.c | 3 + sound/soc/sof/amd/pci-rn.c | 3 + sound/soc/sof/core.c | 4 +- sound/soc/sof/intel/hda.c | 12 +- sound/usb/quirks-table.h | 29 +++ tools/objtool/arch/x86/decode.c | 2 +- tools/objtool/check.c | 21 +- .../selftests/net/forwarding/mirror_gre_changes.sh | 3 +- .../testing/selftests/net/forwarding/tc_actions.sh | 18 +- 255 files changed, 2074 insertions(+), 1100 deletions(-)
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
For RCU, Tested-by: Joel Fernandes (Google) joel@joelfernandes.org
thanks,
- Joel
Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 6.1.47-rc1
Yangtao Li frank.li@vivo.com mmc: f-sdh30: fix order of function calls in sdhci_f_sdh30_remove
Jason Xing kernelxing@tencent.com net: fix the RTO timer retransmitting skb every 1ms if linear option is enabled
Karol Herbst kherbst@redhat.com drm/nouveau/disp: fix use-after-free in error handling of nouveau_connector_create
Kuniyuki Iwashima kuniyu@amazon.com af_unix: Fix null-ptr-deref in unix_stream_sendpage().
Guchun Chen guchun.chen@amd.com drm/amdgpu: keep irq count in amdgpu_irq_disable_all
Tim Huang Tim.Huang@amd.com drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU v13.0.4/11
Mark Brown broonie@kernel.org arm64/ptrace: Ensure that SME is set up for target when writing SSVE state
Borislav Petkov (AMD) bp@alien8.de x86/srso: Correct the mitigation status when SMT is disabled
Peter Zijlstra peterz@infradead.org objtool/x86: Fixup frame-pointer vs rethunk
Petr Pavlu petr.pavlu@suse.com x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG
Borislav Petkov (AMD) bp@alien8.de x86/srso: Disable the mitigation on unaffected configurations
Borislav Petkov (AMD) bp@alien8.de x86/CPU/AMD: Fix the DIV(0) initial fix attempt
Sean Christopherson seanjc@google.com x86/retpoline: Don't clobber RFLAGS during srso_safe_ret()
Peter Zijlstra peterz@infradead.org x86/static_call: Fix __static_call_fixup()
Borislav Petkov (AMD) bp@alien8.de x86/srso: Explain the untraining sequences a bit more
Peter Zijlstra peterz@infradead.org x86/cpu: Cleanup the untrain mess
Peter Zijlstra peterz@infradead.org x86/cpu: Rename srso_(.*)_alias to srso_alias_\1
Peter Zijlstra peterz@infradead.org x86/cpu: Rename original retbleed methods
Peter Zijlstra peterz@infradead.org x86/cpu: Clean up SRSO return thunk mess
Peter Zijlstra peterz@infradead.org x86/alternative: Make custom return thunk unconditional
Peter Zijlstra peterz@infradead.org x86/cpu: Fix up srso_safe_ret() and __x86_return_thunk()
Peter Zijlstra peterz@infradead.org x86/cpu: Fix __x86_return_thunk symbol type
Xin Long lucien.xin@gmail.com netfilter: set default timeout to 3 secs for sctp shutdown send and recv state
Mike Kravetz mike.kravetz@oracle.com hugetlb: do not clear hugetlb dtor until allocating vmemmap
Saaem Rizvi SyedSaaem.Rizvi@amd.com drm/amd/display: Implement workaround for writing to OTG_PIXEL_RATE_DIV register
Vincent Guittot vincent.guittot@linaro.org sched/fair: Remove capacity inversion detection
Vincent Guittot vincent.guittot@linaro.org sched/fair: unlink misfit task from cpu overutilized
Sergey Senozhatsky senozhatsky@chromium.org zsmalloc: allow only one active pool compaction context
Daniel Miess daniel.miess@amd.com drm/amd/display: disable RCO for DCN314
Arnd Bergmann arnd@arndb.de ASoC: amd: vangogh: select CONFIG_SND_AMD_ACP_CONFIG
Umio Yasuno coelacanth_dream@protonmail.com drm/amdgpu/pm: fix throttle_status for other than MP1 11.0.7
Tim Huang Tim.Huang@amd.com drm/amdgpu: skip fence GFX interrupts disable/enable for S0ix
Mario Limonciello mario.limonciello@amd.com drm/amd: flush any delayed gfxoff on suspend entry
Jani Nikula jani.nikula@intel.com drm/i915/sdvo: fix panel_type initialization
Wander Lairson Costa wander@redhat.com drm/qxl: fix UAF on handle creation
Yibin Ding yibin.ding@unisoc.com mmc: block: Fix in_flight[issue_type] value error
Yang Yingliang yangyingliang@huawei.com mmc: wbsd: fix double mmc_free_host() in wbsd_init()
Sweet Tea Dorminy sweettea-kernel@dorminy.me blk-crypto: dynamically allocate fallback profile
Yogesh Hegde yogi.kernel@gmail.com arm64: dts: rockchip: Fix Wifi/Bluetooth on ROCK Pi 4 boards
Hawkins Jiawei yin31149@gmail.com virtio-net: Zero max_tx_vq field for VIRTIO_NET_CTRL_MQ_HASH_CONFIG case
Mingzheng Xing xingmingzheng@iscas.ac.cn riscv: Handle zicsr/zifencei issue between gcc and binutils
Russell Harmon via samba-technical samba-technical@lists.samba.org cifs: Release folio lock on fscache read hit.
dengxiang dengxiang@nfschina.com ALSA: usb-audio: Add support for Mythware XA001AU capture and playback interfaces.
Tony Lindgren tony@atomide.com serial: 8250: Fix oops for port->pm on uart_change_pm()
Alexandre Ghiti alexghiti@rivosinc.com riscv: uaccess: Return the number of bytes effectively not copied
Kailang Yang kailang@realtek.com ALSA: hda/realtek - Remodified 3k pull low procedure
Jiasheng Jiang jiasheng@iscas.ac.cn soc: aspeed: socinfo: Add kfree for kstrdup
Zev Weiss zev@bewilderbeest.net soc: aspeed: uart-routing: Use __sysfs_match_string
Stefan Binding sbinding@opensource.cirrus.com ALSA: hda/realtek: Add quirks for HP G11 Laptops
Jerome Brunet jbrunet@baylibre.com ASoC: meson: axg-tdm-formatter: fix channel slot allocation
Zhang Shurong zhang_shurong@foxmail.com ASoC: rt5665: add missed regulator_bulk_disable
Alexander Stein alexander.stein@ew.tq-group.com arm64: dts: imx93: Fix anatop node size
Xiaolei Wang xiaolei.wang@windriver.com ARM: dts: imx: Set default tuning step for imx6sx usdhc
Fabio Estevam festevam@denx.de arm64: dts: imx8mm: Drop CSI1 PHY reference clock configuration
Andrej Picej andrej.picej@norik.com ARM: dts: imx6: phytec: fix RTC interrupt level
Krzysztof Kozlowski krzysztof.kozlowski@linaro.org ARM: dts: imx: align LED node names with dtschema
Christopher Obbard chris.obbard@collabora.com arm64: dts: rockchip: Disable HS400 for eMMC on ROCK 4C+
Christopher Obbard chris.obbard@collabora.com arm64: dts: rockchip: Disable HS400 for eMMC on ROCK Pi 4
Dmitry Baryshkov dmitry.baryshkov@linaro.org arm64: dts: qcom: qrb5165-rb5: fix thermal zone conflict
Tony Lindgren tony@atomide.com bus: ti-sysc: Flush posted write on enable before reset
Marcin Szycik marcin.szycik@linux.intel.com ice: Block switchdev mode when ADQ is active and vice versa
Manish Chopra manishc@marvell.com qede: fix firmware halt over suspend and resume
Eric Dumazet edumazet@google.com net: do not allow gso_size to be set to GSO_BY_FRAGS
Abel Wu wuyun.abel@bytedance.com sock: Fix misuse of sk_under_memory_pressure()
Edward Cree ecree.xilinx@gmail.com sfc: don't unregister flow_indr if it was never registered
Alfred Lee l00g33k@gmail.com net: dsa: mv88e6xxx: Wait for EEPROM done before HW reset
Andrii Staikov andrii.staikov@intel.com i40e: fix misleading debug logs
Piotr Gardocki piotrx.gardocki@intel.com iavf: fix FDIR rule fields masks validation
Jakub Kicinski kuba@kernel.org net: openvswitch: reject negative ifindex
Ziyang Xuan william.xuanziyang@huawei.com team: Fix incorrect deletion of ETH_P_8021AD protocol vid from slaves
Justin Chen justin.chen@broadcom.com net: phy: broadcom: stub c45 read/write for 54810
Pablo Neira Ayuso pablo@netfilter.org netfilter: nft_dynset: disallow object maps
Sishuai Gong sishuai.system@gmail.com ipvs: fix racy memcpy in proc_do_sync_threshold
Florian Westphal fw@strlen.de netfilter: nf_tables: deactivate catchall elements in next generation
Florian Westphal fw@strlen.de netfilter: nf_tables: fix false-positive lockdep splat
Michal Schmidt mschmidt@redhat.com octeon_ep: cancel tx_timeout_task later in remove sequence
Radhey Shyam Pandey radhey.shyam.pandey@amd.com net: macb: In ZynqMP resume always configure PS GTR for non-wakeup source
Luca Ceresoli luca.ceresoli@bootlin.com drm/panel: simple: Fix AUO G121EAN01 panel timings according to the docs
Petr Machata petrm@nvidia.com selftests: mirror_gre_changes: Tighten up the TTL test match
Russell King (Oracle) rmk+kernel@armlinux.org.uk net: phy: fix IRQ-based wake-on-lan over hibernate / power off
Xiang Yang xiangyang3@huawei.com net: pcs: Add missing put_device call in miic_create
Jason Wang jasowang@redhat.com virtio-net: set queues after driver_ok
Laurent Vivier lvivier@redhat.com virtio_net: notify MAC address change on device initialization
Lin Ma linma@zju.edu.cn xfrm: add forgotten nla_policy for XFRMA_MTIMER_THRESH
Lin Ma linma@zju.edu.cn xfrm: add NULL check in xfrm_update_ae_params
Zhengchao Shao shaozhengchao@huawei.com ip_vti: fix potential slab-use-after-free in decode_session6
Zhengchao Shao shaozhengchao@huawei.com ip6_vti: fix slab-use-after-free in decode_session6
Zhengchao Shao shaozhengchao@huawei.com xfrm: fix slab-use-after-free in decode_session6
Lin Ma linma@zju.edu.cn net: xfrm: Amend XFRMA_SEC_CTX nla_policy structure
Lin Ma linma@zju.edu.cn net: af_key: fix sadb_x_filter validation
Lin Ma linma@zju.edu.cn net: xfrm: Fix xfrm_address_filter OOB read
Tam Nguyen tamnguyenchi@os.amperecomputing.com i2c: designware: Handle invalid SMBus block data response length value
Quan Nguyen quan@os.amperecomputing.com i2c: designware: Correct length byte validation logic
xiaoshoukui xiaoshoukui@gmail.com btrfs: fix BUG_ON condition in btrfs_cancel_balance
Josef Bacik josef@toxicpanda.com btrfs: fix incorrect splitting in btrfs_drop_extent_map_range
Sherry Sun sherry.sun@nxp.com tty: serial: fsl_lpuart: Clear the error flags by writing 1 for lpuart32 platforms
Yi Yang yiyang13@huawei.com tty: n_gsm: fix the UAF caused by race condition in gsm_cleanup_mux
Dragos Tatulea dtatulea@nvidia.com vdpa: Enable strict validation for netlinks ops
Lin Ma linma@zju.edu.cn vdpa: Add max vqp attr to vdpa_nl_policy for nlattr length check
Lin Ma linma@zju.edu.cn vdpa: Add queue index attr to vdpa_nl_policy for nlattr length check
Lin Ma linma@zju.edu.cn vdpa: Add features attr to vdpa_nl_policy for nlattr length check
Nathan Lynch nathanl@linux.ibm.com powerpc/rtas_flash: allow user copy to flash block cache objects
Yuanjun Gong ruc_gongyuanjun@163.com fbdev: mmp: fix value check in mmphw_probe()
Parker Newman pnewman@connecttech.com i2c: tegra: Fix i2c-tegra DMA config option processing
Yicong Yang yangyicong@hisilicon.com i2c: hisi: Only handle the interrupt of the driver's transfer
Chengfeng Ye dg573847474@gmail.com i2c: bcm-iproc: Fix bcm_iproc_i2c_isr deadlock issue
Steve French stfrench@microsoft.com cifs: fix potential oops in cifs_oplock_break
Eugenio Pérez eperezma@redhat.com vdpa/mlx5: Delete control vq iotlb in destroy_mr only when necessary
Dragos Tatulea dtatulea@nvidia.com vdpa/mlx5: Fix mr->initialized semantics
Maxime Coquelin maxime.coquelin@redhat.com vduse: Use proper spinlock for IRQ injection
Wolfram Sang wsa+renesas@sang-engineering.com virtio-mmio: don't break lifecycle of vm_dev
Filipe Manana fdmanana@suse.com btrfs: fix use-after-free of new block group that became unused
David Sterba dsterba@suse.com btrfs: convert btrfs_block_group::seq_zone to runtime flag
David Sterba dsterba@suse.com btrfs: convert btrfs_block_group::needs_free_space to runtime flag
Naohiro Aota naota@elisp.net btrfs: move out now unused BG from the reclaim list
Daniel Vetter daniel.vetter@ffwll.ch video/aperture: Only remove sysfb on the default vga pci device
Thomas Zimmermann tzimmermann@suse.de fbdev/hyperv-fb: Do not set struct fb_info.apertures
Xu Yang xu.yang_2@nxp.com ARM: dts: nxp/imx6sll: fix wrong property name in usbphy node
Marc Zyngier maz@kernel.org KVM: arm64: vgic-v4: Make the doorbell request robust w.r.t preemption
Hersen Wu hersenxs.wu@amd.com drm/amd/display: fix access hdcp_workqueue assert
hersen wu hersenxs.wu@amd.com drm/amd/display: phase3 mst hdcp for multiple displays
hersen wu hersenxs.wu@amd.com drm/amd/display: save restore hdcp state when display is unplugged from mst hub
Song Yoong Siang yoong.siang.song@intel.com igc: read before write to SRRCTL register
Chen Lin chen.lin5@zte.com.cn ring-buffer: Do not swap cpu_buffer during resize process
Andy Shevchenko andriy.shevchenko@linux.intel.com Bluetooth: MGMT: Use correct address for memcpy()
Benjamin Gray bgray@linux.ibm.com powerpc/kasan: Disable KCOV in KASAN code
Luke D. Jones luke@ljones.dev ALSA: hda/realtek: Add quirk for ASUS ROG GZ301V
Luke D. Jones luke@ljones.dev ALSA: hda/realtek: Add quirk for ASUS ROG GA402X
Luke D. Jones luke@ljones.dev ALSA: hda/realtek: Add quirk for ASUS ROG GX650P
Tuo Li islituo@gmail.com ALSA: hda: fix a possible null-pointer dereference due to data race in snd_hdac_regmap_sync()
dengxiang dengxiang@nfschina.com ALSA: hda/realtek: Add quirks for Unis H3C Desktop B760 & Q760
Konstantin Komarov almaz.alexandrovich@paragon-software.com fs/ntfs3: Mark ntfs dirty when on-disk struct is corrupted
Jia-Ju Bai baijiaju@buaa.edu.cn fs: ntfs3: Fix possible null-pointer dereferences in mi_read()
Edward Lo loyuantsung@gmail.com fs/ntfs3: Enhance sanity check while generating attr_list
shanzhulig shanzhulig@gmail.com drm/amdgpu: Fix potential fence use-after-free v2
Xiubo Li xiubli@redhat.com ceph: try to dump the msgs when decoding fails
Matthew Anderson ruinairas1992@gmail.com Bluetooth: btusb: Add MT7922 bluetooth ID for the Asus Ally
Zhengping Jiang jiangzp@google.com Bluetooth: L2CAP: Fix use-after-free
Yuechao Zhao yuechao.zhao@advantech.com.cn watchdog: sp5100_tco: support Hygon FCH/SCH (Server Controller Hub)
Zhang Shurong zhang_shurong@foxmail.com firewire: net: fix use after free in fwnet_finish_incoming_packet()
Mika Westerberg mika.westerberg@linux.intel.com thunderbolt: Limit Intel Barlow Ridge USB3 bandwidth
Mika Westerberg mika.westerberg@linux.intel.com thunderbolt: Add Intel Barlow Ridge PCI ID
Armin Wolf W_Armin@gmx.de pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()
Tuo Li islituo@gmail.com gfs2: Fix possible data races in gfs2_show_options()
Xu Yang xu.yang_2@nxp.com usb: chipidea: imx: add missing USB PHY DPDM wakeup setting
Xu Yang xu.yang_2@nxp.com usb: chipidea: imx: don't request QoS for imx8ulp
Mika Westerberg mika.westerberg@linux.intel.com thunderbolt: Read retimer NVM authentication status prior tb_retimer_set_inbound_sbtx()
Hans Verkuil hverkuil-cisco@xs4all.nl media: platform: mediatek: vpu: fix NULL ptr dereference
Avichal Rakesh arakesh@google.com usb: gadget: uvc: queue empty isoc requests if no video buffer is available
Prashanth K quic_prashk@quicinc.com usb: gadget: u_serial: Avoid spinlock recursion in __gs_console_push
Andrey Konovalov andrey.konovalov@linaro.org media: camss: set VFE bpl_alignment to 16 for sdm845 and sm8250
Yunfei Dong yunfei.dong@mediatek.com media: v4l2-mem2mem: add lock to protect parameter num_rdy
Lu Hongfei luhongfei@vivo.com led: qcom-lpg: Fix resource leaks in for_each_available_child_of_node() loops
Uwe Kleine-König u.kleine-koenig@pengutronix.de serial: stm32: Ignore return value of uart_remove_one_port() in .remove()
Winston Wen wentao@uniontech.com cifs: fix session state check in reconnect to avoid use-after-free issue
Paulo Alcantara pc@manguebit.com smb: client: fix warning in cifs_smb3_do_mount()
Matthew Anderson ruinairas1992@gmail.com ALSA: hda/realtek: Add quirks for ROG ALLY CS35l41 audio
Even Xu even.xu@intel.com HID: intel-ish-hid: ipc: Add Arrow Lake PCI device ID
Peter Ujfalusi peter.ujfalusi@linux.intel.com ASoC: SOF: core: Free the firmware trace before calling snd_sof_shutdown()
Daniel Miess daniel.miess@amd.com drm/amd/display: Enable dcn314 DPP RCO
Nicholas Kazlauskas nicholas.kazlauskas@amd.com drm/amd/display: Skip DPP DTO update if root clock is gated
Patrisious Haddad phaddad@nvidia.com RDMA/mlx5: Return the firmware result upon destroying QP/RQ
Alvin Lee alvin.lee2@amd.com drm/amd/display: Apply 60us prefetch for DCFCLK <= 300Mhz
Lang Yu Lang.Yu@amd.com drm/amdgpu: install stub fence into potential unused fence pointers
Suravee Suthikulpanit suravee.suthikulpanit@amd.com iommu/amd: Introduce Disable IRTE Caching Support
stuarthayhurst stuart.a.hayhurst@gmail.com HID: logitech-hidpp: Add USB and Bluetooth IDs for the Logitech G915 TKL Keyboard
Ofir Bitton obitton@habana.ai accel/habanalabs: add pci health check during heartbeat
gaoxu gaoxu2@hihonor.com dma-remap: use kvmalloc_array/kvfree for larger dma memory remap
Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com ASoC: SOF: Intel: fix SoundWire/HDaudio mutual exclusion
Geert Uytterhoeven geert+renesas@glider.be iopoll: Call cpu_relax() in busy loops
Uday M Bhat uday.m.bhat@intel.com ASoC: Intel: sof_sdw: Add support for Rex soundwire
Bard Liao yung-chuan.liao@linux.intel.com ASoC: Intel: sof_sdw_rt_sdca_jack_common: test SOF_JACK_JDSRC in _exit
Oleksij Rempel linux@rempel-privat.de ARM: dts: imx6dl: prtrvt, prtvt7, prti6q, prtwd2: fix USB related warnings
Venkata Prasad Potturu venkataprasad.potturu@amd.com ASoC: amd: vangogh: Add check for acp config flags in vangogh platform
Wolfram Sang wsa+renesas@sang-engineering.com drm: rcar-du: remove R-Car H3 ES1.* workarounds
Raphael Gallais-Pou raphael.gallais-pou@foss.st.com drm/stm: ltdc: fix late dereference check
Venkata Prasad Potturu venkataprasad.potturu@amd.com ASoC: SOF: amd: Add pci revision id check
Sumit Gupta sumitg@nvidia.com PCI: tegra194: Fix possible array out of bounds access
Peter Ujfalusi peter.ujfalusi@linux.intel.com ASoC: Intel: sof_sdw: add quirk for LNL RVP
Bard Liao yung-chuan.liao@linux.intel.com ASoC: Intel: sof_sdw: add quirk for MTL RVP
Jack Xiao Jack.Xiao@amd.com drm/amdgpu: fix memory leak in mes self test
hackyzh002 hackyzh002@gmail.com drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
Longlong Yao Longlong.Yao@amd.com drm/amdgpu: fix calltrace warning in amddrm_buddy_fini
Li Yang leoyang.li@nxp.com net: phy: at803x: fix the wol setting functions
Christophe JAILLET christophe.jaillet@wanadoo.fr net: phy: at803x: Use devm_regulator_get_enable_optional()
Gerd Bayer gbayer@linux.ibm.com net/smc: Fix setsockopt and sysctl to specify same buffer size again
D. Wythe alibuda@linux.alibaba.com net/smc: replace mutex rmbs_lock and sndbufs_lock with rw_semaphore
Ido Schimmel idosch@nvidia.com selftests: forwarding: tc_actions: Use ncat instead of nc
Davide Caratti dcaratti@redhat.com selftests: forwarding: tc_actions: cleanup temporary files when test is aborted
Andrew Yang andrew.yang@mediatek.com zsmalloc: fix races between modifications of fullness and isolated
Nhat Pham nphamcs@gmail.com zsmalloc: consolidate zs_pool's migrate_lock and size_class's locks
Maulik Shah quic_mkshah@quicinc.com cpuidle: psci: Move enabling OSI mode after power domains creation
Ulf Hansson ulf.hansson@linaro.org cpuidle: psci: Extend information in log about OSI/PC mode
Kunihiko Hayashi hayashi.kunihiko@socionext.com mmc: sdhci-f-sdh30: Replace with sdhci_pltfm
Diffstat:
Documentation/admin-guide/hw-vuln/srso.rst | 4 +- Documentation/admin-guide/kernel-parameters.txt | 1 + Makefile | 4 +- arch/arm/boot/dts/imx50-kobo-aura.dts | 2 +- arch/arm/boot/dts/imx53-cx9020.dts | 10 +- arch/arm/boot/dts/imx53-m53evk.dts | 4 +- arch/arm/boot/dts/imx53-m53menlo.dts | 6 +- arch/arm/boot/dts/imx53-tx53.dtsi | 2 +- arch/arm/boot/dts/imx53-usbarmory.dts | 2 +- arch/arm/boot/dts/imx6dl-b1x5pv2.dtsi | 6 +- arch/arm/boot/dts/imx6dl-prtrvt.dts | 4 + arch/arm/boot/dts/imx6dl-riotboard.dts | 4 +- arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 6 +- arch/arm/boot/dts/imx6q-gw5400-a.dts | 6 +- arch/arm/boot/dts/imx6q-h100.dts | 6 +- arch/arm/boot/dts/imx6q-kp.dtsi | 4 +- arch/arm/boot/dts/imx6q-marsboard.dts | 4 +- arch/arm/boot/dts/imx6q-tbs2910.dts | 2 +- arch/arm/boot/dts/imx6qdl-emcon.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw51xx.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw52xx.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw53xx.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw54xx.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw551x.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-gw552x.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw553x.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw560x.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5903.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-gw5904.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5907.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-gw5910.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5912.dtsi | 6 +- arch/arm/boot/dts/imx6qdl-gw5913.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-nit6xlite.dtsi | 10 +- arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-phytec-mira.dtsi | 8 +- arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-prti6q.dtsi | 11 +- arch/arm/boot/dts/imx6qdl-rex.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 2 +- arch/arm/boot/dts/imx6qdl-ts7970.dtsi | 4 +- arch/arm/boot/dts/imx6qdl-tx6.dtsi | 2 +- arch/arm/boot/dts/imx6sl-evk.dts | 2 +- arch/arm/boot/dts/imx6sll-evk.dts | 2 +- arch/arm/boot/dts/imx6sll.dtsi | 2 +- arch/arm/boot/dts/imx6sx-sabreauto.dts | 2 +- arch/arm/boot/dts/imx6sx-udoo-neo.dtsi | 4 +- arch/arm/boot/dts/imx6sx.dtsi | 6 + arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi | 2 +- arch/arm/boot/dts/imx6ul-tx6ul.dtsi | 2 +- arch/arm64/boot/dts/freescale/imx8mm.dtsi | 7 +- arch/arm64/boot/dts/freescale/imx93.dtsi | 2 +- arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 2 +- .../boot/dts/rockchip/rk3399-rock-4c-plus.dts | 3 +- arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi | 6 +- arch/arm64/include/asm/fpsimd.h | 4 +- arch/arm64/include/asm/kvm_host.h | 2 + arch/arm64/kernel/fpsimd.c | 6 +- arch/arm64/kernel/ptrace.c | 9 +- arch/arm64/kernel/signal.c | 2 +- arch/arm64/kvm/arm.c | 6 +- arch/arm64/kvm/vgic/vgic-v3.c | 2 +- arch/arm64/kvm/vgic/vgic-v4.c | 7 +- arch/powerpc/kernel/rtas_flash.c | 6 +- arch/powerpc/mm/kasan/Makefile | 1 + arch/riscv/Kconfig | 28 +-- arch/riscv/kernel/compat_vdso/Makefile | 8 +- arch/riscv/lib/uaccess.S | 11 +- arch/x86/include/asm/entry-common.h | 1 + arch/x86/include/asm/nospec-branch.h | 28 +-- arch/x86/kernel/cpu/amd.c | 1 + arch/x86/kernel/cpu/bugs.c | 28 ++- arch/x86/kernel/static_call.c | 13 ++ arch/x86/kernel/traps.c | 2 - arch/x86/kernel/vmlinux.lds.S | 20 +- arch/x86/kvm/svm/svm.c | 2 + arch/x86/lib/retpoline.S | 141 +++++++++----- block/blk-crypto-fallback.c | 36 ++-- drivers/bluetooth/btusb.c | 3 + drivers/bus/ti-sysc.c | 2 + drivers/cpuidle/cpuidle-psci-domain.c | 42 ++-- drivers/firewire/net.c | 6 +- drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 8 +- drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 41 +++- drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c | 9 +- drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c | 1 - drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 4 +- drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 6 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 211 +++++++++++++++++---- .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_hdcp.h | 14 ++ .../amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 30 +++ drivers/gpu/drm/amd/display/dc/dcn20/dcn20_dccg.h | 3 +- drivers/gpu/drm/amd/display/dc/dcn31/dcn31_dccg.c | 8 + .../gpu/drm/amd/display/dc/dcn314/dcn314_dccg.c | 5 + .../drm/amd/display/dc/dcn314/dcn314_resource.c | 20 ++ drivers/gpu/drm/amd/display/dc/dcn32/dcn32_dccg.c | 22 +++ drivers/gpu/drm/amd/display/dc/dcn32/dcn32_dccg.h | 3 +- drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c | 2 +- .../gpu/drm/amd/display/dc/dcn32/dcn32_resource.h | 3 +- .../amd/display/dc/dml/dcn32/display_mode_vba_32.c | 4 +- .../amd/display/dc/dml/dcn32/display_mode_vba_32.h | 2 +- drivers/gpu/drm/amd/display/dc/inc/hw/dccg.h | 1 + drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c | 4 +- .../drm/amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 14 +- drivers/gpu/drm/i915/display/intel_sdvo.c | 2 +- drivers/gpu/drm/nouveau/nouveau_connector.c | 8 +- drivers/gpu/drm/panel/panel-simple.c | 24 +-- drivers/gpu/drm/qxl/qxl_drv.h | 2 +- drivers/gpu/drm/qxl/qxl_dumb.c | 5 +- drivers/gpu/drm/qxl/qxl_gem.c | 25 ++- drivers/gpu/drm/qxl/qxl_ioctl.c | 6 +- drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 37 +--- drivers/gpu/drm/rcar-du/rcar_du_drv.c | 48 ----- drivers/gpu/drm/rcar-du/rcar_du_drv.h | 2 - drivers/gpu/drm/rcar-du/rcar_du_regs.h | 3 +- drivers/gpu/drm/stm/ltdc.c | 4 +- drivers/hid/hid-logitech-hidpp.c | 4 + drivers/hid/intel-ish-hid/ipc/hw-ish.h | 1 + drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 + drivers/i2c/busses/i2c-bcm-iproc.c | 11 +- drivers/i2c/busses/i2c-designware-master.c | 16 +- drivers/i2c/busses/i2c-hisi.c | 8 + drivers/i2c/busses/i2c-tegra.c | 2 +- drivers/infiniband/hw/mlx5/qpc.c | 10 +- drivers/iommu/amd/amd_iommu_types.h | 4 + drivers/iommu/amd/init.c | 36 ++++ drivers/leds/rgb/leds-qcom-lpg.c | 8 +- drivers/media/platform/mediatek/vpu/mtk_vpu.c | 6 +- drivers/media/platform/qcom/camss/camss-vfe.c | 6 +- drivers/misc/habanalabs/common/device.c | 15 +- drivers/misc/habanalabs/common/habanalabs.h | 2 + drivers/misc/habanalabs/common/habanalabs_drv.c | 2 - drivers/mmc/core/block.c | 7 +- drivers/mmc/host/sdhci_f_sdh30.c | 66 +++---- drivers/mmc/host/wbsd.c | 2 - drivers/net/dsa/mv88e6xxx/chip.c | 8 + drivers/net/ethernet/cadence/macb_main.c | 9 +- drivers/net/ethernet/intel/i40e/i40e_nvm.c | 16 +- drivers/net/ethernet/intel/iavf/iavf_ethtool.c | 10 + drivers/net/ethernet/intel/iavf/iavf_fdir.c | 77 +++++++- drivers/net/ethernet/intel/iavf/iavf_fdir.h | 2 + drivers/net/ethernet/intel/ice/ice_eswitch.c | 6 + drivers/net/ethernet/intel/ice/ice_main.c | 5 + drivers/net/ethernet/intel/igc/igc_base.h | 11 +- drivers/net/ethernet/intel/igc/igc_main.c | 7 +- .../net/ethernet/marvell/octeon_ep/octep_main.c | 2 +- drivers/net/ethernet/qlogic/qede/qede_main.c | 10 + drivers/net/ethernet/sfc/tc.c | 2 +- drivers/net/pcs/pcs-rzn1-miic.c | 10 +- drivers/net/phy/at803x.c | 89 ++++----- drivers/net/phy/broadcom.c | 13 ++ drivers/net/phy/phy_device.c | 13 +- drivers/net/team/team.c | 4 +- drivers/net/virtio_net.c | 26 ++- drivers/pci/controller/dwc/pcie-tegra194.c | 13 +- drivers/pcmcia/rsrc_nonstatic.c | 2 + drivers/soc/aspeed/aspeed-socinfo.c | 1 + drivers/soc/aspeed/aspeed-uart-routing.c | 2 +- drivers/thunderbolt/nhi.c | 2 + drivers/thunderbolt/nhi.h | 4 + drivers/thunderbolt/quirks.c | 8 + drivers/thunderbolt/retimer.c | 29 ++- drivers/tty/n_gsm.c | 3 +- drivers/tty/serial/8250/8250_port.c | 1 + drivers/tty/serial/fsl_lpuart.c | 4 +- drivers/tty/serial/stm32-usart.c | 5 +- drivers/usb/chipidea/ci_hdrc_imx.c | 5 + drivers/usb/chipidea/usbmisc_imx.c | 2 +- drivers/usb/gadget/function/u_serial.c | 3 + drivers/usb/gadget/function/uvc_video.c | 32 +++- drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 + drivers/vdpa/mlx5/core/mr.c | 105 +++++++--- drivers/vdpa/mlx5/net/mlx5_vnet.c | 4 +- drivers/vdpa/vdpa.c | 9 +- drivers/vdpa/vdpa_user/vduse_dev.c | 8 +- drivers/video/aperture.c | 7 +- drivers/video/fbdev/hyperv_fb.c | 17 +- drivers/video/fbdev/mmp/hw/mmp_ctrl.c | 4 +- drivers/virtio/virtio_mmio.c | 5 +- drivers/watchdog/sp5100_tco.c | 4 +- fs/btrfs/block-group.c | 14 +- fs/btrfs/block-group.h | 18 +- fs/btrfs/extent_map.c | 6 +- fs/btrfs/free-space-tree.c | 10 +- fs/btrfs/tests/free-space-tree-tests.c | 2 +- fs/btrfs/volumes.c | 3 +- fs/btrfs/zoned.c | 7 +- fs/ceph/mds_client.c | 4 + fs/gfs2/super.c | 26 +-- fs/ntfs3/frecord.c | 16 +- fs/ntfs3/fsntfs.c | 2 +- fs/ntfs3/index.c | 6 + fs/ntfs3/ntfs_fs.h | 2 + fs/ntfs3/record.c | 10 +- fs/smb/client/cifsfs.c | 28 +-- fs/smb/client/file.c | 25 ++- fs/smb/client/smb2pdu.c | 6 + include/kvm/arm_vgic.h | 2 +- include/linux/iopoll.h | 2 + include/linux/virtio_net.h | 4 + include/media/v4l2-mem2mem.h | 18 +- include/net/sock.h | 6 + kernel/dma/remap.c | 4 +- kernel/sched/fair.c | 193 +++++++++---------- kernel/sched/sched.h | 19 -- kernel/trace/ring_buffer.c | 14 +- kernel/trace/trace.c | 3 +- mm/hugetlb.c | 75 +++++--- mm/zsmalloc.c | 113 +++++------ net/bluetooth/l2cap_core.c | 5 + net/bluetooth/mgmt.c | 2 +- net/core/sock.c | 2 +- net/ipv4/ip_vti.c | 4 +- net/ipv4/tcp_timer.c | 4 +- net/ipv6/ip6_vti.c | 4 +- net/key/af_key.c | 4 +- net/netfilter/ipvs/ip_vs_ctl.c | 4 + net/netfilter/nf_conntrack_proto_sctp.c | 6 +- net/netfilter/nf_tables_api.c | 1 + net/netfilter/nft_dynset.c | 3 + net/netfilter/nft_set_pipapo.c | 13 +- net/openvswitch/datapath.c | 8 +- net/smc/af_smc.c | 4 +- net/smc/smc.h | 2 +- net/smc/smc_clc.c | 4 +- net/smc/smc_core.c | 80 ++++---- net/smc/smc_core.h | 4 +- net/smc/smc_llc.c | 16 +- net/smc/smc_sysctl.c | 10 +- net/unix/af_unix.c | 9 +- net/xfrm/xfrm_compat.c | 2 +- net/xfrm/xfrm_interface_core.c | 4 +- net/xfrm/xfrm_user.c | 14 +- sound/hda/hdac_regmap.c | 7 +- sound/pci/hda/patch_realtek.c | 91 ++++++++- sound/soc/amd/Kconfig | 1 + sound/soc/amd/vangogh/acp5x.h | 2 + sound/soc/amd/vangogh/pci-acp5x.c | 7 +- sound/soc/codecs/rt5665.c | 2 + sound/soc/intel/boards/sof_sdw.c | 25 +++ sound/soc/intel/boards/sof_sdw_rt711_sdca.c | 3 + sound/soc/meson/axg-tdm-formatter.c | 42 ++-- sound/soc/sof/amd/acp.h | 3 + sound/soc/sof/amd/pci-rmb.c | 3 + sound/soc/sof/amd/pci-rn.c | 3 + sound/soc/sof/core.c | 4 +- sound/soc/sof/intel/hda.c | 12 +- sound/usb/quirks-table.h | 29 +++ tools/objtool/arch/x86/decode.c | 2 +- tools/objtool/check.c | 21 +- .../selftests/net/forwarding/mirror_gre_changes.sh | 3 +- .../testing/selftests/net/forwarding/tc_actions.sh | 18 +- 255 files changed, 2074 insertions(+), 1100 deletions(-)
On Mon, Aug 21, 2023 at 10:58:53PM +0000, Joel Fernandes wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
For RCU, Tested-by: Joel Fernandes (Google) joel@joelfernandes.org
I am getting the following warning which started after my last successful 6.1.47-rc1 run. Looks like others already reported it, but I am just archiving my finding here:
Thanks.
[ 2.169887] ------------[ cut here ]------------ [ 2.170593] missing return thunk: __alt_instructions_end+0x2256/0x227c-srso_untrain_ret+0x0/0x2: e9 c7 a0 ed fe [ 2.171678] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:572 apply_returns+0x1fb/0x230 [ 2.173592] Modules linked in: [ 2.174625] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.47-rc1-g9beeea9636e6 #299 [ 2.175608] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 [ 2.176593] RIP: 0010:apply_returns+0x1fb/0x230 [ 2.177592] Code: a5 01 00 0f 85 ef fe ff ff 49 89 d8 b9 05 00 00 00 4c 89 f2 48 89 de 48 c7 c7 60 3e 9d ad c6 05 fa 2c a5 01 01 e8 45 2d 04 00 <0f> 0b e9 c7 fe ff ff c7 84 24 89 00 00 00 cc cc cc cc 42 c7 84 04 [ 2.179589] RSP: 0000:ffffffffadc03e28 EFLAGS: 00010286 [ 2.180592] RAX: 0000000000000000 RBX: ffffffffae5292f2 RCX: 0000000000000000 [ 2.181591] RDX: 0000000000000003 RSI: 0000000000000001 RDI: 00000000ffffffff [ 2.182595] RBP: 0000000000000000 R08: 00000000ffffdfff R09: 00000000ffffdfff [ 2.184589] R10: ffffffffadc574a0 R11: ffffffffadc574a0 R12: ffffffffadc03e40 [ 2.185591] R13: ffffffffae520414 R14: ffffffffad4033be R15: ffffffffae5203f0 [ 2.186650] FS: 0000000000000000(0000) GS:ffff953a5ca00000(0000) knlGS:0000000000000000 [ 2.187637] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 2.188592] CR2: ffff953a5fa01000 CR3: 000000001ee0c000 CR4: 00000000000006f0 [ 2.189639] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 2.191589] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 2.192593] Call Trace: [ 2.194683] <TASK> [ 2.195595] ? __warn+0x78/0xc0 [ 2.197592] ? apply_returns+0x1fb/0x230 [ 2.198593] ? report_bug+0xe6/0x170 [ 2.199592] ? console_unlock+0x1a3/0x210 [ 2.200594] ? handle_bug+0x3c/0x70 [ 2.201594] ? exc_invalid_op+0x13/0x60 [ 2.202594] ? asm_exc_invalid_op+0x16/0x20 [ 2.203595] ? retbleed_return_thunk+0x7e/0x7e [ 2.205593] ? apply_returns+0x1fb/0x230 [ 2.206594] ? apply_returns+0x1fb/0x230 [ 2.207596] alternative_instructions+0x43/0xf2 [ 2.208672] arch_cpu_finalize_init+0x28/0x47 [ 2.210595] start_kernel+0x5f9/0x6a5 [ 2.211597] secondary_startup_64_no_verify+0xe0/0xeb [ 2.213649] </TASK>>
Hi Greg
On Tue, Aug 22, 2023 at 4:51 AM Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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.47-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 takeshi.ogasawara@futuring-girl.com
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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 bagasdotme@gmail.com
On Tue, 22 Aug 2023 at 01:21, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
NOTE: Kernel warnings noticed on x86_64 while booting the kernel. Paul E. McKenney reported this last week [1] and discussions email thread provided here.
[1] https://lore.kernel.org/lkml/4dc3d0ec-b827-4bce-8927-cfa5d837fd03@paulmck-la...
------------[ cut here ]------------ [ 1.395392] missing return thunk: __ret+0x5/0x7e-__ret+0x0/0x7e: e9 f6 ff ff ff [ 1.395399] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/alternative.c:574 apply_returns+0x1c0/0x3d0 [ 1.397391] Modules linked in: [ 1.398392] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.47-rc1 #1 [ 1.399391] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS 2.5 11/26/2020 [ 1.400392] RIP: 0010:apply_returns+0x1c0/0x3d0
## Build * kernel: 6.1.47-rc1 * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc * git branch: linux-6.1.y * git commit: 5165f4e9738c48a220a13b073c6ccc24824aeb74 * git describe: v6.1.46-195-g5165f4e9738c * test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.46...
## Test Regressions (compared to v6.1.46)
## Metric Regressions (compared to v6.1.46)
## Test Fixes (compared to v6.1.46)
## Metric Fixes (compared to v6.1.46)
## Test result summary total: 150677, pass: 127511, fail: 4079, skip: 18915, xfail: 172
## Build Summary * arc: 5 total, 5 passed, 0 failed * arm: 147 total, 145 passed, 2 failed * arm64: 49 total, 46 passed, 3 failed * i386: 39 total, 37 passed, 2 failed * mips: 30 total, 28 passed, 2 failed * parisc: 3 total, 3 passed, 0 failed * powerpc: 36 total, 34 passed, 2 failed * riscv: 16 total, 13 passed, 3 failed * s390: 16 total, 14 passed, 2 failed * sh: 14 total, 12 passed, 2 failed * sparc: 8 total, 8 passed, 0 failed * x86_64: 46 total, 44 passed, 2 failed
## Test suites summary * boot * kselftest-android * kselftest-arm64 * kselftest-breakpoints * kselftest-capabilities * kselftest-cgroup * kselftest-clone3 * kselftest-core * kselftest-cpu-hotplug * kselftest-cpufreq * kselftest-drivers-dma-buf * kselftest-efivarfs * kselftest-exec * kselftest-filesystems * kselftest-filesystems-binderfs * kselftest-filesystems-epoll * kselftest-firmware * kselftest-fpu * kselftest-ftrace * kselftest-futex * kselftest-gpio * kselftest-intel_pstate * kselftest-ipc * kselftest-ir * kselftest-kcmp * kselftest-kexec * kselftest-kvm * kselftest-lib * 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-tmpfs * kselftest-tpm2 * kselftest-user_events * kselftest-vDSO * kselftest-watchdog * kselftest-x86 * kunit * kvm-unit-tests * libgpiod * log-parser-boot * log-parser-test * ltp-cap_bounds * ltp-commands * ltp-containers * ltp-controllers * ltp-cpuhotplug * ltp-crypto * ltp-cve * ltp-dio * ltp-fcntl-locktests * ltp-filecaps * ltp-fs * ltp-fs_bind * ltp-fs_perms_simple * ltp-fsx * ltp-hugetlb * ltp-io * ltp-ipc * ltp-math * ltp-mm * ltp-nptl * ltp-pty * ltp-sched * ltp-securebits * ltp-smoke * ltp-syscalls * ltp-tracing * network-basic-tests * perf * rcutorture * v4l2-compliance
-- Linaro LKFT https://lkft.linaro.org
Hi,
[Adding Peter Zijlstra to CC]
On Tue, Aug 22, 2023 at 04:25:22PM +0530, Naresh Kamboju wrote:
On Tue, 22 Aug 2023 at 01:21, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
NOTE: Kernel warnings noticed on x86_64 while booting the kernel. Paul E. McKenney reported this last week [1] and discussions email thread provided here.
[1] https://lore.kernel.org/lkml/4dc3d0ec-b827-4bce-8927-cfa5d837fd03@paulmck-la...
Seeing the same warning for the 6.1.47-rc1, which is missing 4ae68b26c3ab ("objtool/x86: Fix SRSO mess"). Unfortunately the commit will not apply cleanly to 6.1.y.
I guess we need at least as well dbcdbdfdf137 ("objtool: Rework instruction -> symbol mapping"), but not sure this is enough.
Peter, is this correct?
Regards, Salvatore
On Tue, Aug 22, 2023 at 05:27:02PM +0200, Salvatore Bonaccorso wrote:
Hi,
[Adding Peter Zijlstra to CC]
On Tue, Aug 22, 2023 at 04:25:22PM +0530, Naresh Kamboju wrote:
On Tue, 22 Aug 2023 at 01:21, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
NOTE: Kernel warnings noticed on x86_64 while booting the kernel. Paul E. McKenney reported this last week [1] and discussions email thread provided here.
[1] https://lore.kernel.org/lkml/4dc3d0ec-b827-4bce-8927-cfa5d837fd03@paulmck-la...
Seeing the same warning for the 6.1.47-rc1, which is missing 4ae68b26c3ab ("objtool/x86: Fix SRSO mess"). Unfortunately the commit will not apply cleanly to 6.1.y.
I tried, and failed, let me try again...
I guess we need at least as well dbcdbdfdf137 ("objtool: Rework instruction -> symbol mapping"), but not sure this is enough.
That gets messy fast, I tried to backport all of the 6.4 objtool changes to 6.1, but ugh, the changes were highly intertwined with many other things.
greg k-h
On Tue, Aug 22, 2023 at 05:51:27PM +0200, Greg Kroah-Hartman wrote:
On Tue, Aug 22, 2023 at 05:27:02PM +0200, Salvatore Bonaccorso wrote:
Hi,
[Adding Peter Zijlstra to CC]
On Tue, Aug 22, 2023 at 04:25:22PM +0530, Naresh Kamboju wrote:
On Tue, 22 Aug 2023 at 01:21, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
Results from Linaro’s test farm. No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing lkft@linaro.org
NOTE: Kernel warnings noticed on x86_64 while booting the kernel. Paul E. McKenney reported this last week [1] and discussions email thread provided here.
[1] https://lore.kernel.org/lkml/4dc3d0ec-b827-4bce-8927-cfa5d837fd03@paulmck-la...
Seeing the same warning for the 6.1.47-rc1, which is missing 4ae68b26c3ab ("objtool/x86: Fix SRSO mess"). Unfortunately the commit will not apply cleanly to 6.1.y.
I tried, and failed, let me try again...
I guess we need at least as well dbcdbdfdf137 ("objtool: Rework instruction -> symbol mapping"), but not sure this is enough.
That gets messy fast, I tried to backport all of the 6.4 objtool changes to 6.1, but ugh, the changes were highly intertwined with many other things.
Hm, I applied that, but now I get build errors:
vmlinux.o: warning: objtool: retbleed_return_thunk(): can't find starting instruction
and
incomplete ORC unwind tables in file: vmlinux Failed to sort kernel tables
Attached below is my backport, what did I get wrong?
thanks,
greg k-h
Hello,
On Mon, 21 Aug 2023 21:39:39 +0200 Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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.
# TODO: Cc damon@lists.linux.dev
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 sj@kernel.org
[1] https://github.com/awslabs/damon-tests/tree/next/corr [2] 5165f4e9738c ("Linux 6.1.47-rc1")
Thanks, SJ
[...]
---
# .config:1408:warning: override: reassigning to symbol CGROUPS ok 15 selftests: damon-tests: build_nomemcg.sh # kselftest dir '/home/sjpark/damon-tests-cont/linux/tools/testing/selftests/damon-tests' is in dirty state. # the log is at '/home/sjpark/log'. [32m 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_m68k.sh ok 12 selftests: damon-tests: build_arm64.sh ok 13 selftests: damon-tests: build_i386_idle_flag.sh ok 14 selftests: damon-tests: build_i386_highpte.sh ok 15 selftests: damon-tests: build_nomemcg.sh [33m [92mPASS [39m _remote_run_corr.sh SUCCESS
On 8/21/23 13:39, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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 skhan@linuxfoundation.org
thanks, -- Shuah
On 8/21/23 12:39, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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 florian.fainelli@broadcom.com
On 8/21/23 12:39 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +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.47-rc1.... 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
Built and booted successfully on RISC-V RV64 (HiFive Unmatched).
Tested-by: Ron Economos re@w6rz.net
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
For x86 I get the same runtime warning as everyone else.
Guenter
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
thanks,
greg k-h
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I see this from lore " This is from overnight testing that hit this only in the KCSAN runs. The KASAN and non-debug runs had no trouble.
Thanx, Paul
"
steps to reproduce: ------------------- tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-13 --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5...
Here is the links to details and build details, [1] https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.46...
[2] https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5...
[3] https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5...
- Naresh
thanks,
greg k-h
On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I see this from lore " This is from overnight testing that hit this only in the KCSAN runs. The KASAN and non-debug runs had no trouble.
Thanx, Paul
"
Ok, that's good, it's not going to hit "normal" users... :)
steps to reproduce:
tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-13 --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5...
Here is the links to details and build details, [1] https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-6.1.y/build/v6.1.46...
[2] https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5...
[3] https://storage.tuxsuite.com/public/linaro/lkft/builds/2UJAv99Wwi6YMltFjlQD5...
You are going to force me to use tuxmake again, aren't you...
I'll dig into this after lunch.
greg k-h
On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I have KFENCE enabled as well, so it may well be that this triggers the warning. I don't see it in 6.4.y or upstream, though.
Guenter
On Wed, Aug 23, 2023 at 06:30:13AM -0700, Guenter Roeck wrote:
On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I have KFENCE enabled as well, so it may well be that this triggers the warning. I don't see it in 6.4.y or upstream, though.
Ok, let me rip out all the x86 and objtool patches from this release, get it out the door with the good things in there that everyone else needs, and then we can focus on this mess...
Maybe I'll just backport _all_ objtool changes to sync things up better, last time I tried that it was a maze of twisty passages, all coated in assembly...
thanks,
greg k-h
On Wed, Aug 23, 2023 at 05:50:42PM +0200, Greg Kroah-Hartman wrote:
On Wed, Aug 23, 2023 at 06:30:13AM -0700, Guenter Roeck wrote:
On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I have KFENCE enabled as well, so it may well be that this triggers the warning. I don't see it in 6.4.y or upstream, though.
Ok, let me rip out all the x86 and objtool patches from this release, get it out the door with the good things in there that everyone else needs, and then we can focus on this mess...
Maybe I'll just backport _all_ objtool changes to sync things up better, last time I tried that it was a maze of twisty passages, all coated in assembly...
I got lost in the maze again today, ick.
Anyway, I give up. I'm just going to push out a -rc1 with just these changes in it today, and if people are upset about the runtime warning, then they can provide a working backport of this objtool patch.
Ideally, the CPU vendor who is causing this mess will do that, as it's their issue we are spending all of this time on, not Linux's issue.
Also, oddly, I can not reproduce this problem here on my hardware at all. Maybe because it's an AMD processor? If so, makes sense, as the SRSO issue is only for Intel chips.
thanks,
greg k-h
On Thu, Aug 24, 2023 at 03:35:55PM +0200, Greg Kroah-Hartman wrote:
On Wed, Aug 23, 2023 at 05:50:42PM +0200, Greg Kroah-Hartman wrote:
On Wed, Aug 23, 2023 at 06:30:13AM -0700, Guenter Roeck wrote:
On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 6.1.47 release. > There are 194 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, 23 Aug 2023 19:40:45 +0000. > Anything received after that time might be too late. >
Build results: total: 157 pass: 156 fail: 1 Failed builds: m68k:sun3_defconfig Qemu test results: total: 521 pass: 519 fail: 2 Failed tests: arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs
The m68k build failure is
Inconsistent kallsyms data Try make KALLSYMS_EXTRA_PASS=1 as a workaround
I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. Nothing to worry about. The f2fs crashes are still seen. They also happen for other architectures, so it is not just an arm problem. I'll probably just disable all f2fs testing going forward. If so I'll send a note clarifying that the lack of reported test failures doesn't mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I have KFENCE enabled as well, so it may well be that this triggers the warning. I don't see it in 6.4.y or upstream, though.
Ok, let me rip out all the x86 and objtool patches from this release, get it out the door with the good things in there that everyone else needs, and then we can focus on this mess...
Maybe I'll just backport _all_ objtool changes to sync things up better, last time I tried that it was a maze of twisty passages, all coated in assembly...
I got lost in the maze again today, ick.
Anyway, I give up. I'm just going to push out a -rc1 with just these changes in it today, and if people are upset about the runtime warning, then they can provide a working backport of this objtool patch.
Or maybe just revert all srso patches.
Ideally, the CPU vendor who is causing this mess will do that, as it's their issue we are spending all of this time on, not Linux's issue.
Also, oddly, I can not reproduce this problem here on my hardware at all. Maybe because it's an AMD processor? If so, makes sense, as the SRSO issue is only for Intel chips.
Apparently I am lost in the maze as well. I am quite sure that SRSO only applies to AMD CPUs, and
arch/x86/Kconfig:config CPU_SRSO arch/x86/Kconfig: Enable the SRSO mitigation needed on AMD Zen1-4 machines.
seems to confirm that. What am I missing ? Do you mean the warning that was supposed to be fixed with the objtool patch(es) is only seen on Intel chips ?
Thanks, Guenter
On Thu, Aug 24, 2023 at 08:08:19AM -0700, Guenter Roeck wrote:
On Thu, Aug 24, 2023 at 03:35:55PM +0200, Greg Kroah-Hartman wrote:
On Wed, Aug 23, 2023 at 05:50:42PM +0200, Greg Kroah-Hartman wrote:
On Wed, Aug 23, 2023 at 06:30:13AM -0700, Guenter Roeck wrote:
On Wed, Aug 23, 2023 at 01:47:39PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 12:33, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Tue, Aug 22, 2023 at 05:49:54PM -0700, Guenter Roeck wrote: > On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 6.1.47 release. > > There are 194 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, 23 Aug 2023 19:40:45 +0000. > > Anything received after that time might be too late. > > > > Build results: > total: 157 pass: 156 fail: 1 > Failed builds: > m68k:sun3_defconfig > Qemu test results: > total: 521 pass: 519 fail: 2 > Failed tests: > arm:fuji-bmc:aspeed_g5_defconfig:notests:mem1G:mtd128,0,8,1:net,nic:aspeed-bmc-facebook-fuji:f2fs > arm:bletchley-bmc,fmc-model=mt25qu02g,spi-model=mt25qu02g:aspeed_g5_defconfig:notests:mem1G:mtd256:net,nic:aspeed-bmc-facebook-bletchley:f2fs > > The m68k build failure is > > Inconsistent kallsyms data > Try make KALLSYMS_EXTRA_PASS=1 as a workaround > > I already have KALLSYMS_EXTRA_PASS=1 enabled, so that doesn't help. > Nothing to worry about. The f2fs crashes are still seen. They > also happen for other architectures, so it is not just an arm problem. > I'll probably just disable all f2fs testing going forward. If so I'll > send a note clarifying that the lack of reported test failures doesn't > mean that it works.
I'll look into this later this week, next week to resolve the f2fs stuff. I wanted to get to the other known bug fixes first.
> For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
It is seen with gcc-13 and clang-17 with few extra configs. We are not booting defconfig.
The Kconfigs are enabled with KFENCE.
I have KFENCE enabled as well, so it may well be that this triggers the warning. I don't see it in 6.4.y or upstream, though.
Ok, let me rip out all the x86 and objtool patches from this release, get it out the door with the good things in there that everyone else needs, and then we can focus on this mess...
Maybe I'll just backport _all_ objtool changes to sync things up better, last time I tried that it was a maze of twisty passages, all coated in assembly...
I got lost in the maze again today, ick.
Anyway, I give up. I'm just going to push out a -rc1 with just these changes in it today, and if people are upset about the runtime warning, then they can provide a working backport of this objtool patch.
Or maybe just revert all srso patches.
Hah, I wish.
{sigh}
I've notified the patch authors about this, hopefully they can come up with something.
Ideally, the CPU vendor who is causing this mess will do that, as it's their issue we are spending all of this time on, not Linux's issue.
Also, oddly, I can not reproduce this problem here on my hardware at all. Maybe because it's an AMD processor? If so, makes sense, as the SRSO issue is only for Intel chips.
Apparently I am lost in the maze as well. I am quite sure that SRSO only applies to AMD CPUs, and
arch/x86/Kconfig:config CPU_SRSO arch/x86/Kconfig: Enable the SRSO mitigation needed on AMD Zen1-4 machines.
seems to confirm that. What am I missing ? Do you mean the warning that was supposed to be fixed with the objtool patch(es) is only seen on Intel chips ?
Ah, sorry, my confusion (too many different cpu bugs lately)
This might be an issue on AMD chips, but for some reason, in running this kernel on my systems here, I have no boot warnings at all. I blamed it on them being only AMD chips. If that's not the issue then I really have no idea, sorry.
thanks,
greg k-h
On Thu, Aug 24, 2023 at 05:15:30PM +0200, Greg Kroah-Hartman wrote: [ ... ]
This might be an issue on AMD chips, but for some reason, in running this kernel on my systems here, I have no boot warnings at all. I blamed it on them being only AMD chips. If that's not the issue then I really have no idea, sorry.
AFAIK it depends on the compiler used and on the enabled debug options. At some point I lost track about what exactly has to be enabled to see the problem. We see it a lot with our (ChromeOS) debug kernel testing which has various debug options enabled, to the point where we may temporarily remove the warning from the kernel to stop the noise.
Alternatively, as I had suggested earlier, we could revert all srso patches because they only seem to cause trouble. So far I have been resisting that because I am concerned that it would make things even worse (like one can not really revert a heart surgery without doing even more damage).
Guenter
On Thu, Aug 24, 2023 at 08:58:46AM -0700, Guenter Roeck wrote:
On Thu, Aug 24, 2023 at 05:15:30PM +0200, Greg Kroah-Hartman wrote: [ ... ]
This might be an issue on AMD chips, but for some reason, in running this kernel on my systems here, I have no boot warnings at all. I blamed it on them being only AMD chips. If that's not the issue then I really have no idea, sorry.
AFAIK it depends on the compiler used and on the enabled debug options. At some point I lost track about what exactly has to be enabled to see the problem. We see it a lot with our (ChromeOS) debug kernel testing which has various debug options enabled, to the point where we may temporarily remove the warning from the kernel to stop the noise.
Alternatively, as I had suggested earlier, we could revert all srso patches because they only seem to cause trouble. So far I have been resisting that because I am concerned that it would make things even worse (like one can not really revert a heart surgery without doing even more damage).
If you don't want the feature, you can disable it at build time (I think), and I know you can disable it at runtime. But there are groups out that that "need" this, to solve a known security hole in some cpus, so it is required for them. To remove the code entirely would not be good for them, so I will say, if they are the ones that need this, they should help fix this warning, no one else should be seeing it :)
thanks,
greg k-h
On Wed, Aug 23, 2023 at 09:03:49AM +0200, Greg Kroah-Hartman wrote:
For x86 I get the same runtime warning as everyone else.
Yeah, this is troubling...
Is it clang only? I'll dig into this today...
No, I build with gcc. More specifically, gcc 11.4.0 and binutils 2.40.
Guenter
Hi Greg,
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build test (gcc version 12.3.1 20230625): 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. Warning on boot, already reported by others. x86_64: Booted on qemu. Warning on boot, already reported by others. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/4765 [2]. https://openqa.qa.codethink.co.uk/tests/4773 [3]. https://openqa.qa.codethink.co.uk/tests/4772
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
On Wed, Aug 23, 2023 at 09:54:45AM +0100, Sudip Mukherjee (Codethink) wrote:
Hi Greg,
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build test (gcc version 12.3.1 20230625): 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. Warning on boot, already reported by others. x86_64: Booted on qemu. Warning on boot, already reported by others. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/4765 [2]. https://openqa.qa.codethink.co.uk/tests/4773 [3]. https://openqa.qa.codethink.co.uk/tests/4772
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
-- Regards Sudip
One question about the warning on boot, all still works afterward, right? Or does the system not work?
thanks,
greg k-h
On Wed, 23 Aug 2023 at 14:56, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Aug 23, 2023 at 09:54:45AM +0100, Sudip Mukherjee (Codethink) wrote:
Hi Greg,
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build test (gcc version 12.3.1 20230625): 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. Warning on boot, already reported by others. x86_64: Booted on qemu. Warning on boot, already reported by others. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/4765 [2]. https://openqa.qa.codethink.co.uk/tests/4773 [3]. https://openqa.qa.codethink.co.uk/tests/4772
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
-- Regards Sudip
One question about the warning on boot, all still works afterward, right? Or does the system not work?
The warning while booting and root login successful and LTP and other test runs are successful.
- Naresh
On Wed, Aug 23, 2023 at 04:02:14PM +0530, Naresh Kamboju wrote:
On Wed, 23 Aug 2023 at 14:56, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Aug 23, 2023 at 09:54:45AM +0100, Sudip Mukherjee (Codethink) wrote:
Hi Greg,
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build test (gcc version 12.3.1 20230625): 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. Warning on boot, already reported by others. x86_64: Booted on qemu. Warning on boot, already reported by others. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/4765 [2]. https://openqa.qa.codethink.co.uk/tests/4773 [3]. https://openqa.qa.codethink.co.uk/tests/4772
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
-- Regards Sudip
One question about the warning on boot, all still works afterward, right? Or does the system not work?
The warning while booting and root login successful and LTP and other test runs are successful.
Same here.
Guenter
On Wed, 23 Aug 2023 at 10:26, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Aug 23, 2023 at 09:54:45AM +0100, Sudip Mukherjee (Codethink) wrote:
Hi Greg,
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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, 23 Aug 2023 19:40:45 +0000. Anything received after that time might be too late.
Build test (gcc version 12.3.1 20230625): 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. Warning on boot, already reported by others. x86_64: Booted on qemu. Warning on boot, already reported by others. [1] arm64: Booted on rpi4b (4GB model). No regression. [2] mips: Booted on ci20 board. No regression. [3]
[1]. https://openqa.qa.codethink.co.uk/tests/4765 [2]. https://openqa.qa.codethink.co.uk/tests/4773 [3]. https://openqa.qa.codethink.co.uk/tests/4772
Tested-by: Sudip Mukherjee sudip.mukherjee@codethink.co.uk
-- Regards Sudip
One question about the warning on boot, all still works afterward, right? Or does the system not work?
I did not notice any problem in testing after boot. Only the warning.
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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.
Fails to build for me with gcc-11/binutils 2.37 on RISC-V. The problematic patch is "riscv: Handle zicsr/zifencei issue between gcc and binutils". Can you drop that please, probably from all of your branches. It certainly affects 6.4 too & I don't personally test anything older than 6.1.
Thanks, Conor.
On Wed, Aug 23, 2023 at 10:35:54AM +0100, Conor Dooley wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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.
Fails to build for me with gcc-11/binutils 2.37 on RISC-V. The problematic patch is "riscv: Handle zicsr/zifencei issue between gcc and binutils". Can you drop that please, probably from all of your branches. It certainly affects 6.4 too & I don't personally test anything older than 6.1.
If I recall correctly, I had to be careful with combining gcc versions and binutils versions. gcc 11.4.0 combined with binutils 2.40 works fine for me. Note that this doesn't just affect riscv. loongarch and ppc are quite notorious for that as well.
Guenter
On Wed, Aug 23, 2023 at 10:35:54AM +0100, Conor Dooley wrote:
On Mon, Aug 21, 2023 at 09:39:39PM +0200, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.47 release. There are 194 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.
Fails to build for me with gcc-11/binutils 2.37 on RISC-V. The problematic patch is "riscv: Handle zicsr/zifencei issue between gcc and binutils". Can you drop that please, probably from all of your branches. It certainly affects 6.4 too & I don't personally test anything older than 6.1.
I've dropped that patch now from all trees, thanks.
greg k-h
-
Bagas Sanjaya -
Conor Dooley -
Florian Fainelli -
Greg Kroah-Hartman -
Guenter Roeck -
Joel Fernandes -
Naresh Kamboju -
Ron Economos -
Salvatore Bonaccorso -
SeongJae Park -
Shuah Khan -
Sudip Mukherjee -
Sudip Mukherjee (Codethink)
-
Takeshi Ogasawara