All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Coddington <ben.coddington@hammerspace.com>
To: calum.mackay@oracle.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH pynfs 0/2] rpc: fix two client connection failures
Date: Thu, 19 Nov 2026 16:40:58 -0500	[thread overview]
Message-ID: <cover.1795124374.git.bcodding@hammerspace.com> (raw)

These fix two bugs in the pynfs RPC client, both seen while running the
4.1 server tests.

The first breaks --secure on a back-to-back run: the client rebinds the
reserved port left in TIME_WAIT by the previous run, connect() fails
with EADDRNOTAVAIL, and the error is replaced by EBADF, so the run ends
with "Initialization failed".

The second hangs a test when the server closes the connection: waiting
calls are never woken, and the polling thread dies in select() on the
closed socket's fd of -1.  With the fix those calls fail with an RPC
error and the test is reported as a FAILURE.

Benjamin Coddington (2):
  rpc: skip secure ports in TIME_WAIT and report connect errors
  rpc: fail pending calls when a connection closes

 rpc/rpc.py | 80 ++++++++++++++++++++++++++++++++++++++++--------------
 1 file changed, 59 insertions(+), 21 deletions(-)


base-commit: cd4701827a8261fedbfb4c6e39029fb9671321a6
-- 
2.53.0


             reply	other threads:[~2026-11-19 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 21:40 Benjamin Coddington [this message]
2026-11-19 21:40 ` [PATCH pynfs 1/2] rpc: skip secure ports in TIME_WAIT and report connect errors Benjamin Coddington
2026-11-19 21:41 ` [PATCH pynfs 2/2] rpc: fail pending calls when a connection closes Benjamin Coddington

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=cover.1795124374.git.bcodding@hammerspace.com \
    --to=ben.coddington@hammerspace.com \
    --cc=calum.mackay@oracle.com \
    --cc=linux-nfs@vger.kernel.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 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.