September 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1190412] New: after update to kernel-default-5.3.18-lp152.87.1.x86_64 machine can't power off
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190412 Bug ID: 1190412 Summary: after update to kernel-default-5.3.18-lp152.87.1.x86_64 machine can't power off Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After update to kernel-default-5.3.18-lp152.87.1.x86_64 the machine can not power off. When I revert to kernel-default-5.3.18-lp152.84.1.x86_64, there is problem. I will now obtain logs to attach here. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190561 https://bugzilla.suse.com/show_bug.cgi?id=1190561#c11 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bpetkov(a)suse.com) | --- Comment #11 from Borislav Petkov <bpetkov(a)suse.com> --- Possible. This here: https://lwn.net/Articles/804937/ talks about taking this patch into a bpf set in order to fix a race: "The patch is necessary to do s/text_poke/text_poke_bp/ in patch 3 to fix the race." And this here looks like a race ... HTH. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190561 https://bugzilla.suse.com/show_bug.cgi?id=1190561#c10 Michal Kube��ek <mkubecek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov(a)suse.com Flags| |needinfo?(bpetkov(a)suse.com) --- Comment #10 from Michal Kube��ek <mkubecek(a)suse.com> --- It's a blind shot but perhaps the problem may be missing backport of c3d6324f841b ("x86/alternatives: Teach text_poke_bp() to emulate instructions") while we have some later backports from times when there was no detour member in struct text_poke_loc, e.g. the commit from comment 9 or backport of commit 285a54efe386 ("x86/alternatives: Sync bp_patching update for avoiding NULL pointer exception"). Boris, what do you think? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190561 http://bugzilla.opensuse.org/show_bug.cgi?id=1190561#c9 --- Comment #9 from Mark Rohrbacher <m.rohrbacher(a)r-dev.de> --- Reverting the commit 28924f7b0963da7e4ce098baa067c3d36dbf49ff could solve the problem: bpf: Simplify __bpf_arch_text_poke poke type handling (bsc#1154353). suse-commit: e9229505be158934fd6d02eb5003ad7c3da74663 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190561 Mark Rohrbacher <m.rohrbacher(a)r-dev.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190561 http://bugzilla.opensuse.org/show_bug.cgi?id=1190561#c8 --- Comment #8 from Mark Rohrbacher <m.rohrbacher(a)r-dev.de> --- Created attachment 852615 --> http://bugzilla.opensuse.org/attachment.cgi?id=852615&action=edit partial output from crash "foreach bt" Attached a cropped output from the "foreach bt" command from "crash", showing the backtrace of the crashing veth_poll+0x337 (I suppose this is veth.c:580, bpf_prog_run_xdp) and the backtrace of the installation of the xdp program. It seems that the call to bpf_prog_run_xdp finally leads to an half-patched bpf_dispatcher_xdp_func: crash> dis bpf_dispatcher_xdp_func 0xffffffff99594790 <bpf_dispatcher_xdp_func>: int3 0xffffffff99594791 <bpf_dispatcher_xdp_func+1>: imul $0xffffffc6,0x76e92729(%rax),%ebx 0xffffffff99594798 <bpf_dispatcher_xdp_func+8>: rex.RX add %r12b,0xf(%rsi) 0xffffffff9959479c <bpf_dispatcher_xdp_func+12>: (bad) 0xffffffff9959479d <bpf_dispatcher_xdp_func+13>: add %r8b,(%rax) Not 100% sure about the following, but: crash> p bp_patching bp_patching = $2 = { vec = 0xffffb0d965ff7488, nr_entries = 1 } crash> p bp_patching.vec[0] $4 = { detour = 0x0, addr = 0xffffffff99594790, len = 5, opcode = "\351k\240)'" } in combination with the line regs->ip = (unsigned long) tp->detour; from the poke_int3_handler could be the problem (note that the text_poke_bp call from __bpf_arch_text_poke supplies "NULL" as detour handler). I re-tested with a recent Tumbleweed kernel (5.13.13-1-default) on a desktop machine with 8 cores (Intel Xeon W-2123) and couldn't reproduce the problem there. The text_poke_bp_patch / poke_int3_handler combination is completely different here and seems to be safe. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190561] OOPS / Invalid RIP in when attaching XDP program to veth interface
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190561 https://bugzilla.suse.com/show_bug.cgi?id=1190561#c7 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbohac(a)suse.com, | |mkubecek(a)suse.com, | |tiwai(a)suse.com --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Looks like the issue with net core stuff. Adding relevant people to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190594] No dvb modules in kernel-default in 15.3
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190594 https://bugzilla.suse.com/show_bug.cgi?id=1190594#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- There is no list found in the documentation, AFAIK. The kernel-default contains the "supported" modules by SLE (that will be maintained over a decade), while kernel-default-extra and *-optional are leaf modules that have less maintenance period. The *-optional is available only on Leap. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190594] No dvb modules in kernel-default in 15.3
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190594 https://bugzilla.suse.com/show_bug.cgi?id=1190594#c2 Thomas Wagner <wagner-thomas(a)gmx.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wagner-thomas@gmx | |.at) | --- Comment #2 from Thomas Wagner <wagner-thomas(a)gmx.at> --- Thank you for pointing out that the kernel-default package was split. I did read the upgrade notes, but could find a hint pointing to the split. After installing the kernel-default-extra package, the DVB modules are working again. As a side-question: Is there some documentation describing what is in which of the kernel-default-* packages? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190567] vmlinuz is no longer present on /boot/ breaking separate boot partitions
by bugzilla_noreply＠suse.com 17 Sep '21

17 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190567 https://bugzilla.suse.com/show_bug.cgi?id=1190567#c7 Marcus Schaefer <ms(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Marcus Schaefer <ms(a)suse.com> --- We fixed the integration tests that tested boot on an extra partition by code that resolves the symlink back to be no link anymore. This fixes our tests. What stays imho is some smell for everybody that wants to build an image were /boot and /usr is not the same storage. That opened a can of worms and some extra code in the kernel post scripts. >The OS moves to /usr and /usr only. Those symlinks are only created for >compatibility until the tooling around bootloaders is adopted. That's fine by me. So /boot will go away from Linux ? That's the driver right ? In this case I'm still confused were the value is in such a change, or in other words what is wrong with /boot and why did it harm users to have data in /boot such that it has to move to /usr I'm asking this to have a good answer to all the people which will come across the appliance building way. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 0