From: syzbot <syzbot+7d19c5fe6a3f1161abb7@syzkaller.appspotmail.com>
To: acme@kernel.org, adilger.kernel@dilger.ca, axboe@kernel.dk,
dvyukov@google.com, fweisbec@gmail.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.lei@redhat.com,
mingo@kernel.org, mingo@redhat.com,
penguin-kernel@i-love.sakura.ne.jp, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
tytso@mit.edu
Subject: Re: INFO: rcu detected stall in ext4_file_write_iter
Date: Fri, 11 Sep 2020 12:33:08 -0700 [thread overview]
Message-ID: <00000000000029b48f05af0ec14f@google.com> (raw)
In-Reply-To: <0000000000009a01370582c6772a@google.com>
syzbot suspects this issue was fixed by commit:
commit 7e24969022cbd61ddc586f14824fc205661bb124
Author: Ming Lei <ming.lei@redhat.com>
Date: Mon Aug 17 10:00:55 2020 +0000
block: allow for_each_bvec to support zero len bvec
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1120f201900000
start commit: 92ed3019 Linux 5.8-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=84f076779e989e69
dashboard link: https://syzkaller.appspot.com/bug?extid=7d19c5fe6a3f1161abb7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170f7cbc900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16a25e38900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: block: allow for_each_bvec to support zero len bvec
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-11 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000009a01370582c6772a@google.com>
2019-02-26 15:17 ` INFO: rcu detected stall in ext4_file_write_iter Theodore Y. Ts'o
2019-02-27 9:58 ` Dmitry Vyukov
2019-02-27 21:57 ` Theodore Y. Ts'o
2019-02-28 9:34 ` Dmitry Vyukov
2019-03-21 17:30 ` syzbot
2020-09-11 19:33 ` syzbot [this message]
2020-09-11 20:03 ` Jens Axboe
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=00000000000029b48f05af0ec14f@google.com \
--to=syzbot+7d19c5fe6a3f1161abb7@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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).