linux-ext4 - Re: kernel BUG at fs/buffer.c:1234!

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:	Thu, 20 Jun 2013 12:34:06 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Dustin Lundquist <dustin@...l-ptr.net>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:1234!

On Thu, Jun 20, 2013 at 09:20:01AM -0700, Dustin Lundquist wrote:
> 
> Since the system is still half way responsive after this occurs, is
> there any other information I can gather after if occurs to aid in
> diagnosing this?

Hmm.... the only thing I can think of is to sprinkle in some

        WARN_ON(irqs_disabled());

calls in various top-half routines in ext4 code, especially in
ext4_lookup() and ext4_find_entry(), and perhaps in the vfs layer to
see if we can figure out where the interrupts are getting disabled.
The fact that blkcipher_walk_done() was showing up in the stack trace
is certainly suspicious.

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html