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]

Date:	Fri, 15 Jun 2012 05:23:25 -0700
From:	Anton Vorontsov <anton.vorontsov@...aro.org>
To:	Kay Sievers <kay@...y.org>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	Kees Cook <keescook@...omium.org>,
	Colin Cross <ccross@...roid.com>,
	Tony Luck <tony.luck@...el.com>,
	John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to
 variable-length record buffer

On Fri, Jun 15, 2012 at 02:07:51PM +0200, Kay Sievers wrote:
[...]
> From: Kay Sievers <kay@...y.org>
> Subject: kmsg - kmsg_dump() use iterator to receice log buffer content
> 
> Provide an iterator to receive the log buffer content, and convert all
> kmsg_dump() user to it.
> 
> The structured data in the kmsg buffer now contains binary data, which
> should no longer be copied verbatim to the kmsg_dump() users.
> 
> The iterator should provide reliable access to the buffer data, and also
> supports proper log line-aware chunking of data while iterating.
> 
> Signed-off-by: Kay Sievers <kay@...y.org>

Thanks Kay, it works!

Reported-by: Anton Vorontsov <anton.vorontsov@...aro.org>
Tested-by: Anton Vorontsov <anton.vorontsov@...aro.org>
--
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/