July 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 09 Jul '20

09 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c40 --- Comment #40 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Takashi Iwai from comment #8) > The problem isn't too serious on TW because the TW kernel (i.e. the upstream > kernel) still has no strict lockdown. SLE / Leap kernel has a stricter > lockdown, so it can be an actual problem. It might be a problem on TW as > well once when the upstream accepts the more lockdown. Seems we didn't listen closely to Takashi. :-( Can we have "less" lockdown, please? ;-) > IOW, it's not only about CONFIG_MODULE_SIG. Rather the key point is whether > the kernel has a lockdown feature for the unsigned module or not. Hmm. Is this configurable? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 09 Jul '20

09 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c39 --- Comment #39 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Michal Kubeček from comment #37) > (In reply to Martin Wilck from comment #36) > > Is this perhaps caused by recent lockdown patches? Is that the reason why it > > doesn't behave the way we were used to? > > Not so recent, actually. The lockdown backport was merged into SLE15-SP2 > branch on November 27th and into openSUSE-15.2 one day later. Not that old. We would need a kernel build before this happened to see whether the lockdown is the culprit here. And if it is I would expect - even if there would an agreement to remove this feature (very unlikely?) - it won't be doable any longer with thousands of patches sitting on top of it meanwhile ... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 09 Jul '20

09 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c38 --- Comment #38 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Martin Wilck from comment #35) > And we also got it wrong in the release notes :-(( > > > https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.2/#sec.drive… > "Importantly, this affects NVIDIA or AMD graphics drivers from the manufacturer's repositories" This sounds very confusing. As if AMD and NVIDIA would provide signed kernel modules. They don't. They only provide a binary part, which gets built/linked against a glue layer source during installation. > "Kernel Module Packages (KMPs) from the official openSUSE repositories are not affected, because the modules they contain > are signed with the openSUSE key." Do we offer any openSUSE KMPs other than the one for NVIDIA? I doubt. And the NVIDIA one is very special, because everything is build/linked on the target system for legal reasons. Or are openSUSE Community repos not considered official? Could be ... > "Kernel modules that are not signed will be treated as being “tainted”. Loading them will result in a warning message, but > they will function." now proved to be a wrong assumption :-( > I have to confess I didn't test this myself, and what Michal said matched my > shady memories how it used to behave when I last tried (+4y ago). I haven't tested this either unfortunately. :-( -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c37 --- Comment #37 from Michal Kubeček <mkubecek(a)suse.com> --- (In reply to Martin Wilck from comment #36) > Is this perhaps caused by recent lockdown patches? Is that the reason why it > doesn't behave the way we were used to? Not so recent, actually. The lockdown backport was merged into SLE15-SP2 branch on November 27th and into openSUSE-15.2 one day later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c36 --- Comment #36 from Martin Wilck <martin.wilck(a)suse.com> --- >From bug 1173682, comment 0: > Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 Is this perhaps caused by recent lockdown patches? Is that the reason why it doesn't behave the way we were used to? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c35 --- Comment #35 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Stefan Dirsch from comment #34) > Obviously this turned out to be fake news. :-( And we also got it wrong in the release notes :-(( > https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.2/#sec.drive… I have to confess I didn't test this myself, and what Michal said matched my shady memories how it used to behave when I last tried (+4y ago). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173591] Build of VMware access to kernel gives issues at interface build time.
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173591 https://bugzilla.suse.com/show_bug.cgi?id=1173591#c8 --- Comment #8 from Dick Waite <dick.waite(a)softwareag.com> --- With the grand help of Michal I now have three phyiscal Leap15.2 machines running with VMware Workstation 15.5.6. Saturday it will be the time for SLES15 SP-2. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173860] kernel-5.3.18-lp152.20.7.1 crash at boot with permissions violation
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173860 https://bugzilla.suse.com/show_bug.cgi?id=1173860#c4 --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- seems ucode unrelated > BUG: Unable to handle page fault for address: 0x.... > #PF: supervisot write access in kernel mode > #PF: error_code(0x0003) - permissions violation > Oops: 0003 [#8635] SMP NOPTI > CPU 0 PID: 495 Comm: systemd-udevd Tainted: ... > Hardware name: To be filled by O.E.M > RIP: 0010:blk_flush_plug_list+0x6c/0xf0 some blocklayer messup -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173448] Webcam(earlier working) doesn't work now. Sony Vaio
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173448 http://bugzilla.opensuse.org/show_bug.cgi?id=1173448#c4 --- Comment #4 from Aman Vaishya <avaish92(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > And this webcam worked in the earlier releases of TW or any other distros? > If yes, could you give that information? yes it worked in earlier versions of opensuse, for Leap 15.1, and Tumbleweed for last year November. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173738] NVIDIA module hangs when X starts
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173738 https://bugzilla.suse.com/show_bug.cgi?id=1173738#c2 --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- Not sure how you extracted the journalctl if the machine hangs before X gets started, but maybe then you can also attach the result of a nvidia-bug-report.sh run. -- You are receiving this mail because: You are the assignee for the bug.

1 0