From: Chris Mason <chris.mason@oracle.com>
To: David Sterba <dave@jikos.cz>
Cc: Tsutomu Itoh <t-itoh@jp.fujitsu.com>,
Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [BUG, integration-test] fs/btrfs/inode.c:835
Date: Fri, 30 Sep 2011 16:10:40 -0400 [thread overview]
Message-ID: <1317413433-sup-5145@shiny> (raw)
In-Reply-To: <20110930105200.GI22205@twin.jikos.cz>
Excerpts from David Sterba's message of 2011-09-30 06:52:00 -0400:
> On Fri, Sep 30, 2011 at 09:06:50AM +0900, Tsutomu Itoh wrote:
> > The problem might be solved by the following patch.
> >
> > http://marc.info/?l=linux-btrfs&m=131556023601191&w=2
>
> Thanks! It's the same BUG_ON line. I rerun the test yesterday for the
> scond time and it triggered again. Now I'm testing integration with
> Miao's fix and so far no crash after a few rounds.
Nice, thanks guys.
-chris
prev parent reply other threads:[~2011-09-30 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 22:05 [BUG, integration-test] fs/btrfs/inode.c:835 David Sterba
2011-09-30 0:06 ` Tsutomu Itoh
2011-09-30 10:52 ` David Sterba
2011-09-30 20:10 ` Chris Mason [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=1317413433-sup-5145@shiny \
--to=chris.mason@oracle.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.com \
/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).