From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>, BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] Btrfs: allocate extent state and check the result properly
Date: Wed, 20 Apr 2011 14:49:17 +0800 [thread overview]
Message-ID: <4DAE81ED.9060505@cn.fujitsu.com> (raw)
In-Reply-To: <1303213987-sup-4275@think>
On 04/19/2011 07:55 PM, Chris Mason wrote:
> Sorry, could you please change this to check the results of the atomic
> allocatoin in set/clear_extent_bit? I'd rather not add a new BUG_ON
> deeper into the code.
>
OK, i have posted the v2 patch to fix it, thanks for your review!
prev parent reply other threads:[~2011-04-20 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 8:14 [PATCH 1/2] Btrfs: allocate extent state and check the result properly Xiao Guangrong
2011-04-12 8:15 ` [PATCH 2/2] Btrfs: fix unsafe usage of merge_state Xiao Guangrong
2011-04-19 1:49 ` [PATCH 1/2] Btrfs: allocate extent state and check the result properly Xiao Guangrong
2011-04-19 11:55 ` Chris Mason
2011-04-20 6:49 ` Xiao Guangrong [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=4DAE81ED.9060505@cn.fujitsu.com \
--to=xiaoguangrong@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).