From: Markus Elfring <Markus.Elfring@web.de>
To: linux-nfs@vger.kernel.org, Anna Schumaker <anna@kernel.org>,
Benjamin Coddington <bcodding@redhat.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
Trond Myklebust <trondmy@kernel.org>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v2 0/2] NFS: Fix exception handling in nfs_alloc_server()
Date: Sun, 14 Jun 2026 10:37:44 +0200 [thread overview]
Message-ID: <4f7c0c98-62b6-44e0-87b4-35abc46303de@web.de> (raw)
In-Reply-To: <1c8e10c9-def7-4f0d-8aa1-23c8035a38c8@wanadoo.fr>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sun, 14 Jun 2026 10:28:05 +0200
Subject: [PATCH v2 0/2] NFS: Fix exception handling in nfs_alloc_server()
A few update suggestions were taken into account from source code analysis.
Markus Elfring (2):
Prevent resource leak
Use common error handling code
v2:
Christophe Jaillet pointed out that ida_free() should be called in
the error handling path after a successful ida_alloc() call.
Thus corresponding tags were added.
See also:
https://elixir.bootlin.com/linux/v7.1-rc7/source/lib/idr.c#L549-L595
fs/nfs/client.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
--
2.54.0
next prev parent reply other threads:[~2026-06-14 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 16:35 [PATCH] NFS: Use common error handling code " Markus Elfring
2026-06-13 20:24 ` Christophe JAILLET
2026-06-14 8:37 ` Markus Elfring [this message]
2026-06-14 8:42 ` [PATCH v2 1/2] NFS: Prevent resource leak " Markus Elfring
2026-06-14 8:43 ` [PATCH v2 2/2] NFS: Use common error handling code " Markus Elfring
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=4f7c0c98-62b6-44e0-87b4-35abc46303de@web.de \
--to=markus.elfring@web.de \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=brauner@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=chuck.lever@oracle.com \
--cc=hch@lst.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®