From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
eddyz87@gmail.com, hodgesd@meta.com
Subject: Re: [PATCH bpf v2 1/2] bpf: Fix a kernel verifier crash in stacksafe()
Date: Tue, 13 Aug 2024 01:30:35 +0000 [thread overview]
Message-ID: <172351263572.1185382.612297994358908116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240812214847.213612-1-yonghong.song@linux.dev>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 12 Aug 2024 14:48:47 -0700 you wrote:
> Daniel Hodges reported a kernel verifier crash when playing with sched-ext.
> The crash dump looks like below:
>
> [ 65.874474] BUG: kernel NULL pointer dereference, address: 0000000000000088
> [ 65.888406] #PF: supervisor read access in kernel mode
> [ 65.898682] #PF: error_code(0x0000) - not-present page
> [ 65.908957] PGD 0 P4D 0
> [ 65.914020] Oops: 0000 [#1] SMP
> [ 65.920300] CPU: 19 PID: 9364 Comm: scx_layered Kdump: loaded Tainted: G S E 6.9.5-g93cea04637ea-dirty #7
> [ 65.941874] Hardware name: Quanta Delta Lake MP 29F0EMA01D0/Delta Lake-Class1, BIOS F0E_3A19 04/27/2023
> [ 65.960664] RIP: 0010:states_equal+0x3ee/0x770
> [ 65.969559] Code: 33 85 ed 89 e8 41 0f 48 c7 83 e0 f8 89 e9 29 c1 48 63 c1 4c 89 e9 48 c1 e1 07 49 8d 14 08 0f
> b6 54 10 78 49 03 8a 58 05 00 00 <3a> 54 08 78 0f 85 60 03 00 00 49 c1 e5 07 43 8b 44 28 70 83 e0 03
> [ 66.007120] RSP: 0018:ffffc9000ebeb8b8 EFLAGS: 00010202
> [ 66.017570] RAX: 0000000000000000 RBX: ffff888149719680 RCX: 0000000000000010
> [ 66.031843] RDX: 0000000000000000 RSI: ffff88907f4e0c08 RDI: ffff8881572f0000
> [ 66.046115] RBP: 0000000000000000 R08: ffff8883d5014000 R09: ffffffff83065d50
> [ 66.060386] R10: ffff8881bf9a1800 R11: 0000000000000002 R12: 0000000000000000
> [ 66.074659] R13: 0000000000000000 R14: ffff888149719a40 R15: 0000000000000007
> [ 66.088932] FS: 00007f5d5da96800(0000) GS:ffff88907f4c0000(0000) knlGS:0000000000000000
> [ 66.105114] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 66.116606] CR2: 0000000000000088 CR3: 0000000388261001 CR4: 00000000007706f0
> [ 66.130873] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [ 66.145145] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [ 66.159416] PKRU: 55555554
> [ 66.164823] Call Trace:
> [ 66.169709] <TASK>
> [ 66.173906] ? __die_body+0x66/0xb0
> [ 66.180890] ? page_fault_oops+0x370/0x3d0
> [ 66.189082] ? console_unlock+0xb5/0x140
> [ 66.196926] ? exc_page_fault+0x4f/0xb0
> [ 66.204597] ? asm_exc_page_fault+0x22/0x30
> [ 66.212974] ? states_equal+0x3ee/0x770
> [ 66.220643] ? states_equal+0x529/0x770
> [ 66.228312] do_check+0x60f/0x5240
> [ 66.235114] do_check_common+0x388/0x840
> [ 66.242960] do_check_subprogs+0x101/0x150
> [ 66.251150] bpf_check+0x5d5/0x4b60
> [ 66.258134] ? __mod_memcg_state+0x79/0x110
> [ 66.266506] ? pcpu_alloc+0x892/0xba0
> [ 66.273829] bpf_prog_load+0x5bb/0x660
> [ 66.281324] ? bpf_prog_bind_map+0x1e1/0x290
> [ 66.289862] __sys_bpf+0x29d/0x3a0
> [ 66.296664] __x64_sys_bpf+0x18/0x20
> [ 66.303811] do_syscall_64+0x6a/0x140
> [ 66.311133] entry_SYSCALL_64_after_hwframe+0x4b/0x53
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: Fix a kernel verifier crash in stacksafe()
https://git.kernel.org/bpf/bpf/c/bed2eb964c70
- [bpf,v2,2/2] selftests/bpf: Add a test to verify previous stacksafe() fix
https://git.kernel.org/bpf/bpf/c/662c3e2db00f
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-08-13 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 21:48 [PATCH bpf v2 1/2] bpf: Fix a kernel verifier crash in stacksafe() Yonghong Song
2024-08-12 21:48 ` [PATCH bpf v2 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix Yonghong Song
2024-08-13 1:23 ` [PATCH bpf v2 1/2] bpf: Fix a kernel verifier crash in stacksafe() Alexei Starovoitov
2024-08-13 1: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=172351263572.1185382.612297994358908116.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hodgesd@meta.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=yonghong.song@linux.dev \
/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