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: 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.
5 matches
Mail list logo
