[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
I have an update on this. I've talked with the LXD team during the engineering sprint in Madrid and at the moment we can't break ubuntu-fan or we could potentially break some running LXD installations. I asked the LXD team to start working as soon as possible to remove the support for this feature, that at this point is going happen in Oracular. Therefore, good job with the iproute2 sync in Oracular @dannf. Unfortunately in Noble we still need to wait for now and support ubuntu- fan... In the meantime I've sent an updated patch set to re-enable ubuntu-fan in the kernel (with a small redesign to prevent potential incompatibilities with the upstream vxlan_policy rules): https://lists.ubuntu.com/archives/kernel-team/2024-May/150684.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
** Description changed:
+ [Impact]
+
+ It seems that kernel 6.8 introduced a regression in the 9pfs related to
+ caching and netfslib, that can cause some user-space apps to read
+ content from files that is not up-to-date (when they are used in a
+ producer/consumer fashion).
+
+ It seems that the offending commit is this one:
+
+ 80105ed2fd27 ("9p: Use netfslib read/write_iter")
+
+ Reverting the commit seems to fix the problem. However the actual bug
+ might be in netfslib or how netfslib is used in the 9p context.
+
+ The regression has been reported upstream and we are still investigating
+ (https://lore.kernel.org/lkml/Zj0ErxVBE3DYT2Ea@gpd/).
+
+ In the meantime it probably makes sense to temporarily revert the commit
+ as a SAUCE patch. Then we will drop the SAUCE patch once we'll have a
+ proper fix upstream.
+
+ [Test case]
+
+ The following test should complete correctly without any timeout:
+
+ pull-lp-source -d hello
+ autopkgtest-buildvm-ubuntu-cloud -r noble
+ autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
+
+
+ [Fix]
+
+ Revert the following commit (until we have a proper fix upstream):
+
+ 80105ed2fd27 ("9p: Use netfslib read/write_iter")
+
+ [Regression potential]
+
+ We may experience other regressions related to 9pfs with this change,
+ however it's quite unlikely to happen since we are reverting a commit,
+ restoring the previous behavior.
+
+ [Original bug report]
+
autopkgtest-virt-qemu sometimes hangs when running tests on noble
images. Originally reported by schopin, who also provided a reproducer:
- pull-lp-source -d hello
- autopkgtest-buildvm-ubuntu-cloud -r noble
- autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
+ pull-lp-source -d hello
+ autopkgtest-buildvm-ubuntu-cloud -r noble
+ autopkgtest -U hello*.dsc -- qemu ./autopkgtest-noble-amd64.img
I've been able to reproduce it with debugging enabled:
- autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
+ autopkgtest -ddd -U hello_2.10-3.dsc -- qemu --debug --show-boot
/path/to/image
It can get stuck during different stages, but AFAICT always during
"copydown" operations, log excerpts follow. It may be a coincidence, but
this started happening around the time linux-image-6.8.0-11-generic
(6.8.0-11.11) migrated to noble. The testbeds I used booted 6.6 but then
rebooted into that 6.8 kernel after being upgraded by autopkgtest.
-- logs --
Removing autopkgtest-satdep (0) ...
[...]
autopkgtest-virt-qemu: DBG: executing copydown
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ /t/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory',
'/tmp/autopkgtest.output.g8v75e]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader
name='/dev/null'>", 'deststdout']
autopkgtest-virt-qemu: DBG: +< tar --directory
/tmp/autopkgtest.output.g8v75e8g/tests-tree/ --
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.ztmr6f5k/runcmd sh -ec
if ! test -d /tmp-
autopkgtest-virt-qemu: DBG: +>?
-- or --
autopkgtest: DBG: sending command to testbed: copydown
/tmp/autopkgtest.output.c9utq3bx/tests-tree/
/tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: executing copydown
/tmp/autopkgtest.output.c9utq3bx/tests-tree/
/tmp/autopkgtest.H8NDfW/build.DLR/src/
autopkgtest-virt-qemu: DBG: ['cmdls', "(['tar', '--directory',
'/tmp/autopkgtest.output.c9utq3bx/tests-tree/', '--warning=none', '-c', '.',
'-f', '-'], ['/tmp/autopkgtest-qemu.qtkcgg5l/runcm]
autopkgtest-virt-qemu: DBG: ['srcstdin', "<_io.BufferedReader
name='/dev/null'>", 'deststdout', "<_io.BufferedReader name='/dev/null'>",
'devnull_read', <_io.BufferedReader name='/dev/null'>]
autopkgtest-virt-qemu: DBG: +< tar --directory
/tmp/autopkgtest.output.c9utq3bx/tests-tree/ --warning=none -c . -f -
autopkgtest-virt-qemu: DBG: +> /tmp/autopkgtest-qemu.qtkcgg5l/runcmd sh -ec
if ! test -d /tmp/autopkgtest.H8NDfW/build.DLR/src/; then mkdir --
/tmp/autopkgtest.H8NDfW/build.DLR/src/; fi; cd-
autopkgtest-virt-qemu: DBG: +>?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
I've uploaded a test kernel here:
https://people.canonical.com/~arighi/lp2056461/amd64/
With this one I can't reproduce the problem. It'd be great if someone
else could test it as well, to confirm that it's actually fixing the
problem.
Note: this kernel is a 6.8.0-32.32 with this commit reverted:
commit 80105ed2fd27 ("9p: Use netfslib read/write_iter")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
I've done some bisecting and it looks like the culprit is this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80105ed2fd2715fb09a8fdb0655a8bdc86c120db I'll prepare a test kernel with this one reverted, then if it's confirmed, we can figure out a proper fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056461 Title: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
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 ubuntu_fan_smoke_test.setup timeout=1200timestamp=1714564085 localtime=May 01 11:48:05 11:48:07 INFO | GOODubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timestamp=1714564087localtime=May 01 11:48:07 completed successfully 11:48:07 INFO | END GOODubuntu_fan_smoke_test.setup ubuntu_fan_smoke_test.setup timestamp=1714564087localtime=May 01 11:48:07 11:48:07 INFO | START ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimeout=1800timestamp=1714564087 localtime=May 01 11:48:07 11:51:46 INFO | Testing Fan Networking (pre-0.13.0 API) 11:51:46 INFO | docker pull --platform linux/amd64 ubuntu: PASSED 11:51:46 INFO | enable disable fan test: PASSED 11:51:46 INFO | fanctl show test: PASSED 11:51:46 INFO | fanctl check bridge config test: PASSED 11:51:46 INFO | fanatic docker test(--dns=192.168.122.1): PASSED 11:51:47 INFO | GOODubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1714564307localtime=May 01 11:51:47 completed successfully 11:51:47 INFO | END GOODubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-testtimestamp=1714564307localtime=May 01 11:51:47 11:51:47 INFO | END GOODtimestamp=1714564307 localtime=May 01 11:51:47 11:51:47 INFO | Report successfully generated at /home/ubuntu/autotest/client/results/default/job_report.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064508] [NEW] re-enable Ubuntu FAN in the Noble kernel
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 it seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper co-existence with the updated vxlan policy requirements in newer 6.8 kernels. The re-introduction of Ubuntu FAN should be considered as a temporary measure, aimed at facilitating a smooth transition during its deprecation without disrupting existing users (specifically Juju), and enabling the backporting of 6.8 kernels to older releases. The main plan is still to deprecate Ubuntu FAN in newer releases. [Test case] Rely on the specific Ubuntu FAN regression test to validate the proper kernel support of this feature: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client- tests/tree/ubuntu_fan_smoke_test?h=autotest3 [Fix] Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to satisfy the strict length validation check. [Regression potential] We may experience regressions with eBPF vxlan capabilities and potentially specific use cases of the Ubuntu FAN technology (Juju installations). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064508 Title: re-enable Ubuntu FAN in the Noble kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2045503] Re: provide a sched-ext enabled kernel for the 24.10 release
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2045503 Title: provide a sched-ext enabled kernel for the 24.10 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063298] [NEW] deprecate ubuntu-fan in Noble
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, after investigations and a detailed assessment we have not found any relevant real-world use-case that still requuires ubuntu-fan, as most of its features are now available in the upstream kernel and user-space tools, using alternative solutions. Moreover, maintaining ubuntu-fan is also slowing down / preventing the development of other packages (see for example LP: #2051672). Therefore, we are proposing to deprecate ubuntu-fan starting with noble. [Test case] We have ubuntu-fan test cases in our regression testing suite. Such tests are expected to fail with the noble kernel, so we can hint/disable them in Noble. [Fix] Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu kernel. [Regression potential] There are still some existing tools/systems that may still rely on ubuntu-fan, so we may experience regressions when such systems are moving to noble. However, the potential of breaking eBPF networking has a much higher impact, so we can probably workaround any potential ubuntu-fan regression using alternative upstream solutions. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063298 Title: deprecate ubuntu-fan in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2063298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
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 to proceed with the plan to deprecate this feature in all the noble kernels. Therefore, all the user-space components that rely on such feature can follow the same plan and drop their corresponding ubuntu-fan support (iproute2 included). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061727] Re: bpfcc-tools autotest failure when multiple linux-tools- packages are installed
Test plan:
- without this change:
/usr/lib/linux-tools-6.8.0-22/bpftool /usr/lib/linux-tools-6.8.0-25/bpftool gen
skeleton /tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.bpf.o >
/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h
Usage: bpftool [OPTIONS] OBJECT { COMMAND | help }
bpftool batch file FILE
bpftool version
OBJECT := { prog | map | link | cgroup | perf | net | feature | btf |
gen | struct_ops | iter }
OPTIONS := { {-j|--json} [{-p|--pretty}] | {-d|--debug} |
{-V|--version} }
make[2]: *** [Makefile:192:
/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h] Error 255
make[2]: *** Deleting file
'/tmp/bpfcc-0.29.1+ds/libbpf-tools/.output/bashreadline.skel.h'
make[2]: Leaving directory '/tmp/bpfcc-0.29.1+ds/libbpf-tools'
- with this change applied:
100% tests passed, 0 tests failed out of 37
Total Test time (real) = 83.22 sec
make: Leaving directory '/tmp/autopkgtest.MOnsj0/tree/obj-x86_64-linux-gnu'
autopkgtest [06:43:12]: test command1: ---]
autopkgtest [06:43:12]: test command1: - - - - - - - - - - results - - - - - -
- - - -
command1 PASS
autopkgtest [06:43:12]: summary
command1 PASS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061727
Title:
bpfcc-tools autotest failure when multiple linux-tools-
packages are installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061727] Re: bpfcc-tools autotest failure when multiple linux-tools- packages are installed
debdiff in attach allows to run the autopkgtest correctly also with multiple kernels installed. ** Patch added: "bpfcc-tools-fix-autopkgtest.debdiff" https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+attachment/5766017/+files/bpfcc-tools-fix-autopkgtest.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061727 Title: bpfcc-tools autotest failure when multiple linux-tools- packages are installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061727] [NEW] bpfcc-tools autotest failure when multiple linux-tools- packages are installed
Public bug reported:
[Impact]
The autopkgtest for bpfcc-tools fails with the following error when
multiple linux-tools packages (multiple kernels) are installed:
942s /usr/lib/linux-tools-6.8.0-22/bpftool
/usr/lib/linux-tools-6.8.0-25/bpftool gen skeleton
/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.bpf.o >
/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.skel.h
942s Usage: bpftool [OPTIONS] OBJECT { COMMAND | help }
942sbpftool batch file FILE
942sbpftool version
942s
942sOBJECT := { prog | map | link | cgroup | perf | net | feature | btf
| gen | struct_ops | iter }
942sOPTIONS := { {-j|--json} [{-p|--pretty}] | {-d|--debug} |
942s {-V|--version} }
942s make[2]: *** [Makefile:192:
/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.skel.h]
Error 255
942s make[2]: *** Deleting file
'/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools/.output/bashreadline.skel.h'
942s make[2]: Leaving directory
'/tmp/autopkgtest.2W4dxr/build.Uhs/src/libbpf-tools'
942s make[1]: *** [debian/rules:44: override_dh_auto_install] Error 2
942s make[1]: Leaving directory '/tmp/autopkgtest.2W4dxr/build.Uhs/src'
The reason is that in debian/rules we evaluate BPFTOOL assuming that
only one kernel is installed, but we may have multiple kernels
(therefore multiple linux-tools-) installed.
[Test case]
Install multiple linux-tools- and run the bpfcc-tools
autopkgtest.
[Fix]
Evaluate BPFTOOL in debian/rules only taking the last bpftool listed in
/usr/lib/linux-tools-*/bpftool.
[Regression potential]
This change affects only the autopkgtest and it allows to run the test
correctly also when multiple kernels are installed, no regresssion is
expected.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: bpfcc-tools 0.29.1+ds-1ubuntu6
ProcVersionSignature: User Name 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20240413
CloudSubPlatform: config-disk (/dev/vdb)
Date: Tue Apr 16 05:38:06 2024
PackageArchitecture: all
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: bpfcc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bpfcc (Ubuntu)
Importance: Undecided
Status: New
** Affects: bpfcc (Ubuntu Noble)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cloud-image noble
** Also affects: bpfcc (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061727
Title:
bpfcc-tools autotest failure when multiple linux-tools-
packages are installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/2061727/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] Re: Apply mitigations for the native BHI hardware vulnerabilty
** 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 indirect branch predictor
entry, and although branch predictor entries are isolated between modes
when eIBRS is enabled, the BHB itself is not isolated between modes.
Previously the only known real-world BHB attack vector was via
unprivileged eBPF. Further research has found attacks that don't require
unprivileged eBPF.
See also:
https://www.phoronix.com/news/Linux-BHI-Branch-History-Inject
[Test case]
https://www.vusec.net/projects/native-bhi/
[Fix]
Backport from upstream the merge that introduces spectre_bhi= boot
option to control BHI mitigation:
2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
ed2e8d49b54d ("KVM: x86: Add BHI_NO")
95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
hardware control if it's available on the system CPUs, otherwise a
- proper software sequence will be deployed at VMexit.
+ proper software sequence will be executed at VMexit.
+
+ NOTE: we may get these changes via stable update in 6.8, when that
+ happens we can drop this backport and apply the patch set like any other
+ regular stable update.
[Regression potential]
We may experience performance regressions with this new mitigation
enabled, especially in VMs and CPUs that don't have the BHI hardware
support capability (due to the extra software sequence executed at
VMexit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
Title:
Apply mitigations for the native BHI hardware vulnerabilty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] Re: Apply mitigations for the native BHI hardware vulnerabilty
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060909 Title: Apply mitigations for the native BHI hardware vulnerabilty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] Re: Backport mitigations for the native BHI hardware vulnerabilty
** 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 branch targets in ring0.
The BHB can still influence the choice of indirect branch predictor
entry, and although branch predictor entries are isolated between modes
when eIBRS is enabled, the BHB itself is not isolated between modes.
Previously the only known real-world BHB attack vector was via
unprivileged eBPF. Further research has found attacks that don't require
unprivileged eBPF.
+ See also:
+ https://www.phoronix.com/news/Linux-BHI-Branch-History-Inject
+
[Test case]
https://www.vusec.net/projects/native-bhi/
[Fix]
Backport from upstream the merge that introduces spectre_bhi= boot
option to control BHI mitigation:
- 2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
- ed2e8d49b54d ("KVM: x86: Add BHI_NO")
- 95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
- ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
- be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
- 0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
- 7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
- 1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
- 0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
+ 2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
+ ed2e8d49b54d ("KVM: x86: Add BHI_NO")
+ 95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
+ ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
+ be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
+ 0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
+ 7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
+ 1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
+ 0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
hardware control if it's available on the system CPUs, otherwise a
proper software sequence will be deployed at VMexit.
[Regression potential]
We may experience performance regressions with this new mitigation
enabled, especially in VMs and CPUs that don't have the BHI hardware
support capability (due to the extra software sequence executed at
VMexit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
Title:
Backport mitigations for the native BHI hardware vulnerabilty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060909] [NEW] Backport mitigations for the native BHI hardware vulnerabilty
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 predictor
entry, and although branch predictor entries are isolated between modes
when eIBRS is enabled, the BHB itself is not isolated between modes.
Previously the only known real-world BHB attack vector was via
unprivileged eBPF. Further research has found attacks that don't require
unprivileged eBPF.
[Test case]
https://www.vusec.net/projects/native-bhi/
[Fix]
Backport from upstream the merge that introduces spectre_bhi= boot
option to control BHI mitigation:
2bb69f5fc721 ("Merge tag 'nativebhi' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
ed2e8d49b54d ("KVM: x86: Add BHI_NO")
95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall
entry")
1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system
calls")
0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs
file")
Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
hardware control if it's available on the system CPUs, otherwise a
proper software sequence will be deployed at VMexit.
[Regression potential]
We may experience performance regressions with this new mitigation
enabled, especially in VMs and CPUs that don't have the BHI hardware
support capability (due to the extra software sequence executed at
VMexit).
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Committed
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060909
Title:
Backport mitigations for the native BHI hardware vulnerabilty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060909/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
@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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060130] Re: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub
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 Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060130
Title:
[SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel
cmdline/initrd sections from EFI stub
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060130/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059080] Re: Add Real-time Linux Analysis tool (rtla) to linux-tools
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059080 Title: Add Real-time Linux Analysis tool (rtla) to linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059762] [NEW] CONFIG_INTEL_TDX_HOST conflicts with kexec in linux >= 6.8 for noble
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 kernel, despite our attempt with
LP: #2046040.
[Fix]
Disable CONFIG_INTEL_TDX_HOST in the generic kernel, until upstream will
properly support this option with kexec.
[Regression potential]
The Intel host TDX feature won't be available in the generic kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Committed
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059762
Title:
CONFIG_INTEL_TDX_HOST conflicts with kexec in linux >= 6.8 for noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2059237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046040] Re: enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for noble
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046040 Title: enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059237] Re: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot
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
correctly defined as the last member of the struct, and its size is
allocated dynamically at runtime, so I would expect that vars->name[0]
is always allocated, unless vars is not initialized properly or there's
an empty name.
So, my guess is that UBSAN isn't really happy about the flexible array
and this is just a false positive.
However, to be 100% sure that we are not actually doing and out-of-bound
access and prevent the warning, we could apply something like the
following on top of our SAUCE patch:
diff --git a/arch/powerpc/kernel/module_64.c b/arch/powerpc/kernel/module_64.c
index 195714fc6e22..1f5960e25758 100644
--- a/arch/powerpc/kernel/module_64.c
+++ b/arch/powerpc/kernel/module_64.c
@@ -350,6 +350,8 @@ static void dedotify_versions(struct modversion_info *vers,
struct modversion_info *end = (void *)vers + size;
for (; vers < end && vers->next; vers = (void *)vers + vers->next) {
+ if (size <= offsetof(struct modversion_info, name))
+ continue;
if (vers->name[0] == '.') {
memmove(vers->name, vers->name+1, strlen(vers->name));
}
In this case even if (for any reason) vars->name[] is an empty string we can
prevent the out-of-bound access and make UBSAN happy.
Opinions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059237
Title:
[Ubuntu-24.04] "array-index-out-of-bounds" error is observed after
every reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2059237/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059080] [NEW] Add Real-time Linux Analysis tool (rtla) to linux-tools
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 performance and observability (see for example https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame- pointers-by-default), it makes sense to provide more tools that can help to analyze timing/responsive performance, such as rtla. [Test case] Simple rtla usage to measure the timer irq / timer thread latency: $ sudo rtla timerlat [Fix] Enable the build of the rtla binary during the kernel build and ship it with linux-tools. [Regression potential] The only potential regression is an increased amount of size in the linux-tools package, due to the extra binary. However, the binary itself is really small, the kernel already has all the required capabilities enabled and we don't need to introduce any additional user-space dependency, therefore such extra space is expected to be minimal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059080 Title: Add Real-time Linux Analysis tool (rtla) to linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
** 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. There is really no reason to do that, because perf is both + backward and forward compatible, but this is a different issue and we + are not going to solve it in this context and it will be addressed in a + separate bug. + + For now, to solve this specific issue, we need to enable the python + module when we build perf (as part of the kernel build) and ship the + library inside the linux-tools- package. + + However, this brings a new problem, because we need to install the + module in a standard python path (so that python applications can be + able to use it in a regular way), but we need to support multiple + installed versions and add some logic to transparently select the right + one when a generic user-space python application uses `import perf`. + + For this reason we need to provide a python wrapper module that is + imported via a regular `import perf` and it transparently loads the + actual python perf module, based on the kernel that is currently + running. + + [Test case] + + Install linux-tools- and run the following simple test + case: + + $ python -c 'import perf; [print(c) for c in perf.cpu_map()]' + + [Fix] + + - Enable the python perf module build during the regular kernel build + - Provide a virtual `perf` python module wrapper in linux-tools-common + + [Regression potential] + + We are adding a new python module to linux-tools (that is something new, + we don't ship any other python module), but we are not changing anything + that is already provided, so the only regression that can happen is an + increased size of the linux-tools package. + + [Original bug report] + The tuned package has some plugins which rely on the perf python module [1], and right now they are not working because we do not have the perf python module available in Ubuntu. Initially, this was reported in this other bug [2], but it seems the scope of that bug is bigger than what we (Server) need for tuned. So filing this new bug as requested by the Kernel team to provide just the python module. For reference, in Fedora it's shipped in the bin:python3-perf package: [root@f39 ~]# rpm -ql python3-perf /usr/lib/.build-id /usr/lib/.build-id/80 /usr/lib/.build-id/80/9022196f598cb3327545c2d497b1d9fdf55630 /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/PKG-INFO /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/SOURCES.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/dependency_links.txt /usr/lib64/python3.12/site-packages/perf-0.1-py3.12.egg-info/top_level.txt /usr/lib64/python3.12/site-packages/perf.cpython-312-x86_64-linux-gnu.so /usr/share/licenses/python3-perf /usr/share/licenses/python3-perf/COPYING Built from their kernel-tools package[3]. - [1] https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290 [2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393 [3] https://src.fedoraproject.org/rpms/kernel-tools/blob/rawhide/f/kernel-tools.spec#_148 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
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 different applications (or interactions between kernel and a particular library). You mention that the last kernel that was working was like a 6.5? There's a huge delta between 6.5 and 6.8. Maybe we could try to restrict this range a bit more... At https://kernel.ubuntu.com/mainline/ you can find the debs of pretty much all the mainline kernel versions, maybe you could also test some kernels between 6.5 and 6.8 (assuming you can easily reproduce the problem), in order to restrict the range of changes and have a better idea where to look. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
@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- team/+archive/ubuntu/bootstrap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
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/ Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058191 Title: Getting SIGSEGV and SIGILL in many programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058165] Re: System freeze on copy large files on usb
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 tee /proc/sys/vm/dirty_bytes $ echo $((16 * 1024 * 1024)) | sudo tee /proc/sys/vm/dirty_background_bytes Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058165 Title: System freeze on copy large files on usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/2058165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056616] Re: left-over ceph debugging printks
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051342] Re: 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051342 Title: Enable lowlatency settings in the generic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056126] Re: hwmon: (coretemp) Fix core count limitation
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056126 Title: hwmon: (coretemp) Fix core count limitation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056126] [NEW] hwmon: (coretemp) Fix core count limitation
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 and it's scheduled for 6.9. We should apply the patch set to the Noble 6.8 kernel, so that we can properly support systems with a large amount of cores per package. [Test case] Read temperature info from /sys/class/hwmon on a system with > 128 cores per package (that means we don't have a proper test case to verify the fix at the moment). [Fix] Apply the following commits (from linux-next): 18cb15e9c108 hwmon: (coretemp) Use dynamic allocated memory for core temp_data f0a5f46b0100 hwmon: (coretemp) Remove redundant temp_data->is_pkg_data 16a29729c00c hwmon: (coretemp) Split package temp_data and core temp_data b48fddda2b30 hwmon: (coretemp) Abstract core_temp helpers a30f3dc6e9bf hwmon: (coretemp) Remove redundant pdata->cpu_map[] e416450cb080 hwmon: (coretemp) Replace sensor_device_attribute with device_attribute 46ee134971bb hwmon: (coretemp) Remove unnecessary dependency of array index 9f360b22929c hwmon: (coretemp) Introduce enum for attr index [Regression potential] We may experience hwmon-related regressions, either systems reading incorrect temperature information or even bugs/crashes when accessing data from /sys/class/hwmon. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056126 Title: hwmon: (coretemp) Fix core count limitation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054682] Re: apfs-dkms FTBS in noble with the latest 6.8 kernel
** Changed in: linux-apfs-rw (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054682 Title: apfs-dkms FTBS in noble with the latest 6.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-apfs-rw/+bug/2054682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages
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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055310 Title: dmesg spammed by virtui-fs and 9pnet-virtio messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951440] Re: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951440 Title: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049390] Re: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049390 Title: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055310] Re: dmesg spammed by virtui-fs and 9pnet-virtio messages
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 regression). If we can unblock/hint this one (hopefully this week, or worst case next week) we'll have a new 6.8 in release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055310 Title: dmesg spammed by virtui-fs and 9pnet-virtio messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977730] [NEW] Kinetic update: v5.18.1 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.18.1 upstream stable release
from git://git.kernel.org/
lockdown: also lock down previous kgdb use
HID: amd_sfh: Add support for sensor discovery
random: fix sysctl documentation nits
init: call time_init() before rand_initialize()
ia64: define get_cycles macro for arch-override
s390: define get_cycles macro for arch-override
parisc: define get_cycles macro for arch-override
alpha: define get_cycles macro for arch-override
powerpc: define get_cycles macro for arch-override
timekeeping: Add raw clock fallback for random_get_entropy()
m68k: use fallback for random_get_entropy() instead of zero
riscv: use fallback for random_get_entropy() instead of zero
mips: use fallback for random_get_entropy() instead of just c0 random
arm: use fallback for random_get_entropy() instead of zero
nios2: use fallback for random_get_entropy() instead of zero
x86/tsc: Use fallback for random_get_entropy() instead of zero
um: use fallback for random_get_entropy() instead of zero
sparc: use fallback for random_get_entropy() instead of zero
xtensa: use fallback for random_get_entropy() instead of zero
random: insist on random_get_entropy() existing in order to simplify
random: do not use batches when !crng_ready()
random: use first 128 bits of input as fast init
random: do not pretend to handle premature next security model
random: order timer entropy functions below interrupt functions
random: do not use input pool from hard IRQs
random: help compiler out with fast_mix() by using simpler arguments
siphash: use one source of truth for siphash permutations
random: use symbolic constants for crng_init states
random: avoid initializing twice in credit race
random: move initialization out of reseeding hot path
random: remove ratelimiting for in-kernel unseeded randomness
random: use proper jiffies comparison macro
random: handle latent entropy and command line from random_init()
random: credit architectural init the exact amount
random: use static branch for crng_ready()
random: remove extern from functions in header
random: use proper return types on get_random_{int,long}_wait()
random: make consistent use of buf and len
random: move initialization functions out of hot pages
random: move randomize_page() into mm where it belongs
random: unify batched entropy implementations
random: convert to using fops->read_iter()
random: convert to using fops->write_iter()
random: wire up fops->splice_{read,write}_iter()
random: check for signals after page of pool writes
ACPI: sysfs: Fix BERT error region memory mapping
ALSA: ctxfi: Add SB046x PCI ID
Linux 5.18.1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Description changed:
+ SRU Justification
- 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 a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- 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 a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ v5.18.1 upstream stable release
+ from git://git.kernel.org/
-v5.18.1 upstream stable release
-from git://git.kernel.org/
+ lockdown: also lock down previous kgdb use
+ HID: amd_sfh: Add support for sensor discovery
+ random: fix sysctl documentation nits
+ init: call time_init() before rand_initialize()
+ ia64: define get_cycles macro for arch-override
+ s390: define get_cycles macro for arch-override
+ parisc: define get_cycles macro for arch-override
+ alpha: define get_cycles macro for arch-override
+ powerpc: define get_cycles
[Bug 1977732] [NEW] Kinetic update: v5.18.2 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.18.2 upstream stable release
from git://git.kernel.org/
Linux 5.18.2
ALSA: usb-audio: Optimize TEAC clock quirk
bpf: Do write access check for kfunc and global func
bpf: Check PTR_TO_MEM | MEM_RDONLY in check_helper_mem_access
bpf: Reject writes for PTR_TO_MAP_KEY in check_helper_mem_access
bpf: Fix excessive memory allocation in stack_map_alloc()
bpf: Fix usage of trace RCU in local storage.
bpf: Enlarge offset check value to INT_MAX in bpf_skb_{load,store}_bytes
bpf: Fix combination of jit blinding and pointers to bpf subprogs.
bpf: Fix potential array overflow in bpf_trampoline_get_progs()
bpf: Fill new bpf_prog_pack with illegal instructions
NFSD: Fix possible sleep during nfsd4_release_lockowner()
NFS: Memory allocation failures are not server fatal errors
docs: submitting-patches: Fix crossref to 'The canonical patch format'
tpm: ibmvtpm: Correct the return value in tpm_ibmvtpm_probe()
tpm: Fix buffer access in tpm2_get_tpm_pt()
media: i2c: imx412: Fix power_off ordering
media: i2c: imx412: Fix reset GPIO polarity
x86/sgx: Ensure no data in PCMD page after truncate
x86/sgx: Fix race between reclaimer and page fault handler
x86/sgx: Obtain backing storage page with enclave mutex held
x86/sgx: Mark PCMD page as dirty when modifying contents
x86/sgx: Disconnect backing page references from dirty status
HID: multitouch: add quirks to enable Lenovo X12 trackpoint
HID: multitouch: Add support for Google Whiskers Touchpad
fs/ntfs3: validate BOOT sectors_per_clusters
raid5: introduce MD_BROKEN
dm verity: set DM_TARGET_IMMUTABLE feature flag
dm stats: add cond_resched when looping over entries
dm crypt: make printing of the key constant-time
dm integrity: fix error code in dm_integrity_ctr()
ARM: dts: s5pv210: Correct interrupt name for bluetooth in Aries
Bluetooth: hci_qca: Use del_timer_sync() before freeing
ALSA: usb-audio: Configure sync endpoints before data
ALSA: usb-audio: Add missing ep_idx in fixed EP quirks
ALSA: usb-audio: Workaround for clock setup on TEAC devices
tools/memory-model/README: Update klitmus7 compat table
zsmalloc: fix races between asynchronous zspage free and page migration
crypto: qat - rework the VF2PF interrupt handling logic
crypto: ecrdsa - Fix incorrect use of vli_cmp
crypto: caam - fix i.MX6SX entropy delay value
KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak
KVM: x86/mmu: Don't rebuild page when the page is synced and no tlb flushing is
required
KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2
KVM: x86: Fix the intel_pt PMI handling wrongly considered from guest
KVM: x86: avoid loading a vCPU after .vm_destroy was called
KVM: x86: avoid calling x86 emulator without a decoded instruction
KVM: x86: fix typo in __try_cmpxchg_user causing non-atomicness
KVM: x86: Use __try_cmpxchg_user() to emulate atomic accesses
KVM: x86: Use __try_cmpxchg_user() to update guest PTE A/D bits
x86/uaccess: Implement macros for CMPXCHG on user addresses
x86, kvm: use correct GFP flags for preemption disabled
x86/kvm: Alloc dummy async #PF token outside of raw spinlock
x86/fpu: KVM: Set the base guest FPU uABI size to sizeof(struct kvm_xsave)
KVM: PPC: Book3S HV: fix incorrect NULL check on list iterator
netfilter: conntrack: re-fetch conntrack after insertion
netfilter: nf_tables: double hook unregistration in netns path
netfilter: nf_tables: hold mutex on netns pre_exit path
netfilter: nf_tables: sanitize nft_set_desc_concat_parse()
netfilter: nft_limit: Clone packet limits' cost value
exfat: check if cluster num is valid
drm/i915: Fix -Wstringop-overflow warning in call to intel_read_wm_latency()
net: ipa: compute proper aggregation limit
pipe: Fix missing lock in pipe_resize_ring()
pipe: make poll_usage boolean and annotate its access
assoc_array: Fix BUG_ON during garbage collect
i2c: ismt: prevent memory corruption in ismt_access()
netfilter: nf_tables: disallow non-stateful expression in sets earlier
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 1976287] Re: casper: qemu instances too small during autopkgtest (potential OOM failures)
** Summary changed: - casper: qemu image too small in autopkgtest + casper: qemu instances too small during autopkgtest (potential OOM failures) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu instances too small during autopkgtest (potential OOM failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] Re: casper: qemu image too small in autopkgtest
Fix for focal (where we are experiencing regressions with hwe-5.15) in the attached debdiff. ** Patch added: "casper-increase-memory-to-test-instances.debdiff" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+attachment/5593861/+files/casper-increase-memory-to-test-instances.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu image too small in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976287] [NEW] casper: qemu image too small in autopkgtest
Public bug reported: [Impact] During autopkgtest we are creating VMs with 768MB of RAM, that used to be enough in the past, but nowdays we typically require more memory and we may trigger some sporadic out-of-memory failures during autopkgtest. [Test case] Run autopkgtest with a recent kernel (e.g., 5.15 or above). [Fix] Bump up the memory size to 1G. [Regression potential] We may see regressions in test systems with a small amount of memory (in the host / hypervisor), because after this change we need more RAM in order to run and complete autopkgtest successfully. ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Affects: casper (Ubuntu Focal) Importance: Undecided Status: New ** Affects: casper (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: casper (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976287 Title: casper: qemu image too small in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1976287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
This seems to fix the test failure. ** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592621/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff ** Patch removed: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975587 Title: systemd: fix test-execute autotest failure with kernel 5.15 in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975587 Title: systemd: fix test-execute autotest failure with kernel 5.15 in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975587] [NEW] systemd: fix test-execute autotest failure with kernel 5.15 in focal
Public bug reported:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.
[Test case]
Run systemd autopkgtest and check for the test-execute result.
[Fix]
Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.
This change is already available in jammy and above.
[Regression potential]
We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only affecting
the specific unit test.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975587
Title:
systemd: fix test-execute autotest failure with kernel 5.15 in focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure
@vorlon JFYI, I've just created LP: #1975499 for kinetic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975499] [NEW] drop oss4-dkms in kinetic
Public bug reported: [Impact] oss4-dkms fails to build in Jammy with the following error: gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’ We have considered to drop support of this package in other architectures (except amd64) - see for example LP: #1969752, but starting from kinetic we may also consider to drop oss4 completely, considering that not many people are still using it. [Test case] $ sudo apt install oss4-dkms [Fix] Drop oss4-dkms completely. [Regression potential] We may still have users of oss4 that would experience a regression, but considering that oss is a quite old technology it could be worth considering to move to a more modern sound system. ** Affects: oss4 (Ubuntu) Importance: Undecided Status: New ** Affects: oss4 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: oss4 (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975499 Title: drop oss4-dkms in kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1975499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974442] [NEW] enable CONFIG_DEVTMPFS_SAFE
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/mounts We should see nosuid,noexec in the mount options if this change is applied, otherwise we should only see nosuid (or none of the above). [Fix] Enable CONFIG_DEVTMPFS_SAFE. [Regression potential] This change can potentially break some drivers that require mmapping /dev/mem with the PROT_EXEC flag (for example non-KSM video drivers, or drivers that need to execute BIOS / firmware code directly from /dev/mem). However, it'd be nice to see if we still have drivers that are still relying on this dangerous behavior and provide some additional safety measures in the system. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974442 Title: enable CONFIG_DEVTMPFS_SAFE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973620] [NEW] prevent kernel panic with overlayfs + shiftfs
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 kernel mode [ 447.040369] #PF: error_code(0x) - not-present page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 [Test case] It is really easy to trigger this specific kernel panic running the lxc autopackage test. [Fix] This bug happens because we don't need to decrement anymore the refcount for the previous vm_file value in ovl_vm_prfile_set(). So the fix simply consists of removing the unnecessary fput(). [Regression potential] This patch affects only overlayfs (only when AUFS is enabled), so we may see regressions in overlayfs in kernels that have AUFS enabled (focal hwe and cloud kernels). ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973620 Title: prevent kernel panic with overlayfs + shiftfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
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 ready to be tested (unless you prepare something before me). :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
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=b4c25dba7993400e9c57d3e60bec4ab8bce1b701 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
@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=e3e60b65fa4db4722bd4b02a9dae58f7ff5d83d2 It'd be great if you could take a look and see if you spot any obvious bugs. I'll do more tests later today, trying to better figure out the real issue here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
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 page [ 447.041002] PGD 0 P4D 0 [ 447.041325] Oops: [#1] SMP NOPTI [ 447.041798] CPU: 0 PID: 73766 Comm: sudo Not tainted 5.15.0-28-generic #29~20.04.1-Ubuntu [ 447.042800] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Ubuntu-1.8.2-1ubuntu1+esm1 04/01/2014 [ 447.043979] RIP: 0010:aa_file_perm+0x3a/0x470 [ 447.044565] Code: 54 53 48 83 ec 68 48 89 7d 80 89 4d 8c 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 63 05 01 0a 19 01 48 03 82 c0 00 00 00 <4c> 8b 68 08 f6 46 40 02 0f 85 d0 00 00 00 41 f6 45 40 02 0f 85 c5 [ 447.046837] RSP: 0018:aefe80a4bca8 EFLAGS: 00010246 [ 447.047481] RAX: RBX: 96e4038abd01 RCX: 0004 [ 447.048351] RDX: 96e4038abd00 RSI: 96e401215eb8 RDI: 9c22a2ac [ 447.049241] RBP: aefe80a4bd38 R08: R09: [ 447.050121] R10: R11: R12: 96e401215eb8 [ 447.051040] R13: 96e4038abd00 R14: 9c22a2ac R15: 0004 [ 447.051942] FS: 7eff3c0f8c80() GS:96e45e40() knlGS: [ 447.052981] CS: 0010 DS: ES: CR0: 80050033 [ 447.053696] CR2: 0008 CR3: 02be2000 CR4: 003506f0 [ 447.054571] Call Trace: [ 447.054883] [ 447.055154] ? unlock_page_memcg+0x2f/0x40 [ 447.055668] ? page_remove_rmap+0x4b/0x320 [ 447.056180] common_file_perm+0x72/0x170 [ 447.056669] apparmor_file_permission+0x1c/0x20 [ 447.057237] security_file_permission+0x30/0x1a0 [ 447.057898] rw_verify_area+0x35/0x60 [ 447.058392] vfs_read+0x6d/0x1a0 [ 447.058842] ksys_read+0xb1/0xe0 [ 447.059276] __x64_sys_read+0x1a/0x20 [ 447.059732] do_syscall_64+0x5c/0xc0 [ 447.060183] ? __set_current_blocked+0x3b/0x60 [ 447.060738] ? exit_to_user_mode_prepare+0x3d/0x1c0 [ 447.061434] ? syscall_exit_to_user_mode+0x27/0x50 [ 447.062099] ? do_syscall_64+0x69/0xc0 [ 447.062603] ? irqentry_exit_to_user_mode+0x9/0x20 [ 447.063210] ? irqentry_exit+0x19/0x30 [ 447.063678] ? exc_page_fault+0x89/0x160 [ 447.064165] ? asm_exc_page_fault+0x8/0x30 [ 447.064675] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 447.065298] RIP: 0033:0x7eff3c2cb002 This panic happens only when AUFS is enabled (so it can be seen only in focal with 5.15 at the moment). I'm going to revert the patch for now, until we figure out a better way to re-apply this change. ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: re-apply missing overlayfs SAUCE patch
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] Re: disable Intel DMA remapping by default
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971699] [NEW] disable Intel DMA remapping by default
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 the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971593] Re: make wireless-tools a dependency for network-manager
** Description changed: The wpa-dhclient autopkgtest is always failing without wireless-tools - installed. Maybe wireless-tools should be an explicit dependency of - network-manager. + installed. Maybe wireless-tools should be added to the test dependencies + (debian/tests/control). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971593 Title: make wireless-tools a dependency for network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971593] [NEW] make wireless-tools a dependency for network-manager
Public bug reported: The wpa-dhclient autopkgtest is always failing without wireless-tools installed. Maybe wireless-tools should be an explicit dependency of network-manager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971593 Title: make wireless-tools a dependency for network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure
@vorlon oss4 is an ancient sound system platform that is rarely used nowdays, it would actually make sense to drop the support completely. Restricting the support to amd64-only seems a good compromise to fix the current build errors w/ modern toolchain, because of the -mfloat- abi=hard build option (that is blocking kernels promotions) and still provide a minimal support for this sound system. I think it's very unlikely to have users of this dkms outside of the amd64 world. But I'm open to better solutions/ideas to fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure
v2: drop -mfloat-abi=hard and build only on amd64. ** Patch added: "oss4-dkms-get-rid-of-hard-float-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+attachment/5582142/+files/oss4-dkms-get-rid-of-hard-float-v2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure
** Patch added: "oss4-dkms-get-rid-of-hard-float.debdiff" https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+attachment/5582052/+files/oss4-dkms-get-rid-of-hard-float.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969752] [NEW] oss4-dkms '-mfloat-abi=hard' build failure
Public bug reported: [Impact] oss4-dkms fails to build in Jammy with the following error: gcc: error: unrecognized command-line option ‘-mfloat-abi=hard’ [Test case] $ sudo apt install oss4-dkms [Fix] Get rid of -float-abi=hard, since it doesn't really provide any benefits nowdays. [Regression potential] We may experience performance regressions in oss4, but getting rid of '-mfloat-abi=hard’ provides a better compatibility across all the supported architectures and toolchains. ** Affects: oss4 (Ubuntu) Importance: Undecided Status: New ** Affects: oss4 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: oss4 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969752 Title: oss4-dkms '-mfloat-abi=hard' build failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1969752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch
** Also affects: linux-azure (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-azure (Ubuntu Jammy) ** No longer affects: linux-azure (Ubuntu Impish) ** No longer affects: linux-azure (Ubuntu) ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Summary changed: - One overlayfs fix has not been backported to the 5.13 branch + re-apply missing overlayfs SAUCE patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: re-apply missing overlayfs SAUCE patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch
** Description changed:
+ [Impact]
+
+ Starting with 5.13 we've incorrectly dropped the following sauce patch:
+
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
+ This patch seems to be required to use overlayfs on top of shiftfs and
+ without this patch we may break containers that rely on shiftfs (using
+ zfs/ceph as storage pool w/ shiftfs enabled).
+
+ [Test case]
+
+ No specific test case provided.
+
+ [Fix]
+
+ The original SAUCE patch relies on AUFS in order to use vma->vm_prfile,
+ but we're not providing AUFS anymore in jammy,.
+
+ The fix consists of re-apply this patch with a little refactoring to be
+ dependent on CONFIG_AUFS_FS.
+
+ [Regression potential]
+
+ This patch is touching overlayfs, so we may see potential regressions in
+ overlayfs.
+
+ [Original bug report]
+
The next patch has not been ported to the the 5.13 branch:
$ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
Author: Alexander Mikhalitsyn
Date: Mon Apr 26 10:11:00 2021 +0200
- UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
-
- BugLink: https://bugs.launchpad.net/bugs/1857257
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
+ BugLink: https://bugs.launchpad.net/bugs/1857257
...
- Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
+ Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay")
-
But it isn't in the 5.13 branch:
- $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
+ $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct
ovl_aio_req
7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying
fs doesn't support direct IO
1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with
shiftfs as underlay
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967924
Title:
One overlayfs fix has not been backported to the 5.13 branch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch
Thanks for pointing this out Andrew. It looks like this patch is relying on AUFS that has been dropped/disabled in jammy, but it's still available in focal, so we should definitely re-apply this patch. I'll make sure this is re-applied to 5.13 and 5.15 (changing the code to properly depend on AUFS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967924 Title: One overlayfs fix has not been backported to the 5.13 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1967924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968984] Re: Jammy update: v5.17.2 upstream stable release Edit
Revert "swiotlb: rework "fix info leak with DMA_FROM_DEVICE"" USB: serial: pl2303: add IBM device IDs dt-bindings: usb: hcd: correct usb-device path USB: serial: pl2303: fix GS type detection USB: serial: simple: add Nokia phone driver mm: kfence: fix missing objcg housekeeping for SLAB locking/lockdep: Avoid potential access of invalid memory in lock_class drm/amdgpu: move PX checking into amdgpu_device_ip_early_init drm/amdgpu: only check for _PR3 on dGPUs iommu/iova: Improve 32-bit free space estimate block: flush plug based on hardware and software queue order block: ensure plug merging checks the correct queue at least once usb: typec: tipd: Forward plug orientation to typec subsystem USB: usb-storage: Fix use of bitfields for hardware data in ene_ub6250.c xhci: fix garbage USBSTS being logged in some cases xhci: fix runtime PM imbalance in USB2 resume xhci: make xhci_handshake timeout for xhci_reset() adjustable xhci: fix uninitialized string returned by xhci_decode_ctrl_ctx() mei: me: disable driver on the ign firmware mei: me: add Alder Lake N device id. mei: avoid iterator usage outside of list_for_each_entry bus: mhi: pci_generic: Add mru_default for Quectel EM1xx series bus: mhi: Fix pm_state conversion to string bus: mhi: Fix MHI DMA structure endianness docs: sphinx/requirements: Limit jinja2<3.1 coresight: Fix TRCCONFIGR.QE sysfs interface coresight: syscfg: Fix memleak on registration failure in cscfg_create_device dt-bindings: iio: adc: zynqmp_ams: Add clock entry iio: adc: xilinx-ams: Fix single channel switching sequence iio: accel: mma8452: use the correct logic to get mma8452_data iio: adc: aspeed: Add divider flag to fix incorrect voltage reading. iio: imu: st_lsm6dsx: use dev_to_iio_dev() to get iio_dev struct iio: afe: rescale: use s64 for temporary scale calculations iio: adc: xilinx-ams: Fixed missing PS channels iio: adc: xilinx-ams: Fixed wrong sequencer register settings iio: inkern: apply consumer scale on IIO_VAL_INT cases iio: inkern: apply consumer scale when no channel scale is available iio: inkern: make a best effort on offset calculation greybus: svc: fix an error handling bug in gb_svc_hello() clk: rockchip: re-add rational best approximation algorithm to the fractional divider clk: uniphier: Fix fixed-rate initialization ptrace: Check PTRACE_O_SUSPEND_SECCOMP permission on PTRACE_SEIZE cifs: truncate the inode and mapping when we simulate fcollapse cifs: fix handlecache and multiuser cifs: we do not need a spinlock around the tree access during umount KEYS: fix length validation in keyctl_pkey_params_get_2() KEYS: asymmetric: enforce that sig algo matches key algo KEYS: asymmetric: properly validate hash_algo and encoding Documentation: add link to stable release candidate tree Documentation: update stable tree link firmware: stratix10-svc: add missing callback parameter on RSU firmware: sysfb: fix platform-device leak in error path HID: intel-ish-hid: Use dma_alloc_coherent for firmware update SUNRPC: avoid race between mod_timer() and del_timer_sync() SUNRPC: Do not dereference non-socket transports in sysfs NFS: NFSv2/v3 clients should never be setting NFS_CAP_XATTR NFSD: prevent underflow in nfssvc_decode_writeargs() NFSD: prevent integer overflow on 32 bit systems f2fs: fix to unlock page correctly in error path of is_alive() f2fs: quota: fix loop condition at f2fs_quota_sync() f2fs: fix to do sanity check on .cp_pack_total_block_count remoteproc: Fix count check in rproc_coredump_write() mm/mlock: fix two bugs in user_shm_lock() pinctrl: ingenic: Fix regmap on X series SoCs pinctrl: samsung: drop pin banks references on error paths net: bnxt_ptp: fix compilation error spi: mxic: Fix the transmit path mtd: spi-nor: Skip erase logic when SPI_NOR_NO_ERASE is set mtd: rawnand: protect access to rawnand devices while in suspend can: ems_usb: ems_usb_start_xmit(): fix double dev_kfree_skb() in error path can: m_can: m_can_tx_handler(): fix use after free of skb can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error path jffs2: fix use-after-free in jffs2_clear_xattr_subsystem jffs2: fix memory leak in jffs2_do_mount_fs jffs2: fix memory leak in jffs2_scan_medium mm: fs: fix lru_cache_disabled race in bh_lru mm: don't skip swap entry even if zap_details specified mm/pages_alloc.c: don't create ZONE_MOVABLE beyond the end of a node mm: invalidate hwpoison page cache page in fault path mempolicy: mbind_range() set_policy() after vma_merge() scsi: core: sd: Add silence_suspend flag to suppress some PM messages scsi: ufs: Fix runtime PM messages never-ending cycle scsi: scsi_transport_fc: Fix FPIN Link Integrity statistics counters scsi: libsas: Fix sas_ata_qc_issue() handling of NCQ NON DATA commands qed: display VF trust config qed: validate and restrict untrusted VFs vlan promisc mode riscv: dts: canaan: Fix SPI3 bus width riscv: Fix fill_callchain return value riscv: Increase stack size under KASAN RISC-V: Declare per cpu boot data as static Revert
[Bug 1968984] [NEW] Jammy update: v5.17.2 upstream stable release Edit
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 a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.17.1 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968984 Title: Jammy update: v5.17.2 upstream stable release Edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968986] [NEW] Jammy update: v5.17.3 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.17.3 upstream stable release
from git://git.kernel.org/
Linux 5.17.3
io_uring: drop the old style inflight file tracking
io_uring: defer file assignment
io_uring: propagate issue_flags state down to file assignment
io_uring: move read/write file prep state into actual opcode handler
static_call: Don't make __static_call_return0 static
mm/sparsemem: fix 'mem_section' will never be NULL gcc 12 warning
irqchip/gic, gic-v3: Prevent GSI to SGI translations
powerpc/64: Fix build failure with allyesconfig in book3s_64_entry.S
irqchip/gic-v4: Wait for GICR_VPENDBASER.Dirty to clear before descheduling
x86/extable: Prefer local labels in .set directives
x86,static_call: Fix __static_call_return0 for i386
sched: Teach the forced-newidle balancer about CPU affinity limitation.
sched/core: Fix forceidle balancing
objtool: Fix SLS validation for kcov tail-call replacement
x86/bug: Prevent shadowing in __WARN_FLAGS
Revert "powerpc: Set max_mapnr correctly"
powerpc: Fix virt_addr_valid() for 64-bit Book3E & 32-bit
Drivers: hv: vmbus: Replace smp_store_mb() with virt_store_mb()
KVM: avoid NULL pointer dereference in kvm_dirty_ring_push
dmaengine: Revert "dmaengine: shdma: Fix runtime PM imbalance on error"
tools build: Use $(shell ) instead of `` to get embedded libperl's ccopts
tools build: Filter out options and warnings not supported by clang
perf python: Fix probing for some clang command line options
perf build: Don't use -ffat-lto-objects in the python feature test when
building with clang-13
bpf: Treat bpf_sk_lookup remote_port as a 2-byte field
selftests/bpf: Fix u8 narrow load checks for bpf_sk_lookup remote_port
bpf: Make remote_port field in struct bpf_sk_lookup 16-bit wide
Revert "selftests: net: Add tls config dependency for tls selftests"
net/smc: send directly on setting TCP_NODELAY
drm/amdkfd: Fix variable set but not used warning
Revert "ACPI: processor: idle: Only flush cache on entering C3"
SUNRPC: Ensure we flush any closed sockets before xs_xprt_free()
drm/amdgpu: don't use BACO for reset in S3
drm/amdkfd: Create file descriptor after client is added to smi_clients list
drm/nouveau/pmu: Add missing callbacks for Tegra devices
drm/amdgpu/vcn: Fix the register setting for vcn1
drm/amdgpu/smu10: fix SoC/fclk units in auto mode
drm/amdgpu/display: change pipe policy for DCN 2.1
drm/amd/display: Fix by adding FPU protection for dcn30_internal_validate_bw
drm/panel: ili9341: fix optional regulator handling
amd/display: set backlight only if required
fbdev: Fix unregistering of framebuffers without device
irqchip/gic-v3: Fix GICR_CTLR.RWP polling
perf/core: Inherit event_caps
perf: qcom_l2_pmu: fix an incorrect NULL check on list iterator
ata: sata_dwc_460ex: Fix crash due to OOB write
perf/x86/intel: Don't extend the pseudo-encoding to GP counters
x86/mm/tlb: Revert retpoline avoidance approach
x86/msi: Fix msi message data shadow struct
gpio: Restrict usage of GPIO chip irq members before initialization
drbd: fix an invalid memory access caused by incorrect use of list iterator
RDMA/hfi1: Fix use-after-free bug for mm struct
arm64: patch_text: Fixup last cpu should be master
qed: fix ethtool register dump
cifs: force new session setup and tcon for dfs
spi: core: add dma_map_dev for __spi_unmap_msg()
btrfs: prevent subvol with swapfile from being deleted
btrfs: avoid defragging extents whose next extents are not targets
btrfs: remove device item and update super block in the same transaction
btrfs: zoned: traverse devices under chunk_mutex in btrfs_can_activate_zone
btrfs: fix qgroup reserve overflow the qgroup limit
perf/x86/intel: Update the FRONTEND MSR mask on Sapphire Rapids
x86/speculation: Restore speculation related MSRs during S3 resume
x86/pm: Save the MSR validity status at context setup
io_uring: fix race between timeout flush and removal
io_uring: implement compat handling for IORING_REGISTER_IOWQ_AFF
io_uring: defer splice/tee file validity check until command issue
io_uring: don't check req->file in io_fsync_prep()
mm/mempolicy: fix mpol_new leak in shared_policy_replace
mmmremap.c: avoid pointless invalidate_range_start/end on mremap(old_size=0)
highmem: fix checks in __kmap_local_sched_{in,out}
lz4: fix LZ4_decompress_safe_partial read out of bound
mmc: core: Fixup support for writeback-cache for eMMC and SD
mmc: renesas_sdhi: don't overwrite TAP settings when HS400 tuning is complete
mmc: renesas_sdhi: special 4tap settings only apply to HS400
mmc: mmci: stm32: correctly check all elements of
[Bug 1968982] Re: Jammy update: v5.17.1 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968982 Title: Jammy update: v5.17.1 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968982] [NEW] Jammy update: v5.17.1 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.17.1 upstream stable release from git://git.kernel.org/ tpm: Fix error handling in async work Bluetooth: btusb: Add another Realtek 8761BU llc: fix netdevice reference leaks in llc_ui_bind() ASoC: sti: Fix deadlock via snd_pcm_stop_xrun() call ALSA: oss: Fix PCM OSS buffer allocation overflow ALSA: usb-audio: add mapping for new Corsair Virtuoso SE ALSA: hda/realtek: Add quirk for Clevo NP70PNJ ALSA: hda/realtek: Add quirk for Clevo NP50PNJ ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc671 ALSA: hda/realtek: Add quirk for ASUS GA402 ALSA: pcm: Fix races among concurrent hw_params and hw_free calls ALSA: pcm: Fix races among concurrent read/write and buffer changes ALSA: pcm: Fix races among concurrent prepare and hw_params/hw_free calls ALSA: pcm: Fix races among concurrent prealloc proc writes ALSA: pcm: Add stream lock during PCM reset ioctl operations ALSA: usb-audio: Add mute TLV for playback volumes on RODE NT-USB ALSA: cmipci: Restore aux vol on suspend/resume ALSA: pci: fix reading of swapped values from pcmreg in AC97 codec drivers: net: xgene: Fix regression in CRC stripping netfilter: nf_tables: initialize registers in nft_do_chain() netfilter: nf_tables: validate registers coming from userspace. ACPI / x86: Work around broken XSDT on Advantech DAC-BJ01 board ACPI: battery: Add device HID and quirk for Microsoft Surface Go 3 ACPI: video: Force backlight native for Clevo NL5xRU and NL5xNU crypto: qat - disable registration of algorithms Bluetooth: btusb: Add one more Bluetooth part for the Realtek RTL8852AE Bluetooth: hci_sync: Add a new quirk to skip HCI_FLT_CLEAR_ALL Bluetooth: btusb: Use quirk to skip HCI_FLT_CLEAR_ALL on fake CSR controllers Revert "ath: add support for special 0x0 regulatory domain" drm/virtio: Ensure that objs is not NULL in virtio_gpu_array_put_free() jbd2: fix use-after-free of transaction_t race rcu: Don't deboost before reporting expedited quiescent state uaccess: fix integer overflow on access_ok() mac80211: fix potential double free on mesh join tpm: fix reference counting for struct tpm_chip tpm: use try_get_ops() in tpm-space.c wcn36xx: Differentiate wcn3660 from wcn3620 m68k: fix access_ok for coldfire nds32: fix access_ok() checks in get/put_user drm/msm/gpu: Fix crash on devices without devfreq support (v2) llc: only change llc->dev when bind() succeeds Linux 5.17.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Fix Committed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Description changed: + SRU Justification - 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 a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - 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 a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.17.1 upstream stable release + from git://git.kernel.org/ -v5.17.1 upstream stable release -from git://git.kernel.org/ + tpm: Fix error handling in async work + Bluetooth: btusb: Add another Realtek 8761BU + llc: fix netdevice reference leaks in llc_ui_bind() + ASoC: sti: Fix deadlock via snd_pcm_stop_xrun() call + ALSA: oss: Fix PCM OSS buffer allocation overflow + ALSA: usb-audio: add mapping for new Corsair Virtuoso SE + ALSA: hda/realtek: Add quirk for Clevo NP70PNJ + ALSA: hda/realtek: Add quirk for Clevo NP50PNJ + ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc671 + ALSA: hda/realtek: Add quirk for ASUS GA402 + ALSA: pcm: Fix races among concurrent hw_params and hw_free calls + ALSA: pcm: Fix
[Bug 1967750] Re: Intel: enable x86 AMX
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967750 Title: Intel: enable x86 AMX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967750] [NEW] Intel: enable x86 AMX
Public bug reported:
[Impact]
Enable AMX (aka TMUL) new instructions on the 5.15 kernel.
[Test case]
Tests have been performed directly by Intel.
[Fix]
Apply the following upstream commits:
20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test")
063452fd94d1 ("x86/fpu/xstate: Fix the ARCH_REQ_XCOMP_PERM implementation")
fa31a4d669bd ("x86/cpufeatures: Put the AMX macros in the word 18 block")
6c3118c32129 ("signal: Skip the altstack update when not needed")
52d0b8b18776 ("x86/fpu/signal: Initialize sw_bytes in save_xstate_epilog()")
d7a9590f608d ("Documentation/x86: Add documentation for using dynamic XSTATE
features")
101c669d165d ("selftests/x86/amx: Add context switch test")
6a3e0651b4a0 ("selftests/x86/amx: Add test cases for AMX state management")
2308ee57d93d ("x86/fpu/amx: Enable the AMX feature in 64-bit mode")
db3e7321b4b8 ("x86/fpu: Add XFD handling for dynamic states")
2ae996e0c1a3 ("x86/fpu: Calculate the default sizes independently")
eec2113eabd9 ("x86/fpu/amx: Define AMX state components and have it used for
boot-time checks")
70c3f1671b0c ("x86/fpu/xstate: Prepare XSAVE feature table for gaps in state
component numbers")
500afbf645a0 ("x86/fpu/xstate: Add fpstate_realloc()/free()")
783e87b40495 ("x86/fpu/xstate: Add XFD #NM handler")
672365477ae8 ("x86/fpu: Update XFD state where required")
5529acf47ec3 ("x86/fpu: Add sanity checks for XFD")
8bf26758ca96 ("x86/fpu: Add XFD state to fpstate")
dae1bd583896 ("x86/msr-index: Add MSRs for XFD")
c351101678ce ("x86/cpufeatures: Add eXtended Feature Disabling (XFD) feature
bit")
e61d6310a0f8 ("x86/fpu: Reset permission and fpstate on exec()")
9e798e9aa14c ("x86/fpu: Prepare fpu_clone() for dynamically enabled features")
53599b4d54b9 ("x86/fpu/signal: Prepare for variable sigframe length")
4b7ca609a33d ("x86/signal: Use fpu::__state_user_size for sigalt stack
validation")
23686ef25d4a ("x86/fpu: Add basic helpers for dynamically enabled features")
db8268df0983 ("x86/arch_prctl: Add controls for dynamic XSTATE components")
c33f0a81a2cf ("x86/fpu: Add fpu_state_config::legacy_features")
6f6a7c09c406 ("x86/fpu: Add members to struct fpu to cache permission
information")
84e4dccc8fce ("x86/fpu/xstate: Provide xstate_calculate_size()")
3aac3ebea08f ("x86/signal: Implement sigaltstack size validation")
1bdda24c4af6 ("signal: Add an optional check for altstack size")
582b01b6ab27 ("x86/fpu: Remove old KVM FPU interface")
d69c1382e1b7 ("x86/kvm: Convert FPU handling to a single swap buffer")
69f6ed1d14c6 ("x86/fpu: Provide infrastructure for KVM FPU cleanup")
75c52dad5e32 ("x86/fpu: Prepare for sanitizing KVM FPU code")
d72c87018d00 ("x86/fpu/xstate: Move remaining xfeature helpers to core")
eda32f4f93b4 ("x86/fpu: Rework restore_regs_from_fpstate()")
daddee247319 ("x86/fpu: Mop up xfeatures_mask_uabi()")
1c253ff2287f ("x86/fpu: Move xstate feature masks to fpu_*_cfg")
2bd264bce238 ("x86/fpu: Move xstate size to fpu_*_cfg")
cd9ae7617449 ("x86/fpu/xstate: Cleanup size calculations")
617473acdfe4 ("x86/fpu: Cleanup fpu__init_system_xstate_size_legacy()")
578971f4e228 ("x86/fpu: Provide struct fpu_config")
5509cc78080d ("x86/fpu/signal: Use fpstate for size and features")
49e4eb4125d5 ("x86/fpu/xstate: Use fpstate for copy_uabi_to_xstate()")
3ac8d75778fc ("x86/fpu: Use fpstate in __copy_xstate_to_uabi_buf()")
ad6ede407aae ("x86/fpu: Use fpstate in fpu_copy_kvm_uabi_to_fpstate()")
0b2d39aa0357 ("x86/fpu/xstate: Use fpstate for xsave_to_user_sigframe()")
073e627a4537 ("x86/fpu/xstate: Use fpstate for os_xsave()")
be31dfdfd75b ("x86/fpu: Use fpstate::size")
248452ce21ae ("x86/fpu: Add size and mask information to fpstate")
2dd8eedc80b1 ("x86/process: Move arch_thread_struct_whitelist() out of line")
f0cbc8b3cdf7 ("x86/fpu: Do not leak fpstate pointer on fork")
2f27b5034244 ("x86/fpu: Remove fpu::state")
63d6bdf36ce1 ("x86/math-emu: Convert to fpstate")
c20942ce5128 ("x86/fpu/core: Convert to fpstate")
7e049e8b7459 ("x86/fpu/signal: Convert to fpstate")
caee31a36c33 ("x86/fpu/regset: Convert to fpstate")
cceb496420fa ("x86/fpu: Convert tracing to fpstate")
1c57572d754f ("x86/KVM: Convert to fpstate")
087df48c298c ("x86/fpu: Replace KVMs xstate component clearing")
18b3fa1ad15f ("x86/fpu: Convert restore_fpregs_from_fpstate() to struct
fpstate")
f83ac56acdad ("x86/fpu: Convert fpstate_init() to struct fpstate")
87d0e5be0fac ("x86/fpu: Provide struct fpstate")
bf5d00470787 ("x86/fpu: Replace KVMs home brewed FPU copy to user")
079ec41b22b9 ("x86/fpu: Provide a proper function for ex_handler_fprestore()")
b56d2795b297 ("x86/fpu: Replace the includes of fpu/internal.h")
6415bb809263 ("x86/fpu: Mop up the internal.h leftovers")
ff0c37e191f2 ("x86/sev: Include fpu/xcr.h")
0ae67cc34f76 ("x86/fpu: Remove internal.h dependency from fpu/signal.h")
90489f1dee8b ("x86/fpu: Move fpstate functions to api.h")
d9d005f32aac ("x86/fpu: Move mxcsr related code to core")
9848fb96839b ("x86/fpu: Move fpregs_restore_userregs() to core")
cdcb6fa14e14
[Bug 1964321] [NEW] obs-studio should support browser objects and twitch integration
Public bug reported: The obs-studio that we provide in Ubuntu is pretty much useless, because it's missing some key features, like browser objects and a better integration with some streaming platforms, such as Twitch. I always need to use obs-studio from ppa:obsproject/obs-studio and that is not a big problem, but it's very annoying when the version of obs- studio in the archive is updated and it overrides the version from the ppa, because it's completely breaking my setup. I know I can `apt-mark hold obs-studio`, but it's still quite annoying... I'm wondering why it's problematic to provide the same features that the version in ppa:obsprojects/obs-studio in our main archive... I'd be happy just with the browser object support. ** Affects: obs-studio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964321 Title: obs-studio should support browser objects and twitch integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1964321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964317] [NEW] make dahdi available only on non-cloud kernels
Public bug reported: [Impact] DAHDI (formly Zaptel) is an interface for telephony devices (e.g. the Asterisk PBX software). Maintaining this module on cloud kernels has been always problematic, because most of the cloud kernels are missing the modules required by this dkms. Moreover it is quite unlikely to find a real world use case that may require to have this module installed in a cloud instance. In kernels such as linux-kvm for example this test has been failing since forever and it has been always hinted. At this point it is better to simply not provide this module. [Test case] Install this module on a kernel typically used in cloud instances, i.e.: $ sudo apt install dahdi-dkms [Fix] Adjust dkms.conf to provide this dkms only on a certain subset of kernels (excluding cloud kernels). [Regression potential] We may incorrectly exclude some kernels that actually require this module, so we may see potential regressions limited to the unavailability of this dkms. ** Affects: dahdi-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964317 Title: make dahdi available only on non-cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1964317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964317] Re: make dahdi available only on non-cloud kernels
Fix to provide this module only the specific set of non-cloud kernels in attach. ** Patch added: "build-dahdi-only-on-specific-kernels.debdiff" https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1964317/+attachment/5567289/+files/build-dahdi-only-on-specific-kernels.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964317 Title: make dahdi available only on non-cloud kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1964317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15
updated debdiff in attach FWIW ** Patch added: "apparmor-fix-autotests.debdiff" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5562493/+files/apparmor-fix-autotests.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15
@alexmurray thanks for the update! BTW I found another issue with test- network.py: this test is failing because utils/apparmor/rule/network.py is missing the mctp protocol (in network_domain_keywords[]). I checked upstream, but I couldn't find any fix for this, do you want me to open another tracking bug / send a patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15
Simple fix in the attached debdiff ** Patch added: "apparmor-fix-test-aa-notify.debdiff" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5561612/+files/apparmor-fix-test-aa-notify.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15
** Description changed: + [Impact] + + test-aa-notify is also checking if the output of `aa-notify --help` + matches a specific text. However it looks like this output has changed + in jammy so the autopkgtest is reporting errors like this: + 05:17:31 ERROR| [stderr] === test-aa-notify.py === 05:17:31 ERROR| [stderr] .ssF. 05:17:31 ERROR| [stderr] == 05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest) 05:17:31 ERROR| [stderr] Test output of help text 05:17:31 ERROR| [stderr] -- 05:17:31 ERROR| [stderr] Traceback (most recent call last): 05:17:31 ERROR| [stderr] File "/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py", line 178, in test_help_contents 05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, result + output) 05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n -h, --helpshow this hel[735 chars]de\n' 05:17:31 ERROR| [stderr] usage: aa-notify [-h] [-p] [--display DISPLAY] [-f FILE] [-l] [-s NUM] [-v] 05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug] - 05:17:31 ERROR| [stderr] + 05:17:31 ERROR| [stderr] 05:17:31 ERROR| [stderr] Display AppArmor notifications or messages for DENIED entries. - 05:17:31 ERROR| [stderr] + 05:17:31 ERROR| [stderr] 05:17:31 ERROR| [stderr] - optional arguments: 05:17:31 ERROR| [stderr] + options: 05:17:31 ERROR| [stderr] -h, --helpshow this help message and exit 05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and display notifications 05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY environment variable (might be needed if 05:17:31 ERROR| [stderr] sudo resets $DISPLAY) 05:17:31 ERROR| [stderr] -f FILE, --file FILE search FILE for AppArmor messages 05:17:31 ERROR| [stderr] -l, --since-last display stats since last login 05:17:31 ERROR| [stderr] -s NUM, --since-days NUM 05:17:31 ERROR| [stderr] show stats for last NUM days (can be used alone or with 05:17:31 ERROR| [stderr] -p) 05:17:31 ERROR| [stderr] -v, --verbose show messages with stats 05:17:31 ERROR| [stderr] -u USER, --user USER user to drop privileges to when not using sudo 05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before displaying notifications (with 05:17:31 ERROR| [stderr] -p) 05:17:31 ERROR| [stderr] --debug debug mode 05:17:31 ERROR| [stderr] : Got output "usage: aa-notify [-h] [-p] [--display DISPLAY] [-f FILE] [-l] [-s NUM] [-v] 05:17:31 ERROR| [stderr] [-u USER] [-w NUM] [--debug] + + [Test case] + + Simply run test-aa-notify.py from the autopkgtests. + + [Fix] + + Update the expected output returned by `aa-notify --help` in test-aa- + notify.py. + + [Regression potential] + + This is just an autopkgtest, we may see regressions if the test is used + with older version of apparmor-notify. With newer versions there's no + risk of regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961196] [NEW] apparmor autotest failure on jammy with linux 5.15
Public bug reported: 05:17:31 ERROR| [stderr] === test-aa-notify.py === 05:17:31 ERROR| [stderr] .ssF. 05:17:31 ERROR| [stderr] == 05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest) 05:17:31 ERROR| [stderr] Test output of help text 05:17:31 ERROR| [stderr] -- 05:17:31 ERROR| [stderr] Traceback (most recent call last): 05:17:31 ERROR| [stderr] File "/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py", line 178, in test_help_contents 05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, result + output) 05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n -h, --helpshow this hel[735 chars]de\n' 05:17:31 ERROR| [stderr] usage: aa-notify [-h] [-p] [--display DISPLAY] [-f FILE] [-l] [-s NUM] [-v] 05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug] 05:17:31 ERROR| [stderr] 05:17:31 ERROR| [stderr] Display AppArmor notifications or messages for DENIED entries. 05:17:31 ERROR| [stderr] 05:17:31 ERROR| [stderr] - optional arguments: 05:17:31 ERROR| [stderr] + options: 05:17:31 ERROR| [stderr] -h, --helpshow this help message and exit 05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and display notifications 05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY environment variable (might be needed if 05:17:31 ERROR| [stderr] sudo resets $DISPLAY) 05:17:31 ERROR| [stderr] -f FILE, --file FILE search FILE for AppArmor messages 05:17:31 ERROR| [stderr] -l, --since-last display stats since last login 05:17:31 ERROR| [stderr] -s NUM, --since-days NUM 05:17:31 ERROR| [stderr] show stats for last NUM days (can be used alone or with 05:17:31 ERROR| [stderr] -p) 05:17:31 ERROR| [stderr] -v, --verbose show messages with stats 05:17:31 ERROR| [stderr] -u USER, --user USER user to drop privileges to when not using sudo 05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before displaying notifications (with 05:17:31 ERROR| [stderr] -p) 05:17:31 ERROR| [stderr] --debug debug mode 05:17:31 ERROR| [stderr] : Got output "usage: aa-notify [-h] [-p] [--display DISPLAY] [-f FILE] [-l] [-s NUM] [-v] 05:17:31 ERROR| [stderr] [-u USER] [-w NUM] [--debug] ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: apparmor (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961196 Title: apparmor autotest failure on jammy with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960361] Re: hwmon: k10temp updates for AMD Genoa in 22.04
** Also affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960361 Title: hwmon: k10temp updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960362] Re: EDAC update for AMD Genoa support in 22.04
** Also affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960362 Title: EDAC update for AMD Genoa support in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960171] Re: [SRU] virtualbox 6.1.32 virtualbox-guest-dkms build failure on focal with linux 5.15
Tested virtualbox-ext-pack (as well as the latest virtualbox-guest-dkms) on focal with linux-hwe-5.15. Everything is working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960171 Title: [SRU] virtualbox 6.1.32 virtualbox-guest-dkms build failure on focal with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1960171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951390] Re: update iproute2
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951390 Title: update iproute2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960309] [NEW] kselftest ftrace inter-event histogram trigger snapshot action failure
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960309 Title: kselftest ftrace inter-event histogram trigger snapshot action failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960171] Re: virtualbox-guest-dkms build failure on focal with linux 5.15
debdiff reported in attach fixes all the build failures on focal with linux 5.15 (all changes are backported from virtualbox 6.1.30 on jammy). ** Patch added: "virtualbox-guest-support-linux-5.15.debdiff" https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1960171/+attachment/5559516/+files/virtualbox-guest-support-linux-5.15.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960171 Title: virtualbox-guest-dkms build failure on focal with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1960171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960171] [NEW] virtualbox-guest-dkms build failure on focal with linux 5.15
Public bug reported:
[Impact]
virtualbox-guest-dkms is failing to build on focal with the latest linux
5.15 kernel:
var/lib/dkms/virtualbox-guest/6.1.26/build/vboxsf/regops.c: In function
‘vbsf_iter_lock_pages’:
/var/lib/dkms/virtualbox-guest/6.1.26/build/vboxsf/regops.c:2129:15: error:
‘struct iov_iter’ has no member named ‘type’
2129 | if (!(iter->type & ITER_KVEC)) {
| ^~
[Test case]
$ sudo apt install virtualbox-guest-dkms
[Fix]
Backport a change (from 6.1.30) in the sharedfolders driver to properly
get iov iter type member which changed name in 5.14.
[Regression potential]
This change is only affecting the sharedfolders driver, so we may
experience potential regressions in virtualbox guest instances that are
using shared folders with the host.
** Affects: virtualbox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960171
Title:
virtualbox-guest-dkms build failure on focal with linux 5.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1960171/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960170] Re: rtl8821ce-dkms build failure on focal with linux hwe 5.15
debdiff in attach fixes build failures on focal with linux hwe 5.15. ** Patch added: "rtl8821ce-support-linux-5.15.debdiff" https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1960170/+attachment/5559390/+files/rtl8821ce-support-linux-5.15.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960170 Title: rtl8821ce-dkms build failure on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1960170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960169] Re: rtl8812au fails to build on focal with linux hwe 5.15
** Description changed: [Impact] /home/ubuntu/rtl8812au-4.3.8.12175.20140902+dfsg/core/rtw_br_ext.c:25:10: fatal error: net/ipx.h: No such file or directory -25 | #include - | ^~~ + 25 | #include + | ^~~ compilation terminated. [Test case] - $ sudo apt install rtl8812au-dkms + $ sudo apt install rtl8812au-dkms [Fix] - Backport patches from jammy to properly support linux 5.15. + Drop IPX support (deprecated in newer kernel). Same patch has been + applied in jammy (this fix is a backport of the same patch). [Regression potential] - We may see regressions restricted to the rtl8812au driver. + IPX is not supported anymore, so we may experience regressions for those + that are still using and relying on this protocol with the rtl8821ce + driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960169 Title: rtl8812au fails to build on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/1960169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960170] [NEW] rtl8821ce-dkms build failure on focal with linux hwe 5.15
Public bug reported: [Impact] rtl8821ce driver fails to build on focal with the latest linux hwe 5.15: fatal error: net/ipx.h: No such file or directory 25 | #include | ^~~ compilation terminated. [Test case] $ sudo apt install rtl8821ce-dkms [Fix] Drop IPX support (deprecated in newer kernel). Same patch has been applied in jammy (this fix is a backport of the same patch). [Regression potential] IPX is not supported anymore, so we may experience regressions for those that are still using and relying on this protocol with the rtl8821ce driver. ** Affects: rtl8821ce (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960170 Title: rtl8821ce-dkms build failure on focal with linux hwe 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1960170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
