From: patchwork-bot+netdevbpf@kernel.org
To: Stefan Wiehler <stefan.wiehler@nokia.com>
Cc: lucien.xin@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
kuniyu@google.com, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/3] Fix SCTP diag locking issues
Date: Tue, 04 Nov 2025 01:20:10 +0000 [thread overview]
Message-ID: <176221921049.2278528.4515165353981721128.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251028161506.3294376-1-stefan.wiehler@nokia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Oct 2025 17:12:25 +0100 you wrote:
> - Hold RCU read lock while iterating over address list in
> inet_diag_msg_sctpaddrs_fill()
> - Prevent TOCTOU out-of-bounds write
> - Hold sock lock while iterating over address list in sctp_sock_dump_one()
>
> v3:
> - Elaborate on TOCTOU call path
> - Merge 3 patches into series
> v2:
> - Add changelog and credit, release sock lock in ENOMEM error path:
> https://patchwork.kernel.org/project/netdevbpf/patch/20251027102541.2320627-2-stefan.wiehler@nokia.com/
> - Add changelog and credit:
> https://patchwork.kernel.org/project/netdevbpf/patch/20251027101328.2312025-2-stefan.wiehler@nokia.com/
> v1:
> - https://patchwork.kernel.org/project/netdevbpf/patch/20251023191807.74006-2-stefan.wiehler@nokia.com/
> - https://patchwork.kernel.org/project/netdevbpf/patch/20251027084835.2257860-1-stefan.wiehler@nokia.com/
> - https://patchwork.kernel.org/project/netdevbpf/patch/20251027085007.2259265-1-stefan.wiehler@nokia.com/
>
> [...]
Here is the summary with links:
- [net,v3,1/3] sctp: Hold RCU read lock while iterating over address list
https://git.kernel.org/netdev/net/c/38f50242bf0f
- [net,v3,2/3] sctp: Prevent TOCTOU out-of-bounds write
https://git.kernel.org/netdev/net/c/95aef86ab231
- [net,v3,3/3] sctp: Hold sock lock while iterating over address list
https://git.kernel.org/netdev/net/c/f1fc201148c7
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:[~2025-11-04 1:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 16:12 [PATCH net v3 0/3] Fix SCTP diag locking issues Stefan Wiehler
2025-10-28 16:12 ` [PATCH net v3 1/3] sctp: Hold RCU read lock while iterating over address list Stefan Wiehler
2025-10-29 16:38 ` Simon Horman
2025-10-29 16:40 ` Simon Horman
2025-10-31 19:28 ` Kuniyuki Iwashima
2025-10-28 16:12 ` [PATCH net v3 2/3] sctp: Prevent TOCTOU out-of-bounds write Stefan Wiehler
2025-10-31 19:27 ` Kuniyuki Iwashima
2025-10-28 16:12 ` [PATCH net v3 3/3] sctp: Hold sock lock while iterating over address list Stefan Wiehler
2025-11-03 19:41 ` [PATCH net v3 0/3] Fix SCTP diag locking issues Xin Long
2025-11-04 1:20 ` 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=176221921049.2278528.4515165353981721128.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan.wiehler@nokia.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