Hi Alexandre, On Fri, 29 Sep 2023 10:25:59 +0200 Alexandre Ghiti <alexghiti@xxxxxxxxxxxx> wrote: > I'm still not convinced this will fix the kasan out-of-bounds > accesses, the page can be valid but the read can happen at an offset > not initialized and trigger such errors right? I still think there is > something weird about the stack frame, as to me this should not happen > (but admittedly I don't know much about that). The added check can confirm that the physical page is invalid (whether it is a vmalloc allocated page or a slab allocated page), and exit the for loop when it is invalid. Perhaps we can trust the test results of syzbot. Thanks, edward
