From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, idosch@nvidia.com,
jiayuan.chen@shopee.com, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v4 0/2] net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop and add selftest
Date: Thu, 05 Mar 2026 16:10:30 +0000 [thread overview]
Message-ID: <177272703078.3188128.539055376981723879.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304113817.294966-1-jiayuan.chen@linux.dev>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Mar 2026 19:38:12 +0800 you wrote:
> syzbot reported a kernel panic [1] when an IPv4 route references
> a loopback IPv6 nexthop object:
>
> BUG: unable to handle page fault for address: ffff8d069e7aa000
> PF: supervisor read access in kernel mode
> PF: error_code(0x0000) - not-present page
> PGD 6aa01067 P4D 6aa01067 PUD 0
> Oops: Oops: 0000 [#1] SMP PTI
> CPU: 2 UID: 0 PID: 530 Comm: ping Not tainted 6.19.0+ #193 PREEMPT
> RIP: 0010:ip_route_output_key_hash_rcu+0x578/0x9e0
> RSP: 0018:ffffd2ffc1573918 EFLAGS: 00010286
> RAX: ffff8d069e7aa000 RBX: ffffd2ffc1573988 RCX: 0000000000000000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: ffffd2ffc1573978 R08: 0000000000000000 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000000 R12: ffff8d060d496000
> R13: 0000000000000000 R14: ffff8d060399a600 R15: ffff8d06019a6ab8
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff8d069e7aa000 CR3: 0000000106eb0001 CR4: 0000000000770ef0
> PKRU: 55555554
> Call Trace:
> <TASK>
> ip_route_output_key_hash+0x86/0x1a0
> __ip4_datagram_connect+0x2b5/0x4e0
> udp_connect+0x2c/0x60
> inet_dgram_connect+0x88/0xd0
> __sys_connect_file+0x56/0x90
> __sys_connect+0xa8/0xe0
> __x64_sys_connect+0x18/0x30
> x64_sys_call+0xfb9/0x26e0
> do_syscall_64+0xd3/0x1510
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> [...]
Here is the summary with links:
- [net,v4,1/2] net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop
https://git.kernel.org/netdev/net/c/21ec92774d15
- [net,v4,2/2] selftests: net: add test for IPv4 route with loopback IPv6 nexthop
https://git.kernel.org/netdev/net/c/46c1ef0cfcea
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-03-05 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 11:38 [PATCH net v4 0/2] net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop and add selftest Jiayuan Chen
2026-03-04 11:38 ` [PATCH net v4 1/2] net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop Jiayuan Chen
2026-03-04 13:54 ` Ido Schimmel
2026-03-04 15:21 ` David Ahern
2026-03-04 11:38 ` [PATCH net v4 2/2] selftests: net: add test for IPv4 route with " Jiayuan Chen
2026-03-04 15:22 ` David Ahern
2026-03-05 16: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=177272703078.3188128.539055376981723879.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiayuan.chen@linux.dev \
--cc=jiayuan.chen@shopee.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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