From: syzbot <syzbot+5cfa9ffce7cc5744fe24@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, sandeen@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] general protection fault in hfs_mdb_commit
Date: Sat, 05 Oct 2024 03:51:01 -0700 [thread overview]
Message-ID: <67011a15.050a0220.49194.04bc.GAE@google.com> (raw)
In-Reply-To: <6700d799.050a0220.49194.04b3.GAE@google.com>
syzbot has bisected this issue to:
commit c87d1f1aa91c2e54234672c728e0e117d2bff756
Author: Eric Sandeen <sandeen@redhat.com>
Date: Mon Sep 16 17:26:21 2024 +0000
hfs: convert hfs to use the new mount api
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b2bbd0580000
start commit: c02d24a5af66 Add linux-next specific files for 20241003
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1472bbd0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1072bbd0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=94f9caf16c0af42d
dashboard link: https://syzkaller.appspot.com/bug?extid=5cfa9ffce7cc5744fe24
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114be307980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bef527980000
Reported-by: syzbot+5cfa9ffce7cc5744fe24@syzkaller.appspotmail.com
Fixes: c87d1f1aa91c ("hfs: convert hfs to use the new mount api")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-05 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 6:07 [syzbot] [hfs?] general protection fault in hfs_mdb_commit syzbot
2024-10-05 10:51 ` syzbot [this message]
2024-10-07 20:28 ` Eric Sandeen
2024-10-07 20:59 ` syzbot
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=67011a15.050a0220.49194.04bc.GAE@google.com \
--to=syzbot+5cfa9ffce7cc5744fe24@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).