| 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
| ||
|
Date: Tue, 8 May 2012 18:27:42 +0200 From: Kay Sievers <kay@...y.org> To: Sasha Levin <levinsasha928@...il.com> Cc: Greg Kroah-Hartmann <greg@...ah.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org, Karel Zak <kzak@...hat.com> Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer On Tue, May 8, 2012 at 5:57 PM, Sasha Levin <levinsasha928@...il.com> wrote: > What about PRINTK_TIME? Are there plans to enable it on console output? Yeah, we should restore the old behaviour. The timestamp is always stored internally, regardless of the CONFIG_PRINTK_TIME or tunable setting. At the moment, seems they are only (conditionally) added to the syslog() output and (unconditionally) to the /dev/kmsg export. I guess we just re-define CONFIG_PRINTK_TIME and the tunable as: "show time in syslog() and on the console output". Karel will likely extend dmesg(1) to use /dev/kmsg instead of syslog() when it's readable and dmesg(1) can still show the time stamps read from /dev/kmsg, even when CONFIG_PRINTK_TIME is not set, so the old tunable basically becomes a "show timestamps on the console" flag. :) Kay -- 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