Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH fstests 1/3] generic/294: don't run this test on NFS
Date: Fri, 01 Sep 2023 06:21:43 -0400	[thread overview]
Message-ID: <8db2e22a71ed9c658945bd3d7f0a4b6cad7db1d3.camel@kernel.org> (raw)
In-Reply-To: <20230901051439.j5jduasrkmh67g6g@zlang-mailbox>

On Fri, 2023-09-01 at 13:14 +0800, Zorro Lang wrote:
> On Thu, Aug 31, 2023 at 02:40:28PM -0400, Jeff Layton wrote:
> > When creating a new dentry (of any type), NFS will optimize away any
> > on-the-wire lookups prior to the create since that means an extra
> > round trip to the server. Because of that, it consistently fails this
> > test.
> > 
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> >  tests/generic/294 | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/tests/generic/294 b/tests/generic/294
> > index 406b1b3954b9..777b62aec9ad 100755
> > --- a/tests/generic/294
> > +++ b/tests/generic/294
> > @@ -15,6 +15,10 @@ _begin_fstest auto quick
> >  
> >  # real QA test starts here
> >  
> > +# NFS will optimize away the on-the-wire lookup before attempting to
> > +# create a new file (since that means an extra round trip).
> > +test $FSTYP = "nfs"  && _notrun "NFS optmizes away lookups on exclusive creates"
> > +
> >  # Modify as appropriate.
> >  _supported_fs generic
> 
> I don't know if nfs-list wants to skip these test cases on nfs. Anyway, if
> there's not an objection from nfs team, the _supported_fs helper can use
> a black list, likes:
> 
>   _supported_fs ^nfs
> 
> If a test case doesn't support nfs totally, you can use this and give it a
> proper comment.
> 

I think we do want to skip it. This one consistently fails on NFS and is
testing very specific and subtle behavior that is not required by POSIX.

I can respin these using the _supported_fs syntax if that's preferred
though. 
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-09-01 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 18:40 [PATCH fstests 0/3] generic: skip a few tests on NFS Jeff Layton
2023-08-31 18:40 ` [PATCH fstests 1/3] generic/294: don't run this test " Jeff Layton
2023-09-01  5:14   ` Zorro Lang
2023-09-01 10:21     ` Jeff Layton [this message]
2023-08-31 18:40 ` [PATCH fstests 2/3] generic/357: " Jeff Layton
2023-08-31 18:40 ` [PATCH fstests 3/3] generic/187: " Jeff Layton

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=8db2e22a71ed9c658945bd3d7f0a4b6cad7db1d3.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=zlang@redhat.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