FS/XFS testing framework
 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 v2 1/3] generic/294: don't run this test on NFS
Date: Fri, 01 Sep 2023 15:37:01 -0400	[thread overview]
Message-ID: <a00bbc4466a517f81cd02bc1f72dce92a8b14ca2.camel@kernel.org> (raw)
In-Reply-To: <20230901191944.lx3b643f2bwmcn3t@zlang-mailbox>

On Sat, 2023-09-02 at 03:19 +0800, Zorro Lang wrote:
> On Fri, Sep 01, 2023 at 01:39:55PM -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 | 6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> > 
> > diff --git a/tests/generic/294 b/tests/generic/294
> > index 406b1b3954b9..46c7001234a5 100755
> > --- a/tests/generic/294
> > +++ b/tests/generic/294
> > @@ -15,8 +15,10 @@ _begin_fstest auto quick
> >  
> >  # real QA test starts here
> >  
> > -# Modify as appropriate.
> > -_supported_fs generic
> > +# NFS will optimize away the on-the-wire lookup before attempting to
> > +# create a new file (since that means an extra round trip).
> > +_supported_fs ^nfs generic
> 
> If we use black list, don't need to use "generic" to specify white list. E.g.
> 
>   $ grep -rsn _supported_fs tests/generic/|grep \\^
>   tests/generic/699:25:_supported_fs ^overlay
>   tests/generic/631:41:_supported_fs ^overlay
>   tests/generic/679:27:_supported_fs ^xfs
>   tests/generic/500:45:_supported_fs ^btrfs
> 
> Anyway, others look good to me, if no objection from nfs list, I can help
> to merge this patchset without the "generic" :)
> 

Ok, I was looking at the _support_fs implementation and it looked like
you needed a "generic" entry on the end or it wouldn't pass for other
fs, but if you're sure, that sounds good to me.

Thanks!
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-09-01 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 17:39 [PATCH fstests v2 0/3] generic: skip a few tests on NFS Jeff Layton
2023-09-01 17:39 ` [PATCH fstests v2 1/3] generic/294: don't run this test " Jeff Layton
2023-09-01 19:19   ` Zorro Lang
2023-09-01 19:37     ` Jeff Layton [this message]
2023-09-01 17:39 ` [PATCH fstests v2 2/3] generic/357: " Jeff Layton
2023-09-01 17:39 ` [PATCH fstests v2 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=a00bbc4466a517f81cd02bc1f72dce92a8b14ca2.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