linux-kernel - Re: [RFC PATCH 1/2] printk: Add context information to the header of /dev/kmsg

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]

Date:	Mon, 19 May 2014 23:36:10 -0400
From:	Valdis.Kletnieks@...edu
To:	Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@...achi.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Kay Sievers <kay@...y.org>, linux-kernel@...r.kernel.org,
	Kees Cook <keescook@...omium.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Petr Mladek <pmladek@...e.cz>,
	Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>,
	yrl.pp-manager.tt@...achi.com,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Joe Perches <joe@...ches.com>, Arun KS <arunks.linux@...il.com>
Subject: Re: [RFC PATCH 1/2] printk: Add context information to the header of /dev/kmsg

On Mon, 19 May 2014 19:28:38 +0900, Yoshihiro YUNOMAE said:

> The header information is changed as follows:
>    <prefix>,<seq#>,<timestamp>,<fragmented>,<PID>/<interrupt context>;<msg>

Has this been tested with popular userspace that reads /dev/kmsg, to make
sure that it actually plays nice with a 5th field being added?  Yes, I know
that Documentation/ABI/dev-kmsg says that added fields should be gracefully
ignored - but we all know how good userspace programmers are about that
sort of thing. :)

Content of type "application/pgp-signature" skipped