APPLIED: [SRU][jammy:linux][PATCH 0/1] Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols

Roxana Nicolescu roxana.nicolescu at canonical.com
Fri Jul 7 12:29:07 UTC 2023


On 18/05/2023 17:55, John Cabaj wrote:
> BugLink: https://bugs.launchpad.net/bugs/2003374
>
> [Impact]
> * When UBSAN is enabled in an s390x kernel configuration, kpatch-build can fail to find matching symbols in the vmlinux symbol table. This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels.
> * UBSAN was disabled in the Jammy 5.15 s390x kernel configuration to resolve the issue
> * Upstream kpatch recently resolved the issue via https://github.com/dynup/kpatch/pull/1332/commits/85344cf524cccc7b8e10bf04ed38a0f586bffd10, so this patch re-enables UBSAN for Jammy 5.15 s390x kernel configuration.
>
> [Fix]
> * Simple config change
>
> [Test Case]
> * Used kpatch-build v0.9.8 to build and load a fs/proc/meminfo.c Livepatch on s390x kernel successfully
>
> [Where problems could occur]
> * Should not introduce any regressions as functionality was enabled since original Jammy 5.15 kernel until v5.15.0-70.77
>
> John Cabaj (1):
>    UBUNTU: [Config] s390x: Re-adding UBSAN to configuration
>
>   debian.master/config/annotations | 26 +++++++++++++-------------
>   1 file changed, 13 insertions(+), 13 deletions(-)
>
>
Applied to jammy:master-next. Thanks!

Roxana



More information about the kernel-team mailing list