diff options
author | Bruce Ashfield <bruce.ashfield@gmail.com> | 2023-08-21 11:44:41 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-08-22 15:13:54 +0100 |
commit | d65e9aa75604d5ce88131f908bfd8b130a08d859 (patch) | |
tree | 175a23e237d7b189a012a73b76674d055e6bab43 /scripts/lib/recipetool/create.py | |
parent | 0dba974a145c312a16cd72e9604afb0d5b087411 (diff) | |
download | poky-d65e9aa75604d5ce88131f908bfd8b130a08d859.tar.gz |
linux-yocto/6.4: fix uninitialized read in nohz_full/isolcpus setup
Integrating the following commit(s) to linux-yocto/6.4:
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: b3a71c7d36e3a4833e90728499e08543257042a1)
(From OE-Core rev: bb5865b10316754213711551fa68a53a4fb741d9)
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/recipetool/create.py')
0 files changed, 0 insertions, 0 deletions