From: Yonghong Song <yonghong.song@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Kernel Team <kernel-team@fb.com>,
Martin KaFai Lau <martin.lau@kernel.org>,
Daniel Hodges <hodgesd@meta.com>
Subject: Re: [PATCH bpf 1/2] bpf: Fix a kernel verifier crash in stacksafe()
Date: Mon, 12 Aug 2024 11:26:27 -0700 [thread overview]
Message-ID: <a4af06f9-5ea7-4541-90fd-1241043d5659@linux.dev> (raw)
In-Reply-To: <CAADnVQJjY9NU7WBxUNqOnLEpm6KhgHL0M_YobQ=2ZjMUHq3_eA@mail.gmail.com>
On 8/12/24 10:50 AM, Alexei Starovoitov wrote:
> On Mon, Aug 12, 2024 at 10:47 AM Eduard Zingerman <eddyz87@gmail.com> wrote:
>> On Mon, 2024-08-12 at 10:44 -0700, Alexei Starovoitov wrote:
>>
>> [...]
>>
>>> Should we move the check up instead?
>>>
>>> if (i >= cur->allocated_stack)
>>> return false;
>>>
>>> Checking it twice looks odd.
>> A few checks before that, namely:
>>
>> if (!(old->stack[spi].spilled_ptr.live & REG_LIVE_READ)
>> && exact == NOT_EXACT) {
>> i += BPF_REG_SIZE - 1;
>> /* explored state didn't use this */
>> continue;
>> }
>>
>> if (old->stack[spi].slot_type[i % BPF_REG_SIZE] == STACK_INVALID)
>> continue;
>>
>> if (env->allow_uninit_stack &&
>> old->stack[spi].slot_type[i % BPF_REG_SIZE] == STACK_MISC)
>> continue;
>>
>> Should be done regardless cur->allocated_stack.
> Right, but then let's sink old->slot_type != cur->slot_type down?
We could do the following to avoid double comparison: diff --git
a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c index
df3be12096cf..1906798f1a3d 100644 --- a/kernel/bpf/verifier.c +++
b/kernel/bpf/verifier.c @@ -17338,10 +17338,13 @@ static bool
stacksafe(struct bpf_verifier_env *env, struct bpf_func_state *old, */
for (i = 0; i < old->allocated_stack; i++) { struct bpf_reg_state
*old_reg, *cur_reg; + bool cur_exceed_bound; spi = i / BPF_REG_SIZE; -
if (exact != NOT_EXACT && + cur_exceed_bound = i >=
cur->allocated_stack; + + if (exact != NOT_EXACT && !cur_exceed_bound &&
old->stack[spi].slot_type[i % BPF_REG_SIZE] !=
cur->stack[spi].slot_type[i % BPF_REG_SIZE]) return false; @@ -17363,7
+17366,7 @@ static bool stacksafe(struct bpf_verifier_env *env, struct
bpf_func_state *old, /* explored stack has more populated slots than
current stack * and these slots were used */ - if (i >=
cur->allocated_stack) + if (cur_exceed_bound) return false; /* 64-bit
scalar spill vs all slots MISC and vice versa. WDYT?
next prev parent reply other threads:[~2024-08-12 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 5:21 [PATCH bpf 1/2] bpf: Fix a kernel verifier crash in stacksafe() Yonghong Song
2024-08-12 5:21 ` [PATCH bpf 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix Yonghong Song
2024-08-12 15:07 ` Yonghong Song
2024-08-12 17:38 ` [PATCH bpf 1/2] bpf: Fix a kernel verifier crash in stacksafe() Eduard Zingerman
2024-08-12 17:44 ` Alexei Starovoitov
2024-08-12 17:47 ` Eduard Zingerman
2024-08-12 17:50 ` Alexei Starovoitov
2024-08-12 17:57 ` Eduard Zingerman
2024-08-12 19:29 ` Alexei Starovoitov
2024-08-12 19:43 ` Eduard Zingerman
2024-08-12 20:02 ` Yonghong Song
2024-08-12 18:26 ` Yonghong Song [this message]
2024-08-12 18:30 ` Eduard Zingerman
2024-08-12 18:36 ` Yonghong Song
2024-08-12 18:41 ` Eduard Zingerman
2024-08-12 19:21 ` Yonghong Song
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=a4af06f9-5ea7-4541-90fd-1241043d5659@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--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 \
/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