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, kuniyu@google.com, dsahern@kernel.org,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot+0141c834e47059395621@syzkaller.appspotmail.com,
petrm@nvidia.com, roopa@nvidia.com, razor@blackwall.org,
bpoirier@nvidia.com, idosch@nvidia.com
Subject: Re: [PATCH net-next] ipv6: guard ip6_mr_output() with rcu
Date: Tue, 01 Jul 2025 01:20:07 +0000 [thread overview]
Message-ID: <175133280734.3630108.2288047934531939034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250627115822.3741390-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 27 Jun 2025 11:58:21 +0000 you wrote:
> syzbot found at least one path leads to an ip_mr_output()
> without RCU being held.
>
> Add guard(rcu)() to fix this in a concise way.
>
> WARNING: net/ipv6/ip6mr.c:2376 at ip6_mr_output+0xe0b/0x1040 net/ipv6/ip6mr.c:2376, CPU#1: kworker/1:2/121
> Call Trace:
> <TASK>
> ip6tunnel_xmit include/net/ip6_tunnel.h:162 [inline]
> udp_tunnel6_xmit_skb+0x640/0xad0 net/ipv6/ip6_udp_tunnel.c:112
> send6+0x5ac/0x8d0 drivers/net/wireguard/socket.c:152
> wg_socket_send_skb_to_peer+0x111/0x1d0 drivers/net/wireguard/socket.c:178
> wg_packet_create_data_done drivers/net/wireguard/send.c:251 [inline]
> wg_packet_tx_worker+0x1c8/0x7c0 drivers/net/wireguard/send.c:276
> process_one_work kernel/workqueue.c:3239 [inline]
> process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3322
> worker_thread+0x8a0/0xda0 kernel/workqueue.c:3403
> kthread+0x70e/0x8a0 kernel/kthread.c:464
> ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
> </TASK>
>
> [...]
Here is the summary with links:
- [net-next] ipv6: guard ip6_mr_output() with rcu
https://git.kernel.org/netdev/net-next/c/af232e7615e4
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-07-01 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 11:58 [PATCH net-next] ipv6: guard ip6_mr_output() with rcu Eric Dumazet
2025-06-27 13:33 ` Nikolay Aleksandrov
2025-06-27 14:50 ` Petr Machata
2025-07-01 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=175133280734.3630108.2288047934531939034.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=syzbot+0141c834e47059395621@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.