Kernel livepatch support for for s390x

Bug #1639924 reported by Frank Heimes
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
High
bugproxy
gcc-11 (Ubuntu)
Fix Released
Medium
Unassigned
Jammy
Fix Released
Medium
Unassigned
Kinetic
Fix Released
Medium
Unassigned
kpatch (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
Kinetic
Invalid
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Medium
Unassigned
Kinetic
Fix Released
Medium
Unassigned

Bug Description

[ Impact ]

 * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels.

 * This SRU is to enable s390x builds of kpatch on kinetic & jammy.

 * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches.

[ Test Plan ]

 * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on:

 - amd64 jammy v5.15
 - amd64 & s390x jammy v5.19
 - amd64 & s390x kinetic v5.19

[ Where problems could occur ]

 * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains.

 * This is a fairly large upstream update to the tooling.

 * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot-module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required.

Additional command line options added '--oot-module-src, -R|--non-replace'.

'--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'.

kpatch-cc utility is added, which is a toolchain wrapper.

Thus adjustments might be needed to scripts used to invoke and create kpatch modules.

 * Majority of non-test/non-doc changes are to do with:
   - add support for s390x and 32bit powerpc
   - add support for newer kernels and compilers (support & bugfixes to various sections and symbols)
   - more strict checking and bugfixes w.r.t. livepatch generation
   - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups.

* Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels.

$ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-build/ > shortlog.txt

d46fea98ef kpatch-build: strengthen conditions for changed sections
9fac261ed0 kpatch-build: rela section could disappear after patched
fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules
8cc0fedefb kpatch-build: use err.h instead of error.h for musl support
07433e98c0 kpatch-cc: fix stripping of source tree prefix
33368a88cd create-diff-object: add support for .return_sites section (x86)
e921c557f9 macros: tweak syscall patching macros
a1171b112e create-diff-object: Create missing section symbol
0308d52bcd kpatch/s390: Enable kpatch build support
b0330ab18e kpatch/s390: Add additional bundled symbols.
eb4a85f778 kpatch/s390: Add exclusion lists
f0d00a9290 kpatch/s390: Add initial support for kpatch
10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch
c6d0b5450b lookup: fix symtab parsing
52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le()
017015a725 create-diff-object: make kpatch_check_relocations() more precise
f0e3da336c create-diff-object: fix string extraction
86d5208b46 create-diff-object: error on symbol conversion failure
325bccd89d create-diff-object: skip conversion for sections which never have symbols
8508abd3b1 create-diff-object: allow converstion of empty symbols
8d5a628bde create-diff-object: add extra check for symbol conversion edge case
01427d50a1 create-diff-object: move addend math to a new function
bec6488af6 create-diff-object: add rela_insn() error check
6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec'
bf212f7750 create-diff-object: error on unsupported rela in symbol conversion
3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms()
79f45d1b0a create-diff-object: fix kpatch_replace_sections_syms() for non-text
61e46094b5 create-diff-object: convert function return types to 'bool'
c24d135f40 create-diff-object: rename "sec" -> "relasec" for rela sections
3b63456817 kpatch-elf: convert functions to static
0c5a1e7753 kpatch-build: make xtrace output less verbose
2784f5056b kpatch-build: add support for openEuler
3392049665 kpatch-build: remove duplicated use_klp_arch
e9c0b67862 macros: add syscall patching macros
c2e73c2cbc create-diff-object: ensure debug sections don't use dynrelas
305ff8a5d8 create-diff-object: include .LCx string literal symbols
b700732f5d create-diff-object: add "_printk" to the __LINE__ detection
79fd60b28d create-diff-object: check arg2 and arg3 on all arches for line detection
f7b27f2fec kpatch-build: Increase name length limit to 55 chars
e6b1664d0e create-diff-object.c: add s390 support for __LINE__ detection
a6920b9381 create-diff-object: fix endian issues in insn_is_load_immediate()
1152e58244 create-diff-object: support __LINE__ detection for btrfs macros
fea0192104 kpatch-build: Allow setting kernel version if --sourcedir and --vmlinux are used
af672577b3 create-diff-object: use toc_rela() in kpatch_line_macro_change_only()
81296117f4 create-diff-object: unify kpatch_line_macro_change_only()
4ba6f1fbc9 create-diff-object: include __dyndbg section when referenced by jump table
8d81cc8517 kpatch-elf: symtab_shndx support
4d8c8102de Fix sym->type condition in locals_match()
4c0e4898d9 create-diff-object: detect architecture from input ELF file
394a907a37 create-diff-object: move kpatch_find_func_profiling_calls definition
0decc79d0b kpatch-build: introduce ability to ignore distro-specific checks
fd0457b9f3 kpatch-build: add cross-compilation support
c4286ee2cb create-diff-object: add support for .retpoline_sites section
9ee9f7a3ec kpatch-build: Add missing allocation failure checks
bdc43561e9 kpatch-build: combine find_special_section_data() variants
34fcfd4d56 kpatch-build: source kernel .config instead of grepping
89a871fff9 Fix oot-module builds
aa85922ec6 Do not unset KBUILD_EXTRA_SYMBOLS
4a7dab17c8 Allow OOT modules to be built with non-distro kernels
6c4c8c0a2d create-diff-object: update for __already_done
f5175a402b kpatch-build: save environment varibles to file
6673c693d6 kmod/patch: clean only rebuildable objs
607ee53e1e livepatch-patch-hook: add comments
4f51ee7fa3 create-diff-object: support ppc64le relative jump labels
cb23c601f6 kpatch-build: Handle error in create-klp-module
ef0ce9715a create-diff-object: fix use after free in kpatch-check-relocations()
70b8fe8f95 kpatch-build: Do not check KLP_REPLACE for kpatch.ko-based patches
eaaced1912 add openEuler build support
99542e864e create-diff-object: rename arguments in most correlate/compare functions
22e16619e0 create-diff-object: base->orig renames
e2b50d7b66 create-diff-object: make locals_match() and maybe_discarded_sym() return bool
720768767d Switch to per-file lookup table pointers.
db442d1405 Make lookup_symbol() accept struct symbol as an argument
56471ffc7c kpatch-build: Support CONFIG_PRINTK_INDEX, part 2
6cf50a6fca create-diff-object: Support CONFIG_PRINTK_INDEX, part 1
ea0470baa7 create-diff-object: change kpatch_line_macro_change_only() return type to bool
a02668a0f7 kmod: remove redundant -mcmodel=large on ppc64le
624e5e3b82 kmod: pass CFLAGS_MODULE to module build
5622e3cc3d Make sure section symbols exist
a26b2af2a3 kpatch-build: set EXTRAVERSION and not localversion for RH kernels
ba3defa060 create-diff-object: Check that the section has a secsym
17dcebf077 kpatch-build: enable klp with replace option by default
d9f49e850a kpatch-build: drop klp.arch support in RHEL-8.4
81f9ca4833 create-diff-object: Fix out-of-range relocation check
fa5a95cafd create-diff-object: Fix out-of-range relocation error message
7be75549ba kpatch-build: add support for static calls
6d466fa76f kpatch-build: drop klp.arch support in RHEL-8.4
f9d2ec1d77 kpatch-build: fix kernel_is_rhel() for rhel-8 z-stream kernels
1b5a17f934 create-build-diff: support for .cold functions with no id suffix
fc4a56f6b2 kpatch-build: check existance of Makefile.modfinal
4cc2f06279 kpatch-build: workaround pahole and CONFIG_DEBUG_INFO_BTF_MODULES
6c83b642a4 create-diff-object: make digit tail optional in kpatch_mengled_strcmp
b6e1d071ff create-diff-object: consider '.L' symbols not static local
fddc6242c6 create-diff-object: support both gcc and clang style of static variables
38c2d7315d create-diff-object: clang __UNIQUE_ID symbol support
488f30c31b create-diff-object: .L.str* symbols support
41de9e763a kpatch-build: clang support
f951c1a92e kpatch-build: apply 'cp -f ... || die' pattern
e25450f5a8 kpatch-build: workaround pahole and CONFIG_DEBUG_INFO_BTF
387914b683 kpatch-gcc: powerpc - skip vdso files
04021bbfd5 kmod/patch: add kpatch.lds as a dependency for $(KPATCH_NAME).o
b8d4611edb kmod: convert __section to __kpatch_section
aea2cb96d6 create-diff-object: fix __dyndbg section inclusion
ef420050e3 kpatch-elf: pass new ELF output file mode to kpatch_write_output_elf()
25f12681fa create-diff-object: cleanup maybe-uninitialized compiler complaints
08056febfd kpatch-build: Check Final module symbols for loadability
e9600c5513 kpatch-build: Check exported symbol version changes
b4c2753684 kpatch-build: Create module symbol version file once
b311112702 deal with the deadlock may occur in stop_machine context.
6531a7e075 kpatch-build: avoid modpost .output.o.cmd complaints
ea647e50ae kpatch-build/Makefile: Fail build on unsupported architectures
17ec03ef95 Keep build.log on --skip-cleanup
ed849a9b3e create-diff-object: Ignore changes to .altinstr_aux
abd2ff81c7 create-diff-object: change rela_equal() to return bool
514acc32e9 create-diff-object: improve jump label warnings
b381a0cc0b lookup: Add __UNIQUE_ID_ to maybe_discarded_sym list
67aa131137 gcc-plugin: GCC 10 - update local/non local insn names
92c42039bf gcc-plugin: abort building klp module on error
fde1a75b7f gcc-plugin: Fix build failure with GCC 10
b958ed601c create-diff-object: Add ppc64le mcount support
9bb75659e2 kpatch-build: Detect R_X86_64_64 dynrelas with large addends
15067fcd64 kmod/core: apply dynrela addend for R_X86_64_64
c1caee1468 create-diff-object: Ignore kpatch_ignored functions/sections missing ftrace hook
1991ff0018 create-diff-object: add support for .klp.arch removal
3982b329bc kpatch-build: drop support for old non-.klp.arch kernels
e80562a8cb kpatch-build: add kpatch.ko deprecation warning
d97de8d554 kpatch-build: readability cleanups
4e0db559c1 lookup: fix Module.symvers reading for newer kernels
89e8574027 create-diff-object: show all jump labels before reporting failure
0a3e6c5f42 create-diff-object: refactor dynrela conversion
d2089a4d72 create-diff-object: rename lookup 'result' -> 'symbol'
ae9f1c17b1 lookup: add duplicate symbol checks
3064cf3c60 lookup: add 'objname' to lookup table and lookup results
7e1f2b0e07 lookup: convert lookup functions to return bool
6cc03f9599 lookup: rename 'pos' to 'sympos'
cd121422d9 lookup: rename 'value' -> 'addr'
5fad6599a4 lookup: remove unused testing code
e4d37dad5d lookup: Skip .dynsym table in symtab_read()
7e48138185 lookup: Simplify first loop in symtab_read()
74c9c99931 create-diff-object: reduce indentation in kpatch_create_patches_sections()
b548ba153f kpatch-build: Look for local static variables in child functions
42128ff78c kpatch-build: Include .part. symbols as child function
b502e5b1cc kpatch-build: Allow function to have multiple child functions
af1fe267c5 create-diff-object: Avoid unnecessary parent symbol inclusion
fbfc8f9bec create-diff-object: Handle ppc64le toc with only constants
687e2caabc create-diff-object: Don't strip callback section symbols
37e950a653 create-kpatch-module: Fix -Wconversion warnings
ea9e708df0 create-klp-module: Fix -Wconversion warnings
f67c2ebce0 kpatch-elf: Fix -Wconversion warnings
5f68db22e5 create-diff-object: Fix -Wconversion warnings
a0c608de70 kpatch-build/Makefile: Skip build insn/plugin with -Wconversion
4e4a8d99da kpatch-build: add -Wconversion/-Wno-sign-conversion CFLAGS
f5f5479614 create-diff-object: fix relocations used for ZERO_PAGE(0)
61c55d9e52 kpatch-build: replace all '-' to '_' in KOBJFILE_NAME
68530e4c2b kpatch-build: Make local static twining stricter
19baa5b7c7 create-diff-object: process debug sections last
852bad5e8d create-diff-object: Use new helpers for static local correlation
e49e3a59c2 create-diff-object: Rename elements getting correlated
49a9adaf74 create-diff-object: Correlate objects related to a section at once
770f529225 kpatch-elf: Ensure stale references are not used
3a1a73f08c Make symvers reading code more flexible.
a02842fb69 kpatch-elf: Free sections in elf teardown
935f199875 create-diff-object: simplify mangled function correlation
e9755413ed kpatch-build: use whole word filename matching in find_parent_obj()
878bac379f create-diff-object: Simplify relocation processing
bd4fae25f9 create-diff-object: Add const to unmodified rela_insn arguments
50476c94cc create-diff-object: Check ELF headers earlier
2499eb2bdc Revert "create-diff-object: Check for *_fixup sections changes"
aabdf9c9c9 Fix parent matches for kernels newer than 5.3
ed5091b16f kpatch-build: Check if /etc/os-release exists
e4525ce311 kpatch-build: sanity check patched filenames
36120b9b08 kmod/patch: check for RHEL8 when setting HAVE_SIMPLE_ENABLE
e187de3fe4 kpatch-build: update core file error message

 * This will be a potentially disruptive SRU, however it is required to introduce building livepatches for the LTS v5.15 GA kernel on s390x, and to continue support building kpatches on an LTS release for the hwe based kernels. Kinetic update is required to not regress support for kpatch building upon upgrades (even though that's not provided by canonical).

[ Other Info ]

 * Anything else you think is useful to include
 * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
 * and address these questions in advance

CVE References

Frank Heimes (fheimes)
description: updated
tags: added: s390x
Revision history for this message
Frank Heimes (fheimes) wrote :

Dear Kernel team - any opinion on that ?

Changed in ubuntu-z-systems:
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
Revision history for this message
Ben Romer (bromer) wrote :

No, unfortunately kpatch-build doesn't work on s390 or ARM due to incompatibility with the stack backtrace code in the kernel, and potentially has other issues beyond that. Could you let me know where you saw that other platforms were supported?

Revision history for this message
Frank Heimes (fheimes) wrote :

Yeah, what I meant was that the live-patch kernel-parts should work on all architectures, but probably not the kpatch-build tooling - in deed.
I read a bit about it at some common information sources, like https://lwn.net/Articles/663858/

But I mainly opened this because of an ongoing conversation between Dustin and Eberhard Pasch (from the Linux on s390x / z performance team at IBM) - Leann and Martin Schwidefsky (sub-system maintainer for s390x) got involved into this thread, too.

"
For the kernel patching - I [Eberhard] talked to Martin Schwidefsky (the s390x
maintainer) before he left for the kernel summit. Livepatch should
work upstream. And it's working in one of the competitive distros [probably SUSE].
If something is broken upstream, we'd like to know as it needs fixing then.
When we implemented it, we had quite some performance troubles with
the additional space we needed at the beginning of every function
and the code around that. But that should been fixed as well.
"

According to your statement about the incompatibility with the stack backtrace code and potentially some other things, it looks like IBM has to have a deeper look at it ...

Can we start to work with IBM to get the remaining issues solved based on this ticket ?
I may ask IBM to reverse proxy this ticket back to their internal bugzilla system ...

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
importance: Undecided → High
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
assignee: Canonical Kernel Team (canonical-kernel-team) → bugproxy (bugproxy)
Frank Heimes (fheimes)
tags: added: reverse-proxy-bugzilla
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
Revision history for this message
Frank Heimes (fheimes) wrote :

Waiting for an update from IBM - setting to Incomplete for now.

Changed in ubuntu-z-systems:
status: Triaged → Incomplete
Revision history for this message
Frank Heimes (fheimes) wrote :

Here is an update about the ongoing upstream discussion and patches:
https://github.com/dynup/kpatch/pull/1203 (https://github.com/dynup/kpatch/pull/1203/commits)

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Incomplete → Triaged
Revision history for this message
Frank Heimes (fheimes) wrote (last edit ):

Like found in 'doc/s390-upstream-prerequisites.md' as part of:
https://github.com/dynup/kpatch/pull/1203/commits/48d997f2a39c9151670b254570679b24d40abb7d
I checked the status of following kernel commits upstream and in jammy master-next:

**Prerequisite kernel patches:**
**v5.19:**
- 69505e3d9a39 bug: Use normal relative pointers in 'struct bug_entry'
==> upstream since v5.19-rc1, so not in jammy (but part of kinetic's target kernel 5.19)

**v5.18:**
- 602bf1687e6f s390/nospec: align and size extern thunks
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- 1d2ad084800e s390/nospec: add an option to use thunk-extern
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- eed38cd2f46f s390/nospec: generate single register thunks if possible
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- 2268169c14e5 s390: remove unused expoline to BC instructions
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)
- f0003a9e4c18 s390/entry: remove unused expoline thunk
==> upstream since v5.18, so not in jammy (but part of kinetic's target kernel 5.19)

**v5.16:**
- torvalds/linux@f6ac18f sched: Improve try_invoke_on_locked_down_task()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@9b3c4ab sched,rcu: Rework try_invoke_on_locked_down_task()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@00619f7 sched,livepatch: Use task_call_func()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@8850cb6 sched: Simplify wake_up_*idle*()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@5de62ea sched,livepatch: Use wake_up_if_idle()
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)
- torvalds/linux@96611c2 sched: Improve wake_up_all_idle_cpus() take #2
==> upstream since v5.16, so not in jammy (but part of kinetic's target kernel 5.19)

**v5.15**
- torvalds/linux@de5012b s390/ftrace: implement hotpatching
==> upstream since v5.15, hence included in jammy (and kinetic)
- torvalds/linux@67ccddf ftrace: Introduce ftrace_need_init_nop()
==> upstream since v5.15, hence included in jammy (and kinetic)

**v5.14:**
- torvalds/linux@7561c14 s390/vdso: add .got.plt in vdso linker script
==> upstream since v5.14, hence included in jammy (and kinetic)

I've also found add. discussions and references about:
"livepatch: Kick idle cpu's tasks to perform transition"
and
"s390/nospec: build expoline.o for modules_prepare target"
"s390/nospec: remove unneeded header includes"
But one of them are upstream - are they required, too?

Frank Heimes (fheimes)
summary: - kpatch-build not available for s390x
+ kernel livepatch not available for s390x
description: updated
Revision history for this message
Frank Heimes (fheimes) wrote (last edit ): Re: kernel livepatch not available for s390x

For the gcc bits I've created:
https://warthogs.atlassian.net/browse/FR-2554

But based on file 'doc/s390-upstream-prerequisites.md' as part of:
https://github.com/dynup/kpatch/pull/1203/commits/48d997f2a39c9151670b254570679b24d40abb7d
"
**Prerequisite gcc patches (all backported to releases/gcc-11 branch):**
- gcc-mirror/gcc@a1c1b7a IBM Z: Define NO_PROFILE_COUNTERS
- gcc-mirror/gcc@0990d93 IBM Z: Use @PLT symbols for local functions in 64-bit mode
- gcc-mirror/gcc@935b522 S/390: New option -mpic-data-is-text-relative
- gcc-mirror/gcc@8753b13 IBM Z: fix section type conflict with -mindirect-branch-table
"
I think it looks quite good for gcc 11.

Revision history for this message
Frank Heimes (fheimes) wrote :

For the kpatch-build patches/commits
(according to https://github.com/dynup/kpatch/pull/1203/commits):
c6d0b54 "lookup: fix symtab parsing"
10002f5 "kpatch/s390: Add gcc prerequisite flags for kpatch"
f0d00a9 "kpatch/s390: Add initial support for kpatch"
eb4a85f "kpatch/s390: Add exclusion lists"
b0330ab "kpatch/s390: Add additional bundled symbols."
0308d52 "kpatch/s390: Enable kpatch build support"
48d997f "README: Update s390 as supported and backporting info"

==> all 7 commits are accepted in kpatch (master),
    but are not yet version tagged (will be > v0.9.6)
    (notice that we are on kpatch level 0.8.0 for jammy and kinetic)

Revision history for this message
Frank Heimes (fheimes) wrote :

Uhhh, according to the changelog of the Ubuntu kpatch package (esp. entry ‘0.8.0-0ubuntu7’) I just noticed that gcc-9 (!) is still needed and used to build kpatch:

Revert the last change, and build explicitly with GCC 9.
kpatch 0.8 is not ready for GCC 10. There is 0.9.2 ...

Revision history for this message
Matthias Klose (doko) wrote :

I have checked that everything needed for GCC 11 is already in 20.04 LTS.

Revision history for this message
Frank Heimes (fheimes) wrote :

Many thx for checking @doko (wow already in 20.04)

I'm updating the affected gcc entry here to Fix Released and to mark it as done.

Changed in gcc-11 (Ubuntu):
status: New → Fix Released
importance: Undecided → Medium
Changed in gcc-11 (Ubuntu Jammy):
status: New → Fix Released
importance: Undecided → Medium
Revision history for this message
Frank Heimes (fheimes) wrote :

Got some more details about kpatch on s390x (and the gcc dependencies) from Sumanth Korikkar:

"
1. kpatch-tools doesn't have those gcc compiler dependencies. Hence, other gcc compiler version should be able to ideally build it.
2. All gcc patches mentioned in PR 1203 are necessary to build both kernel and kpatch livepatching modules.
kernel and kpatch livepatch modules should be built with same compiler version (recommended).

Also note CONFIG_EXPOLINE_EXTERN should be enabled when building the kernel.

Also, note, it would be necessary to also include expoline.o in kernel-devel package to build OOT modules.
1. See https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1756 [ Fedora]
2. c4e789572557 ("s390/nospec: build expoline.o for modules_prepare target") in kernel
"

Revision history for this message
Frank Heimes (fheimes) wrote :

A quick update on the kernel patches:
69505e3d9a39 "bug: Use normal relative pointers in 'struct bug_entry'" is upstream with v5.19-rc1
c4e789572557 "s390/nospec: build expoline.o for modules_prepare target" is upstream with v5.19-rc7
and
a0b0987a7811 "s390/nospec: remove unneeded header includes" is also upstream with v5.19-rc7
(even if it's just a cleanup)
and "livepatch: Kick idle cpu's tasks to perform transition" was an rfc for an issue that was fixed by torvalds/linux@5de62ea "sched,livepatch: Use wake_up_if_idle()" (thx bzolnier for the info)

With that everything related to the kernel itself is in 5.19 (5.19-rc7 upstream)
and since there is already a 5.19(.0.9.9) in kinetic-proposed:
linux-generic | 5.19.0.9.9 | kinetic-proposed | s390x
I'm going to update the status of the affected kinetic kernel entry to Fix Committed (even if the 5.19.0.9.9 will not be the final 5.19 for kinetic).

Changed in linux (Ubuntu Kinetic):
status: New → Fix Committed
Frank Heimes (fheimes)
information type: Private → Public
Frank Heimes (fheimes)
summary: - kernel livepatch not available for s390x
+ Kernel livepatch support for for s390x
Revision history for this message
Frank Heimes (fheimes) wrote :

The minimal patch set for the jammy master-next kernel I've used is:

3d79d0079cae sched: Improve try_invoke_on_locked_down_task()
914f948c313a sched,rcu: Rework try_invoke_on_locked_down_task()
702fa42757b0 sched,livepatch: Use task_call_func()
5516e7085fca sched: Simplify wake_up_*idle*()
86db6bfb3dc8 sched,livepatch: Use wake_up_if_idle()
6fe095210f38 sched: Improve wake_up_all_idle_cpus() take #2
4168d69c57d1 s390/entry: remove unused expoline thunk
a73c3438e6f2 s390: remove unused expoline to BC instructions
1e3807c786b1 s390/nospec: generate single register thunks if possible
[ 0378d08bd3c3 s390/nospec: add an option to use thunk-extern ]
==> 0010-s390-nospec-add-an-option-to-use-thunk-extern.patch
a7f928d3ef3a s390/nospec: align and size extern thunks
298b3cbf7d0e bug: Use normal relative pointers in 'struct bug_entry'
[ 0013 - 816b355fa9ed s390/nospec: build expoline.o for modules_prepare target ]
==> 0013-s390-nospec-build-expoline.o-for-modules_prepare-tar.patch
==> 0014-Set-y-as-default-for-new-CONFIG_EXPOLINE_EXTERN-kern.patch

The two backports and the kernel option patch are attached.

Revision history for this message
Frank Heimes (fheimes) wrote :

The PR is attached here.

Notice the build (in PPA) succeeds either with having:
0014-Set-y-as-default-for-new-CONFIG_EXPOLINE_EXTERN-kern.patch
NOT included,
or with having zfs DKMS disabled
(either having the entire zfs related line removed from debian/dkms-versions
 or just the "arch=s390x" parameter).
Otherwise the build seems to fails for me with an zfs issue.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Config and Packaging of kinetic:linux-unstable and kinetic:linux are incomplete.

Changed in linux (Ubuntu Kinetic):
status: Fix Committed → In Progress
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

The feature in question must first be fully enabled in kinetic, with kinetic tooling, and kinetic kernels. To ensure that it all works correctly end to end, before embarking on backports attempts. As there is risk of going through rounds of backports, only to find out that they are incomplete.

Submitted a missing kernel change for kinetic now - see https://lists.ubuntu.com/archives/kernel-team/2022-September/133076.html

That too, will be needed as part of jammy backports.

Now will try to figure out the missing pieces for kpatch-tools in kinetic.

Revision history for this message
Frank Heimes (fheimes) wrote :

Everything regarding kernel is incl. in linux-generic 5.19.0-17.17 (meanwhile overruled by 5.19.0.18.18) and is with that in kinetic-proposed, hence updating the status to Fix Committed - for kinetic.

Changed in linux (Ubuntu Kinetic):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (18.6 KiB)

This bug was fixed in the package linux - 5.19.0-18.18

---------------
linux (5.19.0-18.18) kinetic; urgency=medium

  * kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)

  * 5.19.0-17.17: kernel NULL pointer dereference, address: 0000000000000084
    (LP: #1990236)
    - Revert "UBUNTU: SAUCE: apparmor: Fix regression in stacking due to label
      flags"
    - Revert "UBUNTU: [Config] disable SECURITY_APPARMOR_RESTRICT_USERNS"
    - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - add an internal buffer""
    - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - don't wait on cleanup""
    - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - don't waste entropy""
    - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - always add a pending
      request""
    - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - unregister device before
      reset""
    - Revert "UBUNTU: SAUCE: Revert "virtio-rng: make device ready before making
      request""
    - Revert "UBUNTU: [Config] update configs after apply new apparmor patch set"
    - Revert "UBUNTU: SAUCE: apparmor: add user namespace creation mediation"
    - Revert "UBUNTU: SAUCE: selinux: Implement userns_create hook"
    - Revert "UBUNTU: SAUCE: bpf-lsm: Make bpf_lsm_userns_create() sleepable"
    - Revert "UBUNTU: SAUCE: security, lsm: Introduce security_create_user_ns()"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: AppArmor: Remove the exclusive
      flag"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Add /proc attr entry for full
      LSM context"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Removed scaffolding function
      lsmcontext_init"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: netlabel: Use a struct lsmblob in
      audit data"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Add record for multiple
      object contexts"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: audit: multiple subject lsm values
      for netlabel"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Add record for multiple task
      security contexts"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Allow multiple records in an
      audit_buffer"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Add a function to report
      multiple LSMs"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Create audit_stamp
      structure"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Keep multiple LSM data in
      audit_names"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: security_secid_to_secctx
      module selection"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: binder: Pass LSM identifier for
      confirmation"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: NET: Store LSM netlabel data in a
      lsmblob"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: security_secid_to_secctx in
      netlink netfilter"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmcontext in
      security_dentry_init_security"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmcontext in
      security_inode_getsecctx"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmcontext in
      security_secid_to_secctx"
    - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM:...

Changed in linux (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Triaged → In Progress
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-01-18 08:14 EDT-------
According to the effort, this can only be on a wishlist, till priority will change.
Set target to 18.04 for revalidation.

------- Comment From <email address hidden> 2018-03-05 05:09 EDT-------
This Feature is currently flagged with Low Prio.
Set to Ubuntu 19.04 for revalidation.

------- Comment From <email address hidden> 2018-12-11 05:26 EDT-------
This feature request will not make it into 19.04/19.10. Need to be prioritized within the overall plan.... Therefore change for the time beeing to 20.04.

------- Comment From <email address hidden> 2019-11-15 04:14 EDT-------
This feature will not make it into 20.04 -> need to be postponend, at least to 20.10....

------- Comment From <email address hidden> 2020-07-09 05:08 EDT-------
Feature request moved to 21.04, will not make it into 20.10 timeframe.
The function need to be implemented within the kpatch package for s390x...

------- Comment From <email address hidden> 2021-03-10 08:40 EDT-------
Feature will not make it into 21.10 , moved to 22.04

------- Comment From <email address hidden> 2022-06-08 08:58 EDT-------
* The kpatch pull request that Sumanth had submitted quite a while ago has now finally been agreed to by the maintainer (after thorough tests and modifications).

This is the relevant pull request:
https://github.com/dynup/kpatch/pull/1203

tags: added: architecture-s39064 bugnameltc-148869 severity-high targetmilestone-inin2204
Revision history for this message
Frank Heimes (fheimes) wrote :

Thx for the update about the PR, Boris!

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
Download full text (3.6 KiB)

This bug was fixed in the package kpatch - 0.9.7-1
Sponsored for Ben Romer (bromer)

---------------
kpatch (0.9.7-1) experimental; urgency=medium

  * Upload to Debian experimental, it's not perfect, but better than
    current situation.

 -- Dimitri John Ledkov <email address hidden> Fri, 21 Oct 2022 14:42:04 +0100

kpatch (0.9.7-0ubuntu1) devel; urgency=medium

  [ Benjamin M Romer ]
  * Upgrade to latest release
  * The following patches were updated and carried forward
     - shellcheck.patch
     - kpatch-build-adjust-dirs.patch
     - use-debian-rules-for-ubuntu.patch
     - ubuntu-kernel-variants.patch
     - add ignore-lubsan-sections.patch

  [ Dimitri John Ledkov ]
  * Trim trailing whitespace.
  * Bump debhelper from old 10 to 13.
  * Set debhelper-compat version in Build-Depends.
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
    Repository-Browse.
  * Add debian/watch file, using github.
  * Add pahole depends on kpatch-build
  * Drop linux-header Depends from kpatch, packages in the archive must
    not depend on linux-headers, as it cannot know which ones are needed
    for any given kernel.
  * Update homepage URL to https
  * Do not install upstart job
  * Drop include-binaries stanzas, source packages must not include
    pre-built binaries.
  * Bump standards version
  * Drop unused VERSION variable from debian/rules
  * Delete embeded .git repository

 -- Dimitri John Ledkov <email address hidden> Fri, 21 Oct 2022 14:07:12 +0100

kpatch (0.8.0-0ubuntu8) impish; urgency=medium

  * Depend on python3-dev instead of python2-dev, c.f.:
    github.com/dynup/kpatch/commit/4df66fa15f95c86946050ae969658c17caebc0d2

 -- Lukas Märdian <email address hidden> Tue, 11 May 2021 16:03:30 +0200

kpatch (0.8.0-0ubuntu7) hirsute; urgency=medium

  * Revert the last change, and build explicitly with GCC 9.
    kpatch 0.8 is not ready for GCC 10. There is 0.9.2 ...

 -- Matthias Klose <email address hidden> Thu, 17 Dec 2020 13:00:04 +0100

kpatch (0.8.0-0ubuntu5) hirsute; urgency=medium

  * Build using gcc-10-plugin-dev.

 -- Matthias Klose <email address hidden> Thu, 17 Dec 2020 12:50:48 +0100

kpatch (0.8.0-0ubuntu4) hirsute; urgency=medium

  * Merge packaging fixes from 0.6.0-0.2 0.6.0-0.1 and 0.3.2-3.1

 -- Gianfranco Costamagna <email address hidden> Fri, 11 Dec 2020 16:03:59 +0100

kpatch (0.8.0-0ubuntu3) hirsute; urgency=medium

  * Drop dh-systemd runtime dependency with debhelper >=10

 -- Gianfranco Costamagna <email address hidden> Fri, 11 Dec 2020 13:08:00 +0100

kpatch (0.8.0-0ubuntu2) focal; urgency=medium

  * No-change rebuild for libgcc-s1 package name change.

 -- Matthias Klose <email address hidden> Sun, 22 Mar 2020 16:45:05 +0100

kpatch (0.8.0-0ubuntu1) focal; urgency=low

  [ Benjamin M Romer ]
  * Upstream bump to 0.8.0
  * These remaining patches have been refreshed to apply to the updated
     upstream:
     - kpatch-build-adjust-dirs.patch
     - use-debian-rules-for-ubuntu-builds.patch
     - ubuntu-kernel-variants.patch
  * Packaging changes to produce only kpatch and kpatch-build
     - kpatch-dkms will be deprecated in the upstream soon
     - kmod-fix-symbol-lookup-on-l...

Read more...

Changed in kpatch (Ubuntu):
status: New → Fix Released
description: updated
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Currently libunwind-dev is not used on s390x by the kernel build, thus the runtime dep for libunwind-dev can probably be dropped, will test.

Also not sure why it is at all specified.

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kpatch (Ubuntu Jammy):
status: New → Confirmed
Changed in kpatch (Ubuntu Kinetic):
status: New → Confirmed
Changed in linux (Ubuntu Jammy):
status: New → Confirmed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2023-01-09 03:47 EDT-------
Hi, Could you please provide the link of the kernel (linux-oem-6.1/6.1.0-1004.4) and iso to be tested. Thank you.

Revision history for this message
Frank Heimes (fheimes) wrote :

Hi Sumanth,
please ignore the comment #27, and the request to verify on jammy with 'linux-oem',
since this ticket was opened against the stock Ubuntu kernel (and not against the linux-oem kernel). On top linux-oem is amd64 only.

Anyway, I'm updating the tag to verification-done-jammy, just to unblock the further processes.

tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

kpatch was updated in lunar, and canonical-livepatch-service has a backport of that in their PPAs to build livepatches on jammy.

Changed in kpatch (Ubuntu Jammy):
status: Confirmed → Invalid
Changed in kpatch (Ubuntu Kinetic):
status: Confirmed → Invalid
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

The next issue that is still to resolve is around UBSAN - https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003374 it appears that kpatch is currently incompatible with our kernel configuration that enables UBSAN.

Revision history for this message
Frank Heimes (fheimes) wrote :

Is the PPA with the backported kpatch tool (that can be used with jammy) public?

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

the liveapatch service builders are ephemeral and private - as unique one is setup for every kernel abi build, with matching build-dependencies, and potentially contains embargoed security updates code. livepatches are consumed via livepatch clients, with an optional onprem server. More information on https://ubuntu.com/security/livepatch

Stefan Bader (smb)
Changed in linux (Ubuntu Jammy):
importance: Undecided → Medium
status: Confirmed → Fix Committed
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: In Progress → Fix Committed
Revision history for this message
Frank Heimes (fheimes) wrote :

The following kernel incl. the needed patches for jammy:
5.15.0.70.68 | jammy-proposed

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.15.0-70.77 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
John Cabaj (john-cabaj) wrote (last edit ):

Moved to https://bugs.launchpad.net/bugs/2013603

Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17).

Patch submitted and tested - pending mailing list review.

Stefan Bader (smb)
Changed in linux (Ubuntu Kinetic):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (29.9 KiB)

This bug was fixed in the package linux - 5.15.0-70.77

---------------
linux (5.15.0-70.77) jammy; urgency=medium

  * jammy/linux: 5.15.0-70.77 -proposed tracker (LP: #2011918)

  * CVE-2023-26545
    - net: mpls: fix stale pointer if allocation fails during device rename

  * CVE-2023-1281
    - net/sched: tcindex: update imperfect hash filters respecting rcu

  * [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG)
    support (LP: #1971151)
    - scsi: mpi3mr: Add bsg device support
    - scsi: mpi3mr: Add support for driver commands
    - scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi
      header
    - scsi: mpi3mr: Add support for MPT commands
    - scsi: mpi3mr: Add support for PEL commands
    - scsi: mpi3mr: Expose adapter state to sysfs
    - scsi: mpi3mr: Add support for NVMe passthrough
    - scsi: mpi3mr: Update driver version to 8.0.0.69.0
    - scsi: mpi3mr: Increase I/O timeout value to 60s
    - scsi: mpi3mr: Hidden drives not removed during soft reset
    - scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR
    - scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init()
    - scsi: mpi3mr: Return error if dma_alloc_coherent() fails
    - scsi: mpi3mr: Add shost related sysfs attributes
    - scsi: mpi3mr: Add target device related sysfs attributes
    - scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings
    - scsi: mpi3mr: Fix kernel-doc

  * cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids
    (LP: #2008519)
    - cpufreq: intel_pstate: Update EPP for AlderLake mobile
    - cpufreq: intel_pstate: Adjust balance_performance EPP for Sapphire Rapids

  * Fail to output sound to external monitor which connects via docking station
    (LP: #2009024)
    - [Config] Enable CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM

  * Fix mediatek wifi driver crash when loading wrong SAR table (LP: #2009118)
    - wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read

  * Jammy update: v5.15.92 upstream stable release (LP: #2011472)
    - ARM: dts: imx: Fix pca9547 i2c-mux node name
    - ARM: dts: vf610: Fix pca9548 i2c-mux node names
    - arm64: dts: freescale: Fix pca954x i2c-mux node names
    - arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI
    - firmware: arm_scmi: Clear stale xfer->hdr.status
    - bpf: Skip task with pid=1 in send_signal_common()
    - erofs/zmap.c: Fix incorrect offset calculation
    - blk-cgroup: fix missing pd_online_fn() while activating policy
    - HID: playstation: sanity check DualSense calibration data.
    - dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init
    - cifs: fix return of uninitialized rc in dfs_cache_update_tgthint()
    - extcon: usbc-tusb320: fix kernel-doc warning
    - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt
    - tools: fix ARRAY_SIZE defines in tools and selftests hdrs
    - selftests/vm: remove ARRAY_SIZE define from individual tests
    - selftests: Provide local define of __cpuid_count()
    - net: fix NULL pointer in skb_segment_list
    - net: mctp: purge receive queues on sk destruction
    - Linux 5.15.92

  * Jammy update: v5.15....

Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Note livepatches can only start with the next abi specifically https://bugs.launchpad.net/kernel-sru-workflow/+bug/2016820 jammy/linux: 5.15.0-71.78 it started building already, and will undergo testing soon.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-hwe-5.15/5.15.0-71.78~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-focal-linux-hwe-5.15 verification-needed-focal
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Note despite the hwe-5.15 obviously picking up all the code changes in the kernel, this feature will not work in hwe-5.15 in focal, due to lack of toolchain support. Thus this is a no-op in focal.

tags: added: verification-done-focal verification-done-jammy
removed: verification-needed-focal verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.15.0-1036.40 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws verification-needed-jammy
removed: verification-done-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.15.0-1038.45 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-intel-iotg-5.15/5.15.0-1029.34~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-focal-linux-intel-iotg-5.15 verification-needed-focal
removed: verification-done-focal
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-xilinx-zynqmp
Revision history for this message
Jian Hui Lee (jianhuilee) wrote :

according to comment #40

tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2023-06-19 06:27 EDT-------
Big thank you to everybody who has contributed and helped to make this important feature available for s390x.

With this being released to Jammy, we can close the bug / LP entry.

Changing the status to CLOSED.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1046.51~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk
Revision history for this message
Frank Heimes (fheimes) wrote :

This bug affects s390x only, hence I'm updating all further verification requests to done, to unblock potential ongoing processes.

tags: added: verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-jammy-linux-mtk
removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy verification-needed-jammy-linux-mtk
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.