[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230929230549.45206-2-twuufnxlz@gmail.com>
Date: Sat, 30 Sep 2023 07:05:49 +0800
From: Edward AD <twuufnxlz@...il.com>
To: alexghiti@...osinc.com
Cc: alex@...ti.fr, aou@...s.berkeley.edu, conor@...nel.org,
gregkh@...uxfoundation.org, guoren@...nel.org,
jirislaby@...nel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-serial@...r.kernel.org,
liushixin2@...wei.com, palmer@...belt.com,
paul.walmsley@...ive.com,
syzbot+8d2757d62d403b2d9275@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com, twuufnxlz@...il.com
Subject: [PATCH] Test for riscv fixes
Hi Alexandre,
On Fri, 29 Sep 2023 10:25:59 +0200 Alexandre Ghiti <alexghiti@...osinc.com> 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
Powered by blists - more mailing lists