** Description changed:
[Impact]
* There is new version of bnx2x firmware
* oem-5.14 and hwe-5.15 kernels use that one; and when not found
fallback to previous version of firmware.
[Test Plan]
* sudo apt install initramfs-tools
* echo bnx2x | sudo tee -a
Public bug reported:
[Impact]
* There is new version of bnx2x firmware
* oem-5.14 and hwe-5.15 kernels use that one; and when not found
fallback to previous version of firmware.
[Test Plan]
* sudo apt install initramfs-tools
* echo bnx2x | sudo tee -a /etc/initramfs-tools/modules
* sudo
assigning myself to review and upload/sponsor.
** Changed in: wireless-regdb (Ubuntu Jammy)
Assignee: Seth Forshee (sforshee) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubu
** Description changed:
- v5.17 cherrypicks for unmatched
+ [Impact]
+
+ * Various features and bugs got fixed in sifive dtbs in v5.17 kernel
+
+ * Some versions of those features/bugs already exist in our kernels,
+ and others are missing.
+
+ * Cherry-pick from upstream all new changes
** Changed in: linux-riscv (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1955042
Title:
SBI SRST extension is missing
Status in
Public bug reported:
v5.17 cherrypicks for unmatched
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
** Summary changed:
- ftbfs with linux 5.16+
+ ftbfs with linux 5.16 & 5.17
** Description changed:
- ftbfs with linux 5.16+
+ [Impact]
- https://github.com/tseliot/nvidia-graphics-drivers/issues/44
+ * FTBFS from with 5.16 & 5.17 kernels
- Due to changes in the kernel w.r.t. stdarg.h
Public bug reported:
ftbfs with linux 5.16+
https://github.com/tseliot/nvidia-graphics-drivers/issues/44
Due to changes in the kernel w.r.t. stdarg.h and stddef.h includes.
** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** Affects:
** Changed in: kdump-tools (Ubuntu)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/1877533
Title:
** Description changed:
Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
This prevents installing OEM kernels with nvidia, offline, from Ubuntu
Desktop Focal point release media.
Note this package is in the ship-live .debs archive pool only.
--
Resolution
** Description changed:
Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
This prevents installing OEM kernels with nvidia, offline, from Ubuntu
Desktop Focal point release media.
Note this package is in the ship-live .debs archive pool only.
--
Resolution
Public bug reported:
Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
This prevents installing OEM kernels with nvidia, offline, from Ubuntu
Desktop Focal point release media.
Note this package is in the ship-live .debs archive pool only.
--
Resolution of this bug report
Downloaded the iso today doesn't mean the iso was built today, or if it
contains this update.
jammy installer iso are attempted to be built daily, but are only
published once they pass automated smoke testing and validation. The
last image that passed that was built on 2nd of February. And builds
Fix was released in busybox 1:1.30.1-7ubuntu3 and requires initramfs
rebuild
your screenshot clearly shows version number 1:1.30.1-7ubuntu2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Also, ubuntu_lxc fails on jammy now; even though it is still using
impish branch of tests.
--
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/1960094
Title:
lxc/1:4.0.6-0ubuntu1~20.04.1
vers are built on arches for which both the
driver and kernel-flavour exist.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received t
** Description changed:
There is a new more efficient debug format enabled via
CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
packaging in the .ddeb before we can enable this. Evaluate whether the
other tooling we have will handle it before doing so.
--
* all
** Description changed:
There is a new more efficient debug format enabled via
CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
packaging in the .ddeb before we can enable this. Evaluate whether the
other tooling we have will handle it before doing so.
+
+ --
+
+ * all
@fheimes @iii-i
thank you for this, we will include that patch into our kernels. Do you
expect that the toolchain change may have affected any other binaries
(ie. userspace binaries)? Or should we re-apply the reverted patch back
in our gcc-11 (given the improvements that it brings)?
--
You
** Description changed:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it is
Public bug reported:
bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev
PPA and installed in pi-kernel snaps.
Some of the firmware files shipped in bluez-firmware are not present in
neither src:linux-firmware nor src:linux-firmware-raspi
It seems like it is an oversight, and
: Dimitri John Ledkov (xnox)
Status: In Progress
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Impish)
** No longer affects: linux
** Description changed:
+ -- initramfs-tools
+
+ [Impact]
+
+ * linux supports xz compressed linux-firmware which saves disk space.
+ In focal, initramfs-tools only knows how to included uncompressed
+ firmware files (even when kernel supports loading compressed ones).
+ Newer releases of
For focal this appears to be required and fixes things for people
https://github.com/openzfs/zfs/issues/10642
I will rerun regression suites on focal with latest kernel, and if that
passes, will mark this as verification done.
--
You received this bug notification because you are a member of
riscv64 ftbfs is not a regression, as we don't build it in updates
either.
** Bug watch added: github.com/openzfs/zfs/issues #10642
https://github.com/openzfs/zfs/issues/10642
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
- regression tests ppc64el (on focal userspace)
- double check focal userspace with hwe-kernel new zfs-dkms
- regression tests arm64
-
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
- regression tests ppc64el (on focal userspace)
- double check focal userspace with hwe-kernel new zfs-dkms
- regression tests arm64
+ -
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
- regression tests ppc64el (on focal userspace)
- double check focal userspace with hwe-kernel new zfs-dkms
+ - regression tests arm64
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
- regression tests s390x
- autopkgtests all arches
+ - regression tests ppc64el (on focal userspace)
+ - double check focal userspace with hwe-kernel new zfs-dkms
TODO
- - double check
** Description changed:
v2.1.2 upgrade complete verification
DONE
- regression tests amd64
+ - regression tests s390x
- autopkgtests all arches
-
TODO
- double check focal userspace with hwe-kernel new zfs-dkms
- zsys in jammy on amd64
- - regression tests s390x
-
: zfs-linux (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Affects: zfs-linux (Ubuntu Jammy)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Tags: block-proposed-jammy
** Tags added
Public bug reported:
port zsys generator changes from shell to C
new zfs has ported zfs mount generator from shell to C, meaning we need
to rewrite zsys specific functionality that we patch into said generator
from shell to C.
** Affects: zfs-linux (Ubuntu)
Importance: Wishlist
@arighi
Explicit nack on zfs-linux patches, that is incomplete merge that drops
ubuntu delta & zsys support.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954676
Title:
jammy
@ilja
Now this is starting to be more fun then. Note our mainframe is z13 2964
and we have reproduced the bug in both LPAR and KVM. I'll try to package
up a more concrete reproducer (to the point of tarring up a full chroot
with all the deps).
--
You received this bug notification because you
Hi, modules built with gcc-11 14ubuntu1 toolchain have the gcc-11 stable
ibmz PLT patch already reverted to make things work again.
One needs to downgrade gcc-11 to 13ubuntu1 to experience the breakage.
You can fetch older gcc-11 from
The revert of the gcc-11 patch mentioned above results in working kernel
builds, which load zfs.ko built-into-kernel and built via zfs-dkms as
well.
** Description changed:
[Impact]
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft
Note above patches causes regression with SEV feature, which has been
subsequently fixed. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-5.8 in Ubuntu.
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4754/+packages build in progress.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954676
Title:
jammy 5.15 kernel soft
We are suspecting
https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7
and trying to do builds with it reverted.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
@ubuntu-archive please promote firwmare-sof from multiverse to
restricted. As blobs are now removed from linux-firmware in favor of
shipping them in firmware-sof.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Changed in: firmware-sof (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1930868
Title:
[SRU][Jammy]Package
1) firmware-sof is good; note that breaks/replaces versions will need to
be adjusted to the correct versions for every series upon every upload
of this change, if it is SRUed.
2) the matching linux-firmware changes are good as well.
--
You received this bug notification because you are a member
Idea: move the strict `nvidia-kernel-common-N (<= N)` from the `linux-
modules-nvidia-N-ABI` package to the meta packages `linux-modules-
nvidia-N-kernelflavour`
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in
The dependencies are intentionally very strict, to ensure that kernel /
nvidia drivers / nvidia userspace are all installed and are compatible
with each other.
However, it was intended to be upgradable unattended. And since one can
have up to three kernel ABIs on disk, one should in theory be
** Also affects: backport-iwlwifi-dkms (Ubuntu)
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/1951580
Title:
backport-iwlwifi-dkms fails to
Public bug reported:
BUILD & CLEAN scripts should support DESTDIR option
When paths are mangled in the BUILD & CLEAN scripts it would be nice if
it injected DESTDIR variable support. Such that one could BUILD/CLEAN
modules in a different target directory when the bits directory is read
only.
**
Public bug reported:
Ubuntu kernel modules are stripped prior to signing:
$(build_cd) $(kmake) $(build_O) $(conc_level) modules_install $(vdso) \
INSTALL_MOD_STRIP=1 INSTALL_MOD_PATH=$(pkgdir)/ \
INSTALL_FW_PATH=$(pkgdir)/lib/firmware/$(abi_release)-$*
Public bug reported:
grep nv-interface.o -r .
./CLEAN:rm -f nvidia/nv-interface.o
./BUILD:/usr/bin/ld.bfd -r -o nvidia/nv-interface.o nvidia/nv.o nvidia/nv-pci.o
nvidia/nv-acpi.o nvidia/nv-cray.o nvidia/nv-dma.o nvidia/nv-i2c.o
nvidia/nv-mmap.o nvidia/nv-p2p.o nvidia/nv-pat.o nvidia/nv-procfs.o
@chaoqin
In https://bugs.launchpad.net/intel/+bug/1842239, the glibc patches
point at https://gitlab.com/x86-glibc/glibc/-/commits/users/hjl/cet/2.31
which we have been applying. Currently we ship them as a backported
patch see
@ Chao Qin (chaoqin) @anthonywong
Do we also need to patch glibc to turn on CET support? Most of Ubuntu
binaries have CET enabled, but I thought there was still a patch needed
to turn the CET support on due to changes in the CET patches done as per
kernel upstream feedback. Or is this patch
$ less pc-kernel_5.4.0-90.101.1_amd64.snap | grep regulatory
-rw-r--r-- root/root 4160 2021-08-29 20:49 /firmware/regulatory.db
-rw-r--r-- root/root 1182 2021-08-29 20:49
/firmware/regulatory.db.p7s
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
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/1947174
Title:
Add final-checks to check certificates
Status
We already ship lib/systemd/system-sleep/hibinit-agent that does post
things in hibinit-resume to workaround things. Including stuff about
networking, due to previous issues with xen-netfront.
Given we already restart systemd-networkd, I wonder if we should do
better and not keep xen-netfront
Added my own review https://lore.kernel.org/linux-
integrity/8d7e1609-f77e-834e-cf40-05e19bbc3...@canonical.com/
A few optional comments; and one required change needed to add one more
ifdef.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Note that dwarves-dfsg portion of this request was done a while back in
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
NAK
we have backported dwarves-dfsg to bionic and up with support for pahole
which is now in use by kernel builds to enable CONFIG_DEBUG_INFO_BTF in
them.
The backports were done in
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811
Why do we need pahole-btf? Given that
Booted impish lxd vm; enabled proposed and upgraded to the new kvm abi:
# uname -a
Linux leading-fly 5.13.0-1005-kvm #5-Ubuntu SMP Tue Oct 26 23:55:45 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
# ls /sys/firmware/efi/mok-variables/
MokListRT MokListXRT SbatLevelRT
# keyctl list %:.blacklist |
failing to get lxd to work to verify this. will try again tomorrow.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1942319
Title:
When booting with UEFI, mokvar table and
sysdig (0.27.1-0.2ubuntu1) impish; urgency=medium
* Fix syscall table base ID on arm64 (LP: #1945757)
-- Andrea Righi Fri, 01 Oct 2021 11:20:07
+0200
** Package changed: linux-oem-5.6 (Ubuntu) => sysdig (Ubuntu)
** Changed in: sysdig (Ubuntu Impish)
Status: Fix Committed => Fix
Public bug reported:
Ubuntu kernels by default ship modprobe.d that excludes many modules
from loading:
# Kernel supplied blacklist for linux 5.4.0-89-generic amd64
# modprobe.d/common.conf
# LP:1434842 -- disable OSS drivers by default to allow pulseaudio to emulate
blacklist snd-mixer-oss
** Also affects: linux-firmware-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1942260
Title:
compress firmware in
** Also affects: initramfs-tools (Ubuntu)
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/1932329
Title:
Benchmark if we can compress kernel
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1942260
Title:
compress firmware in
Why are you using dkms modules, instead of signed lrm modules?
** Also affects: linux-restricted-modules (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in
Public bug reported:
[Impact]
* As part of landing builtin revocation certificates work
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029 it has been
identified that many kernels do not correct enforce newly enfoced keys
in the derivative flavours. I.e. due to annotations not
I wonder if we need before= or after= umount.target
--
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/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
we should check ordering of services for stop in a booted live session
(desktop / server / next-installer) and then figure out if we can add
additional dependencies to finalr.service (after) such that its stop is
ordered before everything else is stopped.
** Also affects: finalrd (Ubuntu)
Our installer could stop finalrd before issuing shutdown too, as a
workaround.
--
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/1840122
Title:
System fails to reboot from live session or
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4684/2021-10-12_16:41:27/impish_nvidia-
graphics-drivers-390_content.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
[Impact]
- * zfs fails reverting to a previous snapshot on reboot when selected on
+ * zfs fails reverting to a previous snapshot on reboot when selected on
grub
- * A miss-merge dropped initramfs hook changes, which result in failing
+ * A miss-merge dropped
Also I wonder if:
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut
-c-6
can be implemented as:
cut -c-6 /proc/sys/kernel/random/uuid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Description changed:
+ [Impact]
+
+ * zfs fails reverting to a previous snapshot on reboot when selected on
+ grub
+
+ * A miss-merge dropped initramfs hook changes, which result in failing
+ to generate and use a new zfs uid.
+
+ [Test Plan]
+
+ * Create snapshot with $ zsysctl save
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs
To fix this on hwe-5.11 all of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930713 needs to be
backported. Given that hwe-5.11 will be rolled over to hwe-5.13 soon, I
am not sure if it is worth the effort.
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Status: Confirmed => Won't Fix
The bug was committed for the linux-hwe-5.13 kernel in proposed:
linux-image-5.13.0-17-generic-dbgsym_5.13.0-17.17~20.04.1_armhf.ddeb (937.5 MiB)
linux-image-5.13.0-17-generic-lpae-dbgsym_5.13.0-17.17~20.04.1_armhf.ddeb
(923.4 MiB)
That also does not work, due to:
/var/lib/dkms/nvidia/390.144/build/nvidia-modeset/nvidia-modeset-linux.c:72:5:
note: in expansion of macro ‘do_div’
72 | do_div(result, 100);
./include/asm-generic/div64.h:245:36: error: passing argument 1 of ‘__div64_32’
from incompatible pointer
That failed, missed one more place. Retesting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
Status in
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531917/+files/lp1946642.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Testing in https://bileto.ubuntu.com/#/ticket/4681
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
Status
Testing patch in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4680
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531904/+files/lp1946642.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
nvidia-graphics-drivers-390 ftbfs on armhf
In file included from
/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16:
/var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function
‘os_flush_cpu_write_combine_buffer’:
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Impish)
Milestone: None => ubuntu-21.10
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux-oem-5.6 (Ubuntu Impish)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1945757
Title:
sysdig-dkms fails to build on
** Description changed:
- When booting with UEFI, mokvar table and %:.platform keyring must be
- available
+ [Impact]
+
+ * When booting with UEFI, mokvar table and %:.platform keyring must be
+ available. These are required for builtin revocation certificates to be
+ present, shim builtin
** Also affects: dwarves-dfsg (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libbpf (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: dwarves-dfsg (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~xnox/ubuntu/+source/linux/+git/focal/+merge/409374
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-5.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1928679
Title:
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
Should we look into this?
--
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/1413664
Title:
15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo
files
Status in linux
Public bug reported:
[Impact]
* pahole used to segfault on 32-bit platforms, which has now been fixed
* pahole used to be too old in focal, which is now being SRUed
* renable DEBUG_INFO_BTF in all the kernels/arches that had it
disabled, as otherwise one cannot compile/use advanced BTF
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Also affects: linux-azure-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-5.8 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-azure-5.8 (Ubuntu)
Status: New => Invalid
** Changed in: linux-azure-5.8 (Ubuntu Bionic)
Status:
** Description changed:
[Impact]
- * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
+ * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
which revokes many Ubuntu kernel hashes and 2012 signing key.
- * Kernel should import those into it's
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Also affects: linux-azure-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-5.8 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-azure-5.8 (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux-azure-5.8 (Ubuntu Xenial)
https://lists.ubuntu.com/archives/kernel-team/2021-September/124249.html
https://lists.ubuntu.com/archives/kernel-team/2021-September/124250.html
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Kernel
./fs/vboxsf is not available in v5.4 kernel.
--
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/1933248
Title:
please drop virtualbox-guest-dkms virtualbox-guest-source
Status in linux
$ git describe 0fd1695766
v5.5-rc6-150-g0fd1695766
0fd1695766 fs: Add VirtualBox guest shared folder (vboxsf) support
** Tags added: block-proposed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
601 - 700 of 1812 matches
Mail list logo
