From: patchwork-bot+netdevbpf@kernel.org
To: Levi Zim via B4 Relay <devnull+rsworktech.outlook.com@kernel.org>
Cc: john.fastabend@gmail.com, jakub@cloudflare.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, dsahern@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, rsworktech@outlook.com
Subject: Re: [PATCH net 0/2] Fix NPE discovered by running bpf kselftest
Date: Fri, 20 Dec 2024 22:20:33 +0000 [thread overview]
Message-ID: <173473323379.3037384.4089610194127923528.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241130-tcp-bpf-sendmsg-v1-0-bae583d014f3@outlook.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Sat, 30 Nov 2024 21:38:21 +0800 you wrote:
> I found that bpf kselftest sockhash::test_txmsg_cork_hangs in
> test_sockmap.c triggers a kernel NULL pointer dereference:
>
> BUG: kernel NULL pointer dereference, address: 0000000000000008
> ? __die_body+0x6e/0xb0
> ? __die+0x8b/0xa0
> ? page_fault_oops+0x358/0x3c0
> ? local_clock+0x19/0x30
> ? lock_release+0x11b/0x440
> ? kernelmode_fixup_or_oops+0x54/0x60
> ? __bad_area_nosemaphore+0x4f/0x210
> ? mmap_read_unlock+0x13/0x30
> ? bad_area_nosemaphore+0x16/0x20
> ? do_user_addr_fault+0x6fd/0x740
> ? prb_read_valid+0x1d/0x30
> ? exc_page_fault+0x55/0xd0
> ? asm_exc_page_fault+0x2b/0x30
> ? splice_to_socket+0x52e/0x630
> ? shmem_file_splice_read+0x2b1/0x310
> direct_splice_actor+0x47/0x70
> splice_direct_to_actor+0x133/0x300
> ? do_splice_direct+0x90/0x90
> do_splice_direct+0x64/0x90
> ? __ia32_sys_tee+0x30/0x30
> do_sendfile+0x214/0x300
> __se_sys_sendfile64+0x8e/0xb0
> __x64_sys_sendfile64+0x25/0x30
> x64_sys_call+0xb82/0x2840
> do_syscall_64+0x75/0x110
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
>
> [...]
Here is the summary with links:
- [net,1/2] skmsg: return copied bytes in sk_msg_memcopy_from_iter
https://git.kernel.org/bpf/bpf/c/fdf478d236dc
- [net,2/2] tcp_bpf: fix copied value in tcp_bpf_sendmsg
https://git.kernel.org/bpf/bpf/c/5153a75ef34b
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:[~2024-12-20 22:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 13:38 [PATCH net 0/2] Fix NPE discovered by running bpf kselftest Levi Zim via B4 Relay
2024-11-30 13:38 ` [PATCH net 1/2] skmsg: return copied bytes in sk_msg_memcopy_from_iter Levi Zim via B4 Relay
2024-11-30 13:38 ` [PATCH net 2/2] tcp_bpf: fix copied value in tcp_bpf_sendmsg Levi Zim via B4 Relay
2024-12-09 7:02 ` John Fastabend
2024-12-09 11:56 ` Levi Zim
2024-12-10 6:14 ` John Fastabend
2024-12-01 1:42 ` [PATCH net 0/2] Fix NPE discovered by running bpf kselftest Levi Zim
2024-12-04 1:01 ` Cong Wang
2024-12-04 6:49 ` Levi Zim
2024-12-17 15:43 ` Björn Töpel
2024-12-19 9:17 ` Björn Töpel
2024-12-20 7:56 ` John Fastabend
2024-12-20 9:00 ` Levi Zim
2024-12-20 9:03 ` Björn Töpel
2024-12-20 16:56 ` John Fastabend
2024-12-02 23:04 ` Jakub Kicinski
2024-12-03 6:42 ` Levi Zim
2024-12-20 22: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=173473323379.3037384.4089610194127923528.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=devnull+rsworktech.outlook.com@kernel.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rsworktech@outlook.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