Messages in this thread | | | Date | Thu, 11 Jul 2002 09:15:23 +0200 (CEST) | From | Ingo Molnar <> | Subject | Re: [patch] sched-2.5.24-D3, batch/idle priority scheduling, SCHED_BATCH |
| |
> > > And users of __KERNEL_SYSCALLS__ and kernel_thread() should not > > > have policy == SCHED_BATCH. > > well, there's one security consequence here - module loading > (request_module()), which spawns a kernel thread must not run as > SCHED_BATCH. I think the right solution for that path is to set the > policy to SCHED_OTHER upon entry, and restore it to the previous one > afterwards - this way the helper thread has SCHED_OTHER priority.
i've solved this problem by making kernel_thread() spawned threads drop back to SCHED_NORMAL:
http://redhat.com/~mingo/O(1)-scheduler/sched-2.5.25-A7
I believe this is the secure way of doing it - independently of SCHED_BATCH - a RT task should not spawn a RT kernel thread 'unwillingly'.
Ingo
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |