All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: Steve French <smfrench@gmail.com>, Ronnie Sahlberg <lsahlber@redhat.com>
Cc: Xiaoli Feng <xifeng@redhat.com>,
	fstests@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH] common/rc: skip atime related tests on CIFS
Date: Thu, 7 Jun 2018 13:39:57 +0800	[thread overview]
Message-ID: <20180607053957.GC2861@desktop> (raw)
In-Reply-To: <CAH2r5msb92E2e7gePY01qBPP4fJ0CKcEsnKLdnL1Ms8cUaQ4sA@mail.gmail.com>

On Mon, May 28, 2018 at 11:11:02PM -0500, Steve French wrote:
> Agreed but I do want to follow up with Ronnie on loosely related question of
> how cifs and NFS and similar filesystems parse no op mount options like noatime

I take this as an ACK then, please let me know if you didn't really mean
that :)

Thank you both for review!

Eryu

> 
> On Mon, May 28, 2018, 22:55 Ronnie Sahlberg <lsahlber@redhat.com> wrote:
> 
>     Hi Xiaoli,
> 
>     I think it is fine to skip the atime tests for CIFS.
> 
>     The behaviour of atime/noatime for cifs is basically noatime always.
>     When we read from the server the server will update the atime independently
>     of
>     cisf.ko but then any further reads that we do from cache will never push
>     any updates
>     to the server.
> 
>     Ronnie
> 
>     ----- Original Message -----
>     > From: "Xiaoli Feng" <xifeng@redhat.com>
>     > To: "Eryu Guan" <guaneryu@gmail.com>, "Leif Sahlberg" <
>     lsahlber@redhat.com>
>     > Cc: fstests@vger.kernel.org, linux-cifs@vger.kernel.org
>     > Sent: Monday, 28 May, 2018 4:40:56 PM
>     > Subject: Re: [PATCH] common/rc: skip atime related tests on CIFS
>     >
>     > Add Ronnie to to list.
>     >
>     > Hello Ronnie,
>     >   what's the expected behavior from CIFS on atime/noatime? We want to
>     skip
>     >   the
>     > atime related tests on cifs for xfstests just like nfs. But not sure if
>     it's
>     > correct. What do you think about it?
>     >
>     > Thanks.
>     >
>     > ----- Original Message -----
>     > > From: "Eryu Guan" <guaneryu@gmail.com>
>     > > To: "XiaoLi Feng" <xifeng@redhat.com>
>     > > Cc: fstests@vger.kernel.org, linux-cifs@vger.kernel.org
>     > > Sent: Sunday, May 27, 2018 8:50:58 PM
>     > > Subject: Re: [PATCH] common/rc: skip atime related tests on CIFS
>     > >
>     > > On Tue, May 22, 2018 at 11:23:56AM +0800, Xiaoli Feng wrote:
>     > > > From: xiaoli feng <xifeng@redhat.com>
>     > > >
>     > > > The atime related mount options have no effect on cifs mounts
>     > > > now or in the future. So skip these tests on CIFS.
>     > > >
>     > > > Signed-off-by: xiaoli feng <xifeng@redhat.com>
>     > >
>     > > Looks fine to me. But I really need an ACK from cifs folks.
>     > >
>     > > > ---
>     > > >  common/rc | 2 ++
>     > > >  1 file changed, 2 insertions(+)
>     > > >
>     > > > diff --git a/common/rc b/common/rc
>     > > > index ffe5323..d3af55f 100644
>     > > > --- a/common/rc
>     > > > +++ b/common/rc
>     > > > @@ -3244,6 +3244,8 @@ _require_atime()
>     > > >   _exclude_scratch_mount_option "noatime"
>     > > >   if [ "$FSTYP" == "nfs" ]; then
>     > > >           _notrun "atime related mount options have no effect on NFS"
>     > > > + elif [ "$FSTYP" == "cifs" ]; then
>     > > > +         _notrun "atime related mount options have no effect on
>     CIFS"
>     > >
>     > > Or just change the check to a case-switch on $FSTYP?
>     >
>     > Ok, I will change it on the next commit.
>     > Thanks!
>     >
>     > >
>     > > Thanks,
>     > > Eryu
>     > >
>     > > >   fi
>     > > >  }
>     > > > 
>     > > > --
>     > > > 1.8.3.1
>     > > >
>     > > > --
>     > > > 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
>     > > --
>     > > 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
>     > >
>     > --
>     > 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
>     >
>     --
>     To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
>     the body of a message to majordomo@vger.kernel.org
>     More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      parent reply	other threads:[~2018-06-07  5:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  3:23 [PATCH] common/rc: skip atime related tests on CIFS XiaoLi Feng
2018-05-27 12:50 ` Eryu Guan
2018-05-28  6:40   ` Xiaoli Feng
2018-05-28 23:26     ` Ronnie Sahlberg
2018-05-31  3:18       ` Xiaoli Feng
     [not found]       ` <CAH2r5msb92E2e7gePY01qBPP4fJ0CKcEsnKLdnL1Ms8cUaQ4sA@mail.gmail.com>
2018-06-07  5:39         ` 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=20180607053957.GC2861@desktop \
    --to=guaneryu@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=smfrench@gmail.com \
    --cc=xifeng@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 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.