From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix to tag FIEMAP_EXTENT_DELALLOC in fiemap() for delay allocated extent
Date: Fri, 7 Apr 2023 13:59:23 -0700 [thread overview]
Message-ID: <ZDCEK2OPkhTmRZrq@google.com> (raw)
In-Reply-To: <20230405144359.930253-1-chao@kernel.org>
This breaks generic/009?
On 04/05, Chao Yu wrote:
> xfstest generic/614 fails to run due below reason:
>
> generic/614 1s ... [not run] test requires delayed allocation buffered writes
>
> The root cause is f2fs tags wrong fiemap flag for delay allocated
> extent.
>
> Quoted from fiemap.h:
> FIEMAP_EXTENT_UNKNOWN 0x00000002 /* Data location unknown. */
> FIEMAP_EXTENT_DELALLOC 0x00000004 /* Location still pending.
> * Sets EXTENT_UNKNOWN. */
> FIEMAP_EXTENT_UNWRITTEN 0x00000800 /* Space allocated, but
> * no data (i.e. zero). */
>
> FIEMAP_EXTENT_UNWRITTEN means block address is preallocated, but w/o
> been written any data, which status f2fs is not supported now, for all
> NEW_ADDR block addresses, it means delay allocated blocks, so let's
> tag FIEMAP_EXTENT_DELALLOC instead.
>
> Testcase:
> xfs_io -f -c 'pwrite 0 64k' /mnt/f2fs/file;
> filefrag -v /mnt/f2fs/file
>
> Output:
> - Before
> Filesystem type is: f2f52010
> Fize of /mnt/f2fs/file is 65536 (16 blocks of 4096 bytes)
> ext: logical_offset: physical_offset: length: expected: flags:
> 0: 0.. 15: 0.. 15: 16: last,unwritten,merged,eof
> /mnt/f2fs/file: 1 extent found
>
> After:
> Filesystem type is: f2f52010
> File size of /mnt/f2fs/file is 65536 (16 blocks of 4096 bytes)
> ext: logical_offset: physical_offset: length: expected: flags:
> 0: 0.. 15: 0.. 0: 0: last,unknown_loc,delalloc,eof
> /mnt/f2fs/file: 1 extent found
>
> Fixes: 7f63eb77af7b ("f2fs: report unwritten area in f2fs_fiemap")
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/data.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 359de650772e..3afc9764743e 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -1995,7 +1995,10 @@ int f2fs_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
> }
>
> if (size) {
> - flags |= FIEMAP_EXTENT_MERGED;
> + if (flags & FIEMAP_EXTENT_DELALLOC)
> + phys = 0;
> + else
> + flags |= FIEMAP_EXTENT_MERGED;
> if (IS_ENCRYPTED(inode))
> flags |= FIEMAP_EXTENT_DATA_ENCRYPTED;
>
> @@ -2035,7 +2038,7 @@ int f2fs_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
> size += blks_to_bytes(inode, 1);
> }
> } else if (map.m_flags & F2FS_MAP_DELALLOC) {
> - flags = FIEMAP_EXTENT_UNWRITTEN;
> + flags = FIEMAP_EXTENT_DELALLOC;
> }
>
> start_blk += bytes_to_blks(inode, size);
> --
> 2.36.1
next prev parent reply other threads:[~2023-04-07 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 14:43 [PATCH] f2fs: fix to tag FIEMAP_EXTENT_DELALLOC in fiemap() for delay allocated extent Chao Yu
2023-04-07 20:59 ` Jaegeuk Kim [this message]
2023-04-08 2:57 ` Chao Yu
2023-04-10 17:57 ` Jaegeuk Kim
2023-04-11 8:14 ` Chao Yu
2023-04-11 8:36 ` [f2fs-dev] " Chao Yu
2023-04-11 17:08 ` Jaegeuk Kim
2023-04-13 9:49 ` Chao Yu
2023-04-19 15:30 ` Chao Yu
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=ZDCEK2OPkhTmRZrq@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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