This bug affects s390x only, hence I'm updating all further verification
requests to done, to unblock potential ongoing processes.
** Tags removed: verification-needed-focal-linux-aws-5.15
verification-needed-jammy verification-needed-jammy-linux-mtk
** Tags added:
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
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
according to comment #40
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel
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
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
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,
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,
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 removed: verification-needed-focal verification-needed-jammy
** Tags added:
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
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.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s390x
Status
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
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s390x
Status in
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.
** Bug watch added:
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 following kernel incl. the needed patches for jammy:
5.15.0.70.68 | jammy-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s390x
Status
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
Is the PPA with the backported kpatch tool (that can be used with jammy)
public?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s390x
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.
--
You received this bug notification because you are a member of Kernel
Packages,
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
--
You received
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
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,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kpatch (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kpatch (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 changed:
[ Impact ]
- * kpatch upstream has gained support for more architectures which we
** Description changed:
- Kernel live-patch is afaik fully upstream and available for 'all' platforms
(incl. s390x).
- But the kpatch-build tool does only support amd64 as of today.
+ [ Impact ]
+
+ * kpatch upstream has gained support for more architectures which we
+ would like to enable on
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 Fri, 21 Oct 2022
14:42:04 +0100
Thx for the update about the PR, Boris!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s390x
Status in Ubuntu on IBM z Systems:
In
--- Comment From heinz-werner_se...@de.ibm.com 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 heinz-werner_se...@de.ibm.com 2018-03-05 05:09 EDT---
This Feature is
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch support for for s390x
Status in
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: 0084
(LP: #1990236)
- Revert
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
--
You
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.
Config and Packaging of kinetic:linux-unstable and kinetic:linux are
incomplete.
** Changed in: linux (Ubuntu Kinetic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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"
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*()
** Summary changed:
- kernel livepatch not available for s390x
+ Kernel livepatch support for for s390x
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1639924
Title:
Kernel livepatch
41 matches
Mail list logo
