Without having access to the hardware it's quite hard to figure out what
is happening exactly, I wasn't able to reproduce the issue in any other
test machines.
I'm wondering if this bug is still happening with a 5.15 kernel (linux
5.15 is available here ppa:canonical-kernel-team/bootstrap). If we
Alright, I checked with Chris Chiu, he confirms that all the tests
kernels that he provided don't have -fcf-protection=none. However, we
still don't think that touching this compiler option is a proper fix for
the bug, more likely it's just hiding the problem, so we could still
have a potential sta
@marco-098 sorry I had to disable zfs, because it doesn't build
correctly with CONFIG_KASAN enabled.
However, thanks to @randombop dmesg.txt now I think I see a potential
stack corruption in the elantech code!
IIRC param[] in elantech_cahnge_report_id must be at least 3 bytes,
because elantech_re
Uploaded another test kernel (5.13.0-22.22+arighi2020+1):
https://kernel.ubuntu.com/~arighi/lp1945590/
However, looking more at the KASAN error, it seems that the reported
error is actually an out-of-bound read... so that still doesn't explain
the stack corruption, but it's still something th
buntu Jammy)
Importance: High
Status: Confirmed
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
@manolo once the fix is applied to the generic kernel all the other
derivatives will be updated as well. About the ISO I need to check, it'd
make sense to update that as well, since there's a critical boot problem
in this case.
--
You received this bug notification because you are a member of Ker
@manolo I asked around and it looks like ISOs are updated only in there
are really critical bugs (but to be 100% sure you should try to ask the
Lubuntu community directly). In this case I guess the only workaround
(if disabling the pad, installing and upgrading the kernel doesn't work)
is to instal
Public bug reported:
Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
In-situ OAM (IOAM6). This lack of support is also triggering the
following kernel selftest failure:
# selftests: net: ioam6.sh
# SKIP: iproute2 too old, missing ioam command
not ok 1 selftests: net: ioam
** Also affects: iproute2 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1951390
Title:
upd
** Patch added: "iproute2-update-to-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541716/+files/iproute2-update-to-5.15.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ub
debdiff against Debian iproute2 5.15.0-1 (re-applied Ubuntu Fan driver).
v2: added this tracking bug to the changelog entry.
** Patch added: "iproute2-update-to-5.15-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541717/+files/iproute2-update-to-5.15-
Public bug reported:
Starting with the following commit, upstream kernel is enabling Intel
IOMMU related options by default:
792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by
default")
We should follow upstream direction enabling
CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU
** Description changed:
- Starting with the following commit, upstream kernel is enabling Intel IOMMU
related options by default:
-
- 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default")
-
- We should follow upstream direction enabling INTEL_IOMMU_DEFAULT_ON and
CO
Public bug reported:
CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
In file included from
/tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3,
from ./arch/x86/include/asm/bug.h:84,
from ./include/linux/bug.h:5,
https://gitlab.com/vicamo/backport-iwlwifi-dkms/-/issues/12 <- also
filed an issue here
--
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 build
Debdiff in attach seems to resolve the problem (tested on jammy with the
latest 5.15 from -proposed).
** Patch added: "iwlwifi-fix-build-error-with-kernel-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+attachment/5542079/+files/iwlwifi-fix-build-error-with-kernel-5
Actually... is this dkms really needed in jammy?
Now that the build is fixed I just noticed that I get this error if I
try to install it on a 5.15 kernel:
iwlwifi.ko:
Running module version sanity check.
Module has been obsoleted due to being included
in kernel 5.14.0. We will avoid installing
Public bug reported:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbs
Attached debdiff can fix the build error on armhf and ppc64el.
** Patch added: "bbswitch-fix-build-error-on-armhf-and-ppc64el.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951583/+attachment/5542102/+files/bbswitch-fix-build-error-on-armhf-and-ppc64el.debdiff
--
You received
Public bug reported:
CC [M] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o
/var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: error: initialization of
‘void (*)(struct device *)’ from incompatible pointer type ‘int (*)(struct
device *)’ [-Werror=incompatible-pointer-types]
1295 |
** Also affects: bbswitch (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Unfortunately I don't have control on the generation of the ISOs, the
best thing I can do is to set this bug to critical and ping people...
** Changed in: linux (Ubuntu Impish)
Importance: High => Critical
** Changed in: linux (Ubuntu Jammy)
Importance: High => Critical
--
You received th
It looks like this dkms is actually needed so ignore my previous
comment.
** Description changed:
+ [Impact]
+
+ backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15:
+
CC [M]
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
In file included from
/
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ [Impact]
+
+ On some thinkpads we may get a kernel panic at boot, because the
+ elantech driver (trakcpad) can trigger out-of-bounds access in the
+ stack.
+
+ [Test case]
+
+ Simply boot the kernel on one of the affected systems (e.g., Thinkpad
+ E14 Gen2).
+
+ [Fix]
I was waiting for a review / acknowledge from the upstream maintainer,
before applying this fix and unfortunately I didn't receive that in time
to push this fix in 5.13.0-22.
But now I got the ok from the maintainer, so I just sent the SRU fix to
the ubuntu kernel team mailing list:
https://list
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
[Impact]
It seems that enabling Intel IOMMU can cause some weird gfx problems, see for
example:
https://bugs.launchpad.net/bugs/1971146
https://bugs.launchpad.net/bugs/1965882
[Test case]
We don't have any specific test case, only other bug reports that
tracked down
** Summary changed:
- disable Intel DMA remapping options by default
+ disable Intel DMA remapping by default
--
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/1971699
Title:
disable Intel
NOTE to clarify: I'm going to revert this patch in focal/hwe-5.15, that
is the only 5.15 kernel with this patch that has AUFS enabled (so the
only kernel where this bug can be triggered).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
This patch seems to introduce this NULL pointer dereference, that can be
triggered systematically running lxc autopkgtest:
BUG: kernel NULL pointer dereference, address: 0008
[ 447.039738] #PF: supervisor read access in kernel mode
[ 447.040369] #PF: error_code(0x) - not-present
@mihalicyn Yes, this patch without AUFS enabled doesn't introduce any
problem, but that's because without AUFS the patch is basically a no-op.
Here's the ported patch that was applied to 5.15:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next&id=e3e60
I think I have a proper fix to re-introduce this patch without panicing
the kernel. I'm currently running some stress tests to make sure nothing
is broken. If everything goes well I'll re-introduce this patch with the
proper fix.
--
You received this bug notification because you are a member of K
Everything looks good, so I re-applied the patch with the addition of
this extra fix:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next&id=b4c25dba7993400e9c57d3e60bec4ab8bce1b701
--
You received this bug notification because you are a member of Ke
Alex, thanks for the review! We can definitely remove the dependency of
AUFS and provide a standalone patch, in this way we can provide this
feature also to those kernels that don't have AUFS enabled (like all the
recent kernels in jammy). I'll work on that and will ping you when I
have a patch rea
The impish kernel is already fixed and the fix is applied to the current
kernel in released. Comment #142 is referring to linux-oem-5.14 in
focal, that also has the fix, so it can be ignored.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this b
JFYI, I've sent an SRU email to apply the kernel fix also to Impish
5.13, just to be safe in case the gcc patch lands in Impish:
https://lists.ubuntu.com/archives/kernel-team/2022-February/127652.html
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also
Public bug reported:
This ftrace sub-test is failing on focal with the latest hwe-5.15:
[stdout] # [67] event trigger - test inter-event histogram trigger
snapshot action[FAIL]
We have not seen this failure before.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
Adding also focal, because with the new linux-hwe-5.15 we get the same
failure.
** Summary changed:
- update iproute2 in jammy
+ update iproute2
** Also affects: iproute2 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
Public bug reported:
[Impact]
The patch that we have recently re-introduced to properly support
overlayfs on top of shiftfs can introduce potential kernel panics, for
example:
BUG: kernel NULL pointer dereference, address: 0008
[ 447.039738] #PF: supervisor read access in ke
Public bug reported:
[Impact]
Use nosuid,noexec mount options on devtmpfs, this allows to provide a
bit of extra security by preventing mmapping stuff in /dev with
PROT_EXEC or having setuid executables.
[Test case]
If we really want to provide a test case for this...:
$ grep devtmpfs /proc/m
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft lockup happens the system isn't
reachable anymore via ssh and on the console we can see some exlicit rcu
stall warnings.
** Affects: zfs-linux (Ubuntu)
Importance: Undecid
Moving to Debian zfs 2.1.1 + applying the debdiff in attach seems to fix
the problem.
** Patch added: "zfs-update-to-2.1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5547343/+files/zfs-update-to-2.1.1.debdiff
** Description changed:
+ [Impact]
+
New debdiff in attach, that also includes the fix for a potential data
corruption with zfs-2.1.1 (https://github.com/openzfs/zfs/issues/12762).
** Bug watch added: github.com/openzfs/zfs/issues #12762
https://github.com/openzfs/zfs/issues/12762
** Patch added: "zfs-update-to-2.1.1-v2.debdiff"
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => 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/1951440
Title:
Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG
New debdiff to move to zfs 2.1.2 in attach.
** Patch added: "zfs-update-to-2.1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5551832/+files/zfs-update-to-2.1.2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages,
New iproute has been merged in jammy. We can close this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1951390
Title:
update iproute2 in jammy
Statu
New iproute has been merged in jammy. We can close this.
** Changed in: iproute2 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https:
Public bug reported:
Running vrf_route_leaking.sh returns the following error:
###
IPv6 (sym route): VRF ICMP fragmentation error route lookup ping
###
Public bug reported:
Script srv6_end_dt4_l3vpn_test.sh reports the following failure
(upstream issue):
15321 19:35:52 DEBUG| [stdout] #
15322 19:35:52 DEBUG| [stdout] # TE
Public bug reported:
Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error
(it seems to be an upstream issue):
15187 19:34:40 DEBUG| [stdout] #
15188 19:
This issue is still present also on jammy 5.15. Some details that I
found:
- the purpose of this test is to verify that an ICMP6 packet is not forwarded
by a virtual router if it needs to do fragmentation
- the test creates 3 network namespaces representing host1, host2 and router
- host1 a
*** This bug is a duplicate of bug 1928890 ***
https://bugs.launchpad.net/bugs/1928890
** This bug has been marked a duplicate of bug 1928890
vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test
failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
--
You
Public bug reported:
[Impact]
c4.large instances are stuck at boot with kernel 5.15.0-15.15.
[Test case]
Simply deploy a c4.large instance and install the latest jammy kernel
(5.15.0-15.15).
[Fix]
It looks like the offending commit is the following:
02c70033b98b ("PCI/MSI: Mask MSI-X vector
Update: we're still getting the same failure even with zfs 2.1.2. I've opened
an issue upstream:
https://github.com/openzfs/zfs/issues/12942
** Bug watch added: github.com/openzfs/zfs/issues #12942
https://github.com/openzfs/zfs/issues/12942
--
You received this bug notification because you
Quick summary: it really looks like a compiler issue, because everything
works using the same version of kernel + zfs, but on Impish. Also trying
to compile zfs with gcc-10 doesn't show any problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
I've tried multiple versions of gcc and here's the result:
- gcc 11.2.0-13ubuntu1 : bad
- gcc 11.2.0-12ubuntu1 : bad
- gcc 11.2.0-10ubuntu1 : bad
- gcc 11.2.0-7ubuntu2 : good
- gcc 10.3.0-13ubuntu1 : good
Apparently the last version of gcc that seems to work with zfs + kernel
5.15 is 11.2.0
** Also affects: gcc-11 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft lockup happens the system isn't
reachable anymore via ssh and on the console
rtance: Undecided => Critical
** Changed in: zfs-linux (Ubuntu Jammy)
Assignee: (unassigned) => Andrea Righi (arighi)
--
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/19
New debdiff in attach that enforces gcc-10 to build the dkms part on
s390x.
** Description changed:
[Impact]
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft lockup happens the system isn't
reachable anymore via ssh and on the console
New debdiff, because v2 was missing the gcc-10 dependency for zfs-dkms
in debian/control.
** Patch added: "zfs-update-to-2.1.2-v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+attachment/5553379/+files/zfs-update-to-2.1.2-v3.debdiff
--
You received this bug notifica
GCC: (Ubuntu 11.2.0-14ubuntu1) 11.2.0
^ This version of gcc is reverting the patch that introduces the bug. It
is possible to reproduce the bug with gcc <= 11.2.0-13ubuntu1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubu
Public bug reported:
It looks like the glibc autopkgtest in jammy for s390x is using gcc-10
and it's failing to build with the following error:
s390x-linux-gnu-gcc-10 ../sysdeps/s390/longjmp.c -c -std=gnu11 -fgnu89-inline
-pipe -O2 -g -fdebug-prefix-map=/tmp/autopkgtest.ehGgT4/build.Jkr/src=. -
** Changed in: linux (Ubuntu)
Status: Expired => 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/1943697
Title:
net veth selftest failure
Status in linux package in Ubun
Public bug reported:
kernel selftest net:test_bpf.sh can return the following error on
ppc64el and arm64:
10664 02:12:25 DEBUG| [stdout] [ 1001.533842] test_bpf: #313
BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test: 0x12 + 0xab = 0xbd
10665 02:12:25 DEBUG| [std
Public bug reported:
[Impact]
Enable AMX (aka TMUL) new instructions on the 5.15 kernel.
[Test case]
Tests have been performed directly by Intel.
[Fix]
Apply the following upstream commits:
20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test")
063452fd94d1 ("x86/fpu/xstate:
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** 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.
https://bugs.launchpad.net/bugs/1968982
Title:
Jammy update: v5.17.1 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Revert "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""
USB: serial: pl2303: add IBM device IDs
dt-bindings: usb: hcd: correct usb-device path
USB: serial: pl2303: fix GS type detection
USB: serial: simple: add Nokia phone driver
mm: kfence: fix missing objcg housekeeping for SLAB
locking/loc
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Thanks for pointing this out Andrew. It looks like this patch is relying
on AUFS that has been dropped/disabled in jammy, but it's still
available in focal, so we should definitely re-apply this patch.
I'll make sure this is re-applied to 5.13 and 5.15 (changing the code to
properly depend on AUFS
** Description changed:
+ [Impact]
+
+ Starting with 5.13 we've incorrectly dropped the following sauce patch:
+
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
+ This patch seems to be required to use overlayfs on top of shiftfs and
+ without this patch
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure (Ub
** Also affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: 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/1960362
Title:
E
** Also affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: 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/1960361
Title:
h
** Also affects: network-manager (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: urfkill (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bu
Public bug reported:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that r
** No longer affects: linux (Ubuntu 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/1983640
Title:
refactoring of overlayfs fix to report the right mnt_id of files
opened from ma
** Summary changed:
- refactoring of overlayfs fix to report the right mnt_id of files opened from
map_files
+ refactoring of overlayfs fix to properly support shiftfs
** Description changed:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
- UBUNTU
** Also affects: linux (Ubuntu Kinetic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Fix Released
** Changed in: linux (Ubuntu Kinetic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ke
Public bug reported:
[Impact]
Intel has requested to support the TDX (trust domain extension) guest
attestation driver interface. In a TDX guest "attestation" is used to
verify the trustworthiness of a TD (trusted domain) before provisioning
secrets to the TD (i.e, encrypted keys to mount an encr
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar (2.1.5) fails to
build with kernels >= 6.1.
[Test case]
$ apt install zfs-dkms
[Fix]
Resync with the latest zfs-linux from debian unstable and apply the
following upstream patch to properly support linux 6.1:
ec
** Also affects: zfs-linux (Ubuntu Lunar)
Importance: Undecided
Status: New
--
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/1998487
Title:
zfs-dkms: support linux 6.1
Statu
With the debdiff in attach applied (on top of the latest debian unstable
zfs) everything seems to work fine on the latest lunar/linux-unstable
(6.1.0-9-generic).
** Patch added: "zfs-dkms-2.1.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1998487/+attachment/5633750/+files
Public bug reported:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-linux-compat dkms). This dkms is not
maintained anymore, but upstream maintainer periodically provides
backported patches for older kernels (like 5.4) in this git repositor
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
- external module (wireguard-linux-compat dkms). This dkms is not
- maintained anymore, but upstream maintainer periodically provides
- backported patches for older kernels (like 5.4) in thi
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Summary changed:
- focal: merge wireguard into the kernel
+ focal: merge upstream wireguard
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maint
Public bug reported:
[Impact]
bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar.
Moreover, with kernels >= 5.17 there's an incorrect access to struct
netdev (see LP: #1998039).
[Test case]
$ sudo apt install bcmwl-kernel-source
[Fix]
The following upstream commits have ch
Debdiff in attach fixes the build problems with linux 6.1 and it should
also fix LP: #1998039 (once confirmed/tested we can set 1998039 as
duplicate of this one).
** Patch added: "bcmwl-kernel-6.1-and-netdev-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+attachment/
401 - 500 of 689 matches
Mail list logo
