From: Trond Myklebust <trondmy@hammerspace.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>,
"anna@kernel.org" <anna@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"wanghai38@huawei.com" <wanghai38@huawei.com>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"kuba@kernel.org" <kuba@kernel.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Refix the socket leak in xs_setup_local()
Date: Wed, 11 May 2022 16:14:18 +0000 [thread overview]
Message-ID: <2125358c4fbdcf2e9f84017a2f6b27830ffcb8f2.camel@hammerspace.com> (raw)
In-Reply-To: <20220511132232.4030-1-wanghai38@huawei.com>
On Wed, 2022-05-11 at 21:22 +0800, Wang Hai wrote:
> Patch1 and patch2 roll back the wrong solution to fix socket leaks.
>
> Patch3 adds safe teardown mechanism to re-fix socket leaks.
>
> Wang Hai (3):
> Revert "SUNRPC: Ensure gss-proxy connects on setup"
> Revert "Revert "SUNRPC: attempt AF_LOCAL connect on setup""
> SUNRPC: Fix local socket leak in xs_setup_local()
>
> include/linux/sunrpc/clnt.h | 1 -
> net/sunrpc/auth_gss/gss_rpc_upcall.c | 2 +-
> net/sunrpc/clnt.c | 3 ---
> net/sunrpc/xprtsock.c | 19 ++++++++++++++++++-
> 4 files changed, 19 insertions(+), 6 deletions(-)
>
Thanks, but there is already a fix for this queued up in the linux-next
branch.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2022-05-11 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 13:22 Wang Hai
2022-05-11 13:22 ` [PATCH 1/3] Revert "SUNRPC: Ensure gss-proxy connects on setup" Wang Hai
2022-05-11 13:22 ` [PATCH 2/3] Revert "Revert "SUNRPC: attempt AF_LOCAL connect on setup"" Wang Hai
2022-05-11 13:22 ` [PATCH 3/3] SUNRPC: Fix local socket leak in xs_setup_local() Wang Hai
2022-05-11 16:14 ` Trond Myklebust [this message]
2022-05-12 1:58 ` [PATCH 0/3] Refix the " wanghai (M)
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=2125358c4fbdcf2e9f84017a2f6b27830ffcb8f2.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna@kernel.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wanghai38@huawei.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
all inboxes | Powered by JetHome®