All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, kuni1840@gmail.com, netdev@vger.kernel.org,
	syzbot+751b587577d0ebca10f2@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 net] ipv6: Protect multiple routes insertion by table lock.
Date: Thu, 29 Oct 2026 00:30:04 +0000	[thread overview]
Message-ID: <179323380457.1497553.16735824787366357153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027065247.2871134-1-kuniyu@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 27 Oct 2026 06:52:45 +0000 you wrote:
> syzbot reported the warning below. [0]
> 
> While call_fib6_multipath_entry_notifiers() is called locklessly,
> fib6_siblings could be changed concurrently, leading to the
> warning (and later null-ptr-deref).
> 
> Let's protect multiple routes insertion with tb6_lock.
> 
> [...]

Here is the summary with links:
  - [v2,net] ipv6: Protect multiple routes insertion by table lock.
    https://git.kernel.org/netdev/net/c/4c6fbb1fbafa

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-29  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27  6:52 [PATCH v2 net] ipv6: Protect multiple routes insertion by table lock Kuniyuki Iwashima
2026-10-27  9:56 ` Eric Dumazet
2026-10-27 14:54 ` David Ahern
2026-10-29  0:30 ` 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=179323380457.1497553.16735824787366357153.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+751b587577d0ebca10f2@syzkaller.appspotmail.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.