Public bug reported:
[Impact]
Hibernation is still unreliable on c5.18xlarge instances, usually the
system hibernates correctly, but on resume it either perfoms a regular
reboot instead of resuming from hibernation, or the system is completely
stuck after the hibernated kernel is loaded in memory
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1918694
Title:
aws: fix hibernation issues on c5.
eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
New debdiff on top of Debian zfs-linux 2.1.9-2. Smoke-tested in a local
VM. Thanks!
** Patch added: "zfs-linux-2.1.9-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+attachment/5651251/+files/zfs-linux-2.1.9-2.debdiff
--
You received this bug notification because
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:
[Impact]
nvidia-dkms-390 fails to build with linux 6.2:
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[Fix]
Chang
debdiff in attatch allows to build nvidia-dkms-390 with linux 6.2.
** Patch added: "nvidia-390-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5651284/+files/nvidia-390-support-linux-6.2.debdiff
--
You received this bu
Public bug reported:
[Impact]
nvidia-dkms-470 fails to build with linux 6.2:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[Fix]
Change the driver to support also the 6.2 kernel ABI.
[Test case]
With linux 6.2 installed, run:
$
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
--
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/2009142
Tit
debdiff in attach allows to use nvidia-dkms-470 with linux 6.2.
** Patch added: "nvidia-470-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2009246/+attachment/5651505/+files/nvidia-470-support-linux-6.2.debdiff
--
You received this bug n
Public bug reported:
[Impact]
nvidia-dkms-510 fails to build with linux 6.2, reporting the following
error:
/var/lib/dkms/nvidia/510.108.03/build/nvidia-drm/nvidia-drm-drv.c:245:21:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
|
** Summary changed:
- nvidia-dkms-390 FTBS with linux 6.2
+ nvidia-dkms-470 FTBS with linux 6.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2009246
Title:
nvidi
debdiff in attach allows to use nvidia-dkms-510 with linux 6.2.
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Patch
Public bug reported:
[Impact]
nvidia-dkms-515 fails to build with linux 6.2, reporting the following
error:
/var/lib/dkms/nvidia/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
|
Public bug reported:
[Impact]
nvidia-dkms-450-server fails to build with linux 6.2, reporting the
following error:
/var/lib/dkms/nvidia-srv/450.216.04/build/nvidia/nv-acpi.c:84:19: error:
initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer
type ‘int (*)(struct acpi_dev
Public bug reported:
[Impact]
nvidia-dkms-470-server fails to build with linux 6.2:
/var/lib/dkms/nvidia-srv/470.161.03/build/nvidia/nv-acpi.c:84:19: error:
initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer
type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompati
debdiff in attach allows to use nvidia-dkms-470-server with linux 6.2.
** Patch added: "nvidia-470-server-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2009254/+attachment/5651533/+files/nvidia-470-server-support-linux-6.2.debdiff
Public bug reported:
[Impact]
nvidia-dkms-515-server fails to build with linux 6.2:
/var/lib/dkms/nvidia-srv/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
| ^
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]
TDX guest attestation has been merged as SAUCE patches in the kinetic
kernel with the following commits:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next&id=285d6d8136ebadcee7fd6452b9e4223996a2a0af
https://git.launchpa
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: 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/1989983
Title:
kinetic: apply new apparmor and L
This was fixed during the regular rebase with upstream. We can close
this one now.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member o
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
It looks like this problem has been introduce by this commit:
a5ddd0de7d8b ("UBUNTU: [Packaging] install headers to debian/linux-libc-
dev directly")
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/lunar/commit/?id=a5ddd0de7d8b2159fc5f8df55527e0e447328953
It seems to include
I've applied this change to lunar. Next lunar 6.2 kernel will have
CONFIG_SERIAL_8250_MID=y.
--
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/2009283
Title:
linux: CONFIG_SERIAL_8250_MID=y
** Also affects: linux (Ubuntu Lunar)
Importance: Critical
Status: 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/2009355
Title:
linux-libc-dev is no longer multi-arc
** Description changed:
+ [Impact]
+
+ CONFIG_SERIAL_8250_MID=y is required to properly use the serial console
+ on some platforms that are using the "mid" serial driver (such as some
+ Intel SoC platforms).
+
+ The generic kernel should build this driver statically to make sure we
+ properly su
Public bug reported:
[Impact]
Try to boot the latest lunar/linux 6.2.0-16.16 on a ppc64 VM triggers
the following bug at boot:
event-sources: Unable to request interrupt 23 for /event-sources/hot-plug-events
WARNING: CPU: 0 PID: 1 at arch/powerpc/platforms/pseries/event_sources.c:26
request_eve
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
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]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30 GPs behind) idle=b
** Description changed:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30
Public bug reported:
[Impact]
Refresh LSM stacking and AppArmor patch sets in linux 6.2. These patches
are required to properly support the new Apparmor features in Ubuntu.
[Test case]
Run Apparmor test cases included in our QA regression testing suite.
[Fix]
Patch set shared in the kernel-te
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => 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/2011748
Title:
lunar/linux 6.2 fails to boot on arm64
Statu
lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
uname -r
6.1.0-1025-oem
sudo dmidecode -s bios-version
2.5.0
Touchpad firmware: 2023.06.05.519, A03
https://www.dell.com/support/home/it-it/drivers/driversdetails?driverid=twdxv&oscode=ubt22&productc
Public bug reported:
[Impact]
zfs-dkms fails to build on jammy with the latest linux hwe 5.19:
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17
[Test case]
$ sudo apt install zfs-dkms
[Fix]
The most reliable fix is probably to move to the same version that is
a
debdiff in attach (that doesn't change anything, it's basically a resync
of the same version in kinetic, recompiled with the jammy toolchain).
With this applied I was able to successfully run ubuntu_zfs_smoke_test
and ubuntu_zfs_stress both on 5.15 and 5.19.
** Patch added: "jammy-zfs-dkms-resync
I confirm that this fix
(https://lore.kernel.org/all/patch-1.thread-41c676.git-41c676c2d153.your-
ad-here.call-01675030179-ext-9637@work.hours/) applied to lunar/linux-
unstable seems to fix the initramfs boot problem, with this fix applied
we can restore the upstream zstd. Thanks!
--
You receive
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: zfs-linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
I just tested autopkgtest and our kernel regression zfs testsuite
(ubuntu_zfs, ubuntu_zfs_fstest, ubuntu_zfs_smoke_test,
ubuntu_zfs_stress, ubuntu_zfs_xfs_generic) both with the new 5.19 kernel
and stock 5.15 in jammy. Everything looks good, no error. I'm trying to
figure out how to test the zsys i
Public bug reported:
[Impact]
Trying to install nvidia-dkms-390 with linux 6.1 in lunar produces the
following error:
error: ‘struct acpi_device’ has no member named ‘children’
[Test case]
$ sudo apt install nvidia-dkms-390
[Fix]
Support linux 6.1 ABI.
[Regression potential]
We may expe
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphi
debdiff in attach disables ACPI support with kernel >= 6.0 and it allows
to use this driver with the latest 6.1 kernel (this should be probably
considered a temporary workaround, until nvidia provides an updated
version of this driver with a proper fix).
** Patch added: "nvidia-dkms-390-support-li
Public bug reported:
[Impact]
dm-writeboost-dkms fails to build with linux 6.1 in lunar with the
following error(s):
/home/righiandr/src/dm-writeboost/src/dm-writeboost.h:506:46: error: ‘struct
dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’?
506 | #define req_is_write(req)
I performed a smoke test with v4l2loopback-dkms in jammy, everything
looks good.
Test case:
$ sudo apt install v4l2loopback-dkms
...
$ sudo modprobe v4l2loopback devices=1 video_nr=8 exclusive_caps=1
max_buffers=2
$ sudo v4l2loopback-ctl set-fps 60 /dev/video8
OK
$ sudo v4l2-ctl --list-device
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1980484
Title:
temporarily disable CONFIG_X86_KERNEL_IBT
=
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
type: HelloRust,
name: "hello_rust",
author: "Andrea Righi ",
description: "Rust hello world example",
license: "GPL",
}
struc
lo_rust.rs ==
+
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
- type: RustMinimal,
- name: b"hello_rust",
- author: b"Andrea Righi ",
- description: b"Rust hello world example",
-
"hello world" test module:
+ Build the following "hello world" test module:
== hello_rust.rs ==
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
- type: HelloRust,
- name: "hello_rust"
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.2, reporting the following configure error:
configure: error:
*** None of the expected "iops->get_acl()" interfaces were detected.
*** This may be because your kerne
debdiff in attach applied to zfs-2.1.9 from Debian seems to work fine on
linux 6.2
** Description changed:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.2, reporting the following configure error:
- configure: error:
- *** None of
Public bug reported:
[Impact]
We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel
to provide additional features that are not available in the upstream
AppArmor.
We have experienced occasional bugs in the lunar kernel (specifically
with the environ.sh test) that can lead to
Potential upstream fix:
https://lore.kernel.org/lkml/20230401094708.77631-1-hanjinke@bytedance.com/
However this seems to partially restore the old behavior of cgroup v1,
because we still need to set io throttling limits in order to get the io
statistics.
We may need an additional fix like th
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.3.
[Test case]
$ apt install zfs-dkms
[Fix]
Resync with zfs version in Debian (2.1.1) and apply the usual Ubuntu
specific changes.
[Regression potential]
We may experience zfs r
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-gcp (Ubuntu)
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also a
** Description changed:
+ [Impact]
+
+ Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced a
+ behavior change in the blkio throttle cgroup subsystem: IO statistics
+ are not reported anymore unless a throttling rule is explicitly defined,
+ because the current code only counts
** Description changed:
+ [Impact]
+
+ After enabling Rust support in the kernel we noticed an increased size
+ in linux-headers, because all the Rust libraries required to build out-
+ of-tree kernel modules are now included in linux-headers directly.
+
+ The increased size goes from ~30MB to
** Description changed:
[Impact]
Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced a
behavior change in the blkio throttle cgroup subsystem: IO statistics
are not reported anymore unless a throttling rule is explicitly defined,
because the current code only counts
Public bug reported:
[Impact]
Starting with lunar we have introduced a new way to manage kernel
configs, unifying the duplicated information defined in the annotations
file + config chunks into an annotations-only model.
[Test case]
An kernel build can be considered a valid test case, in partic
** Description changed:
[Impact]
Starting with lunar we have introduced a new way to manage kernel
configs, unifying the duplicated information defined in the annotations
file + config chunks into an annotations-only model.
[Test case]
- An kernel build can be considered a valid
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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/2009142
Title:
Moving jammy to the same version of the driver used in lunar allows to
use nvidia-dkms-390 both with the stock 5.15 kernel and the new hwe 6.2
(verified in a VM doing a simple test build).
** Patch added: "nvidia-dkms-390-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics
Better debdiff to backport only the patch required to support linux 6.2
(that is much better from an SRU perspective). Tested with positive
result in a VM both with 5.15 and the new hwe 6.2 kernels. So, please
ignore my previous comment.
** Patch added: "nvidia-dkms-390-jammy-support-linux-6.2.deb
Public bug reported:
[Impact]
Instead of disabling acpi support completely with nvidia-dkms-390, we
should try instead to see if it's possible to support it somehow.
[Fix]
This patch looks promising (even if it says huge hack in the comments...):
https://gitlab.com/herecura/packages/nvidia-390x
** Patch added: "nvidia-dkms-390-mantic-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5673352/+files/nvidia-dkms-390-mantic-better-support-for-linux-6.2.debdiff
--
You received this bug notification because
Test kernel with the additional overlayfs fix applied:
https://kernel.ubuntu.com/~arighi/lp2016398/
--
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/2016398
Title:
stacked overlay file sys
@bluescreen-avenger thanks for testing, I'll send a proper SRU email to
apply this fix to the affected kernels!
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: l
** Description changed:
+ [Impact]
+
+ Opened files reported in /proc/pid/map_files can be shows with the wrong
+ mount point using overlayfs with filesystem namspaces.
+
+ This incorrect behavior is fixed:
+
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
** Changed in: linux-lowlatency (Ubuntu Mantic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/2023007
Title:
kernel .config lowlatency imp
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2021605
Title:
introduce do_lib_rust=true|false to enab
Public bug reported:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol length
in modversion")
This patch can potentially introduce a user-space regression, beca
** Also affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Jammy)
** Changed in: linux-hwe-6.2 (Ubuntu Jammy)
Status: New => Fix Committed
** Also affects: linux-lowlatency-hwe-6.2 (Ubuntu)
@mihalicyn yes, it looks like we are missing "UBUNTU: SAUCE: overlayfs:
allow with shiftfs as underlay" in all the kernels >= 6.2. I'll open a
separate bug for this.
I'm wondering... do we really need to support overlayfs on top of
shiftfs? Of course we don't want to break the old behavior, so the
@mihalicyn update: I did some tests and even if we're missing
d24b8a547be1 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay") in kernels >= 6.2 I'm able to use overlayfs on top of shiftfs
(using the shiftfs mount-point as lower). I even tried the test case
mentioned in the commit and I co
Between 6.2.0-1006-kvm and 6.2.0-1007-kvm the main kernel changed from
6.2.0-23 to 6.2.0-24, but the changes are minimal (only 2 fixes), that
seem unrelated to any potential size increase.
Maybe there was a toolchain/binutils update? I'll check the binaries to
see if I spot something interesting.
Applied to mantic/linux-unstable:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable/commit/?id=6f2091e61e72ed73f92cf49d882fb19c50dd860c
Do you think we should SRU this change to lunar kernels (and jammy as
well)?
Thanks!
** Also affects: linux (Ubuntu Mantic)
Impo
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
+ The ubunt
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:
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
Public bug reported:
[Impact]
Provide an updated patch set for apparmor / LSM stacking with all the
custom features that we need in the Ubuntu kernel.
This patch set is required to provide the proper confinement with snaps
and other Ubuntu-specific security features.
[Fix]
Apply the latest upd
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 Mantic)
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/2028253
Title:
update apparmor and LSM stacking patch set
S
Public bug reported:
[Impact]
When the zfs module is loaded we can see the following errors in dmesg
with the latest 6.5 kernel in mantic:
[ 10.730318] UBSAN: array-index-out-of-bounds in
/build/mantic/debian/build/build-generic/
debdiff in attach fixes the UBSAN warnings with linux 6.5 on mantic.
** Patch added: "zfs-fix-ubsan-warnings.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2033385/+attachment/5696047/+files/zfs-fix-ubsan-warnings.debdiff
--
You received this bug notification because you a
Add LP bug reference to the changelog.
** Patch added: "zfs-fix-ubsan-warnings.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2033385/+attachment/5696048/+files/zfs-fix-ubsan-warnings.debdiff
--
You received this bug notification because you are a member of Kernel
Packages
Public bug reported:
[Impact]
On unload the spl module is not properly cleaning up the registered
sysctl entries with kernel 6.5 in Mantic:
06:58 ubuntu@mantic$ sudo modprobe spl
modprobe: ERROR: could not insert 'spl': Protocol driver not attached
06:58 ubuntu@mantic$ sudo dmesg | grep duplicat
Upstream pull request to fix this issue:
https://github.com/openzfs/zfs/pull/15239
--
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/2034510
Title:
spl fails to unregister sysctl entrie
Attached debdiff seems to fix the bug (reproduced and tested in a local
VM with the latest Mantic 6.5 kernel).
** Patch added: "spl-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2034510/+attachment/5697900/+files/spl-fix.debdiff
--
You received this bug notification b
** Changed in: linux (Ubuntu Mantic)
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/2030525
Title:
Installation support for SMARC RZ/G2L platfor
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:
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
This bug should be fixed by 458ec0c8f359 ("drm/i915: fix null pointer
dereference"), I'll prepare a test kernel with this fix applied on top
of 5.19.0-19.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://b
Test kernel (5.19.0-19.19+i915fix) available here:
https://kernel.ubuntu.com/~arighi/lp-1991703/
It would be great if someone affected by this problem could test this
out. Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
701 - 800 of 851 matches
Mail list logo
