[Bug 671622] New: sytemd: panic caused by Secure Access Key (systemd gets killed by SysRQ-K)
https://bugzilla.novell.com/show_bug.cgi?id=671622 https://bugzilla.novell.com/show_bug.cgi?id=671622#c0 Summary: sytemd: panic caused by Secure Access Key (systemd gets killed by SysRQ-K) Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de CC: kasievers@novell.com Found By: Third Party Developer/Partner Blocker: --- systemd gets killed by the Secure Access Key on console 1. I'm not sure if this is a kernel bug (should PID 1 ever get a kill signal?) or a systemd bug (should it detach from console?), but it is damn annoying and security relevant (using SAK before logging in on console is mandatory IMHO). sysvinit does of course survive SAK. How to reproduce: Enable SysRQ, switch to console 1, press SysRQ K. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671622 https://bugzilla.novell.com/show_bug.cgi?id=671622#c1 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@novell.com --- Comment #1 from Jiri Slaby <jslaby@novell.com> 2011-02-14 09:58:34 UTC --- (In reply to comment #0)
systemd gets killed by the Secure Access Key on console 1.
I'm not sure if this is a kernel bug (should PID 1 ever get a kill signal?) or a systemd bug (should it detach from console?), but it is damn annoying and security relevant (using SAK before logging in on console is mandatory IMHO).
sysvinit does of course survive SAK.
Probably systemd is bound to some tty. SAK is expected to kill everybody bound to the tty. Could you set logging to a high level and to the current tty to see who the kernel kills and the do SAK? (klogconsole -l 8 -r 0) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671622 https://bugzilla.novell.com/show_bug.cgi?id=671622#c Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider| |seife@novell.slipkontur.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671622 https://bugzilla.novell.com/show_bug.cgi?id=671622#c2 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|seife@novell.slipkontur.de | --- Comment #2 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-02-14 11:23:01 CET --- I agree with your assessment, but I'm not sure what information the log will bring. Yes, SAK kills systemd on console 1 (it does not e.g. on console 2), probably because it is bound to tty1. So before killing my system for no reason to find out stuff we already know, it would be good to know what we want to achieve with the log (which will be hard to capture ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671622 https://bugzilla.novell.com/show_bug.cgi?id=671622#c3 --- Comment #3 from Stefan Seyfried <seife@novell.slipkontur.de> 2011-02-14 11:46:30 CET --- Ok. Trying to reproduce it does not happen anymore but everything looks fine :-( Maybe related to the general systemd problems I had https://bugzilla.novell.com/show_bug.cgi?id=671561 So feel free to close this. Even though it might be worth thinking if SAK should ever kill PID 1, even if it misbehaves (init=/bin/bash gets killed by SAK because its fd 0 is current tty), but that's probably something for an upstream discussion, maybe I should cook up a patch ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=671622 https://bugzilla.novell.com/show_bug.cgi?id=671622#c4 Brandon Philips <bphilips@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |bphilips@novell.com Resolution| |FIXED --- Comment #4 from Brandon Philips <bphilips@novell.com> 2011-03-08 00:15:51 UTC --- Closing via Comment #3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com