From: patchwork-bot+netdevbpf@kernel.org
To: Xiaoming Ni <nixiaoming@huawei.com>
Cc: linux-kernel@vger.kernel.org, kiyin@tencent.com,
stable@vger.kernel.org, gregkh@linuxfoundation.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 resend 0/4] nfc: fix Resource leakage and endless loop
Date: Fri, 26 Mar 2021 00:30:10 +0000 [thread overview]
Message-ID: <161671861047.2256.9727486806659792945.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210325035113.49323-1-nixiaoming@huawei.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Thu, 25 Mar 2021 11:51:09 +0800 you 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
>
> Xiaoming Ni (4):
> nfc: fix refcount leak in llcp_sock_bind()
> nfc: fix refcount leak in llcp_sock_connect()
> nfc: fix memory leak in llcp_sock_connect()
> nfc: Avoid endless loops caused by repeated llcp_sock_connect()
>
> [...]
Here is the summary with links:
- [resend,1/4] nfc: fix refcount leak in llcp_sock_bind()
https://git.kernel.org/netdev/net/c/c33b1cc62ac0
- [resend,2/4] nfc: fix refcount leak in llcp_sock_connect()
https://git.kernel.org/netdev/net/c/8a4cd82d62b5
- [resend,3/4] nfc: fix memory leak in llcp_sock_connect()
https://git.kernel.org/netdev/net/c/7574fcdbdcb3
- [resend,4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect()
https://git.kernel.org/netdev/net/c/4b5db93e7f2a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-26 0:30 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 ` [PATCH 0/4] nfc: fix Resource leakage and endless loop Greg KH
2021-03-25 3:51 ` [PATCH resend " 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 ` patchwork-bot+netdevbpf [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=161671861047.2256.9727486806659792945.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.