From: Chris Mason <chris.mason@oracle.com>
To: "jeff.liu" <jeff.liu@oracle.com>
Cc: Tao Ma <tao.ma@oracle.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] btrfs: Don't return extent in fiemap if we meet with a hole.
Date: Mon, 21 Jun 2010 20:57:23 -0400 [thread overview]
Message-ID: <20100622005723.GJ23009@think> (raw)
In-Reply-To: <4C1F167D.3040908@oracle.com>
On Mon, Jun 21, 2010 at 03:36:29PM +0800, jeff.liu wrote:
> Hi Chris,
>
> Could you please also consider another tiny patch below combine with Tao's?
> It fix extent flags to FIEMAP_FLAG_UNWRITTEN if it was fallocate(2) and its "em->block_start ==
> EXTENT_MAP_LAST_BYTE".
Thanks, will do.
-chris
next prev parent reply other threads:[~2010-06-22 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 6:37 [PATCH RESEND] btrfs: Don't return extent in fiemap if we meet with a hole Tao Ma
2010-06-21 7:36 ` jeff.liu
2010-06-22 0:57 ` Chris Mason [this message]
2010-06-22 0:56 ` Chris Mason
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=20100622005723.GJ23009@think \
--to=chris.mason@oracle.com \
--cc=jeff.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tao.ma@oracle.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).