lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 2 Apr 2014 20:49:27 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Mateusz Guzik <mguzik@...hat.com> Cc: LKML <linux-kernel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>, Mel Gorman <mgorman@...e.de>, Kay Sievers <kay@...y.org> Subject: Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline On Thu, 3 Apr 2014 00:12:13 +0200 Mateusz Guzik <mguzik@...hat.com> wrote: > Well, parsing kernel cmdline by systemd is a bad idea, and hiding > "debug" is even worse. What will happen when the next keyword clashes? > And how should I check the kernel is booted with "debug"? No, I think you got it backwards. Hiding "debug" is a bad idea, having systemd abuse the hell out of it is even worse. > > If there is a real need to pass arguments to systemd, how about a > dedicated option (initargs= or whatever, where it has to be last in > cmdline), then systemd would be spawned with these arguments and would > just go over its argv. > No, the correct solution was to have systemd use its own flag. Say "systemd.debug", which I believe from froward reading my emails, Greg has already sent a patch to do so. That solution was even suggested in the BZ and was turned down with the quote I had in my change log. That we don't own the generic terms, even though it's our f*cking command line, not theirs! -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists