Re: [PATCH bpf-next v7 4/9] bpf, x86: emit KASAN checks in x86 JITed programs
| Newsgroups | org.kernel.vger.linux-kselftest,org.kernel.vger.bpf,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <b2de3e4da41eccf60d05631644e3975af9a89584e96121f38fa9caac3ec76f2d@mail.kernel.org> |
> diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c > index 13ba3232993a..8134d028a2f2 100644 > --- a/arch/x86/net/bpf_jit_comp.c > +++ b/arch/x86/net/bpf_jit_comp.c > @@ -21,6 +21,17 @@ > #include <asm/unwind.h> > #include <asm/cfi.h> > > +#if IS_ENABLED(CONFIG_BPF_JIT_KASAN) > +void __asan_load1(void *p); > +void __asan_store1(void *p); > +void __asan_load2(void *p); > +void __asan_store2(void *p); > +void __asan_load4(void *p); > +void __asan_store4(void *p); > +void __asan_load8(void *p); > +void __asan_store8(void *p); > +#endif > + This isn't a bug, but these eight prototypes duplicate declarations from mm/kasan/kasan.h. Would it be worth exporting them from a shared header such as include/linux/kasan.h under CONFIG_KASAN_GENERIC so each JIT does not have to re-declare them? Also, this uses #if IS_ENABLED() while the matching guard in emit_kasan_check() uses #ifdef CONFIG_BPF_JIT_KASAN. [ ... ] --- AI reviewed your patch. Please fix the bug or email reply why it's not a bug. See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md CI run summary: https://github.com/kernel-patches/bpf/actions/runs/32534828209