From: Edward AD <twuufnxlz@gmail.com>
To: alexghiti@rivosinc.com
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, conor@kernel.org,
gregkh@linuxfoundation.org, guoren@kernel.org,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
liushixin2@huawei.com, palmer@dabbelt.com,
paul.walmsley@sifive.com,
syzbot+8d2757d62d403b2d9275@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, twuufnxlz@gmail.com
Subject: [PATCH] Test for riscv fixes
Date: Sat, 30 Sep 2023 07:05:49 +0800 [thread overview]
Message-ID: <20230929230549.45206-2-twuufnxlz@gmail.com> (raw)
In-Reply-To: <CAHVXubhG2c=ShFHF4hMMFm8=BYDTyDUduOizujbUWQBW+55wTw@mail.gmail.com>
Hi Alexandre,
On Fri, 29 Sep 2023 10:25:59 +0200 Alexandre Ghiti <alexghiti@rivosinc.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
next prev parent reply other threads:[~2023-09-29 23:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 16:36 [syzbot] [serial?] KASAN: stack-out-of-bounds Read in sched_show_task syzbot
2023-09-26 10:59 ` [PATCH] riscv: fix out of bounds in walk_stackframe Edward AD
2023-09-26 11:12 ` Conor Dooley
2023-09-26 11:43 ` Edward AD
2023-09-26 11:49 ` Greg KH
2023-09-28 8:02 ` Alexandre Ghiti
2023-09-28 8:15 ` Alexandre Ghiti
2023-09-28 23:12 ` Edward AD
2023-09-29 6:04 ` Greg KH
2023-09-29 23:05 ` [PATCH] Test for riscv fixes Edward AD
2023-09-30 6:13 ` Greg KH
2023-09-30 8:24 ` Conor Dooley
2023-10-02 10:20 ` Aleksandr Nogikh
2023-09-29 6:05 ` [PATCH] riscv: fix out of bounds in walk_stackframe Greg KH
2023-09-29 8:25 ` Alexandre Ghiti
2023-09-29 23:05 ` Edward AD [this message]
2023-10-02 7:13 ` [PATCH] Test for riscv fixes Alexandre Ghiti
2023-10-02 13:41 ` Mark Rutland
2023-10-06 11:38 ` Alexandre Ghiti
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=20230929230549.45206-2-twuufnxlz@gmail.com \
--to=twuufnxlz@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@kernel.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=liushixin2@huawei.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=syzbot+8d2757d62d403b2d9275@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).