[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 1 Jul 2011 15:20:51 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Vasiliy Kulikov <segoon@...nwall.com>
Cc: kernel-hardening@...ts.openwall.com,
Linus Torvalds
<torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
James Morris <jmorris@...ei.org>, Namhyung Kim <namhyung@...il.com>,
Greg
Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH v2] kernel: escape non-ASCII and
control characters in printk()
> $ dmesg | tail
> ...
> [16291.982492] init[21579]: segfault at 0 ip 00007f527186028a sp 00007fff08251dd8 error 4 in libc-2.11.1.so[7f52717d8000+17a000]
> [16379.001357] fail[21586]: segfault at 0 ip 00007f332831028a sp 00007fffc52de568 error 4 in libc-2.11.1.so[7f3328288000+17a000]
> $
> (see 1234 => init change)
>
> As you see here, the previous log entry was showed not as it was
> initally logged. Core dump message was chosen fully arbitrary, just to
> show that some specific part of it can be "edited".
Your syslog daemon appears to need improvement and that would be the
right fix for dmesg etc.
The other case is the actual printk direct to console case, particularly
on a serial port. That one actually has more potential for actual
annoyance.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
