From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
eddyz87@gmail.com, memxor@gmail.com, puranjay@kernel.org
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next] bpf: Fix arm64 KASAN false positive after bpf_throw
Date: Wed, 12 Aug 2026 16:16:11 -0700 [thread overview]
Message-ID: <fe199e37-5231-41c2-b80d-c60a6907612c@linux.dev> (raw)
In-Reply-To: <20260812-hello_world-v1-1-c3c2ddcb362d@meta.com>
On 8/12/26 7:47 AM, Mykyta Yatsenko wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> arm64 passes zero as the stack pointer while walking BPF frames, so
> bpf_throw() leaves stale KASAN stack poison after jumping to the
> exception callback.
>
> Use the frame pointer as the fallback stack watermark.
>
> Fixes: e74cb1b42213 ("arm64: stacktrace: Implement arch_bpf_stack_walk() for the BPF JIT")
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
Tested-by: Ihor Solodrai <ihor.solodrai@linux.dev>
https://github.com/kernel-patches/vmtest/actions/runs/31634900957/job/94290630981
> ---
> kernel/bpf/helpers.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c
> index 6388b6b23e49..bbad75895331 100644
> --- a/kernel/bpf/helpers.c
> +++ b/kernel/bpf/helpers.c
> @@ -3395,11 +3395,13 @@ __bpf_kfunc void bpf_throw(u64 cookie)
> WARN_ON_ONCE(!ctx.aux->exception_boundary);
> WARN_ON_ONCE(!ctx.bp);
> WARN_ON_ONCE(!ctx.cnt);
> - /* Prevent KASAN false positives for CONFIG_KASAN_STACK by unpoisoning
> + /*
> + * Prevent KASAN false positives for CONFIG_KASAN_STACK by unpoisoning
> * deeper stack depths than ctx.sp as we do not return from bpf_throw,
> - * which skips compiler generated instrumentation to do the same.
> + * which skips compiler generated instrumentation to do the same. Some
> + * architectures cannot recover sp while unwinding, so fall back to bp.
> */
> - kasan_unpoison_task_stack_below((void *)(long)ctx.sp);
> + kasan_unpoison_task_stack_below((void *)(long)(ctx.sp ?: ctx.bp));
> ctx.aux->bpf_exception_cb(cookie, ctx.sp + ctx.aux->stack_arg_sp_adjust, ctx.bp, 0, 0);
> WARN(1, "A call to BPF exception callback should never return\n");
> }
>
> ---
> base-commit: 53cc65185a51fa9dd288cd1137a21467eced2df4
> change-id: 20260812-hello_world-2b03ed2aa5b4
>
> Best regards,
> --
> Mykyta Yatsenko <yatsenko@meta.com>
>
prev parent reply other threads:[~2026-08-12 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 14:47 [PATCH bpf-next] bpf: Fix arm64 KASAN false positive after bpf_throw Mykyta Yatsenko
2026-08-12 23:16 ` Ihor Solodrai [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=fe199e37-5231-41c2-b80d-c60a6907612c@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=puranjay@kernel.org \
--cc=yatsenko@meta.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