From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Eryu Guan <guaneryu@gmail.com>, fstests <fstests@vger.kernel.org>,
Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [ANNOUNCE] fstests: master branch updated to 1e24e5173efa
Date: Mon, 13 Nov 2017 12:12:06 +0800 [thread overview]
Message-ID: <20171113041206.GB17339@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAOQ4uxgveiWmid80JCQaozT4eYQiMyJjYTQkmVYFnk0cB9iuyg@mail.gmail.com>
On Sun, Nov 12, 2017 at 11:50:55AM +0200, Amir Goldstein wrote:
> On Sun, Nov 12, 2017 at 11:09 AM, Eryu Guan <guaneryu@gmail.com> wrote:
> > Hi all,
> >
> > The master branch of the xfstests repository at:
> >
> > git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> >
> > have just been updated. This update contains a new open_by_handle test from
> > Amir and the remaining bits from Darrick to prepare for v4.15 merge window.
> > Other commits are random bug fixes.
> >
> > New failures I've noticed in this update:
> > - generic/467 fails on NFSv3 and NFSv4.0 (passes on NFSv4.[12] though)
>
> Can you please share the failure errors on NFSv3.
Sure.
NFSv3:
test_file_handles TEST_DIR/467-dir -rp
+open_by_handle(/mnt/testarea/test) returned 116 incorrectly on a linked dir!
...
test_file_handles TEST_DIR/467-dir.renamed -rp
+open_by_handle(/mnt/testarea/test) returned 116 incorrectly on a linked dir!
test_file_handles TEST_DIR/467-dir.new -rp
+open_by_handle(/mnt/testarea/test) returned 116 incorrectly on a linked dir!
NFSv4.0:
test_file_handles TEST_DIR/467-dir -rp
+open_by_handle(/mnt/testarea/test/467-dir/file000000) returned 116 incorrectly on a linked file!
...
test_file_handles TEST_DIR/467-dir -dkr
test_file_handles TEST_DIR/467-dir -lr
+open_by_handle(/mnt/testarea/test/467-dir/file000000) returned 116 incorrectly on a linked file!
...
test_file_handles TEST_DIR/467-dir -ur
+open_by_handle(/mnt/testarea/test/467-dir/file000000) returned 116 incorrectly on a linked file!
...
test_file_handles TEST_DIR/467-dir -mr
+open_by_handle(/mnt/testarea/test/467-dir/file000000) returned 116 incorrectly on a linked file!
...
test_file_handles TEST_DIR/467-dir.renamed -rp
+open_by_handle(/mnt/testarea/test/467-dir.renamed/file000000) returned 116 incorrectly on a linked file!
...
test_file_handles TEST_DIR/467-dir.new -rp
+open_by_handle(/mnt/testarea/test/467-dir.new/file000000) returned 116 incorrectly on a linked file!
Thanks,
Eryu
>
> Test is also failing on tmpfs, which was acknowledged by nfsd maintainers
> as a tmpfs bug or at least very undesired behavior for exported tmpfs.
>
> Thanks,
> Amir.
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-11-13 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 9:09 [ANNOUNCE] fstests: master branch updated to 1e24e5173efa Eryu Guan
2017-11-12 9:50 ` Amir Goldstein
2017-11-13 4:12 ` Eryu Guan [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=20171113041206.GB17339@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=jlayton@poochiereds.net \
/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