From: Christoph Hellwig <hch@infradead.org>
To: Pavel Shilovsky <pshilovsky@samba.org>
Cc: fstests@vger.kernel.org, linux-cifs@vger.kernel.org,
samba-technical@samba.org, David Disseldorp <ddiss@suse.de>,
Steve French <smfrench@gmail.com>
Subject: Re: [PATCH v2 3/3] cifs: skip tests that need POSIX support for nounix mounts
Date: Wed, 27 Aug 2014 08:58:32 -0700 [thread overview]
Message-ID: <20140827155832.GA3103@infradead.org> (raw)
In-Reply-To: <1409084918-17764-4-git-send-email-pshilovsky@samba.org>
On Wed, Aug 27, 2014 at 12:28:38AM +0400, Pavel Shilovsky wrote:
> CIFS/SMB protocol without POSIX extensions doesn't support operations
> with symbolic links and advisory byte-range locks from the same process.
> Add a check for nounix mounts and use it in generic tests that
> require such operations.
+_require_test_posix_ext seems very cifs specific. Can you take
a look at the tests and see what posix feature they require and
add features based on that? Let's have a quick discussion here on the
requirements of the tests before even writing the code.
> diff --git a/tests/generic/005 b/tests/generic/005
> index d78e43f..0c2b51f 100755
> --- a/tests/generic/005
> +++ b/tests/generic/005
> @@ -67,6 +67,7 @@ _touch()
> # real QA test starts here
> _supported_fs generic
> _require_test
> +_require_test_posix_ext
>
> # IRIX UDF does not support symlinks
> if [ $FSTYP == 'udf' ]; then
this suggest 005 needs symlinks and plain cifs doesn't support them.
We should also fold this test for IRIX udf into the _requires_symlink
tests.
> diff --git a/tests/generic/023 b/tests/generic/023
> index 114485c..91b8a37 100755
> --- a/tests/generic/023
> +++ b/tests/generic/023
> @@ -45,6 +45,7 @@ _supported_os Linux
>
> _require_test
> _requires_renameat2
> +_require_test_posix_ext
023-025 just require a working renameat2, and nothing in Posix. What's
the problem for cifs here?
> diff --git a/tests/generic/131 b/tests/generic/131
> index b4e3ff0..9736963 100755
> --- a/tests/generic/131
> +++ b/tests/generic/131
> @@ -45,6 +45,7 @@ _cleanup()
> _supported_fs generic
> _supported_os Linux
> _require_test
> +_require_test_posix_ext
>
> TESTFILE=$TEST_DIR/lock_file
131 tests fcntl style file locking, so we should test for that.
next prev parent reply other threads:[~2014-08-27 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 20:28 [PATCH v2 0/3] CIFS support for XFS test suite Pavel Shilovsky
2014-08-26 20:28 ` [PATCH v2 1/3] generic/013: encapsulate remount during cleanup Pavel Shilovsky
2014-08-28 17:08 ` Christoph Hellwig
2014-08-28 18:50 ` Pavel Shilovsky
2014-08-26 20:28 ` [PATCH v2 2/3] common: add cifs support Pavel Shilovsky
2014-08-28 17:18 ` Christoph Hellwig
2014-08-28 19:08 ` Pavel Shilovsky
2014-08-26 20:28 ` [PATCH v2 3/3] cifs: skip tests that need POSIX support for nounix mounts Pavel Shilovsky
2014-08-27 15:58 ` Christoph Hellwig [this message]
2014-08-27 16:17 ` Steve French
2014-08-27 19:49 ` Pavel Shilovsky
2014-08-27 22:50 ` Christoph Hellwig
2014-08-28 7:25 ` Pavel Shilovsky
2014-08-27 6:59 ` [PATCH v2 0/3] CIFS support for XFS test suite Pavel Shilovsky
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=20140827155832.GA3103@infradead.org \
--to=hch@infradead.org \
--cc=ddiss@suse.de \
--cc=fstests@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=pshilovsky@samba.org \
--cc=samba-technical@samba.org \
--cc=smfrench@gmail.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