From: dai.ngo@oracle.com
To: Matthew Wilcox <willy@infradead.org>
Cc: brauner@kernel.org, Jorge Mora <Jorge.Mora@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: nfstest_posix failed with 6.7 kernel (resend)
Date: Mon, 15 Jan 2024 13:24:37 -0800 [thread overview]
Message-ID: <3ca3cf50-9f2a-4110-b429-e85a2901396c@oracle.com> (raw)
In-Reply-To: <ZaWgL7RxJtAHeayb@casper.infradead.org>
On 1/15/24 1:14 PM, Matthew Wilcox wrote:
> On Mon, Jan 15, 2024 at 01:05:37PM -0800, dai.ngo@oracle.com wrote:
>> (resend with correct Jorge Mora address)
>>
>> The 'open' tests of nfstest_posix failed with 6.7 kernel with these errors:
>>
>> FAIL: open - opening existent file should return an error when O_EXCL|O_CREAT is used (256 passed, 256 failed)
>> FAIL: open - opening symbolic link should return an error when O_EXCL|O_CREAT is used (256 passed, 256 failed)
> it might be helpful if you either included a source code snippet of
> "nfstest_posix" or a link to where we can see what it's doing. or an
> strace of the failing call.
>
This is the link to source code of nfstest:
http://wiki.linux-nfs.org/wiki/index.php/NFStest#Download To reproduce
the problem run the test as follow: nfstest_posix --server /nfs_server/
--export=//home/nfs_share/ --notty --createlog --nfsversion=4.1
--tmpdir=/var/tmp/nfstestlogs --verbose all --runtest open -Dai
next prev parent reply other threads:[~2024-01-15 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 21:05 nfstest_posix failed with 6.7 kernel (resend) dai.ngo
2024-01-15 21:14 ` Matthew Wilcox
2024-01-15 21:24 ` dai.ngo [this message]
2024-01-16 9:25 ` Christian Brauner
2024-01-16 20:51 ` dai.ngo
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=3ca3cf50-9f2a-4110-b429-e85a2901396c@oracle.com \
--to=dai.ngo@oracle.com \
--cc=Jorge.Mora@netapp.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=willy@infradead.org \
/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