This project is mirrored from https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10.git.
Pull mirroring updated .
- Mar 03, 2025
-
-
Julio Faracco authored
Signed-off-by:Julio Faracco <jfaracco@redhat.com>
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/318 JIRA: https://issues.redhat.com/browse/RHEL-67594 Upstream Status: RHEL Only Signed-off-by:
Rupinderjit Singh <rusingh@redhat.com> Approved-by:
Mika Penttilä <mpenttil@redhat.com> Approved-by:
Mark Langsdorf <mlangsdo@redhat.com> Approved-by:
Nirmala Dalvi <ndalvi@redhat.com> Approved-by:
CKI KWF Bot <cki-ci-bot+kwf-gitlab-com@redhat.com> Merged-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/332 JIRA: https://issues.redhat.com/browse/RHEL-77292 CVE: CVE-2024-57937 - mm: reinstate ability to map write-sealed memfd mappings read-only - selftests/memfd: add test for mapping write-sealed memfd read-only Signed-off-by:
Rafael Aquini <raquini@redhat.com> Approved-by:
Herton R. Krzesinski <herton@redhat.com> Approved-by:
Nico Pache <npache@redhat.com> Approved-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/345 JIRA: https://issues.redhat.com/browse/RHEL-74426 ``` bonding: Correctly support GSO ESP offload The referenced fix is incomplete. It correctly computes bond_dev->gso_partial_features across slaves, but unfortunately netdev_fix_features discards gso_partial_features from the feature set if NETIF_F_GSO_PARTIAL isn't set in bond_dev->features. This is visible with ethtool -k bond0 | grep esp: tx-esp-segmentation: off [requested on] esp-hw-offload: on esp-tx-csum-hw-offload: on This patch reworks the bonding GSO offload support by: - making aggregating gso_partial_features across slaves similar to the other feature sets (this part is a no-op). - advertising the default partial gso features on empty bond devs, same as with other feature sets (also a no-op). - adding NETIF_F_GSO_PARTIAL to hw_enc_features filtered across slaves. - adding NETIF_F_GSO_PARTIAL to features in bond_setup() With all of these, 'ethtool -k bond0 | grep esp' now reports: tx-esp-segmentation: on esp-hw-offload: on esp-tx-csum-hw-offload: on Fixes: 4861333b4217 ("bonding: add ESP offload features when slaves support") Signed-off-by:
Hangbin Liu <liuhangbin@gmail.com> Signed-off-by:
Cosmin Ratiu <cratiu@nvidia.com> Acked-by:
Jay Vosburgh <jv@jvosburgh.net> Link: https://patch.msgid.link/20250127104147.759658-1-cratiu@nvidia.com Signed-off-by:
Paolo Abeni <pabeni@redhat.com> (cherry picked from commit 9e6c4e6b605c1fa3e24f74ee0b641e95f090188a) ``` Signed-off-by:
CKI Backport Bot <cki-ci-bot+cki-gitlab-backport-bot@redhat.com> --- <small>Created 2025-02-06 02:44 UTC by backporter - [KWF FAQ](https://red.ht/kernel_workflow_doc) - [Slack #team-kernel-workflow](https://redhat-internal.slack.com/archives/C04LRUPMJQ5) - [Source](https://gitlab.com/cki-project/kernel-workflow/-/blob/main/webhook/utils/backporter.py) - [Documentation](https://gitlab.com/cki-project/kernel-workflow/-/blob/main/docs/README.backporter.md) - [Report an issue](https://gitlab.com/cki-project/kernel-workflow/-/issues/new?issue%5Btitle%5D=backporter%20webhook%20issue)</small > Approved-by:
Xin Long <lxin@redhat.com> Approved-by:
José Ignacio Tornos Martínez <jtornosm@redhat.com> Approved-by:
Kamal Heib <kheib@redhat.com> Approved-by:
-
- Mar 02, 2025
-
-
Jan Stancek authored
JIRA: INTERNAL Upstream Status: RHEL only Don't bring in changes from .gitlab-ci.yml, Makefile.rhelver, changelog and self-tests. Regenerate self-tests data for 10.1. Signed-off-by:Jan Stancek <jstancek@redhat.com>
-
- Feb 27, 2025
-
-
Julio Faracco authored
Signed-off-by: -
Julio Faracco authored
Merge: RHEL10 [6.11.0-0.rc5.23.el10.ppc64le] FW1110 FS/EXT4: generic/390 test with 4k_adv/64_adv config fails with call traces MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/156 JIRA: https://issues.redhat.com/browse/RHEL-73465 ``` quota: flush quota_release_work upon quota writeback One of the paths quota writeback is called from is: freeze_super() sync_filesystem() ext4_sync_fs() dquot_writeback_dquots() Since we currently don't always flush the quota_release_work queue in this path, we can end up with the following race: 1. dquot are added to releasing_dquots list during regular operations. 2. FS Freeze starts, however, this does not flush the quota_release_work queue. 3. Freeze completes. 4. Kernel eventually tries to flush the workqueue while FS is frozen which hits a WARN_ON since transaction gets started during frozen state: ext4_journal_check_start+0x28/0x110 [ext4] (unreliable) __ext4_journal_start_sb+0x64/0x1c0 [ext4] ext4_release_dquot+0x90/0x1d0 [ext4] quota_release_workfn+0x43c/0x4d0 Which is the following line: WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE); Which ultimately results in generic/390 failing due to dmesg noise. This was detected on powerpc machine 15 cores. To avoid this, make sure to flush the workqueue during dquot_writeback_dquots() so we dont have any pending workitems after freeze. Reported-by:
Disha Goel <disgoel@linux.ibm.com> CC: stable@vger.kernel.org Fixes: dabc8b20 ("quota: fix dqput() to follow the guarantees dquot_srcu should provide") Reviewed-by:
Baokun Li <libaokun1@huawei.com> Signed-off-by:
Ojaswin Mujoo <ojaswin@linux.ibm.com> Signed-off-by:
Jan Kara <jack@suse.cz> Link: https://patch.msgid.link/20241121123855.645335-2-ojaswin@linux.ibm.com (cherry picked from commit ac6f420291b3fee1113f21d612fa88b628afab5b) ``` Signed-off-by:
Brian Foster <bfoster@redhat.com> Approved-by:
Carlos Maiolino <cmaiolino@redhat.com> Approved-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/272 JIRA: https://issues.redhat.com/browse/RHEL-76349 Commits: ``` 9988df07dbe1ca8282f5ae95f1b534f91bab73fc ``` Signed-off-by:
Mete Durlu <mdurlu@redhat.com> Approved-by:
Steve Best <sbest@redhat.com> Approved-by:
Tony Camuso <tcamuso@redhat.com> Approved-by:
-
Jan Stancek authored
Signed-off-by: -
Jan Stancek authored
JIRA: INTERNAL Upstream Status: RHEL only RHEL-10 dropped the trailing ".0" from branch names. Signed-off-by: -
Jan Stancek authored
MR: https://gitlab.com/redhat/rhel/src/kernel/rhel-10/-/merge_requests/22 JIRA: INTERNAL Upstream Status: RHEL only Now that we have forked from CentOS Stream, we need to switch the release number to use the zstream scheme and update our default disttag to match that used by the brew build environment for RHEL 10.0. Signed-off-by:
Bruno Goncalves <bgoncalv@redhat.com> Approved-by:
Patrick Talbert <ptalbert@redhat.com> Approved-by:
Scott Weaver <scweaver@redhat.com> Approved-by:
Eder Zulian <ezulian@redhat.com> Merged-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/rhel/src/kernel/rhel-10/-/merge_requests/17 JIRA: https://issues.redhat.com/browse/RHEL-76109 Upstream Status: RHEL only The commit breaks TPM device on Google Clouds's SNP and TDX instances, the problem was acknowledged upstream but the fix is still being worked on, see https://lore.kernel.org/lkml/Z5P_Rj4Uc82lJBDx@google.com/ https://lore.kernel.org/lkml/20250201005048.657470-1-seanjc@google.com/ For now, restore the status quo by reverting the commit. Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> Approved-by:
Maxim Levitsky <mlevitsk@redhat.com> Approved-by:
Paolo Bonzini <bonzini@gnu.org> Approved-by:
-
- Feb 25, 2025
-
-
Julio Faracco authored
Signed-off-by: -
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/380 Description: updates for cpufreq amd-pstate JIRA: https://issues.redhat.com/browse/RHEL-75925 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66691904 Tested: Successful platform test results on AMD (amd-genoa-03) system. Omitted-fix: e120829dbf927c8b93cd5e06acfec0332cc82e02 Signed-off-by:
Desnes Nunes <desnesn@redhat.com> Approved-by:
Lenny Szubowicz <lszubowi@redhat.com> Approved-by:
David Arcari <darcari@redhat.com> Approved-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/344 Description: updates bring up to turbostat version 2025.02.02 JIRA: https://issues.redhat.com/browse/RHEL-77986 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66582553 Tested: Successful platform test results on Intel (intel-arrowlake-s-02) system. Signed-off-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/400 Description: updates for drivers/thermal/intel JIRA: https://issues.redhat.com/browse/RHEL-79162 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66704543 Tested: Successful platform test results on Intel (intel-arrowlake-s-02) system. Signed-off-by:
Eric Chanudet <echanude@redhat.com> Approved-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/334 Description: updates for platform/x86 ISST and tools/power/x86/intel-speed-select JIRA: https://issues.redhat.com/browse/RHEL-76843 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66560650 Tested: Successful platform test results on Intel (intel-eaglestream-emr-03) system. Signed-off-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/364 Description: updates for cpufreq intel_pstate JIRA: https://issues.redhat.com/browse/RHEL-78189 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66594995 Tested: Successful platform test results on Intel (intel-arrowlake-s-02) system. Signed-off-by:
-
- Feb 24, 2025
-
-
Jan Stancek authored
JIRA: INTERNAL Upstream Status: RHEL only Now that we have forked from CentOS Stream, we need to switch the release number to use the zstream scheme and update our default disttag to match that used by the brew build environment for RHEL 10.0. Signed-off-by: -
Rupinderjit Singh authored
JIRA: https://issues.redhat.com/browse/RHEL-67594 Upstream Status: RHEL Only commit c8347f91 ("gpu: host1x: Fix boot regression for Tegra") caused a use of uninitialized mutex leading to below warning when CONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_LOCK_ALLOC are enabled. [ 41.662843] ------------[ cut here ]------------ [ 41.663012] DEBUG_LOCKS_WARN_ON(lock->magic != lock) [ 41.663035] WARNING: CPU: 4 PID: 794 at kernel/locking/mutex.c:587 __mutex_lock+0x670/0x878 [ 41.663458] Modules linked in: rtw88_8822c(+) bluetooth(+) rtw88_pci rtw88_core mac80211 aquantia libarc4 crc_itu_t cfg80211 tegra194_cpufreq dwmac_tegra(+) arm_dsu_pmu stmmac_platform stmmac pcs_xpcs rfkill at24 host1x(+) tegra_bpmp_thermal ramoops reed_solomon fuse loop nfnetlink xfs mmc_block rpmb_core ucsi_ccg ina3221 crct10dif_ce xhci_tegra ghash_ce lm90 sha2_ce sha256_arm64 sha1_ce sdhci_tegra pwm_fan sdhci_pltfm sdhci gpio_keys rtc_tegra cqhci mmc_core phy_tegra_xusb i2c_tegra tegra186_gpc_dma i2c_tegra_bpmp spi_tegra114 dm_mirror dm_region_hash dm_log dm_mod [ 41.665078] CPU: 4 UID: 0 PID: 794 Comm: (udev-worker) Not tainted 6.11.0-29.31_1538613708.el10.aarch64+debug #1 [ 41.665838] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.3.0-gcid-35594366 02/26/2024 [ 41.672555] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 41.679636] pc : __mutex_lock+0x670/0x878 [ 41.683834] lr : __mutex_lock+0x670/0x878 [ 41.688035] sp : ffff800084b77090 [ 41.691446] x29: ffff800084b77160 x28: ffffdd4bebf7b000 x27: ffffdd4be96b1000 [ 41.698799] x26: 1fffe0002308361c x25: 1ffff0001096ee18 x24: 0000000000000000 [ 41.706149] x23: 0000000000000000 x22: 0000000000000002 x21: ffffdd4be6e3c7a0 [ 41.713500] x20: ffff800084b770f0 x19: ffff00011841b1e8 x18: 0000000000000000 [ 41.720675] x17: 0000000000000000 x16: 0000000000000000 x15: 0720072007200720 [ 41.728023] x14: 0000000000000000 x13: 0000000000000001 x12: ffff6001a96eaab3 [ 41.735375] x11: 1fffe001a96eaab2 x10: ffff6001a96eaab2 x9 : ffffdd4be4838bbc [ 41.742723] x8 : 00009ffe5691554e x7 : ffff000d4b755593 x6 : 0000000000000001 [ 41.749985] x5 : ffff000d4b755590 x4 : 1fffe0001d88f001 x3 : dfff800000000000 [ 41.756988] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000ec478000 [ 41.764251] Call trace: [ 41.766695] __mutex_lock+0x670/0x878 [ 41.770373] mutex_lock_nested+0x2c/0x40 [ 41.774134] host1x_intr_start+0x54/0xf8 [host1x] [ 41.778863] host1x_runtime_resume+0x150/0x228 [host1x] [ 41.783935] pm_generic_runtime_resume+0x84/0xc8 [ 41.788485] __rpm_callback+0xa0/0x478 [ 41.792422] rpm_callback+0x15c/0x1a8 [ 41.795922] rpm_resume+0x698/0xc08 [ 41.799597] __pm_runtime_resume+0xa8/0x140 [ 41.803621] host1x_probe+0x810/0xbc0 [host1x] [ 41.807909] platform_probe+0xcc/0x1a8 [ 41.811845] really_probe+0x188/0x800 [ 41.815347] __driver_probe_device+0x164/0x360 [ 41.819810] driver_probe_device+0x64/0x1a8 [ 41.823834] __driver_attach+0x180/0x490 [ 41.827773] bus_for_each_dev+0x104/0x1a0 [ 41.831797] driver_attach+0x44/0x68 [ 41.835296] bus_add_driver+0x23c/0x4e8 [ 41.839235] driver_register+0x15c/0x3a8 [ 41.843170] __platform_register_drivers+0xa4/0x208 [ 41.848159] tegra_host1x_init+0x4c/0xff8 [host1x] [ 41.853147] do_one_initcall+0xd4/0x380 [ 41.856997] do_init_module+0x1dc/0x698 [ 41.860758] load_module+0xc70/0x1300 [ 41.864435] __do_sys_init_module+0x1a8/0x1d0 [ 41.868721] __arm64_sys_init_module+0x74/0xb0 [ 41.873183] invoke_syscall.constprop.0+0xdc/0x1e8 [ 41.877997] do_el0_svc+0x154/0x1d0 [ 41.881671] el0_svc+0x54/0x140 [ 41.884820] el0t_64_sync_handler+0x120/0x130 [ 41.889285] el0t_64_sync+0x1a4/0x1a8 [ 41.892960] irq event stamp: 69737 [ 41.896370] hardirqs last enabled at (69737): [<ffffdd4be6d7768c>] _raw_spin_unlock_irqrestore+0x44/0xe8 [ 41.905739] hardirqs last disabled at (69736): [<ffffdd4be59dcd40>] clk_enable_lock+0x98/0x198 [ 41.914314] softirqs last enabled at (68082): [<ffffdd4be466b1d0>] handle_softirqs+0x4c8/0x890 [ 41.922977] softirqs last disabled at (67945): [<ffffdd4be44f02a4>] __do_softirq+0x1c/0x28 [ 41.931289] ---[ end trace 0000000000000000 ]--- Inside the probe function when pm_runtime_enable() is called, the PM core invokes a resume callback if the device Host1x is in a suspended state. As it can be seen in the logs above, this leads to host1x_intr_start() function call which is trying to acquire a mutex lock. But, the function host_intr_init() only gets called after the pm_runtime_enable() where mutex is initialised leading to the use of mutex prior to its initialisation. Fix this by moving the mutex initialisation prior to the runtime PM enablement function pm_runtime_enable() in probe. Fixes: c8347f91 ("gpu: host1x: Fix boot regression for Tegra") Signed-off-by:
Jon Hunter <jonathanh@nvidia.com> Tested-by:
Thierry Reding <treding@nvidia.com> Link: https://patchwork.ozlabs.org/project/linux-tegra/patch/20250206155803.201942-1-rusingh@redhat.com/
-
- Feb 20, 2025
-
-
Julio Faracco authored
Signed-off-by: -
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/372 Description: updates for cpupower JIRA: https://issues.redhat.com/browse/RHEL-78946 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66664135 Tested: Successful platform test results on Intel (intel-arrowlake-s-02) system. Signed-off-by:
-
Julio Faracco authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/376 Description: updates for powercap: intel_rapl JIRA: https://issues.redhat.com/browse/RHEL-79097 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=66676240 Tested: Successful platform test results on Intel (intel-arrowlake-s-02) system. Signed-off-by:
-
Julio Faracco authored
JIRA: INTERNAL Upstream Status: RHEL only Signed-off-by: -
Vitaly Kuznetsov authored
JIRA: https://issues.redhat.com/browse/RHEL-76109 Upstream Status: RHEL only This reverts commit 8e690b81. The commit breaks TPM device on Google Clouds's SNP and TDX instances, the problem was acknowledged upstream but the fix is still being worked on, see https://lore.kernel.org/lkml/Z5P_Rj4Uc82lJBDx@google.com/ https://lore.kernel.org/lkml/20250201005048.657470-1-seanjc@google.com/ For now, restore the status quo by reverting the commit. Signed-off-by:
-
- Feb 19, 2025
-
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 207a792d01603faae08d9bd82846bd99c42c30cc Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Date: Wed Dec 18 13:44:44 2024 -0800 thermal: intel: Fix compile issue when CONFIG_NET is not defined If CONFIG_NET is not defined then THERMAL_NETLINK can't be selected. Hence add dependency on CONFIG_NET. Othewise it will generate compile errors while compiling thermal_netlink.c. Fixes: 4596cbea0ed2 ("thermal: intel: Remove explicit user_space governor selection") Reported-by:
kernel test robot <lkp@intel.com> Signed-off-by:
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Link: https://patch.msgid.link/20241218214444.1904650-1-srinivas.pandruvada@linux.intel.com [ rjw: Merge the "depends on" lines ] Signed-off-by:
Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit b59bd75a4b0983d6bcd10987b32ea9b9042db88c Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Date: Mon Dec 16 13:18:10 2024 -0800 thermal: intel: int340x: Panther Lake power floor and workload hint support Panther Lake follows same register set as Lunar Lake. Enable feature flags to support workload hints and power floor status. Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit e50eeababa946d92f1669fd4d66a5f652b143b05 Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Date: Mon Dec 16 13:18:09 2024 -0800 thermal: intel: int340x: Panther Lake DLVR support Panther Lake follows same register set as Lunar Lake for DLVR. Enable feature flag to support DLVR. Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 4596cbea0ed2ef4f563a92775c9f612700ece145 Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Date: Mon Dec 16 11:08:21 2024 -0800 thermal: intel: Remove explicit user_space governor selection Currently some user space programs like Linux thermald needs to register to get notifications from both thermal user space governor and also Thermal netlink. This is required as some messages like HFI (Hardware Feedback Notifications) requires Thermal netlink. This results in additional processing in kernel and user space to process both notifications. The cost of using user space governor using kobject_uevent is much higher as this is also used by other user space daemons like udev daemon. Do not select user_space thermal governor by default. If it is present user space programs can always use this governor by writing to "policy" attribute. Instead from the kernel select THERMAL_NETLINK. Trip temperature violation can be received by user space programs via thermal netlink events: THERMAL_GENL_EVENT_TZ_TRIP_UP THERMAL_GENL_EVENT_TZ_TRIP_DOWN Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 3fd3697ebfb49ee218416340b084208377ea081d Author: Zhang Rui <rui.zhang@intel.com> Date: Tue Dec 3 15:58:02 2024 +0800 ACPI: DPTF: Support Panther Lake Add Panther Lake ACPI IDs for DPTF. Signed-off-by:
Zhang Rui <rui.zhang@intel.com> Link: https://patch.msgid.link/20241203075802.584741-4-rui.zhang@intel.com [ rjw: Changelog edit ] Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 3cc83aeea0cd061e424f634da62dfcabe7fdd5c5 Author: Zhang Rui <rui.zhang@intel.com> Date: Tue Dec 3 15:58:01 2024 +0800 thermal: intel: int340x: processor: Enable MMIO RAPL for Panther Lake Enable MMIO RAPL support for PantherLake platform. Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 13f3cbfbb8c9f3825a1e4e4371fe040fb35e41d5 Author: Thomas Weißschuh <linux@weissschuh.net> Date: Thu Nov 21 17:29:32 2024 +0100 thermal: int3400: Remove unneeded data_vault attribute_group The group only contains a single entry and the conditionals around its lifecycle make clear that this won't change. Remove the unnecessary group. This saves some memory and it's easier to read. The removal of a non-const bin_attribute[] instance is also a preparation for the constification of struct bin_attributes. Signed-off-by:
Thomas Weißschuh <linux@weissschuh.net> Link: https://patch.msgid.link/20241121-sysfs-const-bin_attr-int340x_thermal-v1-1-2436facf9dae@weissschuh.net Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 7082503622986537f57bdb5ef23e69e70cfad881 Author: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Date: Thu Nov 14 12:02:13 2024 -0800 thermal: int3400: Fix reading of current_uuid for active policy When the current_uuid attribute is set to the active policy UUID, reading back the same attribute is returning "INVALID" instead of the active policy UUID on some platforms before Ice Lake. In platforms before Ice Lake, firmware provides a list of supported thermal policies. In this case, user space can select any of the supported thermal policies via a write to attribute "current_uuid". In commit c7ff2976 ("thermal: int340x: Update OS policy capability handshake")', the OS policy handshake was updated to support Ice Lake and later platforms and it treated priv->current_uuid_index=0 as invalid. However, priv->current_uuid_index=0 is for the active policy, only priv->current_uuid_index=-1 is invalid. Fix this issue by updating the priv->current_uuid_index check. Fixes: c7ff2976 ("thermal: int340x: Update OS policy capability handshake") Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit dd64594ca2c5b952570c3b885763b93ebe26fe9a Author: Uwe Kleine-König <u.kleine-koenig@baylibre.com> Date: Sat Oct 19 18:34:11 2024 +0200 thermal: Switch back to struct platform_driver::remove() After commit 0edb555a ("platform: Make platform_driver::remove() return void") .remove() is (again) the right callback to implement for platform drivers. Convert all platform drivers below drivers/thermal to use .remove(), with the eventual goal to drop struct platform_driver::remove_new(). As .remove() and .remove_new() have the same prototypes, conversion is done by just changing the structure member name in the driver initializer. On the way make a few whitespace changes to make indention consistent. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@baylibre.com> Link: https://lore.kernel.org/r/20241019163412.304422-2-u.kleine-koenig@baylibre.com Signed-off-by:
Daniel Lezcano <daniel.lezcano@linaro.org> Signed-off-by:
-
Steve Best authored
JIRA: https://issues.redhat.com/browse/RHEL-79162 commit 110213b8f0e7021819d4db273facb27701bc3381 Author: Tony Luck <tony.luck@intel.com> Date: Thu Oct 31 11:57:33 2024 -0700 x86/cpu: Fix FAM5_QUARK_X1000 to use X86_MATCH_VFM() This family 5 CPU escaped notice when cleaning up all the family 6 CPUs. Signed-off-by:
Tony Luck <tony.luck@intel.com> Signed-off-by:
Dave Hansen <dave.hansen@linux.intel.com> Link: https://lore.kernel.org/all/20241031185733.17327-1-tony.luck%40intel.com Signed-off-by:
-
- Feb 16, 2025
-
-
Jan Stancek authored
Signed-off-by: -
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/317 ovl: support encoding fid from inode with no alias JIRA: https://issues.redhat.com/browse/RHEL-77301 CVE: CVE-2025-21654 Signed-off-by:
Miklos Szeredi <mszeredi@redhat.com> Approved-by:
Ian Kent <ikent@redhat.com> Approved-by:
David Howells <dhowells@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/307 JIRA: https://issues.redhat.com/browse/RHEL-77240 CVE: CVE-2025-21668 ``` pmdomain: imx8mp-blk-ctrl: add missing loop break condition Currently imx8mp_blk_ctrl_remove() will continue the for loop until an out-of-bounds exception occurs. pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : dev_pm_domain_detach+0x8/0x48 lr : imx8mp_blk_ctrl_shutdown+0x58/0x90 sp : ffffffc084f8bbf0 x29: ffffffc084f8bbf0 x28: ffffff80daf32ac0 x27: 0000000000000000 x26: ffffffc081658d78 x25: 0000000000000001 x24: ffffffc08201b028 x23: ffffff80d0db9490 x22: ffffffc082340a78 x21: 00000000000005b0 x20: ffffff80d19bc180 x19: 000000000000000a x18: ffffffffffffffff x17: ffffffc080a39e08 x16: ffffffc080a39c98 x15: 4f435f464f006c72 x14: 0000000000000004 x13: ffffff80d0172110 x12: 0000000000000000 x11: ffffff80d0537740 x10: ffffff80d05376c0 x9 : ffffffc0808ed2d8 x8 : ffffffc084f8bab0 x7 : 0000000000000000 x6 : 0000000000000000 x5 : ffffff80d19b9420 x4 : fffffffe03466e60 x3 : 0000000080800077 x2 : 0000000000000000 x1 : 0000000000000001 x0 : 0000000000000000 Call trace: dev_pm_domain_detach+0x8/0x48 platform_shutdown+0x2c/0x48 device_shutdown+0x158/0x268 kernel_restart_prepare+0x40/0x58 kernel_kexec+0x58/0xe8 __do_sys_reboot+0x198/0x258 __arm64_sys_reboot+0x2c/0x40 invoke_syscall+0x5c/0x138 el0_svc_common.constprop.0+0x48/0xf0 do_el0_svc+0x24/0x38 el0_svc+0x38/0xc8 el0t_64_sync_handler+0x120/0x130 el0t_64_sync+0x190/0x198 Code: 8128c2d0 ffffffc0 aa1e03e9 d503201f Fixes: 556f5cf9 ("soc: imx: add i.MX8MP HSIO blk-ctrl") Cc: stable@vger.kernel.org Signed-off-by:
Xiaolei Wang <xiaolei.wang@windriver.com> Reviewed-by:
Lucas Stach <l.stach@pengutronix.de> Reviewed-by:
Fabio Estevam <festevam@gmail.com> Reviewed-by:
Frank Li <Frank.Li@nxp.com> Link: https://lore.kernel.org/r/20250115014118.4086729-1-xiaolei.wang@windriver.com Signed-off-by:
Ulf Hansson <ulf.hansson@linaro.org> (cherry picked from commit 726efa92e02b460811e8bc6990dd742f03b645ea) ``` Signed-off-by:
Jennifer Berringer <jberring@redhat.com> Approved-by:
Radu Rendec <rrendec@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/368 JIRA: https://issues.redhat.com/browse/RHEL-78677 CVE: CVE-2025-21686 Signed-off-by:
Jeff Moyer <jmoyer@redhat.com> Approved-by:
Ming Lei <ming.lei@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/301 JIRA: https://issues.redhat.com/browse/RHEL-77214 CVE: CVE-2025-21666 ``` vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] Recent reports have shown how we sometimes call vsock_*_has_data() when a vsock socket has been de-assigned from a transport (see attached links), but we shouldn't. Previous commits should have solved the real problems, but we may have more in the future, so to avoid null-ptr-deref, we can return 0 (no space, no data available) but with a warning. This way the code should continue to run in a nearly consistent state and have a warning that allows us to debug future problems. Fixes: c0cfa2d8 ("vsock: add multi-transports support") Cc: stable@vger.kernel.org Link: https://lore.kernel.org/netdev/Z2K%2FI4nlHdfMRTZC@v4bel-B760M-AORUS-ELITE-AX/ Link: https://lore.kernel.org/netdev/5ca20d4c-1017-49c2-9516-f6f75fd331e9@rbox.co/ Link: https://lore.kernel.org/netdev/677f84a8.050a0220.25a300.01b3.GAE@google.com/ Co-developed-by:
Hyunwoo Kim <v4bel@theori.io> Signed-off-by:
Wongi Lee <qwerty@theori.io> Signed-off-by:
Stefano Garzarella <sgarzare@redhat.com> Reviewed-by:
Luigi Leonardi <leonardi@redhat.com> Reviewed-by:
Jon Maloy <jmaloy@redhat.com> Approved-by:
-
