linux-kernel - Re: [RFC] Add Alternative Log Buffer Support for printk 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: <20090121.123739.97186745.davem@davemloft.net>
Date:	Wed, 21 Jan 2009 12:37:39 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	gerickson@...vations.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] Add Alternative Log Buffer Support for printk Messages

From: Grant Erickson <gerickson@...vations.com>
Date: Wed, 21 Jan 2009 09:39:46 -0800

> This merges support for the previously DENX-only kernel feature of
> specifying an alternative, "external" buffer for kernel printk
> messages and their associated metadata. In addition, this ports
> architecture support for this feature from arch/ppc to arch/powerpc.
> 
> When this option is enabled, an architecture- or machine-specific log
> buffer is used for all printk messages. This allows entities such as
> boot loaders (e.g. U-Boot) to place printk-compatible messages into
> this buffer and for the kernel to coalesce them with its normal
> messages.
> 
> Signed-off-by: Grant Erickson <gerickson@...vations.com>

Nice.

This would also be useful on Sparc where it is possible to tell
the firmware to set aside a piece of physical memory which survives
soft resets and thus can be inspected post reboot.
--
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/