From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: Xiong Zhou <xzhou@redhat.com>, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v3 1/3] fcntl16: Skip fcntl16 tests on NFS
Date: Thu, 21 Aug 2014 18:14:16 +0400 [thread overview]
Message-ID: <53F5FEB8.7080203@oracle.com> (raw)
In-Reply-To: <389062153.22364213.1408594355921.JavaMail.zimbra@redhat.com>
Hi!
On 08/21/2014 08:12 AM, Xiong Zhou wrote:
>
> According to nfs(5), NLM supports advisory file locks only. So skip
> fcntl16 test if NFS.
>
I've just took a fresh look at fcntl16.c and found that block1 of this
test case may be executed on NFS. And, IMHO, this block1 test case is
not 100% implemented by other fcntl*.c tests.
So I think that it will be more correct to have only block2, block3 skipped.
Sorry. I had to figure it out at the first time. :(
Thank you.
PS: And you pointed me one interesting issue.
The patch:
commit 5387ba03ce8eaddc7ec330ed03e579eed92596cc
Author: subrata_modak <subrata_modak>
Date: Mon May 5 08:49:34 2008 +0000
These test cases fail on the NFS environment due to NFS relates
issue(s). Hence abondon these tests when NFS is detected. By, Sridhar
Vinay <vinaysridhar@in.ibm.com>.
disabled entire tests and not particular test cases. And I think it's
not quite correct, because some of the test cases may be executed on NFS.
For example, fcntl14.c has 4 test blocks, and only one of them doesn't
work with NFS - block2 (mandatory locking).
Reviewing/fixing other fcntl*.c test cases looks like a useful activity.
But for a later time :)
> Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> ---
> testcases/kernel/syscalls/fcntl/fcntl16.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/testcases/kernel/syscalls/fcntl/fcntl16.c b/testcases/kernel/syscalls/fcntl/fcntl16.c
> index 44b6a80..7dba6ea 100644
> --- a/testcases/kernel/syscalls/fcntl/fcntl16.c
> +++ b/testcases/kernel/syscalls/fcntl/fcntl16.c
> @@ -51,6 +51,8 @@
> #include <sys/types.h>
> #include <sys/wait.h>
>
> +#include "tst_fs_type.h"
> +
> #define SKIPVAL 0x0f00
> //#define SKIP SKIPVAL, 0, 0L, 0L, IGNORED
> #define SKIP 0,0,0L,0L,0
> @@ -412,6 +414,12 @@ void setup(void)
>
> tst_tmpdir();
>
> + /* On NFS or not */
> + if (tst_fs_type(cleanup, ".") == TST_NFS_MAGIC) {
> + tst_brkm(TCONF, cleanup, "Cannot test madatory locking "
> + "on a file located on an NFS filesystem");
> + }
> +
> /* set up temp filename */
> sprintf(tmpname, "fcntl4.%d", parent);
>
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-08-21 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <951473587.22362927.1408594230035.JavaMail.zimbra@redhat.com>
2014-08-21 4:12 ` [LTP] [PATCH v3 1/3] fcntl16: Skip fcntl16 tests on NFS Xiong Zhou
2014-08-21 14:14 ` Stanislav Kholmanskikh [this message]
2014-08-22 3:20 ` Xiong Zhou
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=53F5FEB8.7080203@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=xzhou@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.