linux-kernel - Re: WARNING in rcu_check_gp_start

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20190223105638.GA27239@zn.tnic>
Date:   Sat, 23 Feb 2019 11:56:48 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     syzbot <syzbot+111bc509cd9740d7e4aa@...kaller.appspotmail.com>,
        "H. Peter Anvin" <hpa@...or.com>, konrad.wilk@...cle.com,
        Len Brown <len.brown@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>, puwen@...on.cn,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Thomas Gleixner <tglx@...utronix.de>, wang.yi59@....com.cn,
        the arch/x86 maintainers <x86@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: WARNING in rcu_check_gp_start_stall

On Sat, Feb 23, 2019 at 11:50:49AM +0100, Dmitry Vyukov wrote:
> Peter, what is the canonical location to reference for this issue
> (open bug or something)? When we get back to this report later, how
> does one know if this is fixed or not and what's the status?

bugzilla.kernel.org maybe?

> The C repro hanged the machine even faster, so it must be some other difference.
> I would expect compiler to not make difference. qemu, number of CPUs
> and maybe host kernel config (at least for interrupt granularity or
> something?) may be relevant.
> 
> But if you want to run syzkaller reproducer with syz-execprog, there
> is a docs link in the "syz repro" link.

Thanks.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.