linux-kernel - Re: [RFC][PATCH] add blockconsole

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]

Date:	Wed, 25 Apr 2012 09:25:14 -0400
From:	Jörn Engel <joern@...fs.org>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] add blockconsole

On Wed, 25 April 2012 09:42:39 -0400, Jeff Moyer wrote:
> 
> Neat idea, but I'm curious to know how it works when the system panics
> and you no longer can schedule the writeback thread.  What are the
> limitations you've seen in practice?

If the writeback thread doesn't get scheduled, you lose that
information.  Formerly I did the submit_bio directly, but lockdep
reminded me that I shouldn't do so from interrupt context.  Bummer.

Also, this is pretty young code so far.  We are starting to deploy it
in numbers just about now.  The obvious hope is that it will record a
non-zero class of problems that doesn't make it to syslog.  And the
obvious fear is that it will fail to record another non-zero class of
problems.  As to the extend of those two classes, we just don't have
good data yet.

But as they say, release early, release often, and hope some reviewer
finds a bug you can fix before having to debug it the hard way. ;)

Jörn
--
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/