On Wed, Nov 05, 2014 at 10:52:18PM +0000, Steven Honeyman wrote:
> dmesg (from util-linux) currently has two methods for reading the kernel
> message ring buffer: /dev/kmsg and syslog(2). Since kernel 3.5.0 kmsg has
> been the default, which escapes control characters (e.g. new lines) before
> they are shown.
>
> This change means that when dmesg is using /dev/kmsg, a 2 line printk makes
> the output messy, because the second line does not get a timestamp.
> For example:
>
> [ 0.012863] CPU0: Thermal monitoring enabled (TM1)
> [ 0.012869] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
> Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
> [ 0.012958] Freeing SMP alternatives memory: 28K (ffffffff81d86000 -
> ffffffff81d8d000)
> [ 0.014961] dmar: Host address width 39
>
> Because printk.c intentionally escapes control characters, they should not be
> there in the first place.
> This patch fixes two occurrences of this.
>
> V2: Revert change to log level, only fix the newline formatting issue
> V3: Expand patch description
> V3b: Fix silly mistake (log level)
>
> Signed-off-by: Steven Honeyman <stevenhoney...@gmail.com>
Acked-by: Borislav Petkov <b...@suse.de>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
