[PATCH] Remove set_fs() in stop_machine()

From: Brian Gerst
Date: Fri Jan 06 2006 - 18:34:39 EST


Call sched_setscheduler() directly instead.

Signed-off-by: Brian Gerst <bgerst@xxxxxxxxxxxxx>

---
commit f9ba016f085bd87e730790e76f03db87667dd407
tree 4f75884b818ac68b97fe2a737d339ed54a130b1f
parent 41297aae94d08bb3a4c8c1a777ce373b5b432141
author Brian Gerst <bgerst@xxxxxxxxxxxxx> Thu, 05 Jan 2006 19:17:25 -0500
committer Brian Gerst <bgerst@xxxxxxxxxxxxx> Fri, 06 Jan 2006 16:23:09 -0500

kernel/stop_machine.c | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/kernel/stop_machine.c b/kernel/stop_machine.c
index b3d4dc8..dcfb5d7 100644
--- a/kernel/stop_machine.c
+++ b/kernel/stop_machine.c
@@ -87,13 +87,9 @@ static int stop_machine(void)
{
int i, ret = 0;
struct sched_param param = { .sched_priority = MAX_RT_PRIO-1 };
- mm_segment_t old_fs = get_fs();

/* One high-prio thread per cpu. We'll do this one. */
- set_fs(KERNEL_DS);
- sys_sched_setscheduler(current->pid, SCHED_FIFO,
- (struct sched_param __user *)&param);
- set_fs(old_fs);
+ sched_setscheduler(current, SCHED_FIFO, &param);

atomic_set(&stopmachine_thread_ack, 0);
stopmachine_num_threads = 0;


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/