From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: Re: [PATCH] ext4: return FIEMAP_EXTENT_UNKNOWN if an extent is delayed allocations
Date: Fri, 7 Jun 2013 19:54:22 +0800 [thread overview]
Message-ID: <20130607115422.GA12217@gmail.com> (raw)
In-Reply-To: <51B08F45.1050605@oracle.com>
On Thu, Jun 06, 2013 at 09:31:49PM +0800, Jeff Liu wrote:
> From: Jie Liu <jeff.liu@oracle.com>
>
> Return the FIEMAP_EXTENT_UNKNOWN flag as well except the
> FIEMAP_EXTENT_DELALLOC because the data location of an
> delayed allocation extent is unknown.
>
> Signed-off-by: Jie Liu <jeff.liu@oracle.com>
Reviewed-by: Zheng Liu <wenqing.lz@taobao.com>
- Zheng
> ---
> fs/ext4/extents.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index bc0f191..47e17b1 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -2125,7 +2125,8 @@ static int ext4_fill_fiemap_extents(struct inode *inode,
> next_del = ext4_find_delayed_extent(inode, &es);
> if (!exists && next_del) {
> exists = 1;
> - flags |= FIEMAP_EXTENT_DELALLOC;
> + flags |= (FIEMAP_EXTENT_DELALLOC |
> + FIEMAP_EXTENT_UNKNOWN);
> }
> up_read(&EXT4_I(inode)->i_data_sem);
>
> --
> 1.7.9.5
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-07 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 13:31 [PATCH] ext4: return FIEMAP_EXTENT_UNKNOWN if an extent is delayed allocations Jeff Liu
2013-06-07 11:54 ` Zheng Liu [this message]
2013-06-18 15:08 ` Theodore Ts'o
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=20130607115422.GA12217@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=jeff.liu@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).