From: syzbot <syzbot+99043e2052d9c50c81fc@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, duyuyang@gmail.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] kernel BUG in mpage_prepare_extent_to_map
Date: Sat, 12 Jun 2021 20:32:06 -0700 [thread overview]
Message-ID: <00000000000093166f05c49d62ea@google.com> (raw)
In-Reply-To: <0000000000003853da05c39afd00@google.com>
syzbot has bisected this issue to:
commit 68e9dc29f8f42c79d2a3755223ed910ce36b4ae2
Author: Yuyang Du <duyuyang@gmail.com>
Date: Mon May 6 08:19:36 2019 +0000
locking/lockdep: Check redundant dependency only when CONFIG_LOCKDEP_SMALL
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f2bda8300000
start commit: ad347abe Merge tag 'trace-v5.13-rc5-2' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11f2bda8300000
console output: https://syzkaller.appspot.com/x/log.txt?x=16f2bda8300000
kernel config: https://syzkaller.appspot.com/x/.config?x=30f476588412c065
dashboard link: https://syzkaller.appspot.com/bug?extid=99043e2052d9c50c81fc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1204231fd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1324e4d0300000
Reported-by: syzbot+99043e2052d9c50c81fc@syzkaller.appspotmail.com
Fixes: 68e9dc29f8f4 ("locking/lockdep: Check redundant dependency only when CONFIG_LOCKDEP_SMALL")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-06-13 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 7:15 [syzbot] kernel BUG in mpage_prepare_extent_to_map syzbot
2021-06-12 21:55 ` syzbot
2021-06-13 3:32 ` 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=00000000000093166f05c49d62ea@google.com \
--to=syzbot+99043e2052d9c50c81fc@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=duyuyang@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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 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.