[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190330190548.GG5935@zn.tnic>
Date: Sat, 30 Mar 2019 20:05:48 +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 11:07:40PM +0900, Tetsuo Handa wrote:
> I think that syzbot should for now refrain from testing syscalls that change
> scheduling related attributes,
And how would we know about problems there, otherwise?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists