[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200107131146.GX2827@hirez.programming.kicks-ass.net>
Date: Tue, 7 Jan 2020 14:11:46 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
syzbot <syzbot+bcad772bbc241b4c6147@...kaller.appspotmail.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Ingo Molnar <mingo@...hat.com>,
James Morris <jmorris@...ei.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: INFO: rcu detected stall in sys_sendfile64
On Tue, Jan 07, 2020 at 02:02:47PM +0100, Dmitry Vyukov wrote:
> > >> This is not a LSM problem, for the reproducer is calling
> > >> sched_setattr(SCHED_DEADLINE) with very large values.
> > >>
> > >> sched_setattr(0, {size=0, sched_policy=0x6 /* SCHED_??? */, sched_flags=0, sched_nice=0, sched_priority=0, sched_runtime=2251799813724439, sched_deadline=4611686018427453437, sched_period=0}, 0) = 0
> > >>
> > >> I think that this problem is nothing but an insane sched_setattr() parameter.
Argh, I had a patch for that somewhere. Let me go dig that out.
Powered by blists - more mailing lists