[rocky8_10] History rebuild for kernel-4.18.0-553.56.1.el8_10 #345

PlaidCat · 2025-06-18T18:29:02Z

General Process:

Download all unprocessed src.rpm
for each src,pm
- Find all commits in changelog up to last known tag ... in this case 4.18.0-553
- Re-play commits in revese order (oldest in change log to newest) with git cherry-pick
- After replay replace ENTIRE code in branch with rpmbuild -bp from corresponding src.rpm.
- Tag Rebuild branch
Do local build with https://github.com/ctrliq/kernel-src-tree/wiki/Kernel-Make,-KABI,-Install,-and-Reboot-script

Checking Rebuild Commits for Potentially missing commits:

kernel-4.18.0-553.56.1.el8_10

Rebuild_History BUILDABLE
Rebuilding Kernel from rpm changelog with Fuzz Limit: 87.50%
Number of commits in upstream range v4.18~1..kernel-mainline: 553283
Number of commits in rpm: 9
Number of commits matched with upstream: 3 (33.33%)
Number of commits in upstream but not in rpm: 553280
Number of commits NOT found in upstream: 6 (66.67%)

Rebuilding Kernel on Branch rocky8_10_rebuild_kernel-4.18.0-553.56.1.el8_10 for kernel-4.18.0-553.56.1.el8_10
Clean Cherry Picks: 2 (66.67%)
Empty Cherry Picks: 1 (33.33%)
_______________________________

__EMPTY COMMITS__________________________
af98d8a36a963e758e84266d152b92c7b51d4ecb sched/fair: Fix CPU bandwidth limit bypass during CPU hotplug

__CHANGES NOT IN UPSTREAM________________
Adding prod certs and changed cert date to 20210620
Adding Rocky secure boot certs
Fixing vmlinuz removal
Fixing UEFI CA path
Porting to 8.10, debranding and Rocky branding
Fixing pesign_key_name values

Build

[jmaple@devbox code]$ egrep -B 5 -A 5 "\[TIMER\]|^Starting Build" kbuild.resf_kernel-4.18.0-553.56.1.el8_10.log
/mnt/code/kernel-src-tree-build
no .config file found, moving on
[TIMER]{MRPROPER}: 0s
x86_64 architecture detected, copying config
'configs/kernel-x86_64.config' -> '.config'
Setting Local Version for build
CONFIG_LOCALVERSION="-rocky8_10_rebuild-1ad2baf0efe1"
Making olddefconfig
--
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf  --olddefconfig Kconfig
#
# configuration written to .config
#
Starting Build
scripts/kconfig/conf  --syncconfig Kconfig
  SYSTBL  arch/x86/include/generated/asm/syscalls_32.h
  SYSHDR  arch/x86/include/generated/asm/unistd_32_ia32.h
  SYSHDR  arch/x86/include/generated/asm/unistd_64_x32.h
  SYSTBL  arch/x86/include/generated/asm/syscalls_64.h
--
  LD [M]  sound/usb/usx2y/snd-usb-usx2y.ko
  LD [M]  sound/virtio/virtio_snd.ko
  LD [M]  sound/x86/snd-hdmi-lpe-audio.ko
  LD [M]  sound/xen/snd_xen_front.ko
  LD [M]  virt/lib/irqbypass.ko
[TIMER]{BUILD}: 1593s
Making Modules
  INSTALL arch/x86/crypto/blowfish-x86_64.ko
  INSTALL arch/x86/crypto/camellia-aesni-avx-x86_64.ko
  INSTALL arch/x86/crypto/camellia-aesni-avx2.ko
  INSTALL arch/x86/crypto/camellia-x86_64.ko
--
  INSTALL sound/virtio/virtio_snd.ko
  INSTALL sound/x86/snd-hdmi-lpe-audio.ko
  INSTALL sound/xen/snd_xen_front.ko
  INSTALL virt/lib/irqbypass.ko
  DEPMOD  4.18.0-rocky8_10_rebuild-1ad2baf0efe1+
[TIMER]{MODULES}: 14s
Making Install
sh ./arch/x86/boot/install.sh 4.18.0-rocky8_10_rebuild-1ad2baf0efe1+ arch/x86/boot/bzImage \
	System.map "/boot"
