From: Simon Horman <simon.horman@corigine.com>
To: Chuck Lever <cel@kernel.org>
Cc: kernel-tls-handshake@lists.linux.dev, netdev@vger.kernel.org,
dan.carpenter@linaro.org
Subject: Re: [PATCH 2/5] net/handshake: Fix handshake_dup() ref counting
Date: Fri, 5 May 2023 15:15:39 +0200 [thread overview]
Message-ID: <ZFUBe016EUW+bwyg@corigine.com> (raw)
In-Reply-To: <168321389545.16695.14828237648251844351.stgit@oracle-102.nfsv4bat.org>
On Thu, May 04, 2023 at 11:25:05AM -0400, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> If get_unused_fd_flags() fails, we ended up calling fput(sock->file)
> twice.
>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Fixes: 3b3009ea8abb ("net/handshake: Create a NETLINK service for handling handshake requests")
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-05-05 13:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:24 [PATCH 0/5] Bug fixes for net/handshake Chuck Lever
2023-05-04 15:24 ` [PATCH 1/5] net/handshake: Remove unneeded check from handshake_dup() Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-04 15:25 ` [PATCH 2/5] net/handshake: Fix handshake_dup() ref counting Chuck Lever
2023-05-05 13:15 ` Simon Horman [this message]
2023-05-05 20:58 ` Jakub Kicinski
2023-05-05 23:28 ` Chuck Lever
2023-05-04 15:25 ` [PATCH 3/5] net/handshake: Fix uninitialized local variable Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-04 15:25 ` [PATCH 4/5] net/handshake: handshake_genl_notify() shouldn't ignore @flags Chuck Lever
2023-05-05 13:15 ` Simon Horman
2023-05-04 15:26 ` [PATCH 5/5] net/handshake: Enable the SNI extension to work properly Chuck Lever
2023-05-05 13:16 ` Simon Horman
2023-05-05 20:39 ` [PATCH 0/5] Bug fixes for net/handshake Jakub Kicinski
2023-05-05 23:16 ` Chuck Lever
2023-05-05 23:47 ` Jakub Kicinski
2023-05-05 23:58 ` Chuck Lever
2023-05-08 5:51 ` Paolo Abeni
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=ZFUBe016EUW+bwyg@corigine.com \
--to=simon.horman@corigine.com \
--cc=cel@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).