This project is mirrored from https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9.git.
Pull mirroring updated .
- Apr 11, 2025
-
-
Augusto Caringi authored
Signed-off-by:Augusto Caringi <acaringi@redhat.com>
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6683 JIRA: https://issues.redhat.com/browse/RHEL-85318 This backports two commits: 7f77300f ("selftest/mm: va_high_addr_switch: add ppc64 support check") f4b06636 ("selftests/mm: va_high_addr_switch: reduce test noise") Signed-off-by:
Li Wang <liwang@redhat.com> Approved-by:
Waiman Long <longman@redhat.com> Approved-by:
Rafael Aquini <raquini@redhat.com> Approved-by:
CKI KWF Bot <cki-ci-bot+kwf-gitlab-com@redhat.com> Merged-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6617 JIRA: INTERNAL Upstream Status: RHEL-only (ARK commit 587236d6984d26002a8ba3cd3b0dffcb8b75fe21) warning: /builddir/build/SPECS/kernel.spec: line 1555: unexpected argument to non-parametric macro %uname_suffix warning: /builddir/build/SPECS/kernel.spec: line 1597: unexpected argument to non-parametric macro %uname_variant ... Signed-off-by:
Jan Stancek <jstancek@redhat.com> Approved-by:
Scott Weaver <scweaver@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6648 JIRA: https://issues.redhat.com/browse/RHEL-78426 In RHEL 9 running the "perf stat STD output linter" test fails: ``` 91: perf stat STD output linter: --- start --- test child forked, pid 648531 Checking STD output: no args Unknown event name in TopdownL1 # 2.5 percent of slots slots_lost_misspeculation_fraction ---- end(-1) ---- 91: perf stat STD output linter : FAILED! ``` This MR adds TopdownL1 to the list of skipped metrics in the test. Signed-off-by:
Anubhav Shelat <ashelat@redhat.com> Approved-by:
Michael Petlan <mpetlan@redhat.com> Approved-by:
Tony Camuso <tcamuso@redhat.com> Approved-by:
jbrnak <jbrnak@redhat.com> Approved-by:
Jarod Wilson <jarod@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6679 Description: Updates for powerpc longer H_CALLS JIRA: https://issues.redhat.com/browse/RHEL-79919 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=67194264 Tested: Verified Brew build test kernel RPMs Signed-off-by:
Mamatha Inamdar <minamdar@redhat.com> commit 784354349d2c988590c63a5a001ca37b2a6d4da1 Author: Nayna Jain <nayna@linux.ibm.com> Date: Wed Apr 17 23:12:30 2024 -0400 powerpc/pseries: make max polling consistent for longer H_CALLs Currently, plpks_confirm_object_flushed() function polls for 5msec in total instead of 5sec. Keep max polling time consistent for all the H_CALLs, which take longer than expected, to be 5sec. Also, make use of fsleep() everywhere to insert delay. Reported-by:
Nageswara R Sastry <rnsastry@linux.ibm.com> Fixes: 2454a7af0f2a ("powerpc/pseries: define driver for Platform KeyStore") Signed-off-by:
Nayna Jain <nayna@linux.ibm.com> Tested-by:
Andrew Donnellan <ajd@linux.ibm.com> Signed-off-by:
Michael Ellerman <mpe@ellerman.id.au> Link: https://msgid.link/20240418031230.170954-1-nayna@linux.ibm.com Signed-off-by:
Steve Best <sbest@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6643 JIRA: https://issues.redhat.com/browse/RHEL-83459 Signed-off-by:
Charles Mirabile <cmirabil@redhat.com> Approved-by:
Bastien Nocera <bnocera@redhat.com> Approved-by:
John W. Linville <linville@redhat.com> Approved-by:
-
Augusto Caringi authored
Merge: CVE-2024-57998 kernel: OPP: add index check to assert to avoid buffer overflow in _read_freq() MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6578 ## Summary of Changes Backport upstream `d659bc68ed48` ("OPP: add index check to assert to avoid buffer overflow in \_read\_freq()") to fix CVE-2024-57998, plus a few other patches that prevent conflicts. Note that `b44b9bc7cab2` ("OPP: fix dev\_pm\_opp\_find\_bw\_\*() when bandwidth table not initialized") fixes CVE-2024-58068 and is also included because it's in the same series as `d659bc68ed48`. ## Approved Development Ticket(s) JIRA: https://issues.redhat.com/browse/RHEL-81432 CVE: CVE-2024-57998 JIRA: https://issues.redhat.com/browse/RHEL-84805 CVE: CVE-2024-58068 Signed-off-by:
Jared Kangas <jkangas@redhat.com> Approved-by:
Brian Masney <bmasney@redhat.com> Approved-by:
Radu Rendec <rrendec@redhat.com> Approved-by:
Eric Chanudet <echanude@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6672 JIRA: https://issues.redhat.com/browse/RHEL-72676 Conflicts: Minor merge conflict - no functional change Commits: ``` 388cf16d90f6 90e6f191e1ee 2478d43ed621 ``` Signed-off-by:
Mete Durlu <mdurlu@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6448 JIRA: https://issues.redhat.com/browse/RHEL-81064 CVE: CVE-2024-54456 ``` commit 49fd4e34751e90e6df009b70cd0659dc839e7ca8 Author: Zichen Xie <zichenxie0106@gmail.com> Date: Wed Dec 18 00:13:12 2024 +0800 NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() name is char[64] where the size of clnt->cl_program->name remains unknown. Invoking strcat() directly will also lead to potential buffer overflow. Change them to strscpy() and strncat() to fix potential issues. Signed-off-by:
Zichen Xie <zichenxie0106@gmail.com> Reviewed-by:
Benjamin Coddington <bcodding@redhat.com> Signed-off-by:
Anna Schumaker <anna.schumaker@oracle.com>```> Signed-off-by:
CKI Backport Bot <cki-ci-bot+cki-gitlab-backport-bot@redhat.com> --- <small>Created 2025-02-27 09:10 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:
Olga Kornievskaia <okorniev@redhat.com> Approved-by:
Scott Mayhew <smayhew@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6671 JIRA: https://issues.redhat.com/browse/RHEL-79720 Signed-off-by:
David Arcari <darcari@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6649 JIRA: https://issues.redhat.com/browse/RHEL-79410 Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=67144184 Upstream Status: v6.15.rc1 Tested: Guest can boot with 16GB huge pages and none disk cache mode It's possible a folio's size exceeds 4GB. For example, 16GB huge page is available when the base page size is 64KB. In this case, the offset of a folio can't be held in a 'unsigned int' variable. Otherwise, it causes warning in bio_add_folio_nofail() and IO failure because of overflowing, and eventually leads to guest booting failure when the disk cache mode is none. Pick up upstream commit 26064d3e2b4d ("block: fix adding folio to bio") to fix the issue. Signed-off-by:
Gavin Shan <gshan@redhat.com> Approved-by:
Ming Lei <ming.lei@redhat.com> Approved-by:
Jeff Moyer <jmoyer@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6637 JIRA: https://issues.redhat.com/browse/RHEL-53784 Omitted-fix: e120829dbf92 - this is typically brought in by perf updates Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6597 JIRA: https://issues.redhat.com/browse/RHEL-83537 Hit buildids have been incorrectly stored in perf.data, thus the `perf buildid-list --with-hits` command showed no hashes, which has broken perf-archive. With this fix, it should be working again. Signed-off-by:
Jerome Marchand <jmarchan@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6692 Description: Updates for powerpc rtas scheduling JIRA: https://issues.redhat.com/browse/RHEL-81040 Build Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=67038845 Tested: Verified Brew build test kernel RPMs and confirmed issue is resovled Signed-off-by:
Nathan Lynch <nathanl@linux.ibm.com> Reviewed-by:
Nicholas Piggin <npiggin@gmail.com> Reviewed-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/5378 JIRA: https://issues.redhat.com/browse/RHEL-29207 Patches are required to activate the GNR-D platform. Signed-off-by:
Petr Oros <poros@redhat.com> Signed-off-by:
Michal Schmidt <mschmidt@redhat.com> Approved-by:
José Ignacio Tornos Martínez <jtornosm@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6528 JIRA: https://issues.redhat.com/browse/RHEL-82456 CVE: CVE-2024-58069 ``` commit 3ab8c5ed4f84fa20cd16794fe8dc31f633fbc70c Author: Oleksij Rempel <linux@rempel-privat.de> Date: Wed Dec 18 20:34:58 2024 +0100 rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read The nvmem interface supports variable buffer sizes, while the regmap interface operates with fixed-size storage. If an nvmem client uses a buffer size less than 4 bytes, regmap_read will write out of bounds as it expects the buffer to point at an unsigned int. Fix this by using an intermediary unsigned int to hold the value. Fixes: fadfd092 ("rtc: pcf85063: add nvram support") Signed-off-by:
Oleksij Rempel <o.rempel@pengutronix.de> Signed-off-by:
Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.kernel.org/r/20241218-rtc-pcf85063-stack-corruption-v1-1-12fd0ee0f046@pengutronix.de Signed-off-by:
Alexandre Belloni <alexandre.belloni@bootlin.com>```> Signed-off-by:
Daniel Horak <dhorak@redhat.com> Approved-by:
Lucas Zampieri <lzampier@redhat.com> Approved-by:
Myron Stowe <mstowe@redhat.com> Approved-by:
-
- Apr 10, 2025
-
-
David Arcari authored
JIRA: https://issues.redhat.com/browse/RHEL-53784 commit e1bc02646527fc1ed74f00eb599b2b74d49671c7 Author: K Prateek Nayak <kprateek.nayak@amd.com> Date: Mon Dec 23 04:34:04 2024 +0000 x86/topology: Use x86_sched_itmt_flags for PKG domain unconditionally x86_sched_itmt_flags() returns SD_ASYM_PACKING if ITMT support is enabled by the system. Without ITMT support being enabled, it returns 0 similar to current x86_die_flags() on non-Hybrid systems (!X86_HYBRID_CPU and !X86_FEATURE_AMD_HETEROGENEOUS_CORES) On Intel systems that enable ITMT support, either the MC domain coincides with the PKG domain, or in case of multiple MC groups within a PKG domain, either Sub-NUMA Cluster (SNC) is enabled or the processor features Hybrid core layout (X86_HYBRID_CPU) which leads to three distinct possibilities: o If PKG and MC domains coincide, PKG domain is degenerated by sd_parent_degenerate() when building sched domain topology. o If SNC is enabled, PKG domain is never added since "x86_has_numa_in_package" is set and the topology will instead contain NODE and NUMA domains. o On X86_HYBRID_CPU which contains multiple MC groups within the PKG, the PKG domain requires x86_sched_itmt_flags(). Thus, on Intel systems that contains multiple MC groups within the PKG and enables ITMT support, the PKG domain requires x86_sched_itmt_flags(). In all other cases PKG domain is either never added or is degenerated. Thus, returning x86_sched_itmt_flags() unconditionally at PKG domain on Intel systems should not lead to any functional changes. On AMD systems with multiple LLCs (MC groups) within a PKG domain, enabling ITMT support requires setting SD_ASYM_PACKING to the PKG domain since the core rankings are assigned PKG-wide. Core rankings on AMD processors is currently set by the amd-pstate driver when Preferred Core feature is supported. A subset of systems that support Preferred Core feature can be detected using X86_FEATURE_AMD_HETEROGENEOUS_CORES however, this does not cover all the systems that support Preferred Core ranking. Detecting Preferred Core support on AMD systems requires inspecting CPPC Highest Perf on all present CPUs and checking if it differs on at least one CPU. Previous suggestion to use a synthetic feature to detect Preferred Core support [1] was found to be non-trivial to implement since BSP alone cannot detect if Preferred Core is supported and by the time AP comes up, alternatives are patched and setting a X86_FEATURE_* then is not possible. Since x86 processors enabling ITMT support that consists multiple non-NUMA MC groups within a PKG requires SD_ASYM_PACKING flag set at the PKG domain, return x86_sched_itmt_flags unconditionally for the PKG domain. Since x86_die_flags() would have just returned x86_sched_itmt_flags() after the change, remove the unnecessary wrapper and pass x86_sched_itmt_flags() directly as the flags function. Fixes: f3a052391822 ("cpufreq: amd-pstate: Enable amd-pstate preferred core support") Signed-off-by:
K Prateek Nayak <kprateek.nayak@amd.com> Signed-off-by:
Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by:
Tim Chen <tim.c.chen@linux.intel.com> Link: https://lore.kernel.org/r/20241223043407.1611-6-kprateek.nayak@amd.com Signed-off-by:
-
David Arcari authored
JIRA: https://issues.redhat.com/browse/RHEL-53784 commit 537e247879589f6bace747e3479e4abf42dbbbdc Author: K Prateek Nayak <kprateek.nayak@amd.com> Date: Mon Dec 23 04:34:03 2024 +0000 x86/topology: Remove x86_smt_flags and use cpu_smt_flags directly x86_*_flags() wrappers were introduced with commit d3d37d85 ("x86/sched: Add SD_ASYM_PACKING flags to x86 ITMT CPU") to add x86_sched_itmt_flags() in addition to the default domain flags for SMT and MC domain. commit 995998ebdebd ("x86/sched: Remove SD_ASYM_PACKING from the SMT domain flags") removed the ITMT flags for SMT domain but not the x86_smt_flags() wrappers which directly returns cpu_smt_flags(). Remove x86_smt_flags() and directly use cpu_smt_flags() to derive the flags for SMT domain. No functional changes intended. Signed-off-by:
-
David Arcari authored
JIRA: https://issues.redhat.com/browse/RHEL-53784 Conflicts: RHEL is missing upstream 78eb4ea25cd5 and 83e291d3f596 commit d04013a4b21bd5a4e10c42f71ed1e5e299cacdfe Author: K Prateek Nayak <kprateek.nayak@amd.com> Date: Mon Dec 23 04:34:02 2024 +0000 x86/itmt: Move the "sched_itmt_enabled" sysctl to debugfs "sched_itmt_enabled" was only introduced as a debug toggle for any funky ITMT behavior. Move the sysctl controlled from "/proc/sys/kernel/sched_itmt_enabled" to debugfs at "/sys/kernel/debug/x86/sched_itmt_enabled" with a notable change that a cat on the file will return "Y" or "N" instead of "1" or "0" to indicate that feature is enabled or disabled respectively. Either "0" or "N" (or any string that kstrtobool() interprets as false) can be written to the file will disable the feature, and writing either "1" or "Y" (or any string that kstrtobool() interprets as true) will enable it back when the platform supports ITMT ranking. Since ITMT is x86 specific (and PowerPC uses SD_ASYM_PACKING too), the toggle was moved to "/sys/kernel/debug/x86/" as opposed to "/sys/kernel/debug/sched/" Suggested-by:
-
David Arcari authored
JIRA: https://issues.redhat.com/browse/RHEL-53784 commit b0979e53645825a38f814ca5d3d09aed2745911d Author: Perry Yuan <perry.yuan@amd.com> Date: Fri Oct 25 12:14:57 2024 -0500 x86/cpu: Enable SD_ASYM_PACKING for PKG domain on AMD Enable the SD_ASYM_PACKING domain flag for the PKG domain on AMD heterogeneous processors. This flag is beneficial for processors with one or more CCDs and relies on x86_sched_itmt_flags(). Signed-off-by:
Perry Yuan <perry.yuan@amd.com> Co-developed-by:
Mario Limonciello <mario.limonciello@amd.com> Signed-off-by:
Borislav Petkov (AMD) <bp@alien8.de> Reviewed-by:
Gautham R. Shenoy <gautham.shenoy@amd.com> Link: https://lore.kernel.org/r/20241025171459.1093-4-mario.limonciello@amd.com Signed-off-by:
-
David Arcari authored
JIRA: https://issues.redhat.com/browse/RHEL-53784 commit fc1055d5334f1808e3e445592a83f31624b953f1 Author: K Prateek Nayak <kprateek.nayak@amd.com> Date: Mon Dec 23 04:34:01 2024 +0000 x86/itmt: Use guard() for itmt_update_mutex Use guard() for itmt_update_mutex which avoids the extra mutex_unlock() in the bailout and return paths. Signed-off-by:
-
David Arcari authored
JIRA: https://issues.redhat.com/browse/RHEL-53784 commit 2f6f726bdda5f24227de10bc599038e0ca0d65f4 Author: K Prateek Nayak <kprateek.nayak@amd.com> Date: Mon Dec 23 04:34:00 2024 +0000 x86/itmt: Convert "sysctl_sched_itmt_enabled" to boolean In preparation to move "sysctl_sched_itmt_enabled" to debugfs, convert the unsigned int to bool since debugfs readily exposes boolean fops primitives (debugfs_read_file_bool, debugfs_write_file_bool) which can streamline the conversion. Since the current ctl_table initializes extra1 and extra2 to SYSCTL_ZERO and SYSCTL_ONE respectively, the value of "sysctl_sched_itmt_enabled" can only be 0 or 1 and this datatype conversion should not cause any functional changes. Signed-off-by:
-
- Apr 07, 2025
-
-
Mamatha Inamdar authored
JIRA: https://issues.redhat.com/browse/RHEL-81040 commit 6c606e57eecc37d6b36d732b1ff7e55b7dc32dd4 Author: Nathan Lynch <nathanl@linux.ibm.com> Date: Fri Nov 18 09:07:42 2022 -0600 powerpc/rtas: avoid scheduling in rtas_os_term() It's unsafe to use rtas_busy_delay() to handle a busy status from the ibm,os-term RTAS function in rtas_os_term(): Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b BUG: sleeping function called from invalid context at arch/powerpc/kernel/rtas.c:618 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1, name: swapper/0 preempt_count: 2, expected: 0 CPU: 7 PID: 1 Comm: swapper/0 Tainted: G D 6.0.0-rc5-02182-gf8553a572277-dirty #9 Call Trace: [c000000007b8f000] [c000000001337110] dump_stack_lvl+0xb4/0x110 (unreliable) [c000000007b8f040] [c0000000002440e4] __might_resched+0x394/0x3c0 [c000000007b8f0e0] [c00000000004f680] rtas_busy_delay+0x120/0x1b0 [c000000007b8f100] [c000000000052d04] rtas_os_term+0xb8/0xf4 [c000000007b8f180] [c0000000001150fc] pseries_panic+0x50/0x68 [c000000007b8f1f0] [c000000000036354] ppc_panic_platform_handler+0x34/0x50 [c000000007b8f210] [c0000000002303c4] notifier_call_chain+0xd4/0x1c0 [c000000007b8f2b0] [c0000000002306cc] atomic_notifier_call_chain+0xac/0x1c0 [c000000007b8f2f0] [c0000000001d62b8] panic+0x228/0x4d0 [c000000007b8f390] [c0000000001e573c] do_exit+0x140c/0x1420 [c000000007b8f480] [c0000000001e586c] make_task_dead+0xdc/0x200 Use rtas_busy_delay_time() instead, which signals without side effects whether to attempt the ibm,os-term RTAS call again. Signed-off-by:
-
- Apr 04, 2025
-
-
Augusto Caringi authored
Signed-off-by: -
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6619 JIRA: https://issues.redhat.com/browse/RHEL-47428 Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6584 JIRA: https://issues.redhat.com/browse/RHEL-83272 Upstream Status: RHEL only Ensure that init_rh_check_status gets called by removing the blacklisted optimization in our kernels. Signed-off-by:
Tomas Henzl <thenzl@redhat.com> Approved-by:
Herton R. Krzesinski <herton@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6580 JIRA: https://issues.redhat.com/browse/RHEL-79409 we don't backport "block: Fix potential deadlock while freezing queue and acquiring sysfs_lock Omitted-Fix: 224749be6c23 ("block: Revert "block: Fix potential deadlock while freezing queue and acquiring sysfs_lock"") Omitted-Fix: 2fa07d7a0f00 ("btrfs: pass write-hint for buffered IO") Omitted-Fix: e559ee022658 ("btrfs: validate queue limits") Omitted-Fix: 7467bc5959bf ("btrfs: zoned: calculate max_extent_size properly on non-zoned setup") Omitted-Fix: c7c97ceff98c ("btrfs: handle bio_split() errors") Signed-off-by:
Ewan D. Milne <emilne@redhat.com> Approved-by:
Maurizio Lombardi <mlombard@redhat.com> Approved-by:
Vitaly Kuznetsov <vkuznets@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6512 nfsd: clear acl_access/acl_default after releasing them JIRA: https://issues.redhat.com/browse/RHEL-81523 CVE: CVE-2025-21796 Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6638 Backport huge pfnmap support for significantly faster large mmap'd PCI device BARs JIRA: https://issues.redhat.com/browse/RHEL-73613 Mapping and unmapping PCI BARs into VM va-space is a common VFIO function when assigning a PCIe device to a VM. Currently, the mapping requires setting up the BAR-mappings at a native pagesize level, e.g., 4K on x86, 64K possible on ARM64. This is done using PFNMAP support in the kernel, as these device pages are not backed by the standard page-struct that system memory is mapped under. For relatively small to medium sized BARs, the mapping performance isn't too noticeable; but with vGPUs and BARs in the gigabyte-size ranges, the map time can become a signficant amount of the VM startup time (minutes). Upstream resolved this issue by providing huge PFNMAP support -- superpage PFNMAPs; 2MB, and even 1GB(on x86) pages vs 4K page mappings yields three to ten orders of magnitude speed up in the mapping operation, which is quite visible to the VM user of assigned GPUs in the guest VM. This series backports the core of what upstream did: https://lore.kernel.org/all/20240826204353.2228736-1-peterx@redhat.com/ along with a couple of prior upstream commits which allow these to apply cleanly to RHEL9, as well as a couple bug fixes that patchreview identified, and one related commit the kernel-mm team requested. The code can be tested by doing the following (thanks to AlexW for providing this info): # echo "func vfio_pci_mmap_huge_fault +p" > /proc/dynamic_debug/control Then you'll see things in dmesg like: vfio-pci 0000:5e:00.0: vfio_pci_mmap_huge_fault(,order = 9) BAR 0 page offset 0x0: 0x100 vfio-pci 0000:5e:00.0: vfio_pci_mmap_huge_fault(,order = 9) BAR 0 page offset 0x200: 0x100 vfio-pci 0000:5e:00.0: vfio_pci_mmap_huge_fault(,order = 9) BAR 0 page offset 0x400: 0x100 Here we know order 9 is a 2MB PMD mapping on x86. BAR0 on this device is 16MB, so 2MB mappings is the best we can get. If you have a device with at least a 1GB BAR, you should also see: vfio-pci 0000:5e:00.0: vfio_pci_mmap_huge_fault(,order = 18) BAR 1 page offset 0x240000: 0x100 vfio-pci 0000:5e:00.0: vfio_pci_mmap_huge_fault(,order = 18) BAR 1 page offset 0x280000: 0x100 vfio-pci 0000:5e:00.0: vfio_pci_mmap_huge_fault(,order = 18) BAR 1 page offset 0x2c0000: 0x100 Again here we know order 18 is 1GB PUD mappings and BAR1 of this device is 32GB (NVIDIA A10). You'll need to be running at least QEMU 9.2 to get reliable alignment for PUD mappings (which neither RHEL-9 or RHEL-10 has atm; they have QEMU-9.1) If you see order = 0 mappings for BARs that are at least 2MB, something is wrong. Omitted-fix: 722376934b6c ("mm/memory.c: simplify pfnmap_lockdep_assert") Signed-off-by:
Donald Dutile <ddutile@redhat.com> Approved-by:
Alex Williamson <alex.williamson@redhat.com> Approved-by:
David Hildenbrand <david@redhat.com> Merged-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6574 JIRA: https://issues.redhat.com/browse/RHEL-82298 Brew: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=67019166 Upstream Status: v6.14.rc7 Tested: Passed. kselftests, kvm-unit-tests, virt-install and live migration (4KB/64KB) This series picks up the following fixes, which are no later than v6.14.rc7 and the previous revisions. Note that any features, enhancements and their followup fixes are ignored. 3855a7b91d42 KVM: arm64: Initialize SCTLR_EL1 in __kvm_hyp_init_cpu() 7a68b55ff39b KVM: arm64: Initialize HCR_EL2.E2H early afa9b48f327c KVM: arm64: Shave a few bytes from the EL2 idmap code fa808ed4e199 KVM: arm64: Ensure a VMID is allocated before programming VTTBR_EL2 102c51c50db8 KVM: arm64: Fix tcr_el2 initialisation in hVHE mode b3aa9283c0c5 KVM: arm64: vgic: Hoist SGI/PPI alloc from vgic_init() to kvm_create_vgic() e6e3e0022ef8 KVM: arm64: timer: Drop warning on failed interrupt signalling b938731ed2d4 KVM: arm64: Fix alignment of kvm_hyp_memcache allocations 332b7e6d62b7 KVM: arm64: Simplify warning in kvm_arch_vcpu_load_fp() b450dcce93bc KVM: arm64: timer: Always evaluate the need for a soft timer 5417a2e9b130 KVM: arm64: Fix nested S2 MMU structures reallocation 32392e04cb50 KVM: arm64: Fail protected mode init if no vgic hardware is present 59419f10045b KVM: arm64: Eagerly switch ZCR_EL{1,2} f9dd00de1e53 KVM: arm64: Mark some header functions as inline 9b66195063c5 KVM: arm64: Refactor exit handlers 407a99c4654e KVM: arm64: Remove VHE host restore of CPACR_EL1.SMEN 459f059be702 KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN 8eca7f6d5100 KVM: arm64: Remove host FPSIMD saving for non-protected KVM d4db98791aa5 KVM: arm64: Add predicate for FPMR support in a VM 9bcbb6104a34 KVM: arm64: Flush hyp bss section after initialization of variables in bss 9fb4267a759c KVM: arm64: Fix selftests after sysreg field name update a7f1fa5564be KVM: arm64: Explicitly handle BRBE traps as UNDEFINED dea8838128c5 KVM: arm64: vgic: Use str_enabled_disabled() in vgic_v3_probe() 68344037b764 KVM: arm64: Fix nVHE stacktrace VA bits mask b7f345fbc32a KVM: arm64: Fix FEAT_MTE in pKVM e891432cf717 KVM: arm64: nv: Advertise the lack of AArch32 EL0 support 1eccad35c926 KVM: arm64: Fix the value of the CPTR_EL2 RES1 bitmask for nVHE 2fd5b4b0e7b4 KVM: arm64: Calculate cptr_el2 traps on activating traps 9df9186f8df5 KVM: arm64: Fix RAS trapping in pKVM for protected VMs 8ca19c40c47d KVM: arm64: Drop MDSCR_EL1_DEBUG_MASK 9d86c3c97434 arm64/kvm: Avoid invalid physical addresses to signal owner updates f0da16992aef arm64/kvm: Configure HYP TCR.PS/DS based on host stage1 d3ba35b69eae KVM: arm64: nv: Reload PMU events upon MDCR_EL2.HPME change adf8623b3f51 KVM: arm64: Use KVM_REQ_RELOAD_PMU to handle PMCR_EL0.E change e22c369520d0 KVM: arm64: Add unified helper for reprogramming counters by mask 985bb51f17ab KVM: arm64: Always check the state from hyp_ack_unshare() Changes in v4: Improved commit logs for the following upstream commits (Eric) d3ba35b69eae KVM: arm64: nv: Reload PMU events upon MDCR_EL2.HPME change 59419f10045b KVM: arm64: Eagerly switch ZCR_EL{1,2} Added the following upstream commit, as dependency to upstream commit 7a68b55ff39b and 3855a7b91d42 (Eric) afa9b48f327c KVM: arm64: Shave a few bytes from the EL2 idmap code Changes in v3: 7 upstream commits added per Eric's comments to include 59419f10045b. All other commits are dependencies. 59419f10045b KVM: arm64: Eagerly switch ZCR_EL{1,2} f9dd00de1e53 KVM: arm64: Mark some header functions as inline 9b66195063c5 KVM: arm64: Refactor exit handlers 407a99c4654e KVM: arm64: Remove VHE host restore of CPACR_EL1.SMEN 459f059be702 KVM: arm64: Remove VHE host restore of CPACR_EL1.ZEN 8eca7f6d5100 KVM: arm64: Remove host FPSIMD saving for non-protected KVM d4db98791aa5 KVM: arm64: Add predicate for FPMR support in a VM Changes in v2: 3 upstream commmits added per Eric's comments 1eccad35c926 KVM: arm64: Fix the value of the CPTR_EL2 RES1 bitmask for nVHE 2fd5b4b0e7b4 KVM: arm64: Calculate cptr_el2 traps on activating traps 9df9186f8df5 KVM: arm64: Fix RAS trapping in pKVM for protected VMs 59419f10045b skipped due to too many dependencies Signed-off-by:
Shaoqin Huang <shahuang@redhat.com> Approved-by:
Eric Auger <eric.auger@redhat.com> Approved-by:
Cornelia Huck <cohuck@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6662 ## Summary of Changes Backport `22cf4fae6660` ("soc: qcom: socinfo: Avoid out of bounds read of serial number") to fix CVE-2024-58007, as well as a couple of additional commits to prevent conflicts. ## Approved Development Ticket(s) JIRA: https://issues.redhat.com/browse/RHEL-85597 CVE: CVE-2024-58007 Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6661 JIRA: https://issues.redhat.com/browse/RHEL-85565 Backport [mm fix](https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f66da89d31c ) to report nr_free_pages accurately on boot when DEFERRED_STRUCT_PAGE_INIT is used. Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6660 JIRA: https://issues.redhat.com/browse/RHEL-85522 JIRA: https://issues.redhat.com/browse/RHEL-45063 Signed-off-by:
Lenny Szubowicz <lszubowi@redhat.com> Approved-by:
Mark Langsdorf <mlangsdo@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6405 JIRA: https://issues.redhat.com/browse/RHEL-23495 Update /proc/schedstat with fixes and improved information from upstream. AMD requested these and they don't carry a large risk. Signed-off-by:
Phil Auld <pauld@redhat.com> Approved-by:
Juri Lelli <juri.lelli@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6628 Description: ============ This patch set updates the RDMA core and RDMA ULPs to upstream kernel v6.14. Upstream: ========= Linus's master tree. Issues: ======= JIRA: https://issues.redhat.com/browse/RHEL-78087 Brew: ===== https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=67075815 Testing: ======== https://beaker.engineering.redhat.com/jobs/10846162 https://beaker.engineering.redhat.com/jobs/10846163 https://beaker.engineering.redhat.com/jobs/10846165 https://beaker.engineering.redhat.com/jobs/10846166 https://beaker.engineering.redhat.com/jobs/10846167 https://beaker.engineering.redhat.com/jobs/10846168 https://beaker.engineering.redhat.com/jobs/10846170 Signed-off-by:
Kamal Heib <kheib@redhat.com> Approved-by:
Ivan Vecera <ivecera@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6499 JIRA: https://issues.redhat.com/browse/RHEL-81522 CVE: CVE-2025-21726 MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6499 This MR backports the 3-patch series that includes the fix to CVE-2025-21726 as well as two other minor cleanup and fix patches. Signed-off-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6626 JIRA: https://issues.redhat.com/browse/RHEL-69649 JIRA: https://issues.redhat.com/browse/RHEL-83224 CVE: CVE-2025-21864 Backport of upstream commit 9b6412e6979f ("tcp: drop secpath at the same time as we currently drop dst"). Signed-off-by:
Sabrina Dubroca <sdubroca@redhat.com> Approved-by:
Florian Westphal <fwestpha@redhat.com> Approved-by:
Antoine Tenart <atenart@redhat.com> Approved-by:
-
Augusto Caringi authored
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/6657 JIRA: https://issues.redhat.com/browse/RHEL-85517 Omitted-Fix: e120829dbf92 - this will be brought in during perf update Signed-off-by:
-
- Apr 03, 2025
-
-
Li Wang authored
JIRA: https://issues.redhat.com/browse/RHEL-85318 commit 983e760bcdb6f41ff3cf59e70e32a529537d6ef2 Author: Li Wang <liwang@redhat.com> Date: Thu Mar 27 19:48:13 2025 +0800 selftest/mm: va_high_addr_switch: add ppc64 support check Add PPC64 Radix MMU support to the va_high_addr_switch.sh by introducing check_supported_ppc64(). The function verifies: - 5-level paging (PGTABLE_LEVELS >= 5) enable in kernel config - Radix MMU (required for PPC64 5-level translation) - HugePages availability (needed for some tests) If any check fails, the test is skipped (ksft_skip). This ensures compatibility with Power9/Power10 systems running in Radix MMU mode. Avoid failures on 4-level paging system: # mmap(NULL, MAP_HUGETLB): 0xffffffffffffffff - FAILED # mmap(LOW_ADDR, MAP_HUGETLB): 0xffffffffffffffff - FAILED # mmap(HIGH_ADDR, MAP_HUGETLB): 0xffffffffffffffff - FAILED # mmap(HIGH_ADDR, MAP_HUGETLB) again: 0xffffffffffffffff - FAILED # mmap(HIGH_ADDR, MAP_FIXED | MAP_HUGETLB): 0xffffffffffffffff - FAILED # mmap(-1, MAP_HUGETLB): 0xffffffffffffffff - FAILED # mmap(-1, MAP_HUGETLB) again: 0xffffffffffffffff - FAILED # mmap(ADDR_SWITCH_HINT - PAGE_SIZE, 2*HUGETLB_SIZE, MAP_HUGETLB): 0xffffffffffffffff - FAILED # mmap(ADDR_SWITCH_HINT , 2*HUGETLB_SIZE, MAP_FIXED | MAP_HUGETLB): 0xffffffffffffffff - FAILED Link: https://lkml.kernel.org/r/20250327114813.25980-1-liwang@redhat.com Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
-
Li Wang authored
JIRA: https://issues.redhat.com/browse/RHEL-85318 commit 85e8bcb4190efb0b4443b637fd7a62ca2f05de6f Author: Dev Jain <dev.jain@arm.com> Date: Wed May 22 12:34:34 2024 +0530 selftests/mm: va_high_addr_switch: reduce test noise Patch series "Restructure va_high_addr_switch". The va_high_addr_switch memory selftest tests out some corner cases related to allocation and page/hugepage faulting around the switch boundary. Currently, the page size and hugepage size have been statically defined. Post FEAT_LPA2, the Aarch64 Linux kernel adds support for 4k and 16k translation granules on higher addresses; we restructure the test to support the same. In addition, we avoid invocation of the binary twice, in the shell script, to reduce test noise. This patch (of 2): When invoking the binary with "--run-hugetlb" flag, the testcases involving the base page are anyways going to be run. Therefore, remove duplication by invoking the binary only once. Link: https://lkml.kernel.org/r/20240522070435.773918-1-dev.jain@arm.com Link: https://lkml.kernel.org/r/20240522070435.773918-2-dev.jain@arm.com Signed-off-by:
Dev Jain <dev.jain@arm.com> Cc: Anshuman Khandual <anshuman.khandual@arm.com> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Cc: Shuah Khan <shuah@kernel.org> Signed-off-by:
-