[TIMER]{INSTALL}: 21s
Checking kABI
Checking kABI
kABI check passed
Setting Default Kernel to /boot/vmlinuz-4.18.0-rocky8_10_rebuild-1ad2baf0efe1+ and Index to 3
Hopefully Grub2.0 took everything ... rebooting after time metrices
[TIMER]{MRPROPER}: 0s
[TIMER]{BUILD}: 1593s
[TIMER]{MODULES}: 14s
[TIMER]{INSTALL}: 21s
[TIMER]{TOTAL} 1635s
Rebooting in 10 seconds

KSelftest

[jmaple@devbox code]$ ls ~/workspace/vms/r8-sigcloud/builder/code/kselftest.4.18.0-rocky8_10_rebuild-6f9106f46020+.log kselftest.4.18.0-rocky8_10_rebuild-1ad2baf0efe1+.log | while read line; do echo $line; grep '^ok ' $line | wc -l; done
/home/jmaple/workspace/vms/r8-sigcloud/builder/code/kselftest.4.18.0-rocky8_10_rebuild-6f9106f46020+.log
205
kselftest.4.18.0-rocky8_10_rebuild-1ad2baf0efe1+.log
206

jira LE-3255 Rebuild_History Non-Buildable kernel-4.18.0-553.56.1.el8_10 commit-author Vishal Chourasia <[email protected]> commit af98d8a Empty-Commit: Cherry-Pick Conflicts during history rebuild. Will be included in final tarball splat. Ref for failed cherry-pick at: ciq/ciq_backports/kernel-4.18.0-553.56.1.el8_10/af98d8a3.failed CPU controller limits are not properly enforced during CPU hotplug operations, particularly during CPU offline. When a CPU goes offline, throttled processes are unintentionally being unthrottled across all CPUs in the system, allowing them to exceed their assigned quota limits. Consider below for an example, Assigning 6.25% bandwidth limit to a cgroup in a 8 CPU system, where, workload is running 8 threads for 20 seconds at 100% CPU utilization, expected (user+sys) time = 10 seconds. $ cat /sys/fs/cgroup/test/cpu.max 50000 100000 $ ./ebizzy -t 8 -S 20 // non-hotplug case real 20.00 s user 10.81 s // intended behaviour sys 0.00 s $ ./ebizzy -t 8 -S 20 // hotplug case real 20.00 s user 14.43 s // Workload is able to run for 14 secs sys 0.00 s // when it should have only run for 10 secs During CPU hotplug, scheduler domains are rebuilt and cpu_attach_domain is called for every active CPU to update the root domain. That ends up calling rq_offline_fair which un-throttles any throttled hierarchies. Unthrottling should only occur for the CPU being hotplugged to allow its throttled processes to become runnable and get migrated to other CPUs. With current patch applied, $ ./ebizzy -t 8 -S 20 // hotplug case real 21.00 s user 10.16 s // intended behaviour sys 0.00 s This also has another symptom, when a CPU goes offline, and if the cfs_rq is not in throttled state and the runtime_remaining still had plenty remaining, it gets reset to 1 here, causing the runtime_remaining of cfs_rq to be quickly depleted. Note: hotplug operation (online, offline) was performed in while(1) loop v3: https://lore.kernel.org/all/[email protected] v2: https://lore.kernel.org/all/[email protected] v1: https://lore.kernel.org/all/[email protected] Suggested-by: Zhang Qiao <[email protected]> Signed-off-by: Vishal Chourasia <[email protected]> Signed-off-by: Peter Zijlstra (Intel) <[email protected]> Acked-by: Vincent Guittot <[email protected]> Tested-by: Madadi Vineeth Reddy <[email protected]> Tested-by: Samir Mulani <[email protected]> Link: https://lore.kernel.org/r/[email protected] (cherry picked from commit af98d8a) Signed-off-by: Jonathan Maple <[email protected]> # Conflicts: # kernel/sched/fair.c

