From: syzbot <syzbot+10007d66ca02b08f0e60@syzkaller.appspotmail.com>
To: axboe@kernel.dk, dvyukov@google.com, jack@suse.cz,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: INFO: task hung in __get_super
Date: Thu, 16 May 2019 05:33:00 -0700 [thread overview]
Message-ID: <00000000000074f88405890077a3@google.com> (raw)
In-Reply-To: <20190516114817.GD13274@quack2.suse.cz>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+10007d66ca02b08f0e60@syzkaller.appspotmail.com
Tested on:
commit: e93c9c99 Linux 5.1
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git v5.1
kernel config: https://syzkaller.appspot.com/x/.config?x=5edd1df52e9bc982
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=135c5b02a00000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2019-05-16 12:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 17:08 INFO: task hung in __get_super syzbot
2018-06-19 11:44 ` Tetsuo Handa
2018-06-19 11:53 ` Dmitry Vyukov
2018-06-19 14:10 ` Tetsuo Handa
2018-06-19 14:15 ` Dmitry Vyukov
2018-06-20 1:15 ` Tetsuo Handa
2019-04-28 18:14 ` syzbot
2019-04-28 18:51 ` Al Viro
2019-04-29 1:38 ` Tetsuo Handa
2019-04-29 5:30 ` Dmitry Vyukov
2019-04-30 2:55 ` Jan Kara
2019-04-30 3:11 ` Al Viro
2019-04-30 13:07 ` Jan Kara
2019-04-30 13:18 ` Al Viro
2019-04-30 15:07 ` Jan Kara
2019-04-30 15:34 ` Tetsuo Handa
2019-05-03 10:29 ` Tetsuo Handa
2019-05-14 5:15 ` Tetsuo Handa
2019-05-15 1:02 ` Tetsuo Handa
2019-05-15 10:21 ` Jan Kara
2019-05-15 11:32 ` Tetsuo Handa
2019-05-15 13:07 ` Jan Kara
2019-05-16 11:48 ` Jan Kara
2019-05-16 12:17 ` Tetsuo Handa
2019-05-16 12:32 ` Jan Kara
2019-05-16 12:50 ` Tetsuo Handa
2019-05-16 12:33 ` syzbot [this message]
2019-05-15 11:59 ` 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=00000000000074f88405890077a3@google.com \
--to=syzbot+10007d66ca02b08f0e60@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).