linux-kernel - Re: [PATCH] kmsg_dump: Don't run on non-error paths by default

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: <20120208163720.GB3322@srcf.ucam.org>
Date:	Wed, 8 Feb 2012 16:37:20 +0000
From:	Matthew Garrett <mjg@...hat.com>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	linux-kernel@...r.kernel.org, seiji.aguchi@....com,
	dzickus@...hat.com
Subject: Re: [PATCH] kmsg_dump: Don't run on non-error paths by default

On Wed, Feb 08, 2012 at 11:30:07AM -0500, Vivek Goyal wrote:

> > +	if (reason > KMSG_DUMP_PANIC && !always_kmsg_dump)
> > +		return;
> 
> Did you mean reason > KMSG_DUMP_OOPS to enable oops logging by default?

Bah. Yes, I think my test system was set to panic on oops so I didn't 
catch that.

> Given the fact that not everybody likes kmsg_dump() and it is not known
> how stable it with various backends, will it make sense to keep it disabled
> by default and provide a knob to enable it (instead of always_kmsg_dump).

I think logging panics and oopses by default is a useful feature. It may 
be desirable to have a mechanism to disable it if some other way of 
handling that (serial console, kdump) is available.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/