From: syzbot <syzbot+dd3d9835055dacb66f35@syzkaller.appspotmail.com>
To: bfoster@redhat.com, cam.alvarez.i@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 bch2_checksum
Date: Fri, 19 Jul 2024 09:10:03 -0700 [thread overview]
Message-ID: <00000000000097148b061d9bed31@google.com> (raw)
In-Reply-To: <000000000000e4d9eb061d719657@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=118fe60d980000
start commit: 0434dbe32053 Merge tag 'linux_kselftest-next-6.11-rc1' of ..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=138fe60d980000
console output: https://syzkaller.appspot.com/x/log.txt?x=158fe60d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4b8bd5292e033239
dashboard link: https://syzkaller.appspot.com/bug?extid=dd3d9835055dacb66f35
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d9ccb5980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12633a79980000
Reported-by: syzbot+dd3d9835055dacb66f35@syzkaller.appspotmail.com
Fixes: 03ef80b469d5 ("bcachefs: Ignore unknown mount options")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-07-19 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 13:39 [syzbot] [bcachefs?] general protection fault in bch2_checksum syzbot
2024-07-17 20:43 ` [syzbot] [PATCH] Fix " syzbot
2024-07-19 16:10 ` syzbot [this message]
2024-11-28 22:59 ` [syzbot] syzbot
[not found] <20240717204111.1238897-1-cam.alvarez.i@gmail.com>
2024-07-17 21:50 ` [syzbot] [bcachefs?] general protection fault in bch2_checksum 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=00000000000097148b061d9bed31@google.com \
--to=syzbot+dd3d9835055dacb66f35@syzkaller.appspotmail.com \
--cc=bfoster@redhat.com \
--cc=cam.alvarez.i@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 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.