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: <77650d72-e2ec-e084-c929-210b16b8afb9@i-love.sakura.ne.jp>
Date:   Sat, 30 Mar 2019 19:57:50 +0900
From:   Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:     Borislav Petkov <bp@...en8.de>
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 2019/03/30 19:45, Borislav Petkov wrote:
> On Sat, Mar 30, 2019 at 07:40:11PM +0900, Tetsuo Handa wrote:
>> But how can the scheduler be aware of various watchdogs' thresholds?
> 
> I think what tglx means is sched_setattr() should be fixed to fail due
> to the bogus value.
> 

Yes. But what such threshold be? 0.1 second? 1 second? 10 seconds?
Can we find a threshold where everyone can agree on?