From: Eryu Guan <eguan@redhat.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] generic/294: fix output for nfs
Date: Wed, 21 Jun 2017 16:37:04 +0800 [thread overview]
Message-ID: <20170621083704.GD17669@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1497951333-5925-1-git-send-email-yangx.jy@cn.fujitsu.com>
On Tue, Jun 20, 2017 at 05:35:33PM +0800, Xiao Yang wrote:
> In nfs environment, both mkdir and mknod are optimized and
> return EROFS instead of EEXIST when asking to create an
> already-existing entity on an RO filesystem. We add specific
> output of nfs to fix it.
This test just exercises this code path, it expects EEXIST instead of
EROFS. Not sure if it's NFS that needs to be fixed, not the test case.
cc linux-nfs list to request for more comments.
Thanks,
Eryu
>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
> ---
> tests/generic/294 | 3 +++
> tests/generic/294.cfg | 1 +
> tests/generic/294.out | 5 -----
> tests/generic/294.out.default | 5 +++++
> tests/generic/294.out.nfs | 5 +++++
> 5 files changed, 14 insertions(+), 5 deletions(-)
> create mode 100644 tests/generic/294.cfg
> delete mode 100644 tests/generic/294.out
> create mode 100644 tests/generic/294.out.default
> create mode 100644 tests/generic/294.out.nfs
>
> diff --git a/tests/generic/294 b/tests/generic/294
> index fb5d9aa..bc20dad 100755
> --- a/tests/generic/294
> +++ b/tests/generic/294
> @@ -22,6 +22,7 @@
> #-----------------------------------------------------------------------
> #
>
> +seqfull=$0
> seq=`basename $0`
> seqres=$RESULT_DIR/$seq
> echo "QA output created by $seq"
> @@ -48,6 +49,8 @@ _supported_fs generic
> _supported_os Linux
> _require_scratch
>
> +_link_out_file_named $seqfull.out $FSTYP
> +
> rm -f $seqres.full
> _scratch_mkfs > $seqres.full 2>&1 || _fail "Could not mkfs scratch device"
>
> diff --git a/tests/generic/294.cfg b/tests/generic/294.cfg
> new file mode 100644
> index 0000000..d02b0ce
> --- /dev/null
> +++ b/tests/generic/294.cfg
> @@ -0,0 +1 @@
> +nfs: nfs
> diff --git a/tests/generic/294.out b/tests/generic/294.out
> deleted file mode 100644
> index 7802472..0000000
> --- a/tests/generic/294.out
> +++ /dev/null
> @@ -1,5 +0,0 @@
> -QA output created by 294
> -mknod: SCRATCH_MNT/294.test/testnode: File exists
> -mkdir: cannot create directory 'SCRATCH_MNT/294.test/testdir': File exists
> -touch: cannot touch 'SCRATCH_MNT/294.test/testtarget': Read-only file system
> -ln: creating symbolic link 'SCRATCH_MNT/294.test/testlink': File exists
> diff --git a/tests/generic/294.out.default b/tests/generic/294.out.default
> new file mode 100644
> index 0000000..7802472
> --- /dev/null
> +++ b/tests/generic/294.out.default
> @@ -0,0 +1,5 @@
> +QA output created by 294
> +mknod: SCRATCH_MNT/294.test/testnode: File exists
> +mkdir: cannot create directory 'SCRATCH_MNT/294.test/testdir': File exists
> +touch: cannot touch 'SCRATCH_MNT/294.test/testtarget': Read-only file system
> +ln: creating symbolic link 'SCRATCH_MNT/294.test/testlink': File exists
> diff --git a/tests/generic/294.out.nfs b/tests/generic/294.out.nfs
> new file mode 100644
> index 0000000..71ebeec
> --- /dev/null
> +++ b/tests/generic/294.out.nfs
> @@ -0,0 +1,5 @@
> +QA output created by 294
> +mknod: 'SCRATCH_MNT/294.test/testnode': Read-only file system
> +mkdir: cannot create directory 'SCRATCH_MNT/294.test/testdir': Read-only file system
> +touch: cannot touch 'SCRATCH_MNT/294.test/testtarget': Read-only file system
> +ln: creating symbolic link 'SCRATCH_MNT/294.test/testlink': File exists
> --
> 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
prev parent reply other threads:[~2017-06-21 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 9:35 [PATCH] generic/294: fix output for nfs Xiao Yang
2017-06-21 8:37 ` 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=20170621083704.GD17669@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=yangx.jy@cn.fujitsu.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