** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * Secure boot of Linux on s390x will no longer be possible
+with an upcoming IBM zSystems firmware update.
+
+ [Fix]
+
+ * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add
secure
** Summary changed:
- [UBUNTU 20.04] boot: Add secure boot trailer
+ [UBUNTU 20.04] boot: Add s390x secure boot trailer
--
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/1996071
Title:
Ok, so it's actually like this ... (for focal)
** Attachment removed: "0001-s390-boot-add-secure-boot-trailer.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996071/+attachment/5630383/+files/0001-s390-boot-add-secure-boot-trailer.patch
** Patch added:
Looks like we commented in parallel.
Yes, backport will be helpful.
--
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/1996071
Title:
[UBUNTU 20.04] boot: Add secure boot trailer
Status in
In the focal master-next tree file 'vmlinux.lds.S' is at a different location:
'arch/s390/boot/compressed/' instead of 'arch/s390/boot/'
and the context is also slightly different.
Would you please have a look at the attached backport for focal and confirm
that it's correct?
Since it has this
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
**
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1996071
Title:
[UBUNTU 20.04] boot: Add secure boot
So commit aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot
trailer" was just upstream accepted with v6.1-rc3.
And it got tagged for upstream stable with:
"Cc: # 5.2+"
That means that it will ideally automatically land over time in all Ubuntu
kernels, down to focal's 5.4.
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** 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.
Hello Nico, thanks for raising this.
The fix/patch c3f0e5fd2d33 "KVM: s390: pv: don't present the ecall interrupt
twice" got upstream accepted with kernel v6.0, so I assume that it not only
needs to be applied to 20.04/5.4, but also to 22.04/5.15 and 22.10/5.19.
And I've noticed that it got
I'm also seeing a lot of these msgs on s390x still with kinetic, when
server certification runs are done:
Oct 31 11:33:57 s1lp10 kernel: [592067.859684] request_module:
kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module
crypto-rmd320, throttling...
Oct 31 11:33:57 s1lp10 kernel:
** Changed in: ubuntu-z-systems
Status: Confirmed => 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/1982833
Title:
Bump (kernel) '-mtune' to z16 / arch14 with 23.04
Ubuntu 18.04 kernel 4.15.0-196 (currently in -proposed) incl. this fix.
https://launchpad.net/ubuntu/+source/linux/4.15.0-196.207
--
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/1994601
** Changed in: ubuntu-z-systems
Status: New => Confirmed
--
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/1982833
Title:
Bump (kernel) '-mtune' to z16 / arch14 with 23.04
Status
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1982833
Title:
Bump (kernel) '-mtune' to z16 / arch14 with 23.04
Status in
** Tags removed: l-release
** Tags added: bot-stop-nagging lunar
--
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/1982833
Title:
Bump (kernel) '-mtune' to z16 / arch14 with 23.04
Status
** Information type changed from Private to Public
** Summary changed:
- Consider bumping (kernel) '-mtune' to z16 / arch14 with 23.04
+ Bump (kernel) '-mtune' to z16 / arch14 with 23.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** 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/1994601
Title:
[UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194
Kernel SRU request submitted for bionic:
https://lists.ubuntu.com/archives/kernel-team/2022-October/134331.html
changing status to 'In Progress'.
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-z-systems
Status: Confirmed => In Progress
**
** Summary changed:
- [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL
+ [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
--
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/1994601
** Description changed:
+ SRU Justification:
+ ==
+
+ [ Impact ]
+
+ * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194
+are no longer able to IPL (boot) on IBM z14 or newer hardware.
+
+ * This issue got introduced by upstream commit e4f74400308c
+
I just tried 20.04 (focal legacy image), just to be sure, but it's not
affected and worked fine.
--
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/1994601
Title:
[UBUNTU 18.04] Ubuntu
Hi Christian, all,
both kernels are now ready:
1) with "s390/archrandom: simplify back to earlier design and initialize
earlier" reverted:
f98553359746 (HEAD -> master-next) Revert "s390/archrandom: simplify back to
earlier design and initialize earlier"
Another build is running right now at
https://launchpad.net/~fheimes/+archive/ubuntu/test2
with 's390/archrandom: simplify back to earlier design and initialize earlier'
still in and 's390/setup: init jump labels before command line parsing' on top.
This will take a while - will test it
A test kernel is being build at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/test
(will be available in some minutes)
--
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/1994601
Hi Harald, see my previous comment - I could recreate this on z15 now (but it's
fine on z13).
So seems to be related to (z14) z15 and newer?!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ah - interesting.
I could recreate the situation on z15 / L1III:
$ virsh start bionic --console
Domain 'bionic' started
Connected to domain 'bionic'
Escape character is ^] (Ctrl + ])
ubuntu@z15test:~$
There is obviously a difference in the behavior of the z13 and z15.
I can create a test
Since the Ubuntu kernel team does for every kernel update and SRU regression
testing, a non-bootable kernel would have been identified and the kernel would
not have left -proposed, it would even not have landed in -proposed.
That makes me think that the issue is elsewhere - at the KVM host
Again, 18.04.5 installations for for me, I used this (latest) 18.04.5 ISO:
https://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.5-server-s390x.iso
If there is a reason to revert 's390/archrandom: simplify back to
earlier design and initialize earlier' we could consider that, but works
Btw. for the KVM guest install I used:
sudo qemu-img create -f qcow2 /var/lib/libvirt/images/bionic.qcow2 8G
sudo virt-install --name bionic --vcpus 2 --ram 1024 --disk
path=/var/lib/libvirt/images/bionic.qcow2,size=5,bus=virtio,format=qcow2
--os-type linux --os-variant generic --network
Trying to recreate, I was just able:
- to successfully complete an 18.04 installation on a 22.10 host (that what I
just had at hand) and
- a successful 18.04 installation on a z/VM 6.4 host
I selected in both cases the strongly recommended option 'Install security
updates automatically'.
(And
Thanks for reporting this.
What is the version of the Ubuntu host where you want to install the 18.04
guest onto?
So that I can try to properly recreate this.
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee:
** Changed in: ubuntu-z-systems
Status: In Progress => 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/1852741
Title:
[22.10 FEAT] zKVM: Crypto Passthrough Hotplug -
This bug was not requested for linux-gkeop-5.15 nor for focal.
Hence I'll just set the tag 'verification-done-focal' to unblock the SRU
process.
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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
** 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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for
** 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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on
Okay, that's good - thanks for that.
Closing this ticket as invalid.
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: ubuntu-z-systems
Status: Incomplete => Opinion
** Changed in: ubuntu-z-systems
Status: Opinion => Invalid
--
You received this
** 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/1959542
Title:
[22.10 FEAT] [IO2201] Independent Usage of
** 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/1853306
Title:
[22.04 FEAT] Enhanced Interpretation for PCI
** 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
** 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/1959940
Title:
[22.10 FEAT] KVM: Secure Execution guest dump
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
** Tags removed: kk-release
--
You received this bug notification because you are a member of Kernel
Packages,
This is now incl. in linux-generic | 5.19.0.18.18 | kinetic-proposed
hence updating the status to Fix Committed.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug
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
This is now incl. in linux-generic | 5.19.0.18.18 | kinetic-proposed
hence updating the status to Fix Committed.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug
This is incl. in linux-generic 5.19.0-17.17 (which got overruled by
5.19.0.18.18) and is with that in kinetic-proposed, hence updating the
status to Fix Committed.
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-z-systems
Status: In Progress
This is incl. in linux-generic 5.19.0-16.16 (meanwhile overruled by
5.19.0.18.18) and is with that in kinetic-proposed, hence updating the
status to Fix Committed.
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you
linux-gkeop-5.15 is out of scope for this bug (does not exist for s390x).
To unblock the process I'll add the 'verification-done-focal' tag.
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
linux-gkeop-5.15 is out of scope for this bug (does not exist for s390x).
To unblock the process I'll add the 'verification-done-focal' tag.
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Also affects: s390-tools-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
**
Thx for testing!
The further process is already in place and on a high level (just dates)
described here:
https://kernel.ubuntu.com/
So this fix is now incl. in the kernel SRU cycle "2022.09.19".
Means the updated kernel that incl. the fix will soon (ideally today) land in
the '-proposed' pocket
** Package changed: linux (Ubuntu) => zlib (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Importance: Undecided
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Also affects: s390-tools-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper
Verification done on jammy (on a slightly different setup):
root@s1lp15:~# uname -a
Linux s1lp15 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:23 UTC 2022
s390x s390x s390x GNU/Linux
root@s1lp15:~# ethtool encc000 | grep Duplex
Duplex: Full
root@s1lp15:~# grep qcrdinfo
** Changed in: ubuntu-z-systems
Status: New => Incomplete
--
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/1990275
Title:
[UBUNTU 20.04] Unexpected LAG affinity behaviour with
The file in question:
drivers/net/ethernet/mellanox/mlx5/core/lag/mp.c
does also not exist on latest 5.4 upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/ethernet/mellanox/mlx5/core?h=v5.4.214
(but drivers/net/ethernet/mellanox/mlx5/core/lag_mp.c).
Looks
Well, yes - I just ran into this, while I wanted to proceed on this
ticket.
Things definitely do not apply on focal master next (git clone
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal --branch
master-next --single-branch).
Even the first commit ad11c4f1d8fd is causing
/ubuntu/lp1853306
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: Frank Heimes (fheimes) => Canonical Kernel Team
(canonical-kernel-team)
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-
Since kinetic/22.10 is based on 5.19 and all patches got upstream
accepted with at least v5.18 (one 5.17), everything needed is included
in kinetic/22.10.
For jammy/22.04 I checked master-next and found all patches in
Ubuntu-5.15.0-41 or later, so jammy/22.04 incl. all the fixes and is not
(or
Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes
(fheimes)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
-
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Summary changed:
- [22.04 FEAT] [KRN2006] BEAR enhancement support for new IBM Z Hardware
+ [22.10 FEAT] [KRN2006] BEAR enhancement support for new
** 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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing
** 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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for
Hello and thx for reporting this.
There is a snapshot version in jammy/22.04:
3.17.0+dfsg+20220202.b40982e-0ubuntu1.1
This is obviously based on 3.17, BUT has a lot of commits on top (until date
20220202 and commit b40982e).
So I looked up both commits manually (that's why I don't like packages
Patch request submitted:
https://lists.ubuntu.com/archives/kernel-team/2022-September/thread.html#133176
Updating status to 'In Progress'.
In addition test builds in PPA were done for all major architectures
with a kinetic master-next kernel that incl. the patches mentioned
above.
** Changed in:
Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-September/thread.html#133113
changing status to 'In Progress'.
A test kernel was build in PPA and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1959940
** Changed in:
** Changed in: ubuntu-z-systems
Status: Confirmed => 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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for
in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: Frank Heimes (fheimes) => Canonical Kernel Team
(canonical-kernel-team)
** Information type changed from Private to Public
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
linux-generic 5.19.0.15.15 landed in kinetic
hence updating to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
linux-generic 5.19.0.15.15 landed in kinetic
hence updating to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Many thx, Niklas!
--
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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing device attributes
during recovery
Status in Ubuntu on
Kernel SRU request submitted for focal:
https://lists.ubuntu.com/archives/kernel-team/2022-September/thread.html#132957
changing status to 'In Progress'.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
**
** Description changed:
SRU Justification:
--
[Impact]
- * If the mlx5 driver is reloading while the recovery flow is happening,
-and if it receives new commands before the command interface is up
-again, this can lead to null pointer that tries to access non-
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1988352
Title:
focal autopkgtests
Public bug reported:
While looking to fix some focal-proposed migrations for zlib,
I've noticed these regressions:
autopkgtest for linux-hwe-5.11/5.11.0-61.61: amd64: Pass, arm64: Pass, armhf:
Regression ♻ , ppc64el: Pass, s390x: Pass
autopkgtest for linux-hwe-5.13/5.13.0-52.59~20.04.1: amd64:
** Description changed:
+ SRU Justification:
+ --
+
+ [Impact]
+
+ * If the mlx5 driver is reloading while the recovery flow is happening,
+and if it receives new commands before the command interface is up
+again, this can lead to null pointer that tries to access non-
Updating to Fix Released, because LP#1981864 was updated to Fix
Released.
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member
Test kernels are now available in the following PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1987287
(20.04/focal 5.4 as well as 18.04.5/bionic hwe-5.4)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello 'nafeiy', we indeed wanted to pick this up in the next days.
Just notice that this is a development bug, opened at the Launchpad bug
tracking system, that is mainly used for development.
We will usually produce a patched 20.04/focal/5.4 test kernel, that we make a
available via a so
Yepp, it's all about kernel patches.
This bug was wrongly marked as affecting the ethtool (well, it affects the
ethtool, but not in the 'affects' send of Launchpad), which caused some
confusion.
I just changed that, pointing now to the kernel (which is "linux (Ubuntu)" in
the above affects
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ethtool (Ubuntu)
** Changed in: ethtool (Ubuntu Jammy)
Assignee: Ubuntu Server (ubuntu-server) => (unassigned)
** Changed in: ethtool (Ubuntu Kinetic)
Assignee: Ubuntu Server
Now Fix Released for focal according to LP#1979566.
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: s390-tools (Ubuntu)
Importance:
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-z-systems
Status: New => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Yes, if it get it incl. in the focal 5.4 (GA), it will automatically
find it's way into the bionic hwe-5.4 as well.
--
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/1987287
Title:
[UBUNTU
The patch mentioned is upstream since kernel v5.7-rc7,
hence it's only needed for focal (already incl. in jammy and kinetic).
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** 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.
** 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/1979296
Title:
[UBUNTU 20.04] Include patches to avoid
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** 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.
So yes, this is a new feature / kernel option for (arm only) introduced with
the migration to gcc 12:
[v3,1/2] AARCH64: Add gcc Shadow Call Stack support
https://patchwork.kernel.org/project/linu
x-hardening/patch/20220303074323.86282-1-ashim...@linux.alibaba.com/#24774364
--
You received this
Public bug reported:
The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a
kinetic-proposed migration process (for zlib) and runs into a 'regression':
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: Regression
♻"
The regression is highly likely not due
** 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/1959973
Title:
[22.04 FEAT] KVM: Attestation support for
** 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/1980951
Title:
[UBUNTU 22.04] Kernel oops while removing
Great, thx.
I can confirm that all 3 commits are in Ubuntu-5.19.0-11.11 that is currently
in kinetic-proposed.
Hence updating the status to Fix Committed.
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix
This is good news, thx.
I can confirm that all three patches are in kinetic master-next
and included in kernel 'Ubuntu-5.19.0-11.11'.
But so far we have still 5.19.0.10.10 in kinetic-proposed, hence updating the
status for now to In Progress.
** Changed in: linux (Ubuntu)
Status:
I can confirm that these two patches are incl. in 22.04/jammy:
7e8403ecaf884f307b627f3c371475913dd29292 "s390: add HWCAP_S390_PCI_MIO to ELF
hwcaps"
3322ba0d7bea1e24ae464418626f6a15b69533ab "s390: make PCI mio support a machine
flag"
(but the 2nd one has a different name)
With that updating the
301 - 400 of 3020 matches
Mail list logo
