From: Dustin Lundquist <dustin@null-ptr.net>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/buffer.c:1234!
Date: Tue, 09 Jul 2013 21:05:54 -0700 [thread overview]
Message-ID: <51DCDDA2.1000808@null-ptr.net> (raw)
In-Reply-To: <20130708141201.GG5988@quack.suse.cz>
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
prev parent reply other threads:[~2013-07-10 4:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:41 kernel BUG at fs/buffer.c:1234! Dustin Lundquist
2013-06-19 18:55 ` Theodore Ts'o
2013-06-20 16:20 ` Dustin Lundquist
2013-06-20 16:34 ` Theodore Ts'o
2013-07-04 20:31 ` Dustin Lundquist
2013-07-08 14:12 ` Jan Kara
2013-07-10 4:05 ` Dustin Lundquist [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DCDDA2.1000808@null-ptr.net \
--to=dustin@null-ptr.net \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.