* [patch 1/1] kernel/module.c use __set_current_state() instead of direct assigment
@ 2005-07-07 21:31 domen
0 siblings, 0 replies; only message in thread
From: domen @ 2005-07-07 21:31 UTC (permalink / raw)
To: rusty; +Cc: linux-kernel, Alejandro Andres, domen
[-- Attachment #1: set_current_state-kernel_module.c --]
[-- Type: text/plain, Size: 638 bytes --]
From: aLeJ <fuzzy.alej@gmail.com>
Use of __set_current_state() instead of direct assigment of
current->state.
Signed-off-by: Alejandro Andres <fuzzy.alej@gmail.com>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
module.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: quilt/kernel/module.c
===================================================================
--- quilt.orig/kernel/module.c
+++ quilt/kernel/module.c
@@ -556,7 +556,7 @@ static void wait_for_zero_refcount(struc
break;
schedule();
}
- current->state = TASK_RUNNING;
+ __set_current_state(TASK_RUNNING);
down(&module_mutex);
}
--
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-07-07 21:40 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-07-07 21:31 [patch 1/1] kernel/module.c use __set_current_state() instead of direct assigment domen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®