jira LE-3255 cve CVE-2022-49395 Rebuild_History Non-Buildable kernel-4.18.0-553.56.1.el8_10 commit-author Vincent Whitchurch <[email protected]> commit 2a4a62a syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes. ================================================================== BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0 Read of size 128 at addr 000000006411f6f0 by task swapper/1 CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18 Call Trace: show_stack.cold+0x166/0x2a7 __dump_stack+0x3a/0x43 dump_stack_lvl+0x1f/0x27 print_report.cold+0xdb/0xf81 kasan_report+0x119/0x1f0 kasan_check_range+0x3a3/0x440 memcpy+0x52/0x140 syscall_stub_data+0x70/0xe0 write_ldt_entry+0xac/0x190 init_new_ldt+0x515/0x960 init_new_context+0x2c4/0x4d0 mm_init.constprop.0+0x5ed/0x760 mm_alloc+0x118/0x170 0x60033f48 do_one_initcall+0x1d7/0x860 0x60003e7b kernel_init+0x6e/0x3d4 new_thread_handler+0x1e7/0x2c0 The buggy address belongs to stack of task swapper/1 and is located at offset 64 in frame: init_new_ldt+0x0/0x960 This frame has 2 objects: [32, 40) 'addr' [64, 80) 'desc' ================================================================== Fixes: 858259c ("uml: maintain own LDT entries") Signed-off-by: Vincent Whitchurch <[email protected]> Cc: [email protected] Signed-off-by: Richard Weinberger <[email protected]> (cherry picked from commit 2a4a62a) Signed-off-by: Jonathan Maple <[email protected]>

jira LE-3255 Rebuild_History Non-Buildable kernel-4.18.0-553.56.1.el8_10 commit-author Borislav Petkov <[email protected]> commit fe0a578 ... and stop poking at the MSR directly. Signed-off-by: Borislav Petkov <[email protected]> Link: https://lkml.kernel.org/r/[email protected] (cherry picked from commit fe0a578) Signed-off-by: Jonathan Maple <[email protected]>

Rebuild_History BUILDABLE Rebuilding Kernel from rpm changelog with Fuzz Limit: 87.50% Number of commits in upstream range v4.18~1..kernel-mainline: 553283 Number of commits in rpm: 9 Number of commits matched with upstream: 3 (33.33%) Number of commits in upstream but not in rpm: 553280 Number of commits NOT found in upstream: 6 (66.67%) Rebuilding Kernel on Branch rocky8_10_rebuild_kernel-4.18.0-553.56.1.el8_10 for kernel-4.18.0-553.56.1.el8_10 Clean Cherry Picks: 2 (66.67%) Empty Cherry Picks: 1 (33.33%) _______________________________ Full Details Located here: ciq/ciq_backports/kernel-4.18.0-553.56.1.el8_10/rebuild.details.txt Includes: * git commit header above * Empty Commits with upstream SHA * RPM ChangeLog Entries that could not be matched Individual Empty Commit failures contained in the same containing directory. The git message for empty commits will have the path for the failed commit. File names are the first 8 characters of the upstream SHA

bmastbergen

🥌

jdieter

PlaidCat added 4 commits June 18, 2025 12:53

PlaidCat requested review from jdieter, juphoff, kerneltoast, bmastbergen and thefossguy-ciq June 18, 2025 18:29

PlaidCat self-assigned this Jun 18, 2025

bmastbergen approved these changes Jun 18, 2025

View reviewed changes

jdieter approved these changes Jun 19, 2025

View reviewed changes

PlaidCat merged commit 1ad2baf into rocky8_10 Jun 19, 2025
2 checks passed

PlaidCat deleted the rocky8_10_rebuild branch June 19, 2025 14:16

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[rocky8_10] History rebuild for kernel-4.18.0-553.56.1.el8_10 #345

[rocky8_10] History rebuild for kernel-4.18.0-553.56.1.el8_10 #345

Uh oh!

PlaidCat commented Jun 18, 2025

Uh oh!

bmastbergen left a comment

Uh oh!

jdieter left a comment

Uh oh!

Uh oh!

Uh oh!

[rocky8_10] History rebuild for kernel-4.18.0-553.56.1.el8_10 #345

[rocky8_10] History rebuild for kernel-4.18.0-553.56.1.el8_10 #345

Uh oh!

Conversation

PlaidCat commented Jun 18, 2025

Checking Rebuild Commits for Potentially missing commits:

kernel-4.18.0-553.56.1.el8_10

Build

KSelftest

Uh oh!

bmastbergen left a comment

Choose a reason for hiding this comment

Uh oh!

jdieter left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!