linux-kernel - Re: [PATCH] Print sysrq-m messages with KERN

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: <20070102172846.GC7656@redhat.com>
Date:	Tue, 2 Jan 2007 12:28:46 -0500
From:	Dave Jones <davej@...hat.com>
To:	Alan <alan@...rguk.ukuu.org.uk>
Cc:	Theodore Tso <tytso@....edu>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Print sysrq-m messages with KERN_INFO priority

On Tue, Jan 02, 2007 at 10:33:32AM +0000, Alan Cox wrote:
 > On Mon, 1 Jan 2007 23:37:43 -0500
 > Theodore Tso <tytso@....edu> wrote:
 > > > Is this patch a consistency thing?
 > > 
 > > The goal of the patch was to avoid filling /var/log/messages huge
 > > amounts of sysrq text.  Some of the sysrq commands, especially sysrq-m
 > > and sysrq-t emit a truly vast amount of information, and it's not
 > > really nice to have that filling up /var/log/messages.  
 > 
 > I find it extremely useful that it ends up in /var/log/messages so that I
 > can review the dump later. Often the first glance through a set of dumps
 > on things like a process deadlock don't reveal the right information and
 > you need to go back and look again.

Seconded.  And with the limited scrollback of the ringbuffer, sometimes
looking through the logs is the only way to get the info.

		Dave

-- 
http://www.codemonkey.org.uk
-
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/