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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101103215851.2df7723f@neptune.home>
Date:	Wed, 3 Nov 2010 21:58:51 +0100
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Mike Waychison <mikew@...gle.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Greg KH <gregkh@...e.de>, simon.kagstrom@...insight.net,
	davem@...emloft.net, adurbin@...gle.com, akpm@...ux-foundation.org,
	chavey@...gle.com, linux-kernel@...r.kernel.org,
	linux-api@...r.kernel.org
Subject: Re: [PATCH v1 00/12] netoops support

On Wed, 03 November 2010 Joe Perches wrote:
> On Wed, 2010-11-03 at 11:50 -0700, Randy Dunlap wrote:
> > On Wed, 3 Nov 2010 11:16:34 -0700 Greg KH wrote:
> > > On Tue, Nov 02, 2010 at 08:37:42PM -0700, Mike Waychison wrote:
> > > > On Tue, Nov 2, 2010 at 7:34 PM, Greg KH wrote:
> > > As for the user/kernel interface, perhaps exporting the data in a text
> > > format that is "tagged" would be best?  Then the whole world can parse
> > > it easily.
> > I have been (occasionally) looking at critical kernel messages.
> > IMO we really need an easy way to find them.
> > They can begin with any of these strings (and others can be added
> > too easily):
> > BUG|panic|MCE|NMI|error:|Oops|Bad|Fatal|Unrecoverable|Unhandled|Weird
> > We need a simple (single?) tagging method to identify any/all of these,
> > /methinks.
> 
> Simply marking these messages KERN_CRIT or higher would seem to work.

That's an idea (probably better higher that can be enabled on a console with
a specific flag), though it also invites for filter levels on a per-console
base (e.g. let uart only show KERN_WARN..KERN_CRIT but having more verbosity
on termial or netconsole [per target]).

I've been playing with this last winter, need to dig out that code again and
clean it up for sharing.

Bruno
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