From: syzbot <syzbot+0b56d6ed0d0c0c9a79dc@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
pasha.tatashin@soleen.com, peterx@redhat.com,
syzkaller-bugs@googlegroups.com, usama.anjum@collabora.com
Subject: Re: [syzbot] [mm?] WARNING in __page_table_check_ptes_set (2)
Date: Mon, 30 Sep 2024 07:33:02 -0700 [thread overview]
Message-ID: <66fab69e.050a0220.6bad9.003d.GAE@google.com> (raw)
In-Reply-To: <000000000000b7b11a061ab49122@google.com>
syzbot has bisected this issue to:
commit a1b92a3f14984c96ace381f204b5d72c0805296e
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date: Fri Feb 17 10:55:58 2023 +0000
mm/userfaultfd: support WP on multiple VMAs
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15d9cea9980000
start commit: 3efc57369a0c Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17d9cea9980000
console output: https://syzkaller.appspot.com/x/log.txt?x=13d9cea9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4fcb065287cdb84
dashboard link: https://syzkaller.appspot.com/bug?extid=0b56d6ed0d0c0c9a79dc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a7de80580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b67507980000
Reported-by: syzbot+0b56d6ed0d0c0c9a79dc@syzkaller.appspotmail.com
Fixes: a1b92a3f1498 ("mm/userfaultfd: support WP on multiple VMAs")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-09-30 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 17:18 [syzbot] [mm?] WARNING in __page_table_check_ptes_set (2) syzbot
2024-06-12 17:47 ` Andrew Morton
2024-06-12 18:17 ` Peter Xu
2024-06-12 19:30 ` Andrew Morton
2024-06-12 19:47 ` Peter Xu
2024-09-29 11:39 ` syzbot
2024-09-30 14:33 ` syzbot [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=66fab69e.050a0220.6bad9.003d.GAE@google.com \
--to=syzbot+0b56d6ed0d0c0c9a79dc@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=peterx@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=usama.anjum@collabora.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 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.