linux-kernel - Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFwrc2rbDyJgChwkfWBrZtmoVdC-abH0eOvs_zpnq1MPDQ@mail.gmail.com>
Date:	Sun, 13 May 2012 11:01:31 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mark Lord <kernel@...savvy.com>
Cc:	Sasha Levin <levinsasha928@...il.com>, Kay Sievers <kay@...y.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Yinghai Lu <yinghai@...nel.org>, Joe Perches <joe@...ches.com>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length
 record buffer

On Sun, May 13, 2012 at 6:22 AM, Mark Lord <kernel@...savvy.com> wrote:
>
> Look in syslog ?

That usually requires root permission, so it's an extra (annoying)
step. It also gives all kinds or other mostly irrelevant information
for a kernel person.

Besides, according to the same argument, dmesg shouldn't have times
*at*all*. So the "look in your syslog" is pointless for discussing the
dmesg timestamp.

                   Linus
--
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/