diff options
| author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2023-08-21 11:44:40 -0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-08-22 15:13:54 +0100 |
| commit | 0dba974a145c312a16cd72e9604afb0d5b087411 (patch) | |
| tree | 1359bed27186d004c5801cef7348151006a9dd08 /scripts/lib/scriptutils.py | |
| parent | 5e8e48567c253e50e41c856c586651f36af270d0 (diff) | |
| download | poky-0dba974a145c312a16cd72e9604afb0d5b087411.tar.gz | |
linux-yocto/6.1: fix uninitialized read in nohz_full/isolcpus setup
Integrating the following commit(s) to linux-yocto/6.1:
4675ec8d0b9a kernel/sched: Fix uninitialized read in nohz_full/isolcpus setup
The carry forward of commit from the v5.15 linux-yocto kernel:
https://git.yoctoproject.org/linux-yocto/commit/?id=97c96388922
...in which case the sanity checks are properly *after* the allocation
and processing of the bootargs into the cpumask.
However, it seems patch (or wiggle?) apparently decided to put the
sanity checks *before* the population of the cpumask during the
carry-forward and generation of the new v6.1 kernel. Meaning they are
validating uninitialized memory and hence nohz_full= and isolcpus= are
subject to random failures even for valid input ranges.
(From OE-Core rev: 4b349ee66eab8ebe3150ac4c1b449ea5c264a5be)
(From OE-Core rev: 92642acd1166b7990fb520337b78a4d37ce7cbe4)
Signed-off-by: Adrian Cinal <adriancinal1@gmail.com>
Acked-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/scriptutils.py')
0 files changed, 0 insertions, 0 deletions