All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+57bcc752f0df8bb1365c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@redhat.com, dev.jain@arm.com,
	 jgg@ziepe.ca, jhubbard@nvidia.com, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
	peterx@redhat.com,  syzkaller-bugs@googlegroups.com,
	ziy@nvidia.com
Subject: Re: [syzbot] [mm?] WARNING in follow_page_pte
Date: Wed, 06 Aug 2025 04:21:01 -0700	[thread overview]
Message-ID: <68933a9d.a70a0220.7865.0004.GAE@google.com> (raw)
In-Reply-To: <68930511.050a0220.7f033.003a.GAE@google.com>

syzbot has bisected this issue to:

commit cac1db8c3aad97d6ffb56ced8868d6cbbbd2bfbe
Author: Dev Jain <dev.jain@arm.com>
Date:   Fri Jul 18 09:02:43 2025 +0000

    mm: optimize mprotect() by PTE batching

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13c746a2580000
start commit:   7e161a991ea7 Merge tag 'i2c-for-6.17-rc1-part2' of git://g..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=102746a2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17c746a2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=75e522434dc68cb9
dashboard link: https://syzkaller.appspot.com/bug?extid=57bcc752f0df8bb1365c
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=126e85bc580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=161a22f0580000

Reported-by: syzbot+57bcc752f0df8bb1365c@syzkaller.appspotmail.com
Fixes: cac1db8c3aad ("mm: optimize mprotect() by PTE batching")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection


      parent reply	other threads:[~2025-08-06 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06  7:32 [syzbot] [mm?] WARNING in follow_page_pte syzbot
2025-08-06  7:55 ` David Hildenbrand
2025-08-06  8:01   ` David Hildenbrand
2025-08-06 11:19 ` Dev Jain
2025-08-06 11:23   ` Dev Jain
2025-08-06 12:21   ` David Hildenbrand
2025-08-06 15:38   ` syzbot
2025-08-06 11:21 ` 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=68933a9d.a70a0220.7865.0004.GAE@google.com \
    --to=syzbot+57bcc752f0df8bb1365c@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=peterx@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=ziy@nvidia.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.