From: syzbot <syzbot+138c9e58e3cb22eae3b4@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, cmaiolino@redhat.com,
lczerner@redhat.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] general protection fault in ext4_fill_super
Date: Sat, 05 Feb 2022 14:39:06 -0800 [thread overview]
Message-ID: <000000000000fbf22d05d74d08fb@google.com> (raw)
In-Reply-To: <0000000000001e0ba105d5c2dede@google.com>
syzbot has bisected this issue to:
commit cebe85d570cf84804e848332d6721bc9e5300e07
Author: Lukas Czerner <lczerner@redhat.com>
Date: Wed Oct 27 14:18:56 2021 +0000
ext4: switch to the new mount api
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14902978700000
start commit: 0457e5153e0e Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16902978700000
console output: https://syzkaller.appspot.com/x/log.txt?x=12902978700000
kernel config: https://syzkaller.appspot.com/x/.config?x=cd57c0f940a9a1ec
dashboard link: https://syzkaller.appspot.com/bug?extid=138c9e58e3cb22eae3b4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f7004fb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=178cf108700000
Reported-by: syzbot+138c9e58e3cb22eae3b4@syzkaller.appspotmail.com
Fixes: cebe85d570cf ("ext4: switch to the new mount api")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-05 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 8:23 [syzbot] general protection fault in ext4_fill_super syzbot
2022-02-05 19:50 ` syzbot
2022-02-05 22:39 ` syzbot [this message]
2022-02-07 10:30 ` Lukas Czerner
2022-02-07 11:29 ` Dmitry Vyukov
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=000000000000fbf22d05d74d08fb@google.com \
--to=syzbot+138c9e58e3cb22eae3b4@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=cmaiolino@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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).