From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: syzbot <syzbot+c6879dc677a017f0a21b@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, jannh@google.com, liam@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
pfalcato@suse.de, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in vma_add_pgoff
Date: Tue, 8 Sep 2026 11:24:37 +0100 [thread overview]
Message-ID: <ap_iJsK57kLOY-zb@gremlin> (raw)
In-Reply-To: <90cd8ace-b135-45d6-815b-bf7329cbfa4d@kernel.org>
On Tue, Sep 08, 2026 at 11:32:18AM +0200, Vlastimil Babka (SUSE) wrote:
> On 9/8/26 11:25, Lorenzo Stoakes (ARM) wrote:
> > On Mon, Sep 07, 2026 at 09:15:02PM -0700, syzbot wrote:
> >> Hello,
> >>
> >> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> >>
> >> Reported-by: syzbot+c6879dc677a017f0a21b@syzkaller.appspotmail.com
> >> Tested-by: syzbot+c6879dc677a017f0a21b@syzkaller.appspotmail.com
> >
> > Yup there we are :)
> >
> > Why is this constantly duplicating I wonder...
>
> Going back to the first mail:
>
> syzbot found the following issue on:
>
> HEAD commit: 5445d6419962 arm64: Don't read GMID_EL1 when MTE is disabled
> git tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
>
> We can see it's based from 7.3-rc1:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-kernelci
>
> And since the problem was introduced there, all kinds of development trees
> for 7.4 (or even pending hotfixes for 7.3) based on 7.3-rc1 will now have it.
Yeah but I marked this #syz dupe? I guess that's cleared maybe for a new job?
>
> I guess syzbot has to learn to recognize it's a known problem and ignore it,
> or have some repo of known important fixes merged after rc1 it applies on
> top of such development trees, as they generaly won't be rebased to later rcs.
Yeah, be nice if 'hey check this upstream commit does it fix it?' *syzbot
confirms yes* could -> mark reports redundant.
But maybe harder to actually do than that?
>
> >
> >>
> >> Tested on:
> >>
> >> commit: 35b0fb39 mm/mremap: reset unfaulted VMA page offset fo..
> >> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> >> console output: https://syzkaller.appspot.com/x/log.txt?x=15e13af9580000
> >> kernel config: https://syzkaller.appspot.com/x/.config?x=56ed23170c168d4c
> >> dashboard link: https://syzkaller.appspot.com/bug?extid=c6879dc677a017f0a21b
> >> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> >> userspace arch: arm64
> >>
> >> Note: no patches were applied.
> >> Note: testing is done by a robot and is best-effort only.
> >
> > --
> > Cheers, Lorenzo
>
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-08 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 1:21 [syzbot] [mm?] WARNING in vma_add_pgoff syzbot
2026-09-08 2:25 ` Andrew Morton
2026-09-08 4:15 ` syzbot
2026-09-08 9:25 ` Lorenzo Stoakes (ARM)
2026-09-08 9:32 ` Vlastimil Babka (SUSE)
2026-09-08 10:24 ` Lorenzo Stoakes (ARM) [this message]
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=ap_iJsK57kLOY-zb@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--cc=syzbot+c6879dc677a017f0a21b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.