linux-kernel - Re: INFO: rcu detected stall in sys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aa24ec86-a331-4da4-475f-eb8f487d31d4@i-love.sakura.ne.jp>
Date:   Sun, 20 Jan 2019 10:51:26 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:     Dmitry Vyukov <dvyukov@...gle.com>,
        syzbot <syzbot+3155335ece2c94bead44@...kaller.appspotmail.com>,
        Jens Axboe <axboe@...nel.dk>, Jan Kara <jack@...e.com>
Cc:     linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Al Viro <viro@...iv.linux.org.uk>
Subject: Re: INFO: rcu detected stall in sys_creat

On 2019/01/20 4:00, Dmitry Vyukov wrote:
> "On Sun, Oct 21, 2018 at 7:15 PM syzbot
> <syzbot+3155335ece2c94bead44@...kaller.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