Public bug reported:
The devlink command seems to print a warning that is considered as a
failure during this test:
435612:18:20 DEBUG| Running 'make run_tests -C net
TEST_PROGS=devlink_port_split.py TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
14357 12:18:20 DEBUG| [std
Same issue as LP: #2011748, that should be fixed by: a6d8a9c1e5fa
("arm64: efi: Use SMBIOS processor version to key off Ampere quirk")
--
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/2015741
It might be worth to report this also upstream, apparently there was a
behavior change with the blkio controller in cgroup1 that happend at
some point between 5.15 and 5.19. I'll do more tests and will let you
know if I find anything relevant. Thanks for reporting this!
--
You received this bug n
Public bug reported:
ubuntu_ltp.kernel_misc test failure on impish linux 5.13:
STARTubuntu_ltp.kernel_miscubuntu_ltp.kernel_misc
02:33:58 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189:
compare time spent with and without boost (-2%)
...
384612 Traceb
Public bug reported:
ubuntu_ltp cpuhotplug03 test is failing with the following error on
arm64:
cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on
CPU1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
Some times this test can fail with the following error:
06:20:37 DEBUG| [stdout] tag=isofs stime=1631081630 dur=0 exit=exited stat=32
core=no cu=1 cs=1
...
06:20:37 DEBUG| [stdout] Test timeouted, sending SIGKILL!
06:20:37 DEBUG| [stdout] tst_test.c:1399: TINFO: If you are r
Public bug reported:
I think we need to fix the test itself (not really a kernel issue
probably), but worth investigating:
07:35:14 DEBUG| [stdout] mount: /dev/cpuctl: cpuctl already mounted or mount
point busy.
07:35:14 DEBUG| [stdout] cpuctl_test_fj1 TFAIL : ltpapicmd.c:188: failed
to
Public bug reported:
This is an old error that doesn't seem to happen if we run this test
isolated from the others, maybe the reason is that something is not
cleaned up properly (we should probably consider to exclude this test
from the net tests and run it isolated as a separate test):
1
Public bug reported:
6:28:16 DEBUG| [stdout] tag=af_alg06 stime=1631118362 dur=0 exit=exited stat=0
core=no cu=0 cs=0
16:28:16 DEBUG| [stdout] startup='Wed Sep 8 16:26:02 2021'
16:28:16 DEBUG| [stdout] tst_test.c:1353: TINFO: Timeout per run is 0h 05m 00s
16:28:16 DEBUG| [stdout] ../../../includ
Public bug reported:
We should consider to increase the timeout for this test, because in
some slow systems it may fail with the following error:
16:25:59 DEBUG| [stdout] tag=cve-2018-101 stime=1631117534 dur=0
exit=exited stat=0 core=no cu=0 cs=0
16:25:59 DEBUG| [stdout] startup='Wed Sep 8
Public bug reported:
5.13 with KCSAN enabled reports the following bug on Xen-based
instances.
Maybe it's worth investigating to determine if they are false positives
or not, for now, I think we can just disable CONFIG_KCSAN to prevent
this boot problem:
200 01:51:29
Public bug reported:
12886 Warning: Kernel ABI header at
'tools/include/uapi/linux/if_link.h' differs from latest version at
'include/uapi/linux/if_link.h'
12887 libbpf: elf: skipping unrecognized data
section(5) .rodata.str1.1
We likely need this commit to fix this build issue, but it's not trivial
to backport it, we are going to hint the test for now:
commit 4d1b62986125b6de596c98310543652a7892e097
Author: Alexei Starovoitov
Date: Thu May 13 17:36:20 2021 -0700
selftests/bpf: Convert few tests to light skeleton
Public bug reported:
ubuntu_nbd_smoke_test seems to fail on small instances when tested in
any cloud:
355 NBD device /dev/nbd0 created
356 found nbd export
357 NBD exports found:
358 test
359 starting client with NBD device /dev/nbd0
360
Public bug reported:
This option will disable uprivileged BPF by default. It can be reenabled,
though, as it uses the new value 2 for the kernel.unprivileged_bpf_disabled
sysctl. That value disables it, but allows the sysctl knob to be set back to 0.
This allows sysadmins to enable unprivil
Public bug reported:
81727 04:16:04 INFO | START
ubuntu_ltp_syscalls.perf_event_open02ubuntu_ltp_syscalls.perf_event_open02
timestamp=1632284164timeout=900localtime=Sep 22 04:16:04
81728 04:16:04 DEBUG| Persistent state
client._recor
Public bug reported:
I can trigger the following kernel panic with the latest impish kernel
5.13.0-19-generic, running systemd autopkgtest using --enable-kvm for
the instances created by systemd to run the autotest:
[ 119.987108] BUG: kernel NULL pointer dereference, address: 0098
[
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Impish)
Assignee: (u
Additional information about this (from the memory dump that I was able
to get):
crash> gdb list *(wb_timer_fn+0x44)
0x991abcc4 is in wb_timer_fn (/build/impish/block/blk-wbt.c:237).
235 static int latency_exceeded(struct rq_wb *rwb, struct blk_rq_stat *stat)
236 {
237
https://lore.kernel.org/lkml/YW6N2qXpBU3oc50q@arighi-desktop/T/#u
^ Potential upstream fix (I tested with this one applied and I couldn't
break the kernel), let's wait for a feedback from the LKML, if that fix
is reasonable I'll send a proper SRU email to apply it to the Ubuntu
kernel.
--
You re
Public bug reported:
[Impact]
"UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file
while vmscan is active" has been applied to fix a page leaking issue.
However a slightly different fix has been applied upstream:
9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Import
** Description changed:
[Impact]
"UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file
while vmscan is active" has been applied to fix a page leaking issue.
However a slightly different fix has been applied upstream:
9a24ce5b66f9c8190d63b15f4473600db4935f1f ca
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => Co
** Description changed:
+ [Impact]
+
+ It is possible to trigger a kernel panic with the latest impish kernel
+ running systemd autopkgtest using --enable-kvm with the test instances
+ created by systemd during the autotest. The panic happens in the host,
+ not in the guest VM executed by systemd
Public bug reported:
[Impact]
KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
default, because it's introducing more problems than benefits:
https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u
This also seems to trigger QEMU bugs during the systemd au
Patch in attach (against qa-regression-testing) allows to fix this
issue.
** Patch added:
"0001-scripts-test-kernel-security.py-support-zstd-compres.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038437/+attachment/5706797/+files/0001-scripts-test-kernel-security.py-support-zstd
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.
[
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 refer
** 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 is_rust_mod
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.
**
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 tools/scri
Public bug reported:
[Impact]
Rust is only supported by amd64 at the moment, so there is no reason to
generate linux-lib-rust packages on the other architectures.
[Test case]
Simply build the kernel, generating all the deb packages.
[Fix]
Produce linux-lib-rust only on amd64.
[Regression pot
Public bug reported:
[Impact]
After migrating to the new annotations-only model in jammy we introduced
a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not
migrate to the new model and still use the old configs+annotations.
[Test case]
With debian./config/config.common.ubunt
Public bug reported:
[Impact]
At the moment we can't use the annotations scripts in focal, because we
are using the'|=' update operator for merging dicts, that has been
introduced with python 3.9.
Rewrite the code that is using this operator in a more portable way and
apply this change everywher
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
Importance: Undecid
Attached debdiff contains the SRU patch to fix the same nvidia-dkms-390
build error with kernel 6.2 for lunar.
** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675576/+fi
Wrong debdiff, here's a new one cleaned up properly, ignore comment #5.
** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675615/+files/nvidia-dkms-390-lunar-better-sup
And here's the debdiff for jammy. Same fix.
** Patch added: "nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675616/+files/nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff
--
@zniavre in comment #6 I posted a patch for lunar, so it'll be applied
also there at some point.
--
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/2019869
Title:
nvidi
Public bug reported:
[Impact]
Provide a variable do_lib_rust=true|false in the kernel build system to
selectively enable the Rust packaging (linux-lib-rust) with specific
kernels and specific architectures.
Right now Rust should be enabled only in lunar and mantic and only on
amd64.
[Test case]
** Also affects: nvidia-graphics-drivers-450-server (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-450-server in
Ubuntu.
https://bugs.launchpad.net/bugs/20
Public bug reported:
[Impact]
The lowlatency kernel in Ubuntu is specifically designed to prioritize
high responsiveness, making it ideal for multimedia environments like
DAWs and audio processing platforms, as well as soft real-time
environments.
With the introduction of a real-time kernel, it
Public bug reported:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former contains pages t
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former
** 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/2023629
Title:
enable multi-gen LRU by default
Status in li
This patch should fix this bug without breaking the behavior of
/proc/self/map_files.
Can you give it a try? I can also prepare a test kernel if you need.
** Patch added: "0001-UBUNTU-SAUCE-overlayfs-fix-reference-count-mismatch.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016
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
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 y
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/
Thank
@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: https://launchpad.net/~canonical-kernel-
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
P
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
Title
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 differe
** 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. T
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:
** 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 Ubu
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 performan
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
corre
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
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 are
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
@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,
** 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
301 - 400 of 689 matches
Mail list logo
