From: syzbot <syzbot+7d19c5fe6a3f1161abb7@syzkaller.appspotmail.com>
To: acme@kernel.org, adilger.kernel@dilger.ca, dvyukov@google.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: INFO: rcu detected stall in ext4_file_write_iter
Date: Thu, 21 Mar 2019 10:30:00 -0700 [thread overview]
Message-ID: <0000000000007ab8ab05849e1647@google.com> (raw)
In-Reply-To: <0000000000009a01370582c6772a@google.com>
Bisection is inconclusive: the bug happens on the oldest tested release.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b1becf200000
start commit: [unknown
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1471becf200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1071becf200000
dashboard link: https://syzkaller.appspot.com/bug?extid=7d19c5fe6a3f1161abb7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103908f8c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105e5cd0c00000
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-21 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 6:50 INFO: rcu detected stall in ext4_file_write_iter syzbot
2019-02-26 15:17 ` 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 [this message]
2020-09-11 19:33 ` syzbot
2020-09-11 20:03 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 8:20 Hao Sun
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=0000000000007ab8ab05849e1647@google.com \
--to=syzbot+7d19c5fe6a3f1161abb7@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=dvyukov@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 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.