| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20061206090026.GB28160@elte.hu> Date: Wed, 6 Dec 2006 10:00:26 +0100 From: Ingo Molnar <mingo@...e.hu> To: Randy Dunlap <randy.dunlap@...cle.com> Cc: Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org Subject: Re: [patch] add ignore_loglevel boot option * Randy Dunlap <randy.dunlap@...cle.com> wrote: > > sometimes the kernel prints something interesting while userspace > > bootup keeps messages turned off via loglevel. Enable the printing > > of /all/ kernel messages via the "ignore_loglevel" boot option. Off > > by default. > > Hi, > > Is this equivalent to using the "debug" kernel parameter except that > userspace (init scripts) cannot muck it up (modify the setting)? yeah. > I've seen init scripts modify the loglevel, much to my dismay. yeah - i once lost a few hours of debugging to such an incident. > I'd say that this is useful, but it's really userspace that needs to > be fixed. well, loglevel /can/ be managed by userspace, and sometimes an important kernel message might have a too high loglevel. Also, sometimes the kernel does spurious messages during hardware detect, etc., so userspace naturally wants to prevent them from going to the console. So it's really a mix of a problem and i wouldnt put the blame on user-space. User-space used the only control they have to fix the situation. Ingo - 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