From: syzbot <syzbot+ccc0e1cfdb72b664f0d8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, broonie@kernel.org, hdanton@sina.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-usb@vger.kernel.org,
lorenzo.stoakes@oracle.com, pasha.tatashin@soleen.com,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
vbabka@suse.cz
Subject: Re: [syzbot] [mm?] kernel BUG in __page_table_check_zero (2)
Date: Wed, 11 Dec 2024 07:59:03 -0800 [thread overview]
Message-ID: <6759b6c7.050a0220.17f54a.003f.GAE@google.com> (raw)
In-Reply-To: <67230d7e.050a0220.529b6.0005.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 5de195060b2e251a835f622759550e6202167641
Author: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Date: Tue Oct 29 18:11:48 2024 +0000
mm: resolve faulty mmap_region() error path behaviour
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1507b8f8580000
start commit: 850925a8133c Merge tag '9p-for-6.12-rc5' of https://github..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=309bb816d40abc28
dashboard link: https://syzkaller.appspot.com/bug?extid=ccc0e1cfdb72b664f0d8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=158ab65f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=120e6a87980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm: resolve faulty mmap_region() error path behaviour
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-12-11 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 4:54 [syzbot] [mm?] kernel BUG in __page_table_check_zero (2) syzbot
2024-10-31 11:17 ` Hillf Danton
2024-10-31 16:16 ` syzbot
2024-11-05 4:00 ` Andrew Morton
2024-11-05 16:39 ` Alan Stern
2024-11-05 19:02 ` Andrew Morton
2024-11-05 20:42 ` Alan Stern
2024-11-05 21:30 ` Andrew Morton
2024-12-11 15:59 ` 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=6759b6c7.050a0220.17f54a.003f.GAE@google.com \
--to=syzbot+ccc0e1cfdb72b664f0d8@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=hdanton@sina.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pasha.tatashin@soleen.com \
--cc=stern@rowland.harvard.edu \
--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.