From: syzbot <syzbot+a537ff48a9cb940d314c@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: locking bug in __ext4_ioctl
Date: Fri, 14 Jul 2023 07:07:36 -0700 [thread overview]
Message-ID: <000000000000878978060072f85a@google.com> (raw)
In-Reply-To: <0000000000001b4f6505fd59fb12@google.com>
syzbot has bisected this issue to:
commit aff3bea95388299eec63440389b4545c8041b357
Author: Theodore Ts'o <tytso@mit.edu>
Date: Wed May 24 03:49:51 2023 +0000
ext4: add lockdep annotations for i_data_sem for ea_inode's
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=121e2492a80000
start commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=111e2492a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=161e2492a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=12d3428a307a1111
dashboard link: https://syzkaller.appspot.com/bug?extid=a537ff48a9cb940d314c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1489ffb8a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=145c302ca80000
Reported-by: syzbot+a537ff48a9cb940d314c@syzkaller.appspotmail.com
Fixes: aff3bea95388 ("ext4: add lockdep annotations for i_data_sem for ea_inode's")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-07-14 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 4:03 [syzbot] [ext4?] WARNING: locking bug in __ext4_ioctl syzbot
2023-07-04 1:06 ` syzbot
2023-07-14 14:07 ` 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=000000000000878978060072f85a@google.com \
--to=syzbot+a537ff48a9cb940d314c@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 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).