From: Chris Mason <chris.mason@fusionio.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Mitch Harder <mitch.harder@sabayonlinux.org>
Subject: Re: [PATCH] Btrfs: fix wrong outstanding_extents when doing DIO write
Date: Thu, 21 Feb 2013 08:26:27 -0500 [thread overview]
Message-ID: <20130221132627.GC12051@shiny.masoncoding.com> (raw)
In-Reply-To: <5125ED66.4060405@cn.fujitsu.com>
On Thu, Feb 21, 2013 at 02:48:22AM -0700, Miao Xie wrote:
> When running the 083th case of xfstests on the filesystem with
> "compress-force=lzo", the following WARNINGs were triggered.
> WARNING: at fs/btrfs/inode.c:7908
> WARNING: at fs/btrfs/inode.c:7909
> WARNING: at fs/btrfs/inode.c:7911
> WARNING: at fs/btrfs/extent-tree.c:4510
> WARNING: at fs/btrfs/extent-tree.c:4511
>
> This problem was introduced by the patch "Btrfs: fix deadlock due
> to unsubmitted". In this patch, there are two bugs which caused
> the above problem.
I saw this as well on test 132 last night. My plan was to track it down
this morning, so discovering it already fixed while I slept was
wonderful.
Thanks Miao. Josef I've got this one and Miao's defrag unmount patch
queued up.
-chris
next prev parent reply other threads:[~2013-02-21 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 5:35 Kernel WARNINGs on btrfs-next Mitch Harder
2013-02-21 9:48 ` [PATCH] Btrfs: fix wrong outstanding_extents when doing DIO write Miao Xie
2013-02-21 13:26 ` Chris Mason [this message]
2013-02-21 14:19 ` Mitch Harder
2013-02-21 9:53 ` Kernel WARNINGs on btrfs-next Miao Xie
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=20130221132627.GC12051@shiny.masoncoding.com \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=mitch.harder@sabayonlinux.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