All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: XiaoLi Feng <xifeng@redhat.com>
Cc: fstests@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH] common/rc: skip atime related tests on CIFS
Date: Sun, 27 May 2018 20:50:58 +0800	[thread overview]
Message-ID: <20180527125058.GC6581@desktop> (raw)
In-Reply-To: <1526959436-7170-1-git-send-email-xifeng@redhat.com>

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?

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

  reply	other threads:[~2018-05-27 12:51 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 [this message]
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

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=20180527125058.GC6581@desktop \
    --to=guaneryu@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --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.