All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dai Ngo <dai.ngo@oracle.com>
Cc: chuck.lever@oracle.com, jlayton@redhat.com,
	viro@zeniv.linux.org.uk, linux-nfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC v21 0/7] NFSD: Initial implementation of NFSv4 Courteous Server
Date: Mon, 25 Apr 2022 13:53:27 -0400	[thread overview]
Message-ID: <20220425175327.GD24825@fieldses.org> (raw)
In-Reply-To: <20220425161722.GC24825@fieldses.org>

I'm getting a few new pynfs failures after applying these.  I haven't
tried to investigage what's happening.

--b.

**************************************************
RENEW3   st_renew.testExpired                                     : FAILURE
           nfs4lib.BadCompoundRes: Opening file b'RENEW3-1':
           operation OP_OPEN should return NFS4_OK, instead got
           NFS4ERR_DELAY
LKU10    st_locku.testTimedoutUnlock                              : FAILURE
           nfs4lib.BadCompoundRes: Opening file b'LKU10-1':
           operation OP_OPEN should return NFS4_OK, instead got
           NFS4ERR_DELAY
CLOSE9   st_close.testTimedoutClose2                              : FAILURE
           nfs4lib.BadCompoundRes: Opening file b'CLOSE9-1':
           operation OP_OPEN should return NFS4_OK, instead got
           NFS4ERR_DELAY
CLOSE8   st_close.testTimedoutClose1                              : FAILURE
           nfs4lib.BadCompoundRes: Opening file b'CLOSE8-1':
           operation OP_OPEN should return NFS4_OK, instead got
           NFS4ERR_DELAY

  reply	other threads:[~2022-04-25 17:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 18:44 [PATCH RFC v21 0/7] NFSD: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-04-23 18:44 ` [PATCH RFC v21 1/7] NFSD: add courteous server support for thread with only delegation Dai Ngo
2022-04-25 18:51   ` J. Bruce Fields
2022-04-25 19:42     ` dai.ngo
2022-04-25 20:40       ` J. Bruce Fields
2022-04-25 21:35         ` dai.ngo
2022-04-25 21:48           ` J. Bruce Fields
2022-04-25 22:24             ` dai.ngo
2022-04-25 23:17               ` J. Bruce Fields
2022-04-23 18:44 ` [PATCH RFC v21 2/7] NFSD: add support for share reservation conflict to courteous server Dai Ngo
2022-04-24 12:18   ` kernel test robot
2022-04-25 13:15   ` Chuck Lever III
2022-04-25 15:08     ` dai.ngo
2022-04-23 18:44 ` [PATCH RFC v21 3/7] NFSD: move create/destroy of laundry_wq to init_nfsd and exit_nfsd Dai Ngo
2022-04-25 15:27   ` dai.ngo
2022-04-25 19:35     ` J. Bruce Fields
2022-04-25 19:46       ` dai.ngo
2022-04-23 18:44 ` [PATCH RFC v21 4/7] fs/lock: add helper locks_owner_has_blockers to check for blockers Dai Ngo
2022-04-23 18:44 ` [PATCH RFC v21 5/7] fs/lock: add 2 callbacks to lock_manager_operations to resolve conflict Dai Ngo
2022-04-23 18:44 ` [PATCH RFC v21 6/7] NFSD: add support for lock conflict to courteous server Dai Ngo
2022-04-23 18:44 ` [PATCH RFC v21 7/7] NFSD: Show state of courtesy client in client info Dai Ngo
2022-04-25 16:17 ` [PATCH RFC v21 0/7] NFSD: Initial implementation of NFSv4 Courteous Server J. Bruce Fields
2022-04-25 17:53   ` J. Bruce Fields [this message]
2022-04-25 18:16     ` dai.ngo
2022-04-25 19:19       ` J. Bruce Fields

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=20220425175327.GD24825@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.