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] [day] [month] [year] [list]

Message-ID: <20190401064208.GH29508@localhost.localdomain>
Date:   Mon, 1 Apr 2019 08:42:08 +0200
From:   Juri Lelli <juri.lelli@...hat.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        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>
Subject: Re: INFO: rcu detected stall in corrupted (3)

Hi,

On 30/03/19 12:09, Borislav Petkov wrote:
> 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.

Looks like this is the same problem we discussed a while ago [1], but
couldn't reach an agreement on what's best to do about it.

I'll need to go back and refresh memory.

Thanks,

- Juri

1 - https://lore.kernel.org/lkml/000000000000a4ee200578172fde@google.com/