From: trondmy@kernel.org
To: Omar Sandoval <osandov@osandov.com>
Cc: Jeff Layton <jlayton@kernel.org>, Chris Mason <clm@meta.com>,
linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Two more places that need to handle ENETDOWN/ENETUNREACH
Date: Sun, 6 Apr 2025 11:11:19 +0200 [thread overview]
Message-ID: <cover.1743930506.git.trond.myklebust@hammerspace.com> (raw)
From: Trond Myklebust <trond.myklebust@hammerspace.com>
Omar Sandoval reports seeing layouts that are leaked when a container is
shut down uncleanly.
Trond Myklebust (2):
NFSv4: Handle fatal ENETDOWN and ENETUNREACH errors
NFSv4/pnfs: Layoutreturn on close must handle fatal networking errors
fs/nfs/nfs4proc.c | 9 +++++++++
fs/nfs/pnfs.c | 10 +++++++++-
2 files changed, 18 insertions(+), 1 deletion(-)
--
2.49.0
next reply other threads:[~2025-04-06 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-06 9:11 trondmy [this message]
2025-04-06 9:11 ` [PATCH 1/2] NFSv4: Handle fatal ENETDOWN and ENETUNREACH errors trondmy
2025-04-06 13:08 ` Jeff Layton
2025-04-06 15:28 ` Trond Myklebust
2025-04-06 9:11 ` [PATCH 2/2] NFSv4/pnfs: Layoutreturn on close must handle fatal networking errors trondmy
2025-04-06 13:16 ` Jeff Layton
2025-04-06 15:29 ` Trond Myklebust
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.1743930506.git.trond.myklebust@hammerspace.com \
--to=trondmy@kernel.org \
--cc=clm@meta.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=osandov@osandov.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