From: syzbot <syzbot+09b7d050e4806540153d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, andrii@kernel.org, ast@kernel.org,
eddyz87@gmail.com, hdanton@sina.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, shakeel.butt@linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio (4)
Date: Sun, 06 Apr 2025 16:09:02 -0700 [thread overview]
Message-ID: <67f3098e.050a0220.0a13.0276.GAE@google.com> (raw)
In-Reply-To: <67392d6d.050a0220.e1c64.000a.GAE@google.com>
syzbot has bisected this issue to:
commit ad41251c290dfe3c01472c94d2439a59de23fe97
Author: Andrii Nakryiko <andrii@kernel.org>
Date: Thu Aug 29 17:42:28 2024 +0000
lib/buildid: implement sleepable build_id_parse() API
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1601923f980000
start commit: a2cc6ff5ec8f Merge tag 'firewire-updates-6.15' of git://gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1501923f980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1101923f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6fe3b5e6a2cb1cc2
dashboard link: https://syzkaller.appspot.com/bug?extid=09b7d050e4806540153d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15743998580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10143404580000
Reported-by: syzbot+09b7d050e4806540153d@syzkaller.appspotmail.com
Fixes: ad41251c290d ("lib/buildid: implement sleepable build_id_parse() API")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-04-06 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 23:40 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio (4) syzbot
2024-11-17 0:18 ` Hillf Danton
2024-11-17 0:37 ` syzbot
2025-04-06 23:09 ` 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=67f3098e.050a0220.0a13.0276.GAE@google.com \
--to=syzbot+09b7d050e4806540153d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=eddyz87@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shakeel.butt@linux.dev \
--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 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.