From: syzbot <syzbot+344aaa8697ebd232bfc8@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] [ext4?] WARNING in __ext4fs_dirhash
Date: Wed, 10 May 2023 23:15:26 -0700 [thread overview]
Message-ID: <0000000000001f3bf005fb64ea0a@google.com> (raw)
In-Reply-To: <0000000000009b5b5705fb5dfda0@google.com>
syzbot has bisected this issue to:
commit 08dd966cfd2bef467acd1835ae10c32356037bc3
Author: Theodore Ts'o <tytso@mit.edu>
Date: Sat May 6 15:59:13 2023 +0000
ext4: improve error handling from ext4_dirhash()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15ecb2fa280000
start commit: 578215f3e21c Add linux-next specific files for 20230510
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17ecb2fa280000
console output: https://syzkaller.appspot.com/x/log.txt?x=13ecb2fa280000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb5a64fc61c29c5f
dashboard link: https://syzkaller.appspot.com/bug?extid=344aaa8697ebd232bfc8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13b80e32280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=113f582a280000
Reported-by: syzbot+344aaa8697ebd232bfc8@syzkaller.appspotmail.com
Fixes: 08dd966cfd2b ("ext4: improve error handling from ext4_dirhash()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-05-11 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 21:59 [syzbot] [ext4?] WARNING in __ext4fs_dirhash syzbot
2023-05-10 23:42 ` syzbot
2023-05-11 6:15 ` syzbot [this message]
2023-05-12 16:18 ` Theodore Ts'o
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=0000000000001f3bf005fb64ea0a@google.com \
--to=syzbot+344aaa8697ebd232bfc8@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.