From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: syzbot <syzbot+f12658786a4153df5113@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, jannh@google.com,
kunwu.chan@gmail.com, kunwu.chan@linux.dev, liam@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lixinhai.lxh@gmail.com, pfalcato@suse.de, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com, vbabka@kernel.org
Subject: Re: [syzbot] [mm?] WARNING in vma_set_pgoff
Date: Thu, 3 Sep 2026 09:00:52 +0100 [thread overview]
Message-ID: <apkpGnijB9Wwj8BO@gremlin> (raw)
In-Reply-To: <6a992326.e7659fcc.146146.0005.GAE@google.com>
On Thu, Sep 03, 2026 at 12:35:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-by: syzbot+f12658786a4153df5113@syzkaller.appspotmail.com
> Tested-by: syzbot+f12658786a4153df5113@syzkaller.appspotmail.com
I suppose we can sling this on the patch Andrew? :)
I did mark the 2nd one dup I'm not sure why we're seeing another duplicate.
>
> Tested on:
>
> commit: 940de590 Merge tag 'hardening-v7.3-rc2' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=147d1f79580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=5e4e3a0e188a497e
> dashboard link: https://syzkaller.appspot.com/bug?extid=f12658786a4153df5113
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> userspace arch: i386
> patch: https://syzkaller.appspot.com/x/patch.diff?x=16b190f9580000
>
> Note: testing is done by a robot and is best-effort only.
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-03 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 22:52 [syzbot] [mm?] WARNING in vma_set_pgoff syzbot
2026-08-24 16:14 ` Lorenzo Stoakes (ARM)
2026-09-02 21:35 ` syzbot
2026-09-03 1:54 ` Andrew Morton
2026-09-03 7:35 ` syzbot
2026-09-03 8:00 ` 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=apkpGnijB9Wwj8BO@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=kunwu.chan@gmail.com \
--cc=kunwu.chan@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixinhai.lxh@gmail.com \
--cc=pfalcato@suse.de \
--cc=stable@vger.kernel.org \
--cc=syzbot+f12658786a4153df5113@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.