From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
kuni1840@gmail.com, netdev@vger.kernel.org,
syzkaller@googlegroups.com
Subject: Re: [PATCH v1 net] tcp: Clean up kernel listener's reqsk in inet_twsk_purge()
Date: Thu, 13 Oct 2022 16:50:16 +0000 [thread overview]
Message-ID: <166567981605.2135.16734103655927008557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221012145036.74960-1-kuniyu@amazon.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 12 Oct 2022 07:50:36 -0700 you wrote:
> Eric Dumazet reported a use-after-free related to the per-netns ehash
> series. [0]
>
> When we create a TCP socket from userspace, the socket always holds a
> refcnt of the netns. This guarantees that a reqsk timer is always fired
> before netns dismantle. Each reqsk has a refcnt of its listener, so the
> listener is not freed before the reqsk, and the net is not freed before
> the listener as well.
>
> [...]
Here is the summary with links:
- [v1,net] tcp: Clean up kernel listener's reqsk in inet_twsk_purge()
https://git.kernel.org/netdev/net/c/740ea3c4a0b2
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:[~2022-10-13 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 14:50 [PATCH v1 net] tcp: Clean up kernel listener's reqsk in inet_twsk_purge() Kuniyuki Iwashima
2022-10-12 16:31 ` Eric Dumazet
2022-10-12 17:28 ` Kuniyuki Iwashima
2022-10-12 18:54 ` Eric Dumazet
2022-10-12 19:36 ` Kuniyuki Iwashima
2022-10-13 15:56 ` Eric Dumazet
2022-10-13 16:50 ` 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=166567981605.2135.16734103655927008557.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller@googlegroups.com \
--cc=yoshfuji@linux-ipv6.org \
/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).