From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, dsahern@kernel.org, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/8] ipv6: more data-race annotations
Date: Mon, 19 Jan 2026 18:10:23 +0000 [thread overview]
Message-ID: <176884622327.85277.16857633770768048884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260115094141.3124990-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 15 Jan 2026 09:41:33 +0000 you wrote:
> Inspired by one unrelated syzbot report.
>
> This series adds missing (and boring) data-race annotations in IPv6.
>
> Only the first patch adds sysctl_ipv6_flowlabel group
> to speedup ip6_make_flowlabel() a bit.
>
> [...]
Here is the summary with links:
- [net-next,1/8] ipv6: add sysctl_ipv6_flowlabel group
https://git.kernel.org/netdev/net-next/c/e82a347d92d1
- [net-next,2/8] ipv6: annotate data-races from ip6_make_flowlabel()
https://git.kernel.org/netdev/net-next/c/ded139b59b5d
- [net-next,3/8] ipv6: annotate date-race in ipv6_can_nonlocal_bind()
https://git.kernel.org/netdev/net-next/c/3681282530e6
- [net-next,4/8] ipv6: annotate data-races in ip6_multipath_hash_{policy,fields}()
https://git.kernel.org/netdev/net-next/c/03e9d91dd64e
- [net-next,5/8] ipv6: annotate data-races over sysctl.flowlabel_reflect
https://git.kernel.org/netdev/net-next/c/5ade47c974b4
- [net-next,6/8] ipv6: annotate data-races around sysctl.ip6_rt_gc_interval
https://git.kernel.org/netdev/net-next/c/12eddc685744
- [net-next,7/8] ipv6: exthdrs: annotate data-race over multiple sysctl
https://git.kernel.org/netdev/net-next/c/978b67d28358
- [net-next,8/8] ipv6: annotate data-races in net/ipv6/route.c
https://git.kernel.org/netdev/net-next/c/f062e8e25102
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:[~2026-01-19 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:41 [PATCH net-next 0/8] ipv6: more data-race annotations Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 1/8] ipv6: add sysctl_ipv6_flowlabel group Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 2/8] ipv6: annotate data-races from ip6_make_flowlabel() Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 3/8] ipv6: annotate date-race in ipv6_can_nonlocal_bind() Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 4/8] ipv6: annotate data-races in ip6_multipath_hash_{policy,fields}() Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 5/8] ipv6: annotate data-races over sysctl.flowlabel_reflect Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 6/8] ipv6: annotate data-races around sysctl.ip6_rt_gc_interval Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 7/8] ipv6: exthdrs: annotate data-race over multiple sysctl Eric Dumazet
2026-01-15 9:41 ` [PATCH net-next 8/8] ipv6: annotate data-races in net/ipv6/route.c Eric Dumazet
2026-01-19 16:59 ` [PATCH net-next 0/8] ipv6: more data-race annotations Simon Horman
2026-01-19 18: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=176884622327.85277.16857633770768048884.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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