From: syzbot <syzbot+a3c8e9ac9f9d77240afd@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: Mon, 05 Jun 2023 05:15:28 -0700 [thread overview]
Message-ID: <000000000000b763f505fd60db7a@google.com> (raw)
In-Reply-To: <000000000000d1149605fd5b0c0d@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=11bdb895280000
start commit: 9561de3a55be Linux 6.4-rc5
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13bdb895280000
console output: https://syzkaller.appspot.com/x/log.txt?x=15bdb895280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7474de833c217bf4
dashboard link: https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ff6e93280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11824101280000
Reported-by: syzbot+a3c8e9ac9f9d77240afd@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-06-05 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 5:19 [syzbot] [ext4?] WARNING: locking bug in ext4_ioctl syzbot
2023-06-05 6:29 ` syzbot
2023-06-05 12:15 ` syzbot [this message]
2025-01-07 7:48 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-09-27 16:51 [PATCH] ext4: " Remington Brasga
2024-09-27 18:59 ` [syzbot] [ext4?] " 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=000000000000b763f505fd60db7a@google.com \
--to=syzbot+a3c8e9ac9f9d77240afd@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.