From: Harry Yoo <harry.yoo@oracle.com>
To: syzbot <syzbot+4d9a13f0797c46a29e42@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, jannh@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com, pfalcato@suse.de,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] WARNING in move_page_tables
Date: Wed, 13 Aug 2025 21:20:48 +0900 [thread overview]
Message-ID: <aJyDIAffgcMf6y0h@hyeyoo> (raw)
In-Reply-To: <689c1db2.a70a0220.7865.0047.GAE@google.com>
On Tue, Aug 12, 2025 at 10:08:02PM -0700, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-by: syzbot+4d9a13f0797c46a29e42@syzkaller.appspotmail.com
> Tested-by: syzbot+4d9a13f0797c46a29e42@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 0db9b72d mm/userfaultfd: fix kmap_local LIFO ordering ..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-hotfixes-unstable
> console output: https://syzkaller.appspot.com/x/log.txt?x=128fb5a2580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2323b2d6038203a5
> dashboard link: https://syzkaller.appspot.com/bug?extid=4d9a13f0797c46a29e42
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Note: no patches were applied.
> Note: testing is done by a robot and is best-effort only.
This looks spurious. I was able to reproduce it with the reproducer on
the same commit (the latest mm-hotfixes-unstable).
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2025-08-13 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 21:56 [syzbot] [mm?] WARNING in move_page_tables syzbot
2025-08-13 1:26 ` Hillf Danton
2025-08-13 1:49 ` syzbot
2025-08-13 2:19 ` Hillf Danton
2025-08-13 2:39 ` syzbot
2025-08-13 4:47 ` Lorenzo Stoakes
2025-08-13 5:08 ` syzbot
2025-08-13 12:20 ` Harry Yoo [this message]
2025-08-13 12:20 ` Harry Yoo
2025-08-18 12:54 ` David Hildenbrand
2025-08-18 12:56 ` syzbot
2025-08-18 13:01 ` David Hildenbrand
2025-08-18 13:22 ` syzbot
2025-08-13 13:14 ` Hillf Danton
2025-08-13 13:23 ` syzbot
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=aJyDIAffgcMf6y0h@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=syzbot+4d9a13f0797c46a29e42@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 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.