* Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote: > On Friday 20 June 2008 23:21:10 Ingo Molnar wrote: > > * Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote: [...] > > > (With the appropriate transformation of sched_setscheduler -> __) > > > > > > Better than scattering stray true/falses around the code. > > > > agreed - it would also be less intrusive on the API change side. > > Yes, here's the patch. I've put it in my tree for testing, too. > > sched_setscheduler_nocheck: add a flag to control access checks applied to tip/sched/new-API-sched_setscheduler, thanks Rusty. Also added it to auto-sched-next so that it shows up in linux-next. btw., had to merge this bit manually: > +/** > + * sched_setscheduler_nocheck - change the scheduling policy and/or RT priority of a thread > from kernelspace. > + * @p: the task in question. as it suffered from line-warp damage. Ingo -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
