From: "hch@lst.de" <hch@lst.de>
To: Nate Prodromou <nate@prodromou.com>
Cc: "trond.myklebust@hammerspace.com"
<trond.myklebust@hammerspace.com>,
"anna@kernel.org" <anna@kernel.org>, "hch@lst.de" <hch@lst.de>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS: fix delegation_hash_table leak when nfs4_server_common_setup() fails
Date: Wed, 15 Jul 2026 06:41:33 +0200 [thread overview]
Message-ID: <20260715044133.GA16065@lst.de> (raw)
In-Reply-To: <SA1P220MB14925066FEE37CAC1C083DEBC8F92@SA1P220MB1492.NAMP220.PROD.OUTLOOK.COM>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2026-07-15 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 18:58 [PATCH] NFS: fix delegation_hash_table leak when nfs4_server_common_setup() fails Nate Prodromou
2026-07-15 4:41 ` hch [this message]
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=20260715044133.GA16065@lst.de \
--to=hch@lst.de \
--cc=anna@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nate@prodromou.com \
--cc=trond.myklebust@hammerspace.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