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,
syzbot+d61b595e9205573133b3@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Fix an incorrect verification success with movsx insn
Date: Mon, 07 Aug 2023 23:50:22 +0000 [thread overview]
Message-ID: <169145222232.5057.14232029916065724489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807175721.671696-1-yonghong.song@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 7 Aug 2023 10:57:21 -0700 you wrote:
> syzbot reports a verifier bug which triggers a runtime panic.
> The test bpf program is:
> 0: (62) *(u32 *)(r10 -8) = 553656332
> 1: (bf) r1 = (s16)r10
> 2: (07) r1 += -8
> 3: (b7) r2 = 3
> 4: (bd) if r2 <= r1 goto pc+0
> 5: (85) call bpf_trace_printk#-138320
> 6: (b7) r0 = 0
> 7: (95) exit
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Fix an incorrect verification success with movsx insn
https://git.kernel.org/bpf/bpf-next/c/db2baf82b098
- [bpf-next,2/2] selftests/bpf: Add a movsx selftest for sign-extension of R10
https://git.kernel.org/bpf/bpf-next/c/a5c0a42bd374
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:[~2023-08-07 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:57 [PATCH bpf-next 1/2] bpf: Fix an incorrect verification success with movsx insn Yonghong Song
2023-08-07 17:57 ` [PATCH bpf-next 2/2] selftests/bpf: Add a movsx selftest for sign-extension of R10 Yonghong Song
2023-08-07 18:26 ` [PATCH bpf-next 1/2] bpf: Fix an incorrect verification success with movsx insn Eduard Zingerman
2023-08-07 23:50 ` 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=169145222232.5057.14232029916065724489.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=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=syzbot+d61b595e9205573133b3@syzkaller.appspotmail.com \
--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