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] [day] [month] [year] [list]

Message-ID: <51DCDDA2.1000808@null-ptr.net>
Date:	Tue, 09 Jul 2013 21:05:54 -0700
From:	Dustin Lundquist <dustin@...l-ptr.net>
To:	Jan Kara <jack@...e.cz>
CC:	Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:1234!

On 07/08/2013 07:12 AM, Jan Kara wrote:
>    Hum, so it's interesting that ecryptfs_lookup() WARN_ON() didn't trigger
> but ext4 one did. Strangely enough I don't see a place in the call chain
> where irqs could get disabled. Can you maybe trace using irq tracing at
> which point exactly do we disable interrupts?

I'm not familiar with irq tracing, but I traced it as far as a function 
pointer in a macro at fs/ecryptfs/keystore.c:840 then tried blacklisting 
the aesni_intel module and I haven't been able to reproduce it since.

At this point I would be interested if anyone else can reproduce it on 
another Intel Ivy Bridge system with aesni and Linux 3.10:
1. Setup an ecryptfs mount over an ext4 file system
2. Cause a program running inside ecryptfs mount to core dump

Thanks,

Dustin Lundquist
--
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