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
| ||
|
Message-ID: <9b7f3efc-cfde-df21-1071-a566c970f81e@I-love.SAKURA.ne.jp> Date: Sun, 22 Apr 2018 11:04:49 +0900 From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> To: syzbot <syzbot+108696293d7a21ab688f@...kaller.appspotmail.com>, dvyukov@...gle.com, gregkh@...uxfoundation.org, syzkaller-bugs@...glegroups.com Cc: akpm@...ux-foundation.org, aryabinin@...tuozzo.com, linux-kernel@...r.kernel.org, tchibo@...gle.com, tglx@...utronix.de Subject: Re: INFO: rcu detected stall in __process_echoes On 2018/03/28 16:01, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 3eb2ce825ea1ad89d20f7a3b5780df850e4be274 (Sun Mar 25 22:44:30 2018 +0000) > Linux 4.16-rc7 > syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=108696293d7a21ab688f > > So far this crash happened 10 times on upstream. > C reproducer: https://syzkaller.appspot.com/x/repro.c?id=4941573204738048 > syzkaller reproducer: https://syzkaller.appspot.com/x/repro.syz?id=5314352743710720 > Raw console output: https://syzkaller.appspot.com/x/log.txt?id=5561943247028224 > Kernel config: https://syzkaller.appspot.com/x/.config?id=-8440362230543204781 > compiler: gcc (GCC) 7.1.1 20170620 Reproducer and result are essentially same with another report. Thus, #syz dup: INFO: rcu detected stall in n_tty_receive_char_special
Powered by blists - more mailing lists