From: patchwork-bot+netdevbpf@kernel.org
To: Xiyu Yang <xiyuyang19@fudan.edu.cn>
Cc: davem@davemloft.net, kuba@kernel.org, cong.wang@bytedance.com,
rdunlap@infradead.org, tparkin@katalix.com,
xiongx18@fudan.edu.cn, sishuai@purdue.edu,
mschiffer@universe-factory.net, unixbhaskar@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yuanxzhang@fudan.edu.cn, tanxin.ctf@gmail.com
Subject: Re: [PATCH] net/l2tp: Fix reference count leak in l2tp_udp_recv_core
Date: Thu, 09 Sep 2021 10:10:05 +0000 [thread overview]
Message-ID: <163118220579.5425.12106062593104107133.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1631161930-77772-1-git-send-email-xiyuyang19@fudan.edu.cn>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 9 Sep 2021 12:32:00 +0800 you wrote:
> The reference count leak issue may take place in an error handling
> path. If both conditions of tunnel->version == L2TP_HDR_VER_3 and the
> return value of l2tp_v3_ensure_opt_in_linear is nonzero, the function
> would directly jump to label invalid, without decrementing the reference
> count of the l2tp_session object session increased earlier by
> l2tp_tunnel_get_session(). This may result in refcount leaks.
>
> [...]
Here is the summary with links:
- net/l2tp: Fix reference count leak in l2tp_udp_recv_core
https://git.kernel.org/netdev/net/c/9b6ff7eb6664
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-09-09 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 4:32 [PATCH] net/l2tp: Fix reference count leak in l2tp_udp_recv_core Xiyu Yang
2021-09-09 9:01 ` Tom Parkin
2021-09-09 9:10 ` Tom Parkin
2021-09-09 10:10 ` 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=163118220579.5425.12106062593104107133.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sishuai@purdue.edu \
--cc=tanxin.ctf@gmail.com \
--cc=tparkin@katalix.com \
--cc=unixbhaskar@gmail.com \
--cc=xiongx18@fudan.edu.cn \
--cc=xiyuyang19@fudan.edu.cn \
--cc=yuanxzhang@fudan.edu.cn \
/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