From: Steve Dickson <steved@redhat.com>
To: tbecker@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] rpc.gssd: Two resource leaks
Date: Sat, 11 Jul 2026 12:19:47 -0400 [thread overview]
Message-ID: <20b583fd-cf4d-45ec-9c86-32a96ba819bc@redhat.com> (raw)
In-Reply-To: <20260703163946.2185163-1-tbecker@redhat.com>
On 7/3/26 12:39 PM, tbecker@redhat.com wrote:
> From: Thiago Becker <tbecker@redhat.com>
>
> Patch 1 drops a reference to clnt_info when alloc_upcall_info fails.
> Patch 2 frees the thread attributes before returning from
> start_upcall_thread.
>
> Both leaks were identified by claude sonnet 4.5, among some amount of
> false positives that were hand filtered.
>
> Thiago Becker (2):
> rpc.gssd: Decrement client referece count on error paths
> rpc.gssd: Call pthread_attr_destroy before returning from
> start_upcall_thread
>
> utils/gssd/gssd_proc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
Committed... (tag: nfs-utils-2-9-2-rc5)
steved.
prev parent reply other threads:[~2026-07-11 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 16:39 [PATCH 0/2] rpc.gssd: Two resource leaks tbecker
2026-07-03 16:39 ` [PATCH 1/2] rpc.gssd: Decrement client referece count on error paths tbecker
2026-07-03 16:39 ` [PATCH 2/2] rpc.gssd: Call pthread_attr_destroy before returning from start_upcall_thread tbecker
2026-07-11 16:19 ` Steve Dickson [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=20b583fd-cf4d-45ec-9c86-32a96ba819bc@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tbecker@redhat.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