| 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: <4655BC2D.2070701@oracle.com> Date: Thu, 24 May 2007 09:24:13 -0700 From: Randy Dunlap <randy.dunlap@...cle.com> To: Jan Engelhardt <jengelh@...ux01.gwdg.de> CC: lkml <linux-kernel@...r.kernel.org>, akpm <akpm@...ux-foundation.org> Subject: Re: [PATCH] add "notime" boot option Jan Engelhardt wrote: > On May 22 2007 12:09, Randy Dunlap wrote: >> From: Randy Dunlap <randy.dunlap@...cle.com> >> >> Add "notime" boot option to prevent timing data from being printed on >> each printk message line. >> >> We've seen a few cases of 'time' data locking problems (possibly >> involving netconsole or net drivers). If a kernel is built with >> CONFIG_PRINTK_TIME=y, it may have a boot locking hang. Booting >> with "notime" may (i.e., could) prevent the lock hang and allow the >> kernel to boot successfully, without requiring a kernel rebuild. > > Wonderful, now we have _three_ options to control time... > > time=<bool> > printk.time=<bool> > notime=<bool> Currently the middle one is "printk.printk_time". And the first and last are just "time" and "notime", without a bool value. And as I wrote later, I'd be happy to remove #s 1 and 3 and use only the middle one, renaming the param so that it _is_ printk.time. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - 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