From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net 0/4] ipv6: f6i->fib6_siblings and rt->fib6_nsiblings fixes
Date: Sat, 26 Jul 2025 11:34:17 -0700 [thread overview]
Message-ID: <20250726113417.1371e296@kernel.org> (raw)
In-Reply-To: <20250725140725.3626540-1-edumazet@google.com>
On Fri, 25 Jul 2025 14:07:21 +0000 Eric Dumazet wrote:
> Series based on an internal syzbot report with a repro.
>
> After fixing (in the first patch) the original minor issue,
> I found that syzbot repro was able to trigger a second
> more serious bug in rt6_nlmsg_size().
>
> Code review then led to the two final patches.
>
> I have not released the syzbot bug, because other issues
> still need investigations.
We should probably spend more time on tests that modify things
concurrently for the RCU conversions :$
next prev parent reply other threads:[~2025-07-26 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 14:07 [PATCH net 0/4] ipv6: f6i->fib6_siblings and rt->fib6_nsiblings fixes Eric Dumazet
2025-07-25 14:07 ` [PATCH net 1/4] ipv6: add a retry logic in net6_rt_notify() Eric Dumazet
2025-07-25 14:07 ` [PATCH net 2/4] ipv6: prevent infinite loop in rt6_nlmsg_size() Eric Dumazet
2025-07-25 14:07 ` [PATCH net 3/4] ipv6: fix possible infinite loop in fib6_info_uses_dev() Eric Dumazet
2025-07-25 14:07 ` [PATCH net 4/4] ipv6: annotate data-races around rt->fib6_nsiblings Eric Dumazet
2025-07-26 18:34 ` Jakub Kicinski [this message]
2025-07-26 18:40 ` [PATCH net 0/4] ipv6: f6i->fib6_siblings and rt->fib6_nsiblings fixes patchwork-bot+netdevbpf
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=20250726113417.1371e296@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuniyu@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.