linux-kernel - Re: INFO: rcu detected stall in corrupted (3)

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: <20190330110933.GC5935@zn.tnic>
Date:   Sat, 30 Mar 2019 12:09:33 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        syzbot <syzbot+65cecdd27b726c261799@...kaller.appspotmail.com>,
        syzkaller-bugs@...glegroups.com, "H. Peter Anvin" <hpa@...or.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>, mingo@...hat.com,
        x86@...nel.org, Peter Zijlstra <peterz@...radead.org>,
        Juri Lelli <juri.lelli@...hat.com>
Subject: Re: INFO: rcu detected stall in corrupted (3)

On Sat, Mar 30, 2019 at 07:57:50PM +0900, Tetsuo Handa wrote:
> Yes. But what such threshold be? 0.1 second? 1 second? 10 seconds?
> Can we find a threshold where everyone can agree on?

This is what we do all day on lkml: discussing changes so that (almost)
everyone is happy with them.

:-)

-- 
Regards/Gruss,
    Boris.

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