From: syzbot <syzbot+18a5c5e8a9c856944876@syzkaller.appspotmail.com>
To: bfoster@redhat.com, djahchankoike@gmail.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] general protection fault in __copy_super
Date: Mon, 23 Sep 2024 23:55:04 -0700 [thread overview]
Message-ID: <66f26248.050a0220.3eed3.0023.GAE@google.com> (raw)
In-Reply-To: <66eea5a2.050a0220.3195df.004b.GAE@google.com>
syzbot has bisected this issue to:
commit 03ef80b469d5d83530ce1ce15be78a40e5300f9b
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Sep 23 22:41:51 2023 +0000
bcachefs: Ignore unknown mount options
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1057d107980000
start commit: f8eb5bd9a818 mm: fix build on 32-bit targets without MAX_P..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1257d107980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1457d107980000
kernel config: https://syzkaller.appspot.com/x/.config?x=74ffdb3b3fad1a43
dashboard link: https://syzkaller.appspot.com/bug?extid=18a5c5e8a9c856944876
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174cca27980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a3619f980000
Reported-by: syzbot+18a5c5e8a9c856944876@syzkaller.appspotmail.com
Fixes: 03ef80b469d5 ("bcachefs: Ignore unknown mount options")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-09-24 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 10:53 [syzbot] [bcachefs?] general protection fault in __copy_super syzbot
2024-09-24 6:55 ` 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=66f26248.050a0220.3eed3.0023.GAE@google.com \
--to=syzbot+18a5c5e8a9c856944876@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=djahchankoike@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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