[Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Hi, Guilherme. I think you misunderstood and we are in agreement. What I mean by the first point is that, on Focal, we need to support 5.4 and 5.15. I don't even think we need to support 5.8 and 5.11 any longer, though 5.13, as it will still be supported for a while needs supporting. But I also mean that we should support not only 5.4.0-113 and 5.4.0-114 (versions on -updates and -proposed), we should also support older 5.4 versions (one could argue all the versions that are still livepatchable at least). I don't think the risk of regressions is big here, but it exists. We ought to balance that risk and how much we can test. About the second point, it's just an argument that we should not restrict ourselves to the upstream major makedumpfile version that is in LTS+1. Take focal, which will receive 5.15 from jammy. It may require a newer makedumpfile than the one in Jammy because the one in Jammy may not be sufficient to support 5.15. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970672 Title: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
There are two risks with that plan that we should overcome. One is testing, such updates should not cause regressions. As of right now, the small testing that makedumpfile receives is not sufficient and gives a lot of false negatives. We should be testing that new kernels are still dumpable (and fix either kernel or makedumpfile when they are not). And test that new makedumpfile versions do not break dumping all the supported kernel versions (which, in my opinion is a little harder, and puts some burden on makedumpfile updates). Users do run outdated kernels and would expect dumps when they crash, so this is a bit of a challenge. We do not need to be perfect and test all kernels in all scenarios, but we definitively need to do better. The second one is kernel support. It's not unusual that we release an Ubuntu version with a makedumpfile that cannot dump the GA kernel. So, even without considering HWE kernels, an LTS release may need a newer makedumpfile. One of the reasons is that as we don't test as we upload new kernels to the development series, we don't realize makedumpfile needs additional support for that new kernel. Sometimes, just having the latest released makedumpfile is sufficient. But it's too often the case that upstream makedumpfile is only able to catch up with latest kernel releases after a while. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970672 Title: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972281] Re: ext4: limit length to bitmap_maxbytes
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972281 Title: ext4: limit length to bitmap_maxbytes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972740] Re: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972740] [NEW] Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option
Public bug reported: [Impact] PTRACE_O_SUSPEND_SECCOMP allows CRIU to disable seccomp on a process. However, setting this option requires privilege when used with PTRACE_SETOPTIONS. However, when used with PTRACE_SEIZE, no privilege is required. This allows sandboxed processes to exit the sandbox if they are allowed to use ptrace. [Test case] Run the reproducer from https://bugs.chromium.org/p/project-zero/issues/detail?id=2276. [Potential regression] This may break ptrace users, specially ones using PTRACE_SEIZE or PTRACE_SETOPTIONS. Special attention to processes being sandboxed with seccomp. ** Affects: linux (Ubuntu) Importance: High Status: Fix Committed ** Affects: linux (Ubuntu Xenial) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Triaged ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: High Status: Fix Committed ** Affects: linux (Ubuntu Impish) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: High 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/1972740 Title: Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968340] Re: ip6gre driver does not hold device reference
Fails with the kernel in -updates, 4.15.0-176. Works with kernel in -proposed, 4.15.0-177. ubuntu@bionic:~$ uname -r 4.15.0-177-generic ubuntu@bionic:~$ sudo modprobe ip6_gre ubuntu@bionic:~$ unshare -Urn true ubuntu@bionic:~$ unshare -Urn true ubuntu@bionic:~$ unshare -Urn true ubuntu@bionic:~$ dmesg | tail -2 [ 14.212867] gre: GRE over IPv4 demultiplexor driver [ 14.218947] ip6_gre: GRE over IPv6 tunneling driver ubuntu@bionic:~$ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968340 Title: ip6gre driver does not hold device reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971480] [NEW] issuing invalid ioctl to /dev/vsock may spam dmesg
Public bug reported:
[Impact]
Any user may spam dmesg may issuing an invalid ioctl to /dev/vsock.
[Fix]
Do not print anything to dmesg when an invalid ioctl is issued to /dev/vsock.
[Test case]
ioctl(open("/dev/vsock", O_RDONLY), garbage, 0);
[Potential regression]
vsock users may regress.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Xenial)
Importance: Low
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Low
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Low
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: New => 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/1971480
Title:
issuing invalid ioctl to /dev/vsock may spam dmesg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971480/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962315] Re: xenial upgrade of lockdown patches dropped ioport denial
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962315 Title: xenial upgrade of lockdown patches dropped ioport denial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968340] [NEW] ip6gre driver does not hold device reference
Public bug reported: [Impact] When creating ip6gre interfaces in network namespaces, device references are not held, preventing further network namespaces from being created. [Test case] sudo modprobe ip6_gre unshare -Urn true unshare -Urn true The second unshare won't work and there will be "unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1" messages on kernel log. [Potential regression] ip6gre users can observe regressions. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968340 Title: ip6gre driver does not hold device reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967579] Re: harden indirect calls against BHI attacks
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967579 Title: harden indirect calls against BHI attacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967579] [NEW] harden indirect calls against BHI attacks
*** This bug is a security vulnerability *** Public security bug reported: [Impact] Branch History Injection is made easier when all indirect calls are funneled through very few points where the retpolines were. By replacing the retpoline jumps by indirect calls whenever retpolines are disabled, BHI attacks are more difficult to execute as the BTB is not as fixed as before. [Fixes] Though there are fixes that allow retpoline,lfence to be directly replaced in the indirect calls, given that mitigation is not recommended for most of the situations, that hardening is not as important as the one that works for the spectre_v2=off option (the default one for systems with eIBRS). This latter one is present starting with 5.13, but backporting to 5.4 might be a good measure. ** 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/1967579 Title: harden indirect calls against BHI attacks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
Does changing the sysctl kernel.unprivileged_bpf_disabled to 0 fix the issue? This has been recently changed in all kernels supporting ebpf to default to 2, even on those kernels that do not support CAP_BPF. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961338] Re: Disable unprivileged BPF by default
** Information type changed from Private Security to Public Security ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961338 Title: Disable unprivileged BPF by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960059] Re: linux-4.4 scheduling while atomic on azure
80bfeeb9dd6b54ac108c884c792f0fc7d4912bee ("PCI: hv: Do not sleep in
compose_msi_msg()") might fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960059
Title:
linux-4.4 scheduling while atomic on azure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960059/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** Patch added: "fix for jammy" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+attachment/5563543/+files/kdump-tools_1.6.10ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
The build failed on jammy because of a new shellcheck warning, which was fixed in Debian already. See https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1002270. I have uploaded a merge to a PPA, where it built just fine. I am attaching the debdiff for that. Cascardo. ** Bug watch added: Debian Bug tracker #1002270 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002270 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960059] [NEW] linux-4.4 scheduling while atomic on azure
Public bug reported: [ 11.338145] BUG: scheduling while atomic: systemd-udevd/891/0x0002 [ 11.343832] Modules linked in: edac_core mlx4_core(+) kvm_intel input_leds kvm irqbypass nf_conntrack_ipv4 serio_raw hv_balloon pci_hyperv i2c_piix4 nf_defrag_ipv4 8250_fintek xt_conntrack joydev nf_conntrack mac_hid xt_owner xt_tcpudp iptable_security ip_tables x_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic hid_hyperv hv_utils ptp hv_storvsc hyperv_keyboard hid hv_netvsc pps_core scsi_transport_fc hyperv_fb crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper psmouse pata_acpi cryptd hv_vmbus floppy fjes [ 11.343869] CPU: 10 PID: 891 Comm: systemd-udevd Not tainted 4.4.0-219-lowlatency #252-Ubuntu [ 11.343870] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 11.343872] 0286 1002a46b615445cb 881095a8f598 81861c01 [ 11.343874] 88109f096280 881095a8f5a8 810ac88b [ 11.343876] 881095a8f5f8 8186c241 881095a8f5c8 000a [ 11.343877] Call Trace: [ 11.343883] [] dump_stack+0x6d/0x8b [ 11.343887] [] __schedule_bug+0x4b/0x60 [ 11.343890] [] __schedule+0x641/0x830 [ 11.343892] [] schedule+0x3c/0x90 [ 11.343894] [] schedule_timeout+0x21d/0x2b0 [ 11.343896] [] wait_for_completion+0xa5/0x120 [ 11.343899] [] ? wake_up_q+0x70/0x70 [ 11.343902] [] hv_compose_msi_msg+0x1d6/0x290 [pci_hyperv] [ 11.343904] [] ? put_hvpcibus+0x20/0x20 [pci_hyperv] [ 11.343908] [] irq_chip_compose_msi_msg+0x4b/0x60 [ 11.343910] [] msi_domain_activate+0x2c/0x70 [ 11.343912] [] irq_domain_activate_irq+0x44/0x50 [ 11.343914] [] irq_startup+0x38/0x90 [ 11.343916] [] __setup_irq+0x5a2/0x650 [ 11.343928] [] ? mlx4_free_cmd_mailbox+0x2d/0x40 [mlx4_core] [ 11.343932] [] ? kmem_cache_alloc_trace+0x1ed/0x210 [ 11.343940] [] ? mlx4_interrupt+0x80/0x80 [mlx4_core] [ 11.343942] [] request_threaded_irq+0xfb/0x1a0 [ 11.343948] [] mlx4_init_eq_table+0x3f8/0x630 [mlx4_core] [ 11.343956] [] mlx4_setup_hca+0x1f8/0x770 [mlx4_core] [ 11.343962] [] mlx4_load_one+0xb67/0x1670 [mlx4_core] [ 11.343967] [] mlx4_init_one+0x528/0x6c0 [mlx4_core] [ 11.343970] [] local_pci_probe+0x4a/0xa0 [ 11.343972] [] ? pci_match_device+0xe0/0x110 [ 11.343973] [] pci_device_probe+0x103/0x150 [ 11.343976] [] driver_probe_device+0x1be/0x4b0 [ 11.343978] [] __driver_attach+0x87/0x90 [ 11.343980] [] ? driver_probe_device+0x4b0/0x4b0 [ 11.343982] [] bus_for_each_dev+0x72/0xc0 [ 11.343983] [] driver_attach+0x1e/0x20 [ 11.343985] [] bus_add_driver+0x1e2/0x280 [ 11.343986] [] ? 0xc078e000 [ 11.343988] [] driver_register+0x60/0xe0 [ 11.343990] [] __pci_register_driver+0x4c/0x50 [ 11.343996] [] mlx4_init+0x115/0x1000 [mlx4_core] [ 11.343998] [] do_one_initcall+0xb5/0x200 [ 11.344003] [] ? __vunmap+0xa5/0x100 [ 11.344005] [] ? kfree+0x166/0x180 [ 11.344007] [] do_init_module+0x5f/0x1da [ 11.344010] [] load_module+0x1712/0x1c90 [ 11.344012] [] ? __symbol_put+0x70/0x70 [ 11.344014] [] ? kernel_read+0x50/0x80 [ 11.344016] [] SYSC_finit_module+0xb4/0xe0 [ 11.344018] [] SyS_finit_module+0xe/0x10 [ 11.344020] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ 11.344383] BUG: scheduling while atomic: systemd-udevd/891/0x [ 11.349908] Modules linked in: edac_core mlx4_core(+) kvm_intel input_leds kvm irqbypass nf_conntrack_ipv4 serio_raw hv_balloon pci_hyperv i2c_piix4 nf_defrag_ipv4 8250_fintek xt_conntrack joydev nf_conntrack mac_hid xt_owner xt_tcpudp iptable_security ip_tables x_tables ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic hid_hyperv hv_utils ptp hv_storvsc hyperv_keyboard hid hv_netvsc pps_core scsi_transport_fc hyperv_fb crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper psmouse pata_acpi cryptd hv_vmbus floppy fjes [ 11.349951] CPU: 10 PID: 891 Comm: systemd-udevd Tainted: GW 4.4.0-219-lowlatency #252-Ubuntu [ 11.349953] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 11.349954] 0286 1002a46b615445cb 881095a8f738 81861c01 [ 11.349957] 88109f096280 881095a8f748 810ac88b [ 11.349959] 881095a8f798 8186c241 81293b26 881a [ 11.349961] Call Trace: [ 11.349967] []
[Bug 1958386] [NEW] bpfilter umh restarts
Public bug reported: [Impact] When booting a system, lots of error messages regarding bpfilter are observed, like below. These indicate that the bpfilter user mode helper is exiting after reading the request message. [Test case] Boot a system and do not observe messages like "bpfilter: read fail 0" during boot. [ 260.724579] bpfilter: read fail 0 [ 260.784373] bpfilter: Loaded bpfilter_umh pid 2553 [ 260.784951] bpfilter: read fail 0 [ 260.855731] bpfilter: Loaded bpfilter_umh pid 2555 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958386 Title: bpfilter umh restarts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950666] Re: system crash when removing ipmi_msghandler module
https://lore.kernel.org/all/20211217154410.1228673-1-casca...@canonical.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950666 Title: system crash when removing ipmi_msghandler module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954904] [NEW] bpf pointer tainted kaslr leak
*** This bug is a security vulnerability *** Private security bug reported: [Impact] adjust_ptr_min_max_vals will allow a pointer arithmetic with any value, but set the register to a SCALAR, preventing further pointer operations, leading to a pointer leak, aka, KASLR leak. [Potential regression] Any potential fixes will change the verifier, which means that some BPF code that was previously allowed may be prevented to load. It may also lead to other code being allowed that leads to other vulnerabilities. [Test case] Use a privately shared code to test it. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954904 Title: bpf pointer tainted kaslr leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954815] Re: Support newer kernels
This debdiff for focal is against the version in impish. Contrary to the previous version of the debdiff, this one builds fine on focal. The versioned dependency on debhelper was changed from >= 13 to >= 12, as debhelper 13 is not currently available on focal. Cascardo. ** Patch added: "Proper fix for focal" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+attachment/5547612/+files/crash_7.3.0-1ubuntu1~20.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954815 Title: Support newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954815] Re: Support newer kernels
Notice the debdiff is against the version in impish (-release). ** Patch added: "Fix for hirsute" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+attachment/5547608/+files/crash_7.3.0-1ubuntu1~21.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954815 Title: Support newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954815] Re: Support newer kernels
Notice the debdiff is against the version in impish (-release), which is also the current version in jammy. ** Patch added: "Fix for focal" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+attachment/5547607/+files/crash_7.3.0-1ubuntu1~20.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954815 Title: Support newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954815] Re: Support newer kernels
Now building on ppa:cascardo/kdump2 for testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954815 Title: Support newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954815] [NEW] Support newer kernels
Public bug reported: [Impact] Kernels newer than 5.4 cannot be analyzed using the crash tool from Focal. [Test case] Install a linux dbgsym package and run the command below, replacing vmlinux-5.11.0-1023-azure by the appropriate kernel debug file. crash /usr/lib/debug/boot/vmlinux-5.11.0-1023-azure /proc/kcore [Potential regression] crash might fail to work with older kernels, or some of its commands might not work anymore. ** Affects: crash (Ubuntu) Importance: Undecided Status: Invalid ** Affects: crash (Ubuntu Focal) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: crash (Ubuntu Hirsute) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: crash (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Also affects: crash (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: crash (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: crash (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: crash (Ubuntu) Status: New => Invalid ** Changed in: crash (Ubuntu Impish) Status: New => Fix Released ** Changed in: crash (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: crash (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: crash (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: crash (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: crash (Ubuntu Hirsute) Status: New => In Progress ** Changed in: crash (Ubuntu Focal) Status: New => 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/1954815 Title: Support newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953287] Re: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants
This is the CVE reported for this issue: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-25020 The fix is this upstream commit, which I have backported to bionic, and will submit after running one extra test. https://github.com/torvalds/linux/commit/050fad7c4534c13c8eb1d9c2ba66012e014773cb Thanks. Cascardo. ** Information type changed from Private to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-25020 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Description changed: + [Impact] + A CBPF program jumping over a large number of instructions may lead to kernel code execution. + The test might fail with EINVAL or EOPNOTSUPP, which must be accounted for on different kernel versions. + + [Test case] + Load test_bpf module. + + [Potential regression] + Some CBPF and EBPF programs might not load. + + + + + + Issue found on 4.15.0-1107-ibm-gt with node onibi. This test failed without any obvious error from the test output, the summary shows there is one failure but all 344 test cases were marked as PASS: [ 1851.020315] test_bpf: #0 TAX jited:1 46 44 43 PASS [ 1851.021767] test_bpf: #1 TXA jited:1 43 46 43 PASS [ 1851.024004] test_bpf: #2 ADD_SUB_MUL_K jited:1 45 PASS [ 1851.024886] test_bpf: #3 DIV_MOD_KX jited:1 70 PASS [ 1851.026103] test_bpf: #4 AND_OR_LSH_K jited:1 39 43 PASS [ 1851.027394] test_bpf: #5 LD_IMM_0 jited:1 42 PASS [ 1851.028027] test_bpf: #6 LD_IND jited:1 85 85 85 PASS [ 1851.030687] test_bpf: #7 LD_ABS jited:1 87 85 85 PASS [ 1851.033343] test_bpf: #8 LD_ABS_LL jited:1 90 70 PASS [ 1851.035030] test_bpf: #9 LD_IND_LL jited:1 61 58 58 PASS [ 1851.036890] test_bpf: #10 LD_ABS_NET jited:1 86 70 PASS [ 1851.038590] test_bpf: #11 LD_IND_NET jited:1 77 56 56 PASS [ 1851.040573] test_bpf: #12 LD_PKTTYPE jited:1 43 43 PASS [ 1851.041582] test_bpf: #13 LD_MARK jited:1 41 42 PASS [ 1851.042494] test_bpf: #14 LD_RXHASH jited:1 42 44 PASS [ 1851.043436] test_bpf: #15 LD_QUEUE jited:1 43 43 PASS [ 1851.044379] test_bpf: #16 LD_PROTOCOL jited:1 50 50 PASS [ 1851.045457] test_bpf: #17 LD_VLAN_TAG jited:1 41 41 PASS [ 1851.046363] test_bpf: #18 LD_VLAN_TAG_PRESENT jited:1 39 41 PASS [ 1851.047238] test_bpf: #19 LD_IFINDEX jited:1 44 44 PASS [ 1851.048199] test_bpf: #20 LD_HATYPE jited:1 44 44 PASS [ 1851.049157] test_bpf: #21 LD_CPU jited:1 51 50 PASS [ 1851.050250] test_bpf: #22 LD_NLATTR jited:1 43 68 PASS [ 1851.051465] test_bpf: #23 LD_NLATTR_NEST jited:1 85 233 PASS [ 1851.054890] test_bpf: #24 LD_PAYLOAD_OFF jited:1 527 745 PASS [ 1851.067698] test_bpf: #25 LD_ANC_XOR jited:1 42 42 PASS [ 1851.069510] test_bpf: #26 SPILL_FILL jited:1 45 45 48 PASS [ 1851.071372] test_bpf: #27 JEQ jited:1 85 46 47 PASS [ 1851.073284] test_bpf: #28 JGT jited:1 85 46 49 PASS [ 1851.075260] test_bpf: #29 JGE (jt 0), test 1 jited:1 86 47 47 PASS [ 1851.077151] test_bpf: #30 JGE (jt 0), test 2 jited:1 48 45 44 PASS [ 1851.078613] test_bpf: #31 JGE jited:1 48 46 47 PASS [ 1851.080128] test_bpf: #32 JSET jited:1 45 44 54 PASS [ 1851.081667] test_bpf: #33 tcpdump port 22 jited:1 83 106 72 PASS [ 1851.084383] test_bpf: #34 tcpdump complex jited:1 83 102 93 PASS [ 1851.087279] test_bpf: #35 RET_A jited:1 41 41 PASS [ 1851.088195] test_bpf: #36 INT: ADD trivial jited:1 43 PASS [ 1851.088700] test_bpf: #37 INT: MUL_X jited:1 41 PASS [ 1851.089186] test_bpf: #38 INT: MUL_X2 jited:1 40 PASS [ 1851.089665] test_bpf: #39 INT: MUL32_X jited:1 42 PASS [ 1851.090170] test_bpf: #40 INT: ADD 64-bit jited:1 90 PASS [ 1851.091228] test_bpf: #41 INT: ADD 32-bit jited:1 91 PASS [ 1851.092232] test_bpf: #42 INT: SUB jited:1 88 PASS [ 1851.093260] test_bpf: #43 INT: XOR jited:1 56 PASS [ 1851.093920] test_bpf: #44 INT: MUL jited:1 194 PASS [ 1851.095947] test_bpf: #45 MOV REG64 jited:1 43 PASS [ 1851.096513] test_bpf: #46 MOV REG32 jited:1 45 PASS [ 1851.097471] test_bpf: #47 LD IMM64 jited:1 44 PASS [ 1851.098000] test_bpf: #48 INT: ALU MIX jited:1 73 PASS [ 1851.098807] test_bpf: #49 INT: shifts by register jited:1 53 PASS [ 1851.099421] test_bpf: #50 INT: DIV + ABS jited:1 92 54 PASS [ 1851.100960] test_bpf: #51 INT: DIV by -1 jited:1 85 50 PASS [ 1851.102431] test_bpf: #52 check: missing ret PASS [ 1851.102650] test_bpf: #53 check: div_k_0 PASS [ 1851.102660] test_bpf: #54 check: unknown insn PASS [ 1851.102674] test_bpf: #55 check: out of range spill/fill PASS [ 1851.102685] test_bp
[Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
https://lore.kernel.org/linuxppc- dev/20211207130557.40566-1-casca...@canonical.com/T/#u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
This looks like very similar to the vulnerable case that I changed to return as skipped. It's possible that the host is doing one mitigation while the guest is informed of a different mitigation, leading to this mis-match. I will take this upstream and see how it goes. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
focal/linux-ibm has not been updated to the latest focal/master-next version (5.4.0-92.103), which has the fix. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953366] Re: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el
As this is failing on ADT, it is failing on VMs on an environment we don't have much control of. This could be caused by host kernel, qemu or libvirt combinations that will make the guest kernel observe a given mitigation while it's not really in place. This test was added after 5.4, so the failure won't be observed on kernels before 5.11. I have fixed it once so it detects the Vulnerable case and have the test return the SKIP code. We need to fix this sooner rather than later, otherwise ADT test results will continue to fail. The other option is to skip this on our tests. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953366 Title: spectre_v2 from ubuntu_kernel_selftests ADT test failure with 5.13/5.11 ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
There is already documentation about it. For example, from https://ubuntu.com/server/docs/kernel-crash-dump "If the dump does not work due to OOM (Out Of Memory) error, then try increasing the amount of reserved memory by editing /etc/default/grub.d/kdump-tools.cfg. For example, to reserve 512 megabytes" There are multiple reasons why an OOM might happen during kdump, and there are no plans on detecting them on a case-by-case, so we won't do it for this specific case of root volume decryption. If we use a very large default that might work on almost all cases, it will take much more memory than is necessary for many users. On the other hand, using a default that won't work for most users is not any better. So, noticing that any default will affect all users, including those that do not enable root volume encryption or do not use argon2i; we have 3 options for the new default: 1) Keep 2G-4G:384M; some users won't be able to collect kdump unless they reconfigure the crashkernel option, but most users will, by reserving not more than 384M from a 2G VM. 2) Raise it to 2G-4G: 512M, it reserves more memory, and users with 2G to 4G VMs using argon2i for root volume encryption might be able to collect kdump for the sake of reserving more memory by default for users that don't use root volume encryption. 3) Remove the 2G-4G section of crashkernel: users with VMs smaller than 4G won't be able to collect kdump unless they configure and test a crashkernel configuration by themselves. I still think the first option is the better one. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
This is a debdiff for the proposed solution for kdump-tools, based on latest version on impish. ** Patch added: "kdump-tools_1.6.9ubuntu1+cascardo1.debdiff" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+attachment/5544958/+files/kdump-tools_1.6.9ubuntu1+cascardo1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
Aside from the new default crashkernel (or rather, whether to keep the 2G-4G:320M option or simply not setup crashkernel for the 2G-4G case), how does the new version of kdump-tools on ppa:cascardo/kdump2 work? To give you an answer, it does upgrade the crashkernel value on zipl.conf to a new default whatever value is configured on the current installed /etc/zipl.conf, including if it's not configured by default. However, in case we change the value in the future to a different one, ucf will be able to simply do the update in case the user has kept the old default value and has not done any other change on /etc/zipl.conf. In this latter case, the user will be asked whether to keep the old version or the new version. So, basically, this allows us to update the default in the future without keeping track of which versions supported which defaults. The only drawback is that the user might be prompted a little more often about changes in /etc/zipl.conf. Regards. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952094] Re: CIFS mount error: iocharset utf8 not found
Maybe this is the case of a missing linux-modules-extra installed? nls_utf8 module seems to be shipped on linux-modules-extra, and the missing package would explain the failure. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952094 Title: CIFS mount error: iocharset utf8 not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
Works fine on 5.10.0-1052-oem. Cascardo. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
Working as expected on 5.4.0-91-generic and 5.10.0-1052-oem. $ ldattach HCI /dev/tty ldattach: cannot set line discipline: Operation not permitted ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949516] Re: require CAP_NET_ADMIN to attach N_HCI ldisc
ldattach HCI /dev/tty That command works on 4.15.0-162, and fails with EPERM on 4.15.0-163. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
5 tests failed with 4.15.0-162. ALL pass with 4.15.0-163. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788578 Title: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Description changed: + [Impact] + setgid files may be created on setgid directories owned by the directory + group by users not belonging to that group. That is restricted to XFS. + + [Fix/Backport] + The fix for 5.11 and 5.10 kernels is one simple commit with a minor + backport conflict fixup on 5.10. + + 5.4, on the other hand, required other 3 pre-requisites, which could be + picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. + + [Test case] + creat09 LTP test case. + + [Potential regression] + The creation of files on XFS may have the wrong attributes. Also, on 5.4 + and 4.15, the potential regression is larger, also affecting quota, + statistics and other interfaces where uid, gid and projid are exposed. + + + = + These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:37: TINFO: mkfs is not needed for tmpfs tst_test.c:1431: TINFO: Testing on ext2 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext2 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext3 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext3 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/creat.tmp: Setgid bit not set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:94: TPASS: mntpoint/testdir/open.tmp: Setgid bit not set tst_test.c:1431: TINFO: Testing on ext4 tst_test.c:932: TINFO: Formatting /dev/loop3 with ext4 opts='' extra opts='' mke2fs 1.45.5 (07-Jan-2020) tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88:
[Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Description changed: + [Impact] + Some uses of kernel_read_file_from_fd may lead to a WARN when the file is + not opened for reading. + + The WARNING, however, is not present on earlier kernels, which will return + a different error code. The fix, however, has been applied to upstream stable + and may be worth so tests can PASS without much change. + + [Fix/Backport] + The fix is trivial, but the backport for Focal and Bionic was picked up + from 5.4.y upstream stable tree, because the function was moved to a + different file. + + [Test case] + The finit_module02 test case from LTP covers this. + + [Potential regression] + kernel_read_file_from_fd is used for module loading and kexec, so there is + where regressions might show up. + + + = + ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951132] Re: hirsute:linux-aws ubuntu_ltp Failed test cases : cve-2018-13405
*** This bug is a duplicate of bug 1950239 *** https://bugs.launchpad.net/bugs/1950239 Hey, Tim. This only fails on XFS, now that the test goes through all supported filesystems. This is being tracked and worked on as a different but, LP: #1950239. Marked as duplicate. Cascardo. ** This bug has been marked a duplicate of bug 1950239 creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951132 Title: hirsute:linux-aws ubuntu_ltp Failed test cases : cve-2018-13405 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
The fix has landed on 5.4.156 and 4.14.253. They will likely land on our kernels coming from upstream stable. I will make sure to have them on the mailing list anyway, in case we want to carry those fixes for an easier test verification and don't end up applying those corresponding fixes. Cascardo. ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Impish) Status: Confirmed => 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/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Released ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
There is the in-disk inode structure that makes it complicated to
backport the fix. Eventually, we would need something like the commit
below in older releases.
542951592c99ff7b15c050954c051dd6dd6c0f97 ("xfs: remove the icdinode
di_uid/di_gid members")
Alternatively, just making sure values match might be fine as on this
commit.
3d8f2821502d0b60bac2789d0bea951fda61de0c ("xfs: ensure that the inode
uid/gid match values match the icdinode ones")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950239
Title:
creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from
ubuntu_ltp/cve failed with XFS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Also 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/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
This will require a backport for older kernels as xfs_ialloc was renamed to xfs_init_new_inode. I am working on it. Cascardo. ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
From the LTP creat09 test comment: * This fix is incomplete if file is on xfs filesystem. * * Fixed in: * * commit 01ea173e103edd5ec41acec65b9261b87e123fc2 * Author: Christoph Hellwig * Date: Fri Jan 22 16:48:18 2021 -0800 * * xfs: fix up non-directory creation in SGID directories We need to fix this in all our affected kernels. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
I see a very similar issue from comment #36 on 3.13.0-187 and 3.13.0-188. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748103 Title: apic test in kvm-unit-test failed with timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824289] Re: ioapic in ubuntu_kvm_unit_tests failed on Trusty
Also fails on 3.13.0-187 and 3.13.0-188. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824289 Title: ioapic in ubuntu_kvm_unit_tests failed on Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1824289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions)
Fails on 3.13.0-187 and 3.13.0-188. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821906 Title: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
I found this failing on 3.13.0-187 and 3.13.0-188 as well, though after doing movdqu (write). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932966 Title: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821905] Re: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4
Found on trusty/linux 3.13.0-187 and 3.13.0-188. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821905 Title: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949516] [NEW] require CAP_NET_ADMIN to attach N_HCI ldisc
Public bug reported: [Impact] Any unprivileged user can attach N_HCI ldisc and send packets coming from a virtual controller by using PTYs. This exposes attack surface on systems where bluetooth is not needed or even allow local attacks that would otherwise require physical proximity. [Test case] Try attaching N_HCI ldisc to a tty. ldattach HCI /dev/tty [Potential regression] Users who rely on programs using N_HCI line discipline in order to emulate or proxy a bluetooth controller will require privilege they may not have. ** Affects: linux (Ubuntu) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949516 Title: require CAP_NET_ADMIN to attach N_HCI ldisc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
** Description changed: [Impact] Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. [Test case] Run the bpf test_verifier. [Potential regression] - Loading sample_period of bpf_perf_event_data may fail. + Loading sample_period of bpf_perf_event_data may fail. Unaligned access may lead to processor exceptions on some architectures. == - This issue was only spotted on i386 Bionic kernel.  #146/p unpriv: spill/fill of different pointers ldx FAIL  Unexpected error message!  0: (bf) r6 = r10  1: (07) r6 += -8  2: (15) if r1 == 0x0 goto pc+3  R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0  3: (bf) r2 = r10  4: (07) r2 += -76  5: (7b) *(u64 *)(r6 +0) = r2  6: (55) if r1 != 0x0 goto pc+1  R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp  7: (7b) *(u64 *)(r6 +0) = r1  8: (79) r1 = *(u64 *)(r6 +0)  9: (79) r1 = *(u64 *)(r1 +68)  #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL  Failed to load prog 'Permission denied'!  0: (b7) r0 = 0  1: (71) r0 = *(u8 *)(r1 +68)  invalid bpf_context access off=68 size=1  #353/p check bpf_perf_event_data->sample_period half load permitted FAIL  Failed to load prog 'Permission denied'!  0: (b7) r0 = 0  1: (69) r0 = *(u16 *)(r1 +68)  invalid bpf_context access off=68 size=2  #354/p check bpf_perf_event_data->sample_period word load permitted FAIL  Failed to load prog 'Permission denied'!  0: (b7) r0 = 0  1: (61) r0 = *(u32 *)(r1 +68)  invalid bpf_context access off=68 size=4  #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL  Failed to load prog 'Permission denied'!  0: (b7) r0 = 0  1: (79) r0 = *(u64 *)(r1 +68)  invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices:  total 0  crw-rw 1 root audio 116, 1 Aug 23 08:23 seq  crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb:  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions:  linux-restricted-modules-4.15.0-32-generic N/A  linux-backports-modules-4.15.0-32-generic N/A  linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788578 Title: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)
Backporting everything necessary would be up to many potential regressions. That would include support for BPF calls and the change to make unknown opcode handling more robust. The former would be commit cc8b0b92a1699bc32f7fec71daa2bfc90de43a4d "bpf: introduce function calls (function boundaries)", which would open a big can of worms we don't want to do. The latter is commit 5e581dad4fec0e6d062740dc35b8dc248b39d224 "bpf: make unknown opcode handling more robust". Though it might add more robustness, it changes the table in the interpreter, so I decided not to backport it now, and fixup the error messages in test_verifier, instead. By the way, commit 21ccaf21497b72f42133182716a42dbf573d314b "bpf: add further test cases around div/mod and others" should have been 3, at least 2, different commits. As it only changes tests, I am find simply doing a partial backport of it. I have it ready and tested, will send a patchset to the list. Cascardo. ** Description changed: - This is a scripted bug report about ADT failures while running linux - tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the - dep8 tests of the tested source or the kernel has yet to be determined. + [Impact] + selftests net will fail on i386, requiring engineers time to investigate, or leading to new BPF failures to be ignored. + + [Fix] + The fix is only to tests. + + [Test case] + Run test_bpf.sh from tools/testing/selftests/net/. + + [Potential regression] + Tests could fail on other architectures. + + + + + + This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz - 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
Hey, Andre. As we talked, this is applied to 5.4 kernels as well, 5.4.0-90 should have it. Can you test that it fixes the problem? Thanks. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788578] Re: Some test in ubuntu_bpf test_verifier failed on i386 Bionic kernel
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: + [Impact] + Narrow loads for bpf_perf_event_data is not possible on 32-bit arches. + + [Test case] + Run the bpf test_verifier. + + [Potential regression] + Loading sample_period of bpf_perf_event_data may fail. + + == + + This issue was only spotted on i386 Bionic kernel. - #146/p unpriv: spill/fill of different pointers ldx FAIL - Unexpected error message! - 0: (bf) r6 = r10 - 1: (07) r6 += -8 - 2: (15) if r1 == 0x0 goto pc+3 - R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 - 3: (bf) r2 = r10 - 4: (07) r2 += -76 - 5: (7b) *(u64 *)(r6 +0) = r2 - 6: (55) if r1 != 0x0 goto pc+1 - R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp - 7: (7b) *(u64 *)(r6 +0) = r1 - 8: (79) r1 = *(u64 *)(r6 +0) - 9: (79) r1 = *(u64 *)(r1 +68) - #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (71) r0 = *(u8 *)(r1 +68) - invalid bpf_context access off=68 size=1 - #353/p check bpf_perf_event_data->sample_period half load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (69) r0 = *(u16 *)(r1 +68) - invalid bpf_context access off=68 size=2 - #354/p check bpf_perf_event_data->sample_period word load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (61) r0 = *(u32 *)(r1 +68) - invalid bpf_context access off=68 size=4 - #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL - Failed to load prog 'Permission denied'! - 0: (b7) r0 = 0 - 1: (79) r0 = *(u64 *)(r1 +68) - invalid bpf_context access off=68 size=8 + Â #146/p unpriv: spill/fill of different pointers ldx FAIL + Â Unexpected error message! + Â 0: (bf) r6 = r10 + Â 1: (07) r6 += -8 + Â 2: (15) if r1 == 0x0 goto pc+3 + Â R1=ctx(id=0,off=0,imm=0) R6=fp-8 R10=fp0 + Â 3: (bf) r2 = r10 + Â 4: (07) r2 += -76 + Â 5: (7b) *(u64 *)(r6 +0) = r2 + Â 6: (55) if r1 != 0x0 goto pc+1 + Â R1=ctx(id=0,off=0,imm=0) R2=fp-76 R6=fp-8 R10=fp0 fp-8=fp + Â 7: (7b) *(u64 *)(r6 +0) = r1 + Â 8: (79) r1 = *(u64 *)(r6 +0) + Â 9: (79) r1 = *(u64 *)(r1 +68) + Â #352/p check bpf_perf_event_data->sample_period byte load permitted FAIL + Â Failed to load prog 'Permission denied'! + Â 0: (b7) r0 = 0 + Â 1: (71) r0 = *(u8 *)(r1 +68) + Â invalid bpf_context access off=68 size=1 + Â #353/p check bpf_perf_event_data->sample_period half load permitted FAIL + Â Failed to load prog 'Permission denied'! + Â 0: (b7) r0 = 0 + Â 1: (69) r0 = *(u16 *)(r1 +68) + Â invalid bpf_context access off=68 size=2 + Â #354/p check bpf_perf_event_data->sample_period word load permitted FAIL + Â Failed to load prog 'Permission denied'! + Â 0: (b7) r0 = 0 + Â 1: (61) r0 = *(u32 *)(r1 +68) + Â invalid bpf_context access off=68 size=4 + Â #355/p check bpf_perf_event_data->sample_period dword load permitted FAIL + Â Failed to load prog 'Permission denied'! + Â 0: (b7) r0 = 0 + Â 1: (79) r0 = *(u64 *)(r1 +68) + Â invalid bpf_context access off=68 size=8 Summary: 708 PASSED, 5 FAILED ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: User Name 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic i686 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Aug 23 08:23 seq - crw-rw 1 root audio 116, 33 Aug 23 08:23 timer + Â total 0 + Â crw-rw 1 root audio 116, 1 Aug 23 08:23 seq + Â crw-rw 1 root audio 116, 33 Aug 23 08:23 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Thu Aug 23 08:41:26 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: - Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub - Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Â Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Â Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Â Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub + Â Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Â Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedi
[Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
** Description changed:
+ [Impact]
+ When doing MOD by 1 with a immediate/constant divisor on PPC, the JIT will
produce code that returns the dividend, just like a division, instead of 0.
+
+ Both eBPF and cBPF will fail as well when doing such operations.
+
+ [Test case]
+ $ cat bpf-mod1.c
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+ #include
+
+ #define ARRAY_SIZE(array) (sizeof(array)/sizeof(array[0]))
+
+ static int pair[2];
+
+ static int attach()
+ {
+ int r;
+
+ struct sock_filter insn[] = {
+ { BPF_LD | BPF_W | BPF_ABS, 0, 0, 0 },
+ { BPF_ALU | BPF_MOD, 0, 0, 1 },
+ { BPF_RET | BPF_A, 0, 0, 0 },
+ };
+
+ struct sock_fprog prog = {};
+ prog.filter = insn;
+ prog.len = ARRAY_SIZE(insn);
+
+ socketpair(AF_UNIX, SOCK_DGRAM, 0, pair);
+ setsockopt(pair[1], SOL_SOCKET, SO_ATTACH_FILTER, ,
sizeof(prog));
+ return 0;
+ }
+
+ int main(int argc, char **argv)
+ {
+ int buf[5];
+ int r;
+ r = attach();
+ if (r < 0) {
+ err(1, "function will error out already");
+ }
+ write(pair[0], "hello", 5);
+ r = recv(pair[1], buf, 5, MSG_DONTWAIT);
+ if (r != -1 || errno != EAGAIN) {
+ err(1, "program failed");
+ }
+ return 0;
+ }
+ $ gcc -o bpf-mod1 bpf-mod1.c
+ $ ./bpf-mod1
+ cbpf-mod1: program failed: Success
+
+ After fix:
+ $ ./bpf-mod1
+ $ echo $?
+ 0
+
+ [Potential regression]
+ BPF programs might be misbehave on ppc64el.
+
+
+
This is a scripted bug report about ADT failures while running linux
tests for linux/5.4.0-90.101 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
-
Consistently failing on Focal/linux 5.4.0-90.101
13:15:26 DEBUG| [stdout] # selftests: net: test_bpf.sh
13:15:27 DEBUG| [stdout] # test_bpf: [FAIL]
13:15:27 DEBUG| [stdout] not ok 9 selftests: net: test_bpf.sh # exit=1
-
Testing failed on:
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/linux/20211021_141544_eda49@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948351
Title:
ppc64 BPF JIT mod by 1 will not return 0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
** Also affects: linux (Ubuntu Hirsute) 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/1948351 Title: ppc64 BPF JIT mod by 1 will not return 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948351] Re: ppc64 BPF JIT mod by 1 will not return 0
** Summary changed: - linux ADT test_bpf failure with linux/5.4.0-90.101 + ppc64 BPF JIT mod by 1 will not return 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948351 Title: ppc64 BPF JIT mod by 1 will not return 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101
Reading bionic commit 6e096fe0027f723f746f8179503784cb3579294a
("bpf/tests: Do not PASS tests without actually testing the result"),
and looking at the specific failing tests, it looks to be the case that
the test change has shown these failures starting now. Also included in
focal.
There is a JIT bug on ppc64, fixed by upstream commit
8bbc9d822421d9ac8ff9ed26a3713c9afc69d6c8 ("powerpc/bpf: Fix BPF_MOD when imm ==
1").
Testing with userspace, eBPF works fine, possibly because the verifier
changes the code before giving it to JIT. However, cBPF fails. Both on
4.15.0-160 and 4.15.0-162, so not a regression.
Cascardo.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948351
Title:
linux ADT test_bpf failure with linux/5.4.0-90.101
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947161] [NEW] ACL updates on OCFS2 are not revalidated
Public bug reported:
[Impact]
When ACLs are updated on OCFS2, their caches are not revalidated, requiring
remounts to be able to see the updates.
[Fix]
Upstream commits:
504ec37dfdfbf9c65166c51f7b12126d2a9b18dc ("ocfs2: fix remounting needed after
setfacl command")
9c0f0a03e386f4e1df33db676401547e1b7800c6 ("ocfs2: drop acl cache for
directories too")
[Test case]
On a single node:
setfacl -m u:user1:rwX dir1
getfacl dir1
On multiple nodes:
Node1:
getfacl dir1
Node2:
getfacl dir1
Node1:
setfacl -m u:user1:rwX dir1
getfacl dir1
Node2:
getfacl dir1
[Potential regression]
ACL changes on OCFS2 may stop working properly.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Affects: linux (Ubuntu Impish)
Importance: Medium
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947161
Title:
ACL updates on OCFS2 are not revalidated
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947161/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
[Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
** Also affects: linux (Ubuntu Bionic) 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/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) 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/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785207] Re: openat03 in ubuntu_ltp_syscall failed with Trusty
From glibc:
int
__libc_openat (int fd, const char *file, int oflag, ...)
{
mode_t mode = 0;
if (__OPEN_NEEDS_MODE (oflag))
{
va_list arg;
va_start (arg, oflag);
mode = va_arg (arg, mode_t);
va_end (arg);
}
return SYSCALL_CANCEL (openat, fd, file, oflag, mode);
}
/* Detect if open needs mode as a third argument (or for openat as a fourth
argument). */
#ifdef __O_TMPFILE
# define __OPEN_NEEDS_MODE(oflag) \
(((oflag) & O_CREAT) != 0 || ((oflag) & __O_TMPFILE) == __O_TMPFILE)
#else
# define __OPEN_NEEDS_MODE(oflag) (((oflag) & O_CREAT) != 0)
#endif
So, very likely __OPEN_NEEDS_MODE does not support O_TMPFILE on trusty. So,
this specific test will always fail on trusty. I wonder if this might cause
issues in the real world, and, then, justify a glibc update on trusty ESM.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785207
Title:
openat03 in ubuntu_ltp_syscall failed with Trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1785207/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Sent request upstream: https://lore.kernel.org/linuxppc-dev/YUpIqytZqpohq4EM@mussarela/T/#u I will ping some folks for some help there. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943960] Re: s390x BPF JIT vulnerabilities
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943960 Title: s390x BPF JIT vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
About this latest comment. So, CPU #0 has crashed at pc = c00813566eb8, its ctr and r12 match, same as usual, it was called by __bpf_prog_run_save_cb as the BPF JITed program. Dumping the program from CPU #0 perspective, it has traps at that address. It turns out the JIT fills up a whole page with traps and puts the JITed BPF program on a random offset of that page (look at kernel/bpf/core.c:bpf_jit_binary_alloc). When we go to the hotplugged CPU, however, CPU #9f (159), that same page looks different, with the code placed where it was expected. Still, it looks like fp->aux->jit_data is NULL on both CPUs, which is not as expected. I am wondering if either the icache is not being flushed properly, or RCU is not operating correctly. As other issues are not seen, more likely something related to the icache. But I don't see any IPIs involved when flushing the icache, so possibly firmware or micro- architecture related? Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
9f:mon> di c00813566000 1000 c00813566000 7fe8 trap ... c00813566eb8 6000 nop ... c00813566ec0 7c0802a6 mflrr0 c00813566ec4 f8010010 std r0,16(r1) c00813566ec8 f821ffa1 stdur1,-96(r1) c00813566ecc 3d80c000 lis r12,-16384 c00813566ed0 798c07c6 rldicr r12,r12,32,31 c00813566ed4 658c0036 orisr12,r12,54 c00813566ed8 618c51e0 ori r12,r12,20960 c00813566edc 7d8903a6 mtctr r12 c00813566ee0 4e800421 bctrl c00813566ee4 7c681b78 mr r8,r3 c00813566ee8 38210060 addir1,r1,96 c00813566eec e8010010 ld r0,16(r1) c00813566ef0 7c0803a6 mtlrr0 c00813566ef4 7d034378 mr r3,r8 c00813566ef8 4e800020 blr c00813566efc 7fe8 trap ... 9f:mon> r R00 = c00173d8 R16 = c07fe13e8cb0 R01 = c040074efda0 R17 = c07f8f6a R02 = c22d9900 R18 = c07f8f6a0080 R03 = c040074efbd8 R19 = c07f8f6a0080 R04 = 0020 R20 = c12ff767 R05 = 0003 R21 = c07f8f6a0080 R06 = 0002 R22 = c136cc78 R07 = 00517782 R23 = 0001 R08 = 001ebf7e3a55 R24 = 009f R09 = R25 = 0e60 R10 = 0001 R26 = 0900 R11 = 0f8e R27 = 0500 R12 = 4400 R28 = 0a00 R13 = c07fff6f4f80 R29 = 0f00 R14 = R30 = 0002 R15 = c12f6020 R31 = 0003 pc = c0017038 replay_soft_interrupts+0x68/0x2e0 cfar= lr = c00173d8 arch_local_irq_restore+0x128/0x160 msr = 90001033 cr = 24004428 ctr = c0042468 xer = 2000 trap = 500 9f:mon> c0 [link register ] c0f36d4c __bpf_prog_run_save_cb+0x5c/0x190 [c03a3780] c0fdf76c __ip_finish_output+0x8c/0x140 (unreliable) [c03a37f0] c0f36f2c run_bpf_filter+0xac/0x200 [c03a3850] c0f37104 reuseport_select_sock+0x84/0x170 [c03a3890] c112c1f8 inet6_lhash2_lookup+0x1c8/0x200 [c03a3910] c112c48c inet6_lookup_listener+0x25c/0x280 [c03a3a00] c1105e58 tcp_v6_rcv+0x7b8/0xf50 [c03a3b50] c10b79c0 ip6_protocol_deliver_rcu+0x110/0x630 [c03a3bc0] c10b803c ip6_input+0x10c/0x130 [c03a3c40] c10b76c4 ipv6_rcv+0x194/0x1c0 [c03a3cc0] c0ef68f4 __netif_receive_skb_one_core+0x74/0xb0 [c03a3d10] c0ef6d68 process_backlog+0x138/0x280 [c03a3d80] c0ef7e00 napi_poll+0x100/0x3c0 [c03a3e10] c0ef81b4 net_rx_action+0xf4/0x2d0 [c03a3ea0] c11815f0 __do_softirq+0x150/0x428 [c03a3f90] c002caec call_do_softirq+0x14/0x24 [c8fcf630] c0017448 do_softirq_own_stack+0x38/0x50 [c8fcf650] c01640a0 do_softirq+0xa0/0xb0 [c8fcf680] c01641a8 __local_bh_enable_ip+0xf8/0x120 [c8fcf6a0] c10b1a98 ip6_finish_output2+0x248/0x7c0 [c8fcf740] c10b1410 ip6_xmit+0x370/0x7b0 [c8fcf860] c110f7f4 inet6_csk_xmit+0xb4/0x130 [c8fcf900] c100e910 __tcp_transmit_skb+0x440/0x9f0 [c8fcfa10] c100f758 tcp_connect+0x2e8/0x390 [c8fcfae0] c11023e4 tcp_v6_connect+0x5e4/0x7b0 [c8fcfbd0] c1042e10 __inet_stream_connect+0x130/0x3a0 [c8fcfc30] c10430dc inet_stream_connect+0x5c/0x90 [c8fcfc70] c0eb8e58 __sys_connect_file+0xa8/0xe0 [c8fcfcb0] c0eb8f74 __sys_connect+0xe4/0x140 [c8fcfd90] c0eb8ff8 sys_connect+0x28/0x40 [c8fcfdb0] c0036fe4 system_call_exception+0xf4/0x200 [c8fcfe10] c000d860 system_call_common+0xf0/0x27c --- Exception: c00 (System Call) at 7cf993a78388 SP (712cb970) is in userspace 0:mon> r R00 = c0f36f2c R16 = ada3 R01 = c03a3780 R17 = 000a R02 = c22d9900 R18 = 0001 R03 = c00037c930e0 R19 = 0001 R04 = c00813110038 R20 = c040213f4d48 R05 = c0081311 R21 = R06 = c00037c930e0 R22 = 22b9 R07 = 0001 R23 = 0001 R08 = 0001 R24 = ada3 R09 = R25 = c0081311 R10 = c0011c2edf00 R26 = R11 = R27 = 00a0 R12 = c00813566eb8 R28 = c00037c930e0 R13 = c259 R29 = 0028 R14 = c21fa500 R30 = 0028 R15 = 22b9 R31 = c0081311 pc = c00813566eb8 cfar= c0f36d48 __bpf_prog_run_save_cb+0x58/0x190 lr = c0f36d4c __bpf_prog_run_save_cb+0x5c/0x190 msr = 90029033 cr =
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
*** This bug is a duplicate of bug 1909286 *** https://bugs.launchpad.net/bugs/1909286 I tested that when reuseport_bpf_cpu did not consider the last CPU, the one that has been hotplugged, it didn't crash. It didn't set affinity to that CPU, didn't even allocate socket for it. Then, I realized that attaching the BPF code was happening on that CPU as it happened right after the tests were run, and the last test set the CPU affinity to that CPU. So, I set the affinity to CPU 0 right before attaching the BPF code. So far, the system did not crash either. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
*** This bug is a duplicate of bug 1909286 *** https://bugs.launchpad.net/bugs/1909286 Krzysztof mentioned that this has been found on 5.14 as well. Using a system he lent me (huggins), I also tested with the commit that changed the call to use CTR and it failed as well. But it always failed when __bpf_prog_run_save_cb was calling the jited bpf_func, and CTR always matched NIP (though in that case, it is the CTR from __bpf_prog_run_save_cb, not the JITed code). Sometimes it was NULL (all zeroes), sometimes it looked like a legit kernel address, and I got one 0xfe80fe8000 (or something like it), which looks like some corruption on bpf_prog. Also, I noticed it doesn't happen always on CPU 0, which would be odd on its own. But it seems more likely. And it's either very hard to reproduce without doing the CPU hotplug or it is really necessary, and I left the program running on a loop for a long time and did not have any luck. I also changed it to an eBPF program instead of cBPF, but still a socket filter type. And used get_smp_processor_id instead of the raw_processor_id (though I recall this being the same on ppc64el), and it still reproduced. And when I returned a constant instead of doing the call, it also reproduced. No wonder, as when it fails, the program never runs. But the way those programs are compiled makes no difference. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Test kernel at: https://kernel.ubuntu.com/~cascardo/lp1927076_1.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
I was looking at latest changes since 5.11 to powerpc64 BPF JIT and found the following commit: commit 20ccb004bad659c186f9091015a956da220d615d Author: Naveen N. Rao Date: Wed Jun 9 14:30:24 2021 +0530 powerpc/bpf: Use bctrl for making function calls blrl corrupts the link stack. Instead use bctrl when making function calls from BPF programs. Reported-by: Anton Blanchard Signed-off-by: Naveen N. Rao Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20210609090024.1446800-1-naveen.n@linux.vnet.ibm.com Though the link stack is unarchitected, that is, it should be transparent to the user aside from branch prediction performance, perhaps there is a bug in the implementation. Considering we have only observed this on POWER8 and with different stack traces, I wouldn't discard the possibility. As this is not present on 5.13 either, I am building a test kernel with a backport so it can be tested. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Hi, Patricia. Can you clarify if you always need to run the hotplug test before reuseport_bpf_cpu in order to reproduce? I wonder what is the state that the hotplug test leaves the system in? How is it being run? The makefile runs it with the -a option, which in the systems I have available would fail to offline the last CPU (which is expected, different behavior from x86, where cpu0 cannot be offlined). Running it without any options would only offline the last CPU and online it again. I tried looking for differences between our kernels and 5.11.22 and the only cpuset changes I noticed were already present in the kernel you have just tested, and they were on paths unrelated to hotplug or BPF, so I am still baffled as to the real differences here. And given the different systems fail differently, it looks like this will require a dump or xmon so we can debug it. Thanks for all the help. I may ask for system access next week in order to help there. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923114] Re: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy
While looking for some improvements on cpu-on-off-test.sh, I investigated the path that is taken on azure. One good tool to debug these failures is the cpuhp tracing. echo 1 > /sys/kernel/debug/tracing/events/cpuhp/enable echo 1 > /sys/kernel/debug/tracing/tracing_on cat /sys/kernel/debug/tracing/trace_pipe & echo 0 > /sys/devices/system/cpu/cpu1/online bash-2660[001] 10306.404476: cpuhp_enter: cpu: 0001 target: 143 step: 213 (cpuhp_kick_ap_work) cpuhp/1-14 [001] 10306.404506: cpuhp_enter: cpu: 0001 target: 143 step: 212 (sched_cpu_deactivate) cpuhp/1-14 [001] 10306.420476: cpuhp_exit: cpu: 0001 state: 211 step: 212 ret: 0 cpuhp/1-14 [001] 10306.420502: cpuhp_enter: cpu: 0001 target: 143 step: 189 (msr_device_destroy [msr]) cpuhp/1-14 [001] 10306.420623: cpuhp_exit: cpu: 0001 state: 188 step: 189 ret: 0 cpuhp/1-14 [001] 10306.420629: cpuhp_enter: cpu: 0001 target: 143 step: 187 (mce_cpu_pre_down) cpuhp/1-14 [001] 10306.420653: cpuhp_exit: cpu: 0001 state: 186 step: 187 ret: 0 cpuhp/1-14 [001] 10306.420654: cpuhp_enter: cpu: 0001 target: 143 step: 184 (hv_synic_cleanup) cpuhp/1-14 [001] 10306.420655: cpuhp_exit: cpu: 0001 state: 183 step: 184 ret: -16 cpuhp/1-14 [001] 10306.426523: cpuhp_enter: cpu: 0001 target: 213 step: 185 (compute_batch_value) cpuhp/1-14 [001] 10306.426541: cpuhp_exit: cpu: 0001 state: 185 step: 185 ret: 0 cpuhp/1-14 [001] 10306.426546: cpuhp_enter: cpu: 0001 target: 213 step: 186 (acpi_soft_cpu_online) cpuhp/1-14 [001] 10306.426553: cpuhp_exit: cpu: 0001 state: 186 step: 186 ret: 0 cpuhp/1-14 [001] 10306.426553: cpuhp_enter: cpu: 0001 target: 213 step: 187 (mce_cpu_online) cpuhp/1-14 [001] 10306.426597: cpuhp_exit: cpu: 0001 state: 187 step: 187 ret: 0 cpuhp/1-14 [001] 10306.426606: cpuhp_enter: cpu: 0001 target: 213 step: 188 (console_cpu_notify) cpuhp/1-14 [001] 10306.426607: cpuhp_exit: cpu: 0001 state: 188 step: 188 ret: 0 cpuhp/1-14 [001] 10306.426611: cpuhp_enter: cpu: 0001 target: 213 step: 189 (msr_device_create [msr]) cpuhp/1-14 [001] 10306.426665: cpuhp_exit: cpu: 0001 state: 189 step: 189 ret: 0 cpuhp/1-14 [001] 10306.426667: cpuhp_enter: cpu: 0001 target: 213 step: 212 (sched_cpu_activate) cpuhp/1-14 [001] 10306.426670: cpuhp_exit: cpu: 0001 state: 212 step: 212 ret: 0 Notice the -16 failure on hv_synic_cleanup. It can fail for two reasons: the cpu is VMBUS_CONNECT_CPU, which is 0, not the case here, or the cpu is the target_cpu for a vmbus_channel. # grep 1 /sys/bus/vmbus/devices/*/channels/*/cpu /sys/bus/vmbus/devices/-0001-8899--/channels/3/cpu:1 /sys/bus/vmbus/devices/000d3a6e-002e-000d-3a6e-002e000d3a6e/channels/15/cpu:1 /sys/bus/vmbus/devices/f8b3781b-1e82-4818-a1c3-63d806ec15bb/channels/13/cpu:1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923114 Title: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel
Hey, @joalif. Has this been tested with focal 5.4 kernel too? Thanks. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942784 Title: makedumpfile not properly working on focal with 5.11 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940107] Re: libvirtd fails to create VM
Also working on hirsute:focal-linux on the system where it was found: ubuntu@riccioli:~$ uname -r ; virsh list 5.11.0-34-generic Id Name State 1bionic running And also on an oracle bare-metal instance with hirsute:linux-oracle 5.11.0-1017-oracle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940107 Title: libvirtd fails to create VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] Re: fails to launch linux L2 guests on AMD
Working fine also with 5.11 kernel on riccioli with 5.11.0-34-generic on hirsute. And also on a bare-metal Oracle instance with 5.11.0-1017-oracle on hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] Re: fails to launch linux L2 guests on AMD
Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system poweroff [ 24.054392] reboot: Power down ubuntu@bionic:~$ sudo poweroff Connection to 192.168.122.239 closed by remote host. Connection to 192.168.122.239 closed. ubuntu@riccioli:~$ cat /sys/module/kvm_amd/parameters/vgif 0 ubuntu@riccioli:~$ uname -r 5.4.0-84-generic ubuntu@riccioli:~$ ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940107] Re: libvirtd fails to create VM
Also works fine with focal:linux-oracle-5.11 5.11.0-1017-oracle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940107 Title: libvirtd fails to create VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] Re: fails to launch linux L2 guests on AMD
Same with bionic:linux-oracle-5.4 5.4.0-1054-oracle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] Re: fails to launch linux L2 guests on AMD
Requesting system poweroff [ 12.137724] reboot: Power down ubuntu@bionic:~$ sudo poweroff Connection to 192.168.122.239 closed by remote host. Connection to 192.168.122.239 closed. ubuntu@riccioli:~$ uname -r 4.15.0-156-generic ubuntu@riccioli:~$ ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] Re: fails to launch linux L2 guests on AMD
** Changed in: linux (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] [NEW] fails to launch linux L2 guests on AMD
Public bug reported: [Impact] Users won't be able to run a Linux inside a Linux guest. [Test case] Launch an L1 guest with libvirt, then launch an L2 guest using qemu inside that first/L1 guest. [Potential regression] There might be reduced performance due to vmexits for interrupt handling. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux-hwe-5.8 (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: linux-hwe-5.8 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-hwe-5.8 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940134] Re: fails to launch linux L2 guests on AMD
Adding linux-hwe-5.8 as invalid to document that the test case has been run there, and the bug has not shown up. Cascardo. ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1940134 Title: fails to launch linux L2 guests on AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940107] Re: libvirtd fails to create VM
** Summary changed: - libvirtd failes to create VM + libvirtd fails to create VM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940107 Title: libvirtd fails to create VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940107] Re: libvirtd failes to create VM
We have identified that upstream commit
00b89fe0197f0c55a045775c11553c0cdb7082fe ("sched: Make the idle task
quack like a per-CPU kthread") causes this, and its revert fixes the
problem.
@smb identified commit a8ea6fc9b089156d9230bfeef964dd9be101a4a9 ("sched:
Stop PF_NO_SETAFFINITY from being inherited by various init system
threads") should probably fix it, which will be tested and sent as part
of a respin for 5.11.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940107
Title:
libvirtd failes to create VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940107/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940107] [NEW] libvirtd failes to create VM
Public bug reported: [Impact] libvirtd won't be able to create VMs. [Test case] Start a VM using virsh/libvirtd: virsh start focal [Potential regression] Some other processes won't be able to start inside some cgroups. --- $ virsh start focal error: Failed to start domain focal error: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 22 Invalid argument 2021-08-16T15:11:23.005201Z qemu-system-x86_64: failed to initialize KVM: Invalid argument $ sudo dmesg | grep kvm [ 135.237378] kvm: Nested Virtualization enabled [ 135.237384] SVM: kvm: Nested Paging enabled [ 166.209556] kvm [4082]: kvm_vm_worker_thread: cgroup_attach_task_all failed with err -22 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940107 Title: libvirtd failes to create VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
