linux-kernel - Re: [PATCH] printk: support structured and multi-facility log messages

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: <CAPXgP13XZFw6zPL6=pLP=pp7X-hsFetL2pVm1Jj3v6FX-vJTyw@mail.gmail.com>
Date:	Thu, 5 Apr 2012 10:44:29 +0200
From:	Kay Sievers <kay@...y.org>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org, Greg Kroah-Hartmann <greg@...ah.com>
Subject: Re: [PATCH] printk: support structured and multi-facility log messages

On Thu, Apr 5, 2012 at 10:38, Joe Perches <joe@...ches.com> wrote:
> On Wed, 2012-04-04 at 21:59 +0200, Kay Sievers wrote:
>> From: Kay Sievers <kay@...y.org>
>> + * In a flat text stream of records, every record should be terminated
>> + * by "\n\n", which separates the records from each other.
>
> What do you do about "\n\n" in existing printks?
>
> $ grep -rP --include=*.[ch] '\bprintk\b.*\\n\\n' *

Messages with non-printable characters are exported to the syslog()
syscall or /proc/kmsg as they are, like it always was, but the export
to /dev/kmsg encodes the MESSAGE= property as a binary property then.

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/