This project is mirrored from https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10.git.
Pull mirroring updated .
- Feb 25, 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/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:
Steve Best <sbest@redhat.com> Approved-by:
Tony Camuso <tcamuso@redhat.com> Approved-by:
Desnes Nunes <desnesn@redhat.com> Approved-by:
Lenny Szubowicz <lszubowi@redhat.com> Approved-by:
David Arcari <darcari@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/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:
Mark Langsdorf <mlangsdo@redhat.com> Approved-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 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:
-
- 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 <jstancek@redhat.com>
-
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:
Carlos Maiolino <cmaiolino@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:
CKI Backport Bot <cki-ci-bot+cki-gitlab-backport-bot@redhat.com> --- <small>Created 2025-01-31 18:55 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:
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:
Brian Foster <bfoster@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:
Paolo Abeni <pabeni@redhat.com> (cherry picked from commit 91751e248256efc111e52e15115840c35d85abaf) ``` Signed-off-by:
Jon Maloy <jmaloy@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/365 JIRA: https://issues.redhat.com/browse/RHEL-78685 CVE: CVE-2025-21689 ``` commit 575a5adf48b06a2980c9eeffedf699ed5534fade Author: Qasim Ijaz <qasdev00@gmail.com> Date: Mon Jan 13 18:00:34 2025 +0000 USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb() This patch addresses a null-ptr-deref in qt2_process_read_urb() due to an incorrect bounds check in the following: if (newport > serial->num_ports) { dev_err(&port->dev, "%s - port change to invalid port: %i\n", __func__, newport); break; } The condition doesn't account for the valid range of the serial->port buffer, which is from 0 to serial->num_ports - 1. When newport is equal to serial->num_ports, the assignment of "port" in the following code is out-of-bounds and NULL: serial_priv->current_port = newport; port = serial->port[serial_priv->current_port]; The fix checks if newport is greater than or equal to serial->num_ports indicating it is out-of-bounds. Reported-by:
syzbot <syzbot+506479ebf12fe435d01a@syzkaller.appspotmail.com> Closes: https://syzkaller.appspot.com/bug?extid=506479ebf12fe435d01a Fixes: f7a33e60 ("USB: serial: add quatech2 usb to serial driver") Cc: <stable@vger.kernel.org> # 3.5 Signed-off-by:
Qasim Ijaz <qasdev00@gmail.com> Reviewed-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
Johan Hovold <johan@kernel.org>```> Signed-off-by:
Daniel Horak <dhorak@redhat.com> Approved-by:
John W. Linville <linville@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/358 JIRA: https://issues.redhat.com/browse/RHEL-58817 - lazy tlb: fix hotplug exit race with MMU_LAZY_TLB_SHOOTDOWN (Herton R. Krzesinski) [[RHEL-58817](https://issues.redhat.com/browse/RHEL-58817) ] Signed-off-by:
Herton R. Krzesinski <herton@redhat.com> Approved-by:
Waiman Long <longman@redhat.com> Approved-by:
Phil Auld <pauld@redhat.com> Approved-by:
-
- Feb 14, 2025
-
-
Jan Stancek authored
Signed-off-by: -
Jan Stancek authored
Merge: CVE-2024-56611: mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/253 JIRA: https://issues.redhat.com/browse/RHEL-76120 CVE: CVE-2024-56611 ``` mm/mempolicy: fix migrate_to_node() assuming there is at least one VMA in a MM We currently assume that there is at least one VMA in a MM, which isn't true. So we might end up having find_vma() return NULL, to then de-reference NULL. So properly handle find_vma() returning NULL. This fixes the report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 UID: 0 PID: 6021 Comm: syz-executor284 Not tainted 6.12.0-rc7-syzkaller-00187-gf868cd251776 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 RIP: 0010:migrate_to_node mm/mempolicy.c:1090 [inline] RIP: 0010:do_migrate_pages+0x403/0x6f0 mm/mempolicy.c:1194 Code: ... RSP: 0018:ffffc9000375fd08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffc9000375fd78 RCX: 0000000000000000 RDX: ffff88807e171300 RSI: dffffc0000000000 RDI: ffff88803390c044 RBP: ffff88807e171428 R08: 0000000000000014 R09: fffffbfff2039ef1 R10: ffffffff901cf78f R11: 0000000000000000 R12: 0000000000000003 R13: ffffc9000375fe90 R14: ffffc9000375fe98 R15: ffffc9000375fdf8 FS: 00005555919e1380(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00005555919e1ca8 CR3: 000000007f12a000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> kernel_migrate_pages+0x5b2/0x750 mm/mempolicy.c:1709 __do_sys_migrate_pages mm/mempolicy.c:1727 [inline] __se_sys_migrate_pages mm/mempolicy.c:1723 [inline] __x64_sys_migrate_pages+0x96/0x100 mm/mempolicy.c:1723 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [akpm@linux-foundation.org: add unlikely()] Link: https://lkml.kernel.org/r/20241120201151.9518-1-david@redhat.com Fixes: 39743889 ("[PATCH] Swap Migration V5: sys_migrate_pages interface") Signed-off-by:
David Hildenbrand <david@redhat.com> Reported-by:
<syzbot+3511625422f7aa637f0d@syzkaller.appspotmail.com> Closes: https://lore.kernel.org/lkml/673d2696.050a0220.3c9d61.012f.GAE@google.com/T/ Reviewed-by:
Liam R. Howlett <Liam.Howlett@Oracle.com> Reviewed-by:
Christoph Lameter <cl@linux.com> Cc: Liam R. Howlett <Liam.Howlett@Oracle.com> Cc: <stable@vger.kernel.org> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> (cherry picked from commit 091c1dd2d4df6edd1beebe0e5863d4034ade9572) ``` Signed-off-by:
Aristeu Rozanski <arozansk@redhat.com> Approved-by:
Rafael Aquini <raquini@redhat.com> Approved-by:
Nico Pache <npache@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/378 JIRA: INTERNAL Upstream Status: RHEL only Reinstate s1-gcp-ci.brew-build.tier1.functional test, owners said it's stable now. This reverts commit 6a121851. Signed-off-by:
Eder Zulian <ezulian@redhat.com> Merged-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/374 nvme: remove multipath module parameter JIRA: https://issues.redhat.com/browse/RHEL-78133 Upstream Status: RHEL-only Since device-mapper multipath will no longer be operating on NVMe devices, there is no longer a need for the "multipath" parameter. Note that, when compiled with CONFIG_NVME_MULTIPATH off multi-path capable controllers and namespaces will continue to present multiple device entries - one for each controller/namespace discovered. This could be confusing, as device-mapper multipath relies upon code in nvme/host/multipath.c, and running device-mapper multipath with a kernel compiled with CONFIG_NVME_MULTIPATH disabled is not supported. Closes: https://lore.kernel.org/linux-nvme/20241121220321.40616-1-bgurney@redhat.com/ Tested-by:
John Meneghini <jmeneghi@redhat.com> Reviewed-by:
Bryan Gurney <bgurney@redhat.com> Approved-by:
Ewan D. Milne <emilne@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/370 NFSD: Fix CB_GETATTR status fix JIRA: https://issues.redhat.com/browse/RHEL-56888 Signed-off-by:
Olga Kornievskaia <okorniev@redhat.com> Approved-by:
Scott Mayhew <smayhew@redhat.com> Approved-by:
Benjamin Coddington <bcodding@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/362 JIRA: https://issues.redhat.com/browse/RHEL-78517 CVE: CVE-2024-57949 ``` irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity() The following call-chain leads to enabling interrupts in a nested interrupt disabled section: irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave() <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled This was broken in commit b97e8a2f, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq). Fix the issue by using guard(raw_spinlock). [ tglx: Massaged change log ] Fixes: b97e8a2f ("irqchip/gic-v3-its: Fix potential race condition in its_vlpi_prop_update()") Signed-off-by:
Tomas Krcka <krckatom@amazon.de> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de> Reviewed-by:
Marc Zyngier <maz@kernel.org> Cc: stable@vger.kernel.org Link: https://lore.kernel.org/all/20241230150825.62894-1-krckatom@amazon.de (cherry picked from commit 35cb2c6ce7da545f3b5cb1e6473ad7c3a6f08310) ``` Signed-off-by:
Charles Mirabile <cmirabil@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/361 JIRA: https://issues.redhat.com/browse/RHEL-78322 Upstream status: RHEL-Only Since some of our key projects use erofs we have surveyed the code and assessed upstream support status for the file system and this all looks good from a support perspective. So we are promoting erofs to full support. Signed-off-by:
Eric Sandeen <esandeen@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/356 JIRA: https://issues.redhat.com/browse/RHEL-78388 Signed-off-by:
Marc Dionne <mdionne@redhat.com> Approved-by:
Alice Mitchell <ajmitchell@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/353 JIRA: https://issues.redhat.com/browse/RHEL-78152 Signed-off-by:
Paulo Alcantara <paalcant@redhat.com> Approved-by:
Jay Shin <jaeshin@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/346 JIRA: https://issues.redhat.com/browse/RHEL-78209 commit 8ac412a3361173e3000b16167af3d1f6f90af613 Author: Daniel Xu <dxu@dxuuu.xyz> Date: Tue Jan 14 13:28:43 2025 -0700 bpf: tcp: Mark bpf_load_hdr_opt() arg2 as read-write MEM_WRITE attribute is defined as: "Non-presence of MEM_WRITE means that MEM is only being read". bpf_load_hdr_opt() both reads and writes from its arg2 - void *search_res. This matters a lot for the next commit where we more precisely track stack accesses. Without this annotation, the verifier will make false assumptions about the contents of memory written to by helpers and possibly prune valid branches. Fixes: 6fad274f ("bpf: Add MEM_WRITE attribute") Acked-by:
Martin KaFai Lau <martin.lau@kernel.org> Signed-off-by:
Daniel Xu <dxu@dxuuu.xyz> Link: https://lore.kernel.org/r/730e45f8c39be2a5f3d8c4406cceca9d574cbf14.1736886479.git.dxu@dxuuu.xyz Signed-off-by:
Alexei Starovoitov <ast@kernel.org> Signed-off-by:
Viktor Malik <vmalik@redhat.com> Approved-by:
Tomas Glozar <tglozar@redhat.com> Approved-by:
Jerome Marchand <jmarchan@redhat.com> Approved-by:
Toke Høiland-Jørgensen <toke@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/340 JIRA: https://issues.redhat.com/browse/RHEL-77959 MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/340 The second patch is the fix commit. The first patch fixes a minor issue in the code. Signed-off-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/208 JIRA: https://issues.redhat.com/browse/RHEL-71050 Upstream Status: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm commit d40797d6720e861196e848f3615bb09dae5be7ce Author: Peter Zijlstra <peterz@infradead.org> Date: Fri, 22 Nov 2024 16:54:51 +0100 kasan: make kasan_record_aux_stack_noalloc() the default behaviour kasan_record_aux_stack_noalloc() was introduced to record a stack trace without allocating memory in the process. It has been added to callers which were invoked while a raw_spinlock_t was held. More and more callers were identified and changed over time. Is it a good thing to have this while functions try their best to do a locklessly setup? The only downside of having kasan_record_aux_stack() not allocate any memory is that we end up without a stacktrace if stackdepot runs out of memory and at the same stacktrace was not recorded before To quote Marco Elver from https://lore.kernel.org/all/CANpmjNPmQYJ7pv1N3cuU8cP18u7PP_uoZD8YxwZd4jtbof9nVQ@mail.gmail.com/ | I'd be in favor, it simplifies things. And stack depot should be | able to replenish its pool sufficiently in the "non-aux" cases | i.e. regular allocations. Worst case we fail to record some | aux stacks, but I think that's only really bad if there's a bug | around one of these allocations. In general the probabilities | of this being a regression are extremely small [...] Make the kasan_record_aux_stack_noalloc() behaviour default as kasan_record_aux_stack(). [bigeasy@linutronix.de: dressed the diff as patch] Link: https://lkml.kernel.org/r/20241122155451.Mb2pmeyJ@linutronix.de Fixes: 7cb3007c ("kasan: generic: introduce kasan_record_aux_stack_noalloc()") Signed-off-by:
Peter Zijlstra (Intel) <peterz@infradead.org> Signed-off-by:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Reported-by:
<syzbot+39f85d612b7c20d8db48@syzkaller.appspotmail.com> Closes: https://lore.kernel.org/all/67275485.050a0220.3c8d68.0a37.GAE@google.com Reviewed-by:
Andrey Konovalov <andreyknvl@gmail.com> Reviewed-by:
Marco Elver <elver@google.com> Reviewed-by:
Wander Lairson Costa <wander@redhat.com> Approved-by:
-
Jan Stancek authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/merge_requests/206 JIRA: https://issues.redhat.com/browse/RHEL-74109 CVE: CVE-2024-57888 commit de35994ecd2dd6148ab5a6c5050a1670a04dec77 Author: Tvrtko Ursulin <tvrtko.ursulin@igalia.com> Date: Thu, 19 Dec 2024 09:30:30 +0000 workqueue: Do not warn when cancelling WQ_MEM_RECLAIM work from !WQ_MEM_RECLAIM worker After commit 746ae46c ("drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM") amdgpu started seeing the following warning: [ ] workqueue: WQ_MEM_RECLAIM sdma0:drm_sched_run_job_work [gpu_sched] is flushing !WQ_MEM_RECLAIM events:amdgpu_device_delay_enable_gfx_off [amdgpu] ... [ ] Workqueue: sdma0 drm_sched_run_job_work [gpu_sched] ... [ ] Call Trace: [ ] <TASK> ... [ ] ? check_flush_dependency+0xf5/0x110 ... [ ] cancel_delayed_work_sync+0x6e/0x80 [ ] amdgpu_gfx_off_ctrl+0xab/0x140 [amdgpu] [ ] amdgpu_ring_alloc+0x40/0x50 [amdgpu] [ ] amdgpu_ib_schedule+0xf4/0x810 [amdgpu] [ ] ? drm_sched_run_job_work+0x22c/0x430 [gpu_sched] [ ] amdgpu_job_run+0xaa/0x1f0 [amdgpu] [ ] drm_sched_run_job_work+0x257/0x430 [gpu_sched] [ ] process_one_work+0x217/0x720 ... [ ] </TASK> The intent of the verifcation done in check_flush_depedency is to ensure forward progress during memory reclaim, by flagging cases when either a memory reclaim process, or a memory reclaim work item is flushed from a context not marked as memory reclaim safe. This is correct when flushing, but when called from the cancel(_delayed)_work_sync() paths it is a false positive because work is either already running, or will not be running at all. Therefore cancelling it is safe and we can relax the warning criteria by letting the helper know of the calling context. Signed-off-by:
Tvrtko Ursulin <tvrtko.ursulin@igalia.com> Fixes: fca839c0 ("workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue") References: 746ae46c ("drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM") Cc: Tejun Heo <tj@kernel.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Lai Jiangshan <jiangshanlai@gmail.com> Cc: Alex Deucher <alexander.deucher@amd.com> Cc: Christian König <christian.koenig@amd.com Cc: Matthew Brost <matthew.brost@intel.com> Cc: <stable@vger.kernel.org> # v4.5+ Signed-off-by:
Tejun Heo <tj@kernel.org> Signed-off-by:
-
