From: syzbot <syzbot+70ff52e51b7e7714db8a@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, boqun.feng@gmail.com, jack@suse.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, paulmck@kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: [syzbot] [ext4?] possible deadlock in dquot_commit (2)
Date: Wed, 14 Jun 2023 13:47:26 -0700 [thread overview]
Message-ID: <0000000000003656ed05fe1d0fa5@google.com> (raw)
In-Reply-To: <0000000000004f067905ea8ab9b2@google.com>
syzbot suspects this issue was fixed by commit:
commit f0f44752f5f61ee4e3bd88ae033fdb888320aafe
Author: Boqun Feng <boqun.feng@gmail.com>
Date: Fri Jan 13 06:59:54 2023 +0000
rcu: Annotate SRCU's update-side lockdep dependencies
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1355576f280000
start commit: ab072681eabe Merge tag 'irq_urgent_for_v6.2_rc6' of git://..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c8d5c2ee6c2bd4b8
dashboard link: https://syzkaller.appspot.com/bug?extid=70ff52e51b7e7714db8a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11436221480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15133749480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: rcu: Annotate SRCU's update-side lockdep dependencies
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-06-14 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 19:13 [syzbot] possible deadlock in dquot_commit (2) syzbot
2022-10-10 22:21 ` syzbot
2023-06-14 20:47 ` 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=0000000000003656ed05fe1d0fa5@google.com \
--to=syzbot+70ff52e51b7e7714db8a@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=boqun.feng@gmail.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.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).