| 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
| ||
|
Message-ID: <20150929152951.GQ3816@twins.programming.kicks-ass.net> Date: Tue, 29 Sep 2015 17:29:51 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: mingo@...nel.org, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, fweisbec@...il.com, oleg@...hat.com, umgwanakikbuti@...il.com, tglx@...utronix.de Subject: Re: [RFC][PATCH 05/11] sched: Add preempt argument to __schedule() On Tue, Sep 29, 2015 at 11:30:26AM -0400, Steven Rostedt wrote: > On Tue, 29 Sep 2015 11:28:39 -0400 > Steven Rostedt <rostedt@...dmis.org> wrote: > > > On Tue, 29 Sep 2015 11:28:30 +0200 > > Peter Zijlstra <peterz@...radead.org> wrote: > > > > > There is only a single PREEMPT_ACTIVE use in the regular __schedule() > > > path and that is to circumvent the task->state check. Since the code > > > setting PREEMPT_ACTIVE is the immediate caller of __schedule() we can > > > replace this with a function argument. > > > > > > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org> > > > --- > > > > Reviewed-by: Steven Rostedt <rostedt@...dmis.org> > > I just want to note that this scared me at first, because __schedule() > can be traced by the function tracer that can also do a See 11/11 :-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists