From: patchwork-bot+netdevbpf@kernel.org
To: Or Cohen <orcohen@paloaltonetworks.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vyasevich@gmail.com, nhorman@tuxdriver.com,
marcelo.leitner@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux-sctp@vger.kernel.org, lucien.xin@gmail.com,
nmarkus@paloaltonetworks.com
Subject: Re: [PATCH v2] net/sctp: fix race condition in sctp_destroy_sock
Date: Tue, 13 Apr 2021 22:10:08 +0000 [thread overview]
Message-ID: <161835180857.31494.15153605709607960746.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210413181031.27557-1-orcohen@paloaltonetworks.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 13 Apr 2021 21:10:31 +0300 you wrote:
> If sctp_destroy_sock is called without sock_net(sk)->sctp.addr_wq_lock
> held and sp->do_auto_asconf is true, then an element is removed
> from the auto_asconf_splist without any proper locking.
>
> This can happen in the following functions:
> 1. In sctp_accept, if sctp_sock_migrate fails.
> 2. In inet_create or inet6_create, if there is a bpf program
> attached to BPF_CGROUP_INET_SOCK_CREATE which denies
> creation of the sctp socket.
>
> [...]
Here is the summary with links:
- [v2] net/sctp: fix race condition in sctp_destroy_sock
https://git.kernel.org/netdev/net/c/b166a20b0738
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-04-13 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 18:10 [PATCH v2] net/sctp: fix race condition in sctp_destroy_sock Or Cohen
2021-04-13 19:08 ` Marcelo Ricardo Leitner
2021-04-13 22: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=161835180857.31494.15153605709607960746.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nmarkus@paloaltonetworks.com \
--cc=orcohen@paloaltonetworks.com \
--cc=vyasevich@gmail.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).