| 2023-01-19 20:23:17 |
John Cabaj |
bug |
|
|
added bug |
| 2023-01-19 20:23:17 |
John Cabaj |
attachment added |
|
kpatch-build console output https://bugs.launchpad.net/bugs/2003374/+attachment/5642592/+files/output.log |
|
| 2023-01-19 20:23:54 |
John Cabaj |
attachment added |
|
kpatch-build log file https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/2003374/+attachment/5642593/+files/build.log |
|
| 2023-01-19 20:24:40 |
John Cabaj |
attachment added |
|
Example Livepatch that causes issues with UBSAN https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/2003374/+attachment/5642594/+files/example_livepatch.patch |
|
| 2023-01-19 21:45:38 |
John Cabaj |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-01-19 21:45:38 |
John Cabaj |
bug task added |
|
kpatch (Ubuntu Kinetic) |
|
| 2023-01-19 21:45:38 |
John Cabaj |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-01-19 21:45:38 |
John Cabaj |
bug task added |
|
kpatch (Ubuntu Jammy) |
|
| 2023-01-20 03:44:54 |
John Cabaj |
description |
[ 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, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log).
* Disabling UBAAN in s390x kernel configurations resolved the issue for Jammy 5.15. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality.
[ Test Plan ]
* Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel. This should be successful.
[ Where problems could occur ]
* A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. |
[ 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, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log).
* Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality.
[ Test Plan ]
* Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel. This should be successful.
[ Where problems could occur ]
* A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. |
|
| 2023-01-20 03:46:45 |
John Cabaj |
description |
[ 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, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log).
* Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality.
[ Test Plan ]
* Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel. This should be successful.
[ Where problems could occur ]
* A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. |
[ Impact ]
* When UBSAN is enabled in an s390x kernel configuration, kpatch-build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log).
* Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality.
[ Test Plan ]
* Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful.
[ Where problems could occur ]
* A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. |
|
| 2023-02-08 17:29:38 |
John Cabaj |
kpatch (Ubuntu Jammy): assignee |
|
John Cabaj (john-cabaj) |
|
| 2023-02-15 10:16:13 |
Dimitri John Ledkov |
bug task added |
|
ubuntu-z-systems |
|
| 2023-02-15 10:39:34 |
Frank Heimes |
tags |
|
s390x |
|
| 2023-02-15 16:49:38 |
bugproxy |
tags |
s390x |
architecture-s39064 bugnameltc-201635 s390x severity-high targetmilestone-inin--- |
|
| 2023-02-21 17:03:44 |
Frank Heimes |
bug watch added |
|
https://github.com/dynup/kpatch/issues/1328 |
|
| 2023-02-21 17:03:44 |
Frank Heimes |
bug task added |
|
dh-kpatches |
|
| 2023-02-21 18:22:57 |
John Cabaj |
kpatch (Ubuntu Jammy): assignee |
John Cabaj (john-cabaj) |
|
|
| 2023-02-21 18:44:49 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2023-03-09 17:59:28 |
Frank Heimes |
ubuntu-z-systems: status |
New |
In Progress |
|
| 2023-03-09 17:59:34 |
Frank Heimes |
kpatch (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-03-09 17:59:43 |
Frank Heimes |
kpatch (Ubuntu): status |
New |
In Progress |
|
| 2023-03-09 18:11:24 |
John Cabaj |
bug task added |
|
linux (Ubuntu) |
|
| 2023-03-09 18:11:55 |
John Cabaj |
bug task deleted |
linux (Ubuntu Kinetic) |
|
|
| 2023-03-09 18:30:09 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2023-03-09 18:30:11 |
Ubuntu Kernel Bot |
linux (Ubuntu Jammy): status |
New |
Incomplete |
|
| 2023-07-07 13:36:12 |
Roxana Nicolescu |
linux (Ubuntu Jammy): status |
Incomplete |
Fix Committed |
|
| 2023-07-13 08:42:14 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 s390x severity-high targetmilestone-inin--- |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux s390x severity-high targetmilestone-inin--- verification-needed-jammy |
|
| 2023-07-28 16:31:48 |
John Cabaj |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-07-28 16:32:04 |
John Cabaj |
linux (Ubuntu Jammy): status |
Fix Released |
Fix Committed |
|
| 2023-07-28 16:32:19 |
John Cabaj |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux s390x severity-high targetmilestone-inin--- verification-needed-jammy |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux s390x severity-high targetmilestone-inin--- verification-done-jammy verification-needed-jammy |
|
| 2023-07-28 16:33:20 |
John Cabaj |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux s390x severity-high targetmilestone-inin--- verification-done-jammy verification-needed-jammy |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux s390x severity-high targetmilestone-inin--- verification-done-jammy |
|
| 2023-07-28 19:16:32 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2023-08-08 16:00:48 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux s390x severity-high targetmilestone-inin--- verification-done-jammy |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-jammy |
|
| 2023-08-08 16:01:37 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-jammy |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy |
|
| 2023-08-08 16:01:39 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy |
|
| 2023-08-10 18:01:21 |
Utkarsh Gupta |
kpatch (Ubuntu Kinetic): status |
New |
Won't Fix |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2022-48502 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-0597 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-2124 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3090 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-31248 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3141 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3389 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3390 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3439 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-35001 |
|
| 2023-08-22 18:56:57 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy verification-needed-jammy-linux-aws |
|
| 2023-08-26 20:11:49 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy verification-needed-jammy-linux-aws |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure |
|
| 2023-09-09 14:17:34 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure |
|
| 2023-10-03 20:41:45 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-xilinx-zynqmp |
|
| 2024-02-09 11:00:00 |
bugproxy |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 s390x severity-high targetmilestone-inin--- verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-xilinx-zynqmp |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 s390x severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-xilinx-zynqmp |
|
| 2024-03-01 06:18:23 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 s390x severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-xilinx-zynqmp |
architecture-s39064 bugnameltc-201635 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 s390x severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-mtk verification-needed-jammy-linux-xilinx-zynqmp |
|
| 2024-03-01 07:18:37 |
Frank Heimes |
description |
[ Impact ]
* When UBSAN is enabled in an s390x kernel configuration, kpatch-build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log).
* Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality.
[ Test Plan ]
* Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful.
[ Where problems could occur ]
* A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. |
[ Impact ]
* When UBSAN is enabled in an s390x kernel configuration, kpatch-build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log).
* Disabling UBSAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality.
[ Test Plan ]
* Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful.
[ Where problems could occur ]
* A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. |
|
