From: Greg KH <gregkh@linuxfoundation.org>
To: Xiaoming Ni <nixiaoming@huawei.com>
Cc: linux-kernel@vger.kernel.org, kiyin@tencent.com,
stable@vger.kernel.org, sameo@linux.intel.com,
linville@tuxdriver.com, davem@davemloft.net, kuba@kernel.org,
mkl@pengutronix.de, stefan@datenfreihafen.org,
matthieu.baerts@tessares.net, netdev@vger.kernel.org,
wangle6@huawei.com, xiaoqian9@huawei.com
Subject: Re: [PATCH 0/4] nfc: fix Resource leakage and endless loop
Date: Tue, 23 Mar 2021 14:43:36 +0100 [thread overview]
Message-ID: <YFnwiFmgejk/TKOX@kroah.com> (raw)
In-Reply-To: <20210303061654.127666-1-nixiaoming@huawei.com>
On Wed, Mar 03, 2021 at 02:16:50PM +0800, Xiaoming Ni wrote:
> fix Resource leakage and endless loop in net/nfc/llcp_sock.c,
> reported by "kiyin(尹亮)".
>
> Link: https://www.openwall.com/lists/oss-security/2020/11/01/1
What happened to this series?
Does it need to be resent against the latest networking tree?
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-23 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 6:16 [PATCH 0/4] nfc: fix Resource leakage and endless loop Xiaoming Ni
2021-03-03 6:16 ` [PATCH 1/4] nfc: fix refcount leak in llcp_sock_bind() Xiaoming Ni
2021-03-03 6:16 ` [PATCH 2/4] nfc: fix refcount leak in llcp_sock_connect() Xiaoming Ni
2021-03-03 6:16 ` [PATCH 3/4] nfc: fix memory " Xiaoming Ni
2021-03-03 6:16 ` [PATCH 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect() Xiaoming Ni
2021-03-03 9:28 ` [PATCH 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect()(Internet mail) kiyin(尹亮)
2021-03-05 3:24 ` Xiaoming Ni
2021-03-23 13:43 ` Greg KH [this message]
2021-03-25 3:51 ` [PATCH resend 0/4] nfc: fix Resource leakage and endless loop Xiaoming Ni
2021-03-25 3:51 ` [PATCH resend 1/4] nfc: fix refcount leak in llcp_sock_bind() Xiaoming Ni
2021-03-25 3:51 ` [PATCH resend 2/4] nfc: fix refcount leak in llcp_sock_connect() Xiaoming Ni
2021-03-25 3:51 ` [PATCH resend 3/4] nfc: fix memory " Xiaoming Ni
2021-03-25 3:51 ` [PATCH resend 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect() Xiaoming Ni
2021-03-26 0:30 ` [PATCH resend 0/4] nfc: fix Resource leakage and endless loop patchwork-bot+netdevbpf
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=YFnwiFmgejk/TKOX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=kiyin@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=matthieu.baerts@tessares.net \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=nixiaoming@huawei.com \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=wangle6@huawei.com \
--cc=xiaoqian9@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;
as well as URLs for NNTP newsgroup(s).