From: patchwork-bot+netdevbpf@kernel•org
To: Paolo Abeni <pabeni@redhat•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net,
yoshfuji@linux-ipv6•org, dsahern@kernel•org, edumazet@google•com,
kuba@kernel•org, davejwatson@fb•com, borisp@mellanox•com,
slipper.alive@gmail•com
Subject: Re: [PATCH net] net/ulp: prevent ULP without clone op from entering the LISTEN status
Date: Thu, 05 Jan 2023 04:44:11 +0000 [thread overview]
Message-ID: <167289385147.19861.7104633829687203944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4b80c3d1dbe3d0ab072f80450c202d9bc88b4b03.1672740602.git.pabeni@redhat.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Tue, 3 Jan 2023 12:19:17 +0100 you wrote:
> When an ULP-enabled socket enters the LISTEN status, the listener ULP data
> pointer is copied inside the child/accepted sockets by sk_clone_lock().
>
> The relevant ULP can take care of de-duplicating the context pointer via
> the clone() operation, but only MPTCP and SMC implement such op.
>
> Other ULPs may end-up with a double-free at socket disposal time.
>
> [...]
Here is the summary with links:
- [net] net/ulp: prevent ULP without clone op from entering the LISTEN status
https://git.kernel.org/netdev/net/c/2c02d41d71f9
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:[~2023-01-05 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 11:19 [PATCH net] net/ulp: prevent ULP without clone op from entering the LISTEN status Paolo Abeni
2023-01-05 4:44 ` 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=167289385147.19861.7104633829687203944.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=borisp@mellanox$(echo .)com \
--cc=davejwatson@fb$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=slipper.alive@gmail$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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