From: Hillf Danton <hdanton@sina.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: syzbot <syzbot+ebfd0e44b5c11034e1eb@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in mas_next_slot (2)
Date: Fri, 18 Jul 2025 07:42:11 +0800 [thread overview]
Message-ID: <20250717234212.2329-1-hdanton@sina.com> (raw)
In-Reply-To: <4c29e030-4ba8-48e3-96bb-015d43768db0@lucifer.local>
On Thu, 17 Jul 2025 17:06:34 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Top reply is not encouraged lad.
> OK on second thoughts, there is one additional thing we need to do on each
> loop to avoid observing the same VMA, either the prior logic of checking
> directly or a vma_next().
>
> So this may be a consequence of that.
>
> I will respin the series to make life easier...
>
Better after syzbot gives you Tested-by.
> On Thu, Jul 17, 2025 at 05:18:17AM +0100, Lorenzo Stoakes wrote:
> > This looks to be unrelated to my patch and some issue with syzbot (it's doing
> > weird injection stuff).
> >
> > As I said, I have tested the change with reproducer locally and it fixes the
> > issue, and I have been able to reliably observe that (note, without any of the
> > below stuff happening).
> >
> > Thanks
next prev parent reply other threads:[~2025-07-17 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 17:55 syzbot
2025-07-16 18:27 ` Lorenzo Stoakes
2025-07-16 18:32 ` Lorenzo Stoakes
2025-07-16 19:04 ` Lorenzo Stoakes
2025-07-16 19:38 ` Lorenzo Stoakes
2025-07-16 19:11 ` syzbot
2025-07-17 1:46 ` Hillf Danton
2025-07-17 3:55 ` syzbot
2025-07-17 4:18 ` Lorenzo Stoakes
2025-07-17 16:06 ` Lorenzo Stoakes
2025-07-17 23:42 ` Hillf Danton [this message]
2025-07-18 11:08 ` Lorenzo Stoakes
2025-07-18 12:56 ` Hillf Danton
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=20250717234212.2329-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=akpm@linux-foundation.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=syzbot+ebfd0e44b5c11034e1eb@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®