CloudLinux runtime kernel update for ARM growth difficulties
summary
Shows exactly how KernelCare no-reboot live patches work: allocate kernel memory, freeze processes, swap patched functions and resume, with evidence of success on x86 and partial, brittle porting to ARM. Explains tooling and scale: AWS parallel compilation plus Python orchestration, per-kernel gcc toolchains, a custom hcc/genesis pipeline, and handling 42 ARM relocations including newer R_ARM_CALL26 fallout. Presents measured slowdowns (emulation ×3–4), freeze retries and corner cases, and which fixes actually make ARM updates reliable.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:09Why is live patching required
- 5:04How patch created
- 18:21Patch inside
- 20:38How runtime patching works
- 27:33Toolchan: Relocations
- 28:52Toolchain: Load address
- 30:37Toolchain: Load value
- 31:36Toolchain: Section anchors
- 37:54ARM infrastructure problems
related talks
39mLet's meet the kernel livepatch feature
18mKernel Live Patching: Mitigating CVEs With Zero Downtime
50mProtected KVM on Arm64: A Technical Deep Dive
26mArm64 Linux Kernel Architecture update
49mGeneric System for Safe Rootfs/Kernel Upgrades without Single-Point of Failure
41mKernel Live Patching at Scale
38mUnveiling Arm Confidential Computing Architecture Software Stack
36mStatus of Embedded Linux