netdev - Re: [PATCH 0/3] Refix the socket leak in xs_setup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 12 May 2022 09:58:32 +0800
From:   "wanghai (M)" <wanghai38@...wei.com>
To:     Trond Myklebust <trondmy@...merspace.com>,
        "bfields@...ldses.org" <bfields@...ldses.org>,
        "anna@...nel.org" <anna@...nel.org>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "chuck.lever@...cle.com" <chuck.lever@...cle.com>,
        "kuba@...nel.org" <kuba@...nel.org>
CC:     "linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] Refix the socket leak in xs_setup_local()


在 2022/5/12 0:14, Trond Myklebust 写道:
> 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.
Thanks, sorry to bother you, I found it.

I only subscribed to the linux-kernel@...r.kernel.org mailing list,
not the linux-nfs@...r.kernel.org mailing list separately. So I
didn't notice it was fixed.

-- 
Wang Hai