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
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:
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,
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
** 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
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
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,
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
** 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
** 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.
** 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
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
@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
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
** 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
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.
If the issue is fixed without the extra patch, I think we can ignore it,
it was probably a false positive from UBSAN.
Let's keep an eye on it and if it shows up again in the future we can do
a test with my additional patch. Thanks for update!
--
You received this bug notification because you
Public bug reported:
[Impact]
CONFIG_INTEL_TDX_HOST depends on !KEXEC_CORE in the latest 6.8 kernel.
This was introduced by:
cb8eb06d50fc ("x86/virt/tdx: Disable TDX host support when kexec is
enabled")
We cannot regress kexec, therefore we need to disable
CONFIG_INTEL_TDX_HOST in the generic
Looking at the code this issue seems to be introduced by `UBUNTU: SAUCE:
modpost: support arbitrary symbol length in modversion` and the UBSAN
warning tells us that accessing vers->name[0] could be an out-of-bounds
access.
The struct modversion_info contains a flexibile array (name), that is
Public bug reported:
[Impact]
The **rtla** is a meta-tool that includes a set of commands that aims to
analyze the real-time properties of Linux.
Considering the latest "low-latency" capabilities acquired by the
generic kernel and also considering the recent trend in Ubuntu to focus
on
** Changed in: linux (Ubuntu)
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/2051560
Title:
Provide python perf module
Status in linux package in
Patch sent to the kernel team mailing list for review:
https://lists.ubuntu.com/archives/kernel-team/2024-March/149751.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/2051560
Title:
** Description changed:
+ [Impact]
+
+ We need to provide the python perf module, because some applications
+ (such as tuned) require it.
+
+ This module is implemented inside perf, provided by the kernel.
+
+ At the moment we provide a distinct perf for each kernel installed in
+ the system.
Unfortunately those traces don't say much without the debugging symbols.
If it happens also with the mainline kernel we should see similar bugs
reported upstream, that's why I'm not very convinced about this being a
kernel issue. More likely a library issue, considering that it happens
with
Hm... honestly this looks more like a user-space / brave issue than a
kernel issue. Do you get similar SIGSEGV with other apps?
--
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/2058191
Can you give it a try also with the latest upstream 6.8 (available here
https://kernel.ubuntu.com/mainline/v6.8.1/). This should help to verify
if it's an upstream issue or a specific issue with the Ubuntu kernel.
Thanks!
--
You received this bug notification because you are a member of Kernel
@tijs not exactly that kernel, but a kernel that has all the fixes that
are included in 6.8.1. :)
If you are willing to do one more test to confirm that everything is
fine in the next candidate kernel for 24.04, you could try with
6.8.0-20.20 from this ppa:
I don't have the hardware at the moment. It'd be great if you could do a
test with the latest mainline build, so that we can better understand if
it's an upstream issue or something specific with the Ubuntu kernel (or
maybe a kernel .config issue):
https://kernel.ubuntu.com/mainline/v6.8.1/
The message `mce: [Hardware Error]: Machine check events logged` really
seems to indicate a potential hardware malfunction.
Can you double check if this is happening only with the latest 6.8? Do
you see anything similar in dmesg with other kernels?
--
You received this bug notification because
Can you elaborate more on the freeze part? Does the system completely
freezes and it never recovers or is it a temporary freeze (until the
copy completes)?
How much RAM do you have in your system?
Can you check if the following helps to mitigate the problem?
$ echo $((32 * 1024 * 1024)) | sudo
** 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
** 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
** 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
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
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
** 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
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,
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
** 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
@turner basically any type of I/O workload can benefit from the HZ=1000
change, I haven't posted any test result, because in the scope of this
proposal I wanted to focus mainly at the regression potential for CPU-
intensive workloads and the benefits in terms of power consumption (this
one as a
More tests and results available here:
https://discourse.ubuntu.com/t/enable-low-latency-features-in-the-
generic-ubuntu-kernel-for-24-04/42255
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@andysem yes that is also another possibility. The idea is to do a lot
of tests and if we find that there's a remote possibility to introduce
significant performance regressions in certain cases we can still keep
HZ=250, but definitely go with the other options.
--
You received this bug
@dsmythies IIUC this happens also with a mainline kernel, right? Not
just the Ubuntu lowlatency one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency-hwe-6.5 in
Ubuntu.
https://bugs.launchpad.net/bugs/2051733
@andysem correct, without `nohz_full` specified at boot
CONFIG_NO_HZ_FULL has no effect, except for the little extra overhead
that it's adding to the tick handler (there is still some overhead with
this option enabled, even if it's not used). That's why I'd like to
measure the time spent in some
@colin-king noticed, I just left a thank you message in the article.
I'll still do the tests, but it's nice to see that someone else is
contributing to this!
Another thing that I'd like to measure is to bpftrace the time spent in
the tick handler before and after these changes applied, because we
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
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: Confirmed
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
--
You received this bug notification because you are
@colin-king thanks! Any suggestion in particular? I was thinking to
lmbench, netperf and fio.
--
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
@dsmythies thank you so much for sharing the results of your tests,
really useful info!
I'm planning to do more tests setting the performance governor, I've
been doing my initial tests only with the default Ubuntu settings, that
means with the "Balanced" power mode enabled (that I think it's
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements,
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements,
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements,
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements,
Public bug reported:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but the only
** Also affects: linux (Ubuntu Noble)
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/2045503
Title:
apply sched-ext patch set to
** 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/2046040
Title:
enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for
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
** Also affects: linux (Ubuntu Noble)
Importance: Critical
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/2028253
Title:
update apparmor and LSM stacking
The same problem happens also with nvidia-dkms-545 (still on arm64
only).
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
[Impact]
It looks like nvidia-dkms-535 is using a symbol that became GPL-only in
the latest 6.7 kernel, causing the following build error:
# MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
scripts/mod/modpost -M -m -a -o
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 =
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
** 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
** 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
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
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
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
** 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
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
Public bug reported:
The following patch may break user-space, providing an actual ABI
change:
UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion
This is not critical for new releases (also considering that the
potential breakage is unlikely to happen, unless some
Public bug reported:
Providing zstd compressed modules may break user-space
scripts/tools/binaries that are relying on the .ko naming schema.
The kernel can still support ZSTD compressed modules (via
CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be
just regular .ko files.
**
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
--
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/2038611
Title:
drop all references to
Public bug reported:
[Impact]
The script tools/is_rust_module.sh has been dropped by this commit:
079c66bbe2f8 ("UBUNTU: SAUCE: btf, scripts: rust: drop
is_rust_module.sh")
And upstream as well (in 6.6):
41bdc6decda0 ("btf, scripts: rust: drop is_rust_module.sh")
But we still have a
Public bug reported:
[Impact]
Now that all the filesystems that we officially support have the
idmapped mounts capability we can get rid of shiftfs.
The benefit of this change is that we don't have to maintain an out-of-
tree filesystem anymore and we can completely rely on upstream features.
Patch in attach (against qa-regression-testing) allows to fix this
issue.
** Patch added:
"0001-scripts-test-kernel-security.py-support-zstd-compres.patch"
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
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
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/2030525
Title:
Installation support for SMARC RZ/G2L
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
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
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
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
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
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
** 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
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
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
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
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
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
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
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
** 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
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)
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.
@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
@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
** 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)
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,
1 - 100 of 689 matches
Mail list logo
