From: Petr Vorel <pvorel@suse.cz>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: linux-nfs@vger.kernel.org, Yong Sun <yosun@suse.com>
Subject: pynfs: [NFS 4.0] SEC7, LOCK24 test failures
Date: Tue, 1 Jun 2021 16:01:08 +0200 [thread overview]
Message-ID: <YLY9pKu38lEWaXxE@pevik> (raw)
Hi Bruce,
I've also find different failures on NFS 4.0:
SEC7 st_secinfo.testRPCSEC_GSS : FAILURE
SECINFO returned mechanism list without RPCSEC_GSS
LOCK24 st_lock.testOpenUpgradeLock : FAILURE
OP_LOCK should return NFS4_OK, instead got
NFS4ERR_BAD_SEQID
They're on stable kernel 5.12.3-1-default (openSUSE). I saw them also on older
kernel 4.19.0-16-amd64 (Debian).
Any idea how to find whether are these are wrong setup or test bugs or real
kernel bugs?
Upstreaming your scripts or better documenting the setup would be great.
Kind regards,
Petr
next reply other threads:[~2021-06-01 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 14:01 Petr Vorel [this message]
2021-06-01 15:31 ` pynfs: [NFS 4.0] SEC7, LOCK24 test failures J. Bruce Fields
2021-06-02 7:58 ` Petr Vorel
2022-01-18 4:52 ` NeilBrown
2022-01-20 10:51 ` Petr Vorel
2022-01-25 22:46 ` Bruce Fields
2022-01-25 23:48 ` NeilBrown
2022-01-26 0:14 ` Frank Filz
2022-04-01 13:30 ` Petr Vorel
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=YLY9pKu38lEWaXxE@pevik \
--to=pvorel@suse.cz \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=yosun@suse.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