All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chengguang Xu <cgxu519@mykernel.net>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "guaneryu" <guaneryu@gmail.com>, "fstests" <fstests@vger.kernel.org>
Subject: Re: [PATCH] generic/473: fix expectation properly in out file
Date: Thu, 25 Feb 2021 10:16:39 +0800	[thread overview]
Message-ID: <177d6f95225.10d58c6c517633.3841129799694058715@mykernel.net> (raw)
In-Reply-To: <20210224165057.GB7269@magnolia>

 ---- 在 星期四, 2021-02-25 00:50:57 Darrick J. Wong <djwong@kernel.org> 撰写 ----
 > On Tue, Feb 23, 2021 at 09:40:42PM +0800, Chengguang Xu wrote:
 > > It seems the expected result of testcase of "Hole + Data"
 > > in generic/473 is not correct, so just fix it properly.
 > > 
 > > Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
 > > ---
 > >  tests/generic/473.out | 2 +-
 > >  1 file changed, 1 insertion(+), 1 deletion(-)
 > > 
 > > diff --git a/tests/generic/473.out b/tests/generic/473.out
 > > index 75816388..f1ee5805 100644
 > > --- a/tests/generic/473.out
 > > +++ b/tests/generic/473.out
 > > @@ -6,7 +6,7 @@ Data + Hole
 > >  1: [256..287]: hole
 > >  Hole + Data
 > >  0: [0..127]: hole
 > > -1: [128..255]: data
 > > +1: [128..135]: data
 > 
 > This again.  While the FIEMAP documentation allows the call to return
 > file mapping data outside the requested range, it doesn't require it,
 > and neither XFS nor ext4 have ever done so.

I did more tests on ext4 and found in old 4.14 kernel ext4 returned whole extent range.


 > 
 > This test *enforces* that the FIEMAP implementation provide data outside
 > the requested range, which means it has never passed on xfs/ext4.  This
 > is no surprise, since it's enforcing one behavior where the spec allows
 > for two behaviors.  The only fs I know of where it passes is btrfs.

plus f2fs.

Thanks,
Chengguang

 > 
 > Delete this test or move it to tests/btrfs/, because it should not have
 > been added in the first place.
 > 
 > --D
 > 
 > >  Hole + Data + Hole
 > >  0: [0..127]: hole
 > >  1: [128..255]: data
 > > -- 
 > > 2.27.0
 > > 
 > > 
 > 

      reply	other threads:[~2021-02-25  2:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 13:40 [PATCH] generic/473: fix expectation properly in out file Chengguang Xu
2021-02-24  7:52 ` Su Yue
2021-02-24  8:10   ` Su Yue
2021-02-24  8:55     ` Chengguang Xu
2021-02-24  8:51   ` Chengguang Xu
2021-02-24  9:16     ` Chengguang Xu
2021-02-24  9:22     ` Su Yue
2021-02-24  9:37       ` Chengguang Xu
2021-02-24 13:31         ` Eryu Guan
2021-02-24 13:48           ` Chengguang Xu
2021-02-24 16:50 ` Darrick J. Wong
2021-02-25  2:16   ` Chengguang Xu [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=177d6f95225.10d58c6c517633.3841129799694058715@mykernel.net \
    --to=cgxu519@mykernel.net \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.