From: Theodore Ts'o <tytso@mit.edu>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Linux Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [ext4] BUG: sleeping function called from invalid context at fs/ext4/ext4_jbd2.c:252
Date: Fri, 18 Apr 2014 11:24:56 -0400 [thread overview]
Message-ID: <20140418152456.GA31301@thunk.org> (raw)
In-Reply-To: <20140417033346.GA8702@localhost>
On Thu, Apr 17, 2014 at 11:33:46AM +0800, Fengguang Wu wrote:
>
> FYI, we noticed that simple dd write can trigger the below BUG in
> commit 208b9cc3a32f29b8a9bba682b5bfbb962bc9892d ("ext4: add a new
> spinlock i_raw_lock to protect the ext4's raw inode")
Yes, that was a buggy version of the patch that I thought was fairly
quickly replaced with a new version; something must have gone wrong
with how I pushed out my git branches. Anyway I'm pretty sure it's
not there on ext4.git any more. Let me know if you're still seeing
it, and from which branch.
Cheers,
- Ted
parent reply other threads:[~2014-04-18 15:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140417033346.GA8702@localhost>]
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=20140418152456.GA31301@thunk.org \
--to=tytso@mit.edu \
--cc=fengguang.wu@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).