From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+3155335ece2c94bead44@syzkaller.appspotmail.com>,
Jens Axboe <axboe@kernel.dk>, Jan Kara <jack@suse.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: INFO: rcu detected stall in sys_creat
Date: Sun, 20 Jan 2019 10:51:26 +0900 [thread overview]
Message-ID: <aa24ec86-a331-4da4-475f-eb8f487d31d4@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CACT4Y+YC-=7+1DYeWD=Z53Tr-KBLTo3LG61i_8-_h3MY36rquw@mail.gmail.com>
On 2019/01/20 4:00, Dmitry Vyukov wrote:
> "On Sun, Oct 21, 2018 at 7:15 PM syzbot
> <syzbot+3155335ece2c94bead44@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: 8c60c36d0b8c Add linux-next specific files for 20181019
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=160c9245400000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=8b6d7c4c81535e89
>> dashboard link: https://syzkaller.appspot.com/bug?extid=3155335ece2c94bead44
>> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>>
>> Unfortunately, I don't have any reproducer for this crash yet.
>
> +Tetsuo, Jan, Jens
>
> This is a stall, but it involves __getblk_gfp. Is it the same bug as
> "INFO: task hung in generic_file_write_iter":
> https://syzkaller.appspot.com/bug?id=8afdd02539e35fc02ac7699014bc54a87fdd8dc0
> which will be fixed with "blockdev: Fix livelocks on loop device".
>
> This bug also has 10 other duplicates:
> https://syzkaller.appspot.com/bug?extid=3155335ece2c94bead44
Yes, I think so.
#syz dup: INFO: task hung in generic_file_write_iter
prev parent reply other threads:[~2019-01-20 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 17:15 INFO: rcu detected stall in sys_creat syzbot
2019-01-19 19:00 ` Dmitry Vyukov
2019-01-20 1:51 ` Tetsuo Handa [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=aa24ec86-a331-4da4-475f-eb8f487d31d4@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3155335ece2c94bead44@syzkaller.appspotmail.com \
--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).