Changing the state to Won't fix, because of LP: #2059762.
** Changed in: linux (Ubuntu Noble)
Status: Fix Released => Won't Fix
--
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/204604
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2059080
Title:
Add Real-time Linux Analysis tool (rtla) to linux-to
Applied all the listed commits to noble/linux, including also:
9c55461040a9 ("x86/efistub: Remap kernel text read-only before dropping
NX attribute")
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix
Any news? Pulling firmware from upstream is enough to solve this issue.
--
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/2058830
Title:
vp9 hw decode broken on modern AMD apus, ne
@tijs thanks for testing it! If 6.8.0-19 is working I assume that also
the latest kernel in release (6.8.0-22.22) is also working. If that's
the case I think we can close this for now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Public bug reported:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of indirect branch pre
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
** Description changed:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect b
** Summary changed:
- Backport mitigations for the native BHI hardware vulnerabilty
+ Apply mitigations for the native BHI hardware vulnerabilty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Description changed:
[Impact]
Branch History Injection (BHI) attacks may allow a malicious application
to influence indirect branch prediction in kernel by poisoning the
branch history. eIBRS isolates indirect branch targets in ring0.
The BHB can still influence the choice of in
According to the information that I collected (asking around,
investigating, etc.), it seems that there are no critical users of
ubuntu-fan.
Moreover, considering the impact of the ubuntu-fan kernel patches (that
would require a major refactoring to avoid breaking the network eBPF
ABI), we decided
Public bug reported:
[Impact]
In order to provide ubuntu-fan we need to maintain additional kernel
SAUCE patches that are currently conflicting with upstream code,
potentially breaking networking eBPF APIs.
To prevent such incompatibility the whole patch set requires a major
redesign.
However,
unfortunately the problem is not actually gone in noble. I have upgraded
to the beta and are having significant but intermittent problems. On
6.8.0-31-generic I get periods of normal traffic mixed with 100% packet
loss for some seconds. This looks as follows:
64 bytes from 192.168.16.77: icmp_seq=
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
** Summary changed:
- Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15
+ Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT
I don't see these messages with the latest Noble using the kernel from
the proposed pocket (6.8.0-11-generic). Can you also give it a try (if
you can)?
Hopefully we'll be able to promote a 6.8 in release soon, we are
currently blocked by a glibc regression (that doesn't seem to be a
kernel regress
For the general use case I think that reducing the verbosity makes
sense. About our testing, I think we're not booting kernels with
"quiet", and if we do we should definitely drop it from the kernel boot
options.
--
You received this bug notification because you are a member of Kernel
Packages, w
** Changed in: linux (Ubuntu Noble)
Status: New => 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/1951440
Title:
Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_IN
I haven't been able to reproduce this on my PC yet... Looking at the
error, especially the virtio-fs part, I'm wondering if you're missing
virtiofsd in your host. Can you try to `apt install virtiofsd` (if you
don't have it installed already)?
--
You received this bug notification because you are
Public bug reported:
[Impact]
In linux 6.8 the coretemp driver supports at most 128 cores per package.
Cores higher than 128 will lose their core temperature information.
There is an upstream patch set that allows to support more than 128
cores per package, but it's applied to linux-next for now
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2056126
Title:
hwmon: (coretemp) Fix core count limitation
Status
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2051342
Title:
Enable lowlatency settings in the generic kernel
St
** Changed in: linux (Ubuntu Noble)
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/2056616
Title:
left-over ceph debugging printks
Status in
This is still failing in mantic, "something" in our kernel cranking
process re-added the chmod command in debian.master/reconstruct for
is_rust_module.sh, this needs further investigation.
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-failed-mantic
--
You received
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic
--
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/2038522
Title:
disable shiftfs
Status in linux p
shiftfs has been correctly disabled in 6.5.0-14:
$ uname -r
6.5.0-14-generic
$ sudo modprobe shiftfs
modprobe: FATAL: Module shiftfs not found in directory
/lib/modules/6.5.0-14-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
Public bug reported:
[Impact]
With LP: #2023007 we have decided to enable CONFIG_RCU_LAZY in the
lowlatency kernel to improve power consumption, but this option can
potentially introduce performance regressions in some cases, due to the
fact that RCU callbacks are now batched and flushed all at o
Public bug reported:
[Impact]
sched-ext is a new scheduling class introduced in the Linux kernel that
provides a mechanism to implement scheduling policies as eBPF programs
(https://lwn.net/Articles/922405/). Such programs can also be connected
to user-space counterparts to defer scheduling decis
** Description changed:
[Impact]
sched-ext is a new scheduling class introduced in the Linux kernel that
provides a mechanism to implement scheduling policies as eBPF programs
(https://lwn.net/Articles/922405/). Such programs can also be connected
to user-space counterparts to defer s
** Description changed:
[Impact]
sched-ext is a new scheduling class introduced in the Linux kernel that
provides a mechanism to implement scheduling policies as eBPF programs
(https://lwn.net/Articles/922405/). Such programs can also be connected
to user-space counterparts to defer s
Public bug reported:
[Impact]
Intel Trust Domain Extensions (TDX) protects guest VMs from malicious host and
certain physical attacks.
Linux 6.7 introduced the TDX support for the host to run confidential VMs (TDX
guests).
[Test case]
We should probably define with Intel a proper test case to
Public bug reported:
[Impact]
/var/lib/dkms/nvidia/535.129.03/build/nvidia/libspdm_shash.c:90:26: error:
implicit declaration of function ‘crypto_tfm_ctx_aligned’; did you mean
‘crypto_tfm_ctx_align’? [-Werror=implicit-function-declaration]
90 | char *src_ipad = crypto_tfm_ctx_aligne
Hello, any progress on this? Now that ubuntu-fan is officially
deprecated in Noble can we simply sync iproute2 with Debian? Is there
any pending activity / requirement that are preventing this? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Summary changed:
- apply sched-ext patch set to linux-unstable
+ provide a sched-ext enabled kernel for the 24.10 release
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Noble)
--
You received this bug notification bec
Thanks @dannf for updating the bug! The SRU description looks good to me
and everything seems reasonable, same with the plan.
I'll keep monitoring this tracker and we'll proceed once oracular will
be open.
--
You received this bug notification because you are a member of Kernel
Packages, which i
Public bug reported:
[Impact]
In LP: #2063298, we have opted to deprecate Ubuntu FAN support because
of the maintenance overhead and the possibility of regressions /
conflicts with the new networking eBPF APIs in kernels >= 6.8.
However, we cannot disable this feature in HWE/backport kernels, so
Patch set to re-enable Ubuntu FAN in the 6.8 Noble kernel:
https://lists.ubuntu.com/archives/kernel-team/2024-May/150684.html
--
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/2064508
Title:
Test result with the patch set applied (ubuntu_fan_smoke_test):
11:48:05 INFO | Writing results to /home/ubuntu/autotest/client/results/default
11:48:05 INFO | START timestamp=1714564085localtime=May
01 11:48:05
11:48:05 INFO | START ubuntu_fan_smoke_test.setup
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Assignee: Andrea Righi (arighi)
Status: New
** Also affects: linux-aws-5.0 (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects: linux-aws (Ubuntu Eoan)
Importance: Undecided
Status
Status: New
** Also affects: linux-aws-5.0 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Eoan)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux-aws (Ubuntu Focal)
Assignee: Kamal Mostafa (kamalmostafa) =>
Hi Seth, is this still happening with the latest focal kernel? I'm
trying to reproduce the problem, but I can't:
$ cat /proc/version_signature
Ubuntu 5.4.0-18.22-generic 5.4.24
righiandr@xps-13:~$ apt policy fatrace
fatrace:
Installed: 0.13-2
Candidate: 0.13-2
Version table:
*** 0.13-2 500
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
ewest Ubuntu 22.04, and haven't tested yet here (a
little bit scared, evaluating pro and cons...)
Cheers,
Andrea
Il giorno lun 16 mag 2022 alle ore 07:01 Adolfo Jayme <
1810...@bugs.launchpad.net> ha scritto:
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Wishlist
&
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
501 - 600 of 851 matches
Mail list logo
