From: syzbot <syzbot+7f4a6f7f7051474e40ad@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_move_extents
Date: Tue, 11 Jul 2023 08:19:33 -0700 [thread overview]
Message-ID: <000000000000552b56060037a019@google.com> (raw)
In-Reply-To: <000000000000e55d2005fd59d6c9@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=14abf682a80000
start commit: 3f01e9fed845 Merge tag 'linux-watchdog-6.5-rc2' of git://w..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16abf682a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=12abf682a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=150188feee7071a7
dashboard link: https://syzkaller.appspot.com/bug?extid=7f4a6f7f7051474e40ad
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d8f2b0a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1061e6b0a80000
Reported-by: syzbot+7f4a6f7f7051474e40ad@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
next prev parent reply other threads:[~2023-07-11 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 3:53 [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents syzbot
2023-06-11 2:02 ` syzbot
2023-07-11 15:19 ` syzbot [this message]
2024-07-03 7:48 ` [syzbot] syzbot
2024-10-17 23:58 ` [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents Boqun Feng
2024-10-18 0:57 ` syzbot
[not found] <CA+6bSaugC6skN9XBTqnfOZ4n8zep6+D44fwxYFE4Y0KbBREwSw@mail.gmail.com>
2024-07-03 8:50 ` 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=000000000000552b56060037a019@google.com \
--to=syzbot+7f4a6f7f7051474e40ad@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).