From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+57adb2a4b9d206521bc2@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] general protection fault in hpage_collapse_scan_file
Date: Tue, 9 Apr 2024 16:46:27 -0700 [thread overview]
Message-ID: <20240409164627.b4803e09c81c01ccb6f55601@linux-foundation.org> (raw)
In-Reply-To: <0000000000009db84e0615a73698@google.com>
On Tue, 09 Apr 2024 03:16:20 -0700 syzbot <syzbot+57adb2a4b9d206521bc2@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8568bb2ccc27 Add linux-next specific files for 20240405
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=152f4805180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=48ca5acf8d2eb3bc
> dashboard link: https://syzkaller.appspot.com/bug?extid=57adb2a4b9d206521bc2
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1268258d180000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1256598d180000
Help. From a quick look this seems to be claiming that collapse_file()
got to
VM_BUG_ON_FOLIO(!folio_test_locked(folio), folio);
with folio==NULL, but the code look solid regarding this.
Given that we have a reproducer, can we expect the bot to perform a
bisection for us?
next prev parent reply other threads:[~2024-04-09 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 10:16 syzbot
2024-04-09 23:46 ` Andrew Morton [this message]
2024-04-10 0:32 ` Zach O'Keefe
2024-04-16 23:07 ` Zach O'Keefe
2024-04-17 18:56 ` Zach O'Keefe
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=20240409164627.b4803e09c81c01ccb6f55601@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+57adb2a4b9d206521bc2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox