From: syzbot <syzbot+cdcd444e4d3a256ada13@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, brauner@kernel.org, jack@suse.com,
jack@suse.cz, 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?] possible deadlock in quotactl_fd
Date: Tue, 15 Aug 2023 20:22:31 -0700 [thread overview]
Message-ID: <000000000000528ff0060301ce79@google.com> (raw)
In-Reply-To: <000000000000f1a9d205f909f327@google.com>
syzbot suspects this issue was fixed by commit:
commit 949f95ff39bf188e594e7ecd8e29b82eb108f5bf
Author: Jan Kara <jack@suse.cz>
Date: Tue Apr 11 12:10:19 2023 +0000
ext4: fix lockdep warning when enabling MMP
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13a06a65a80000
start commit: 1dc3731daf1f Merge tag 'for-6.4-rc1-tag' of git://git.kern..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8bc832f563d8bf38
dashboard link: https://syzkaller.appspot.com/bug?extid=cdcd444e4d3a256ada13
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12cc2a92280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dc5fa6280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ext4: fix lockdep warning when enabling MMP
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-08-16 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 6:53 [syzbot] [fs?] possible deadlock in quotactl_fd syzbot
2023-04-11 6:53 ` [syzbot] [fs?] possible deadlock in sys_quotactl_fd syzbot
2023-04-11 10:11 ` [syzbot] [fs?] possible deadlock in quotactl_fd Christian Brauner
2023-04-11 10:55 ` Jan Kara
2023-04-11 13:40 ` Christian Brauner
2023-04-11 14:01 ` Christian Brauner
2023-04-12 10:18 ` Jan Kara
2023-04-29 17:36 ` [syzbot] [ext4?] [fat?] possible deadlock in sys_quotactl_fd syzbot
2023-05-10 7:31 ` [syzbot] [ext4?] possible deadlock in quotactl_fd syzbot
2023-08-16 3:22 ` 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=000000000000528ff0060301ce79@google.com \
--to=syzbot+cdcd444e4d3a256ada13@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--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.