| 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: <20080610155055.GC4345@linux.vnet.ibm.com>
Date: Tue, 10 Jun 2008 21:20:55 +0530
From: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>, Oleg Nesterov <oleg@...sign.ru>
Cc: Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
lkml <linux-kernel@...r.kernel.org>
Subject: Question about task_struct::state
Hi Ingo, Oleg,
sched.h has a comment in task_struct
volatile long state; /* -1 unrunnable, 0 runnable, >0 stopped */
After some searching, I've not been able to figure out how state can
become -1 (or unrunnable). Can you let me know how that happens?
If it cannot reach that state, then maybe this patch is needed.
Signed-off-by: Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Index: linux-2.6/include/linux/sched.h
===================================================================
--- linux-2.6.orig/include/linux/sched.h 2008-06-10 21:13:02.000000000 +0530
+++ linux-2.6/include/linux/sched.h 2008-06-10 21:14:44.000000000 +0530
@@ -1024,7 +1024,7 @@ struct sched_rt_entity {
};
struct task_struct {
- volatile long state; /* -1 unrunnable, 0 runnable, >0 stopped */
+ volatile long state; /* 0 runnable, >0 stopped */
void *stack;
atomic_t usage;
unsigned int flags; /* per process flags, defined below */
--
regards,
Dhaval
--
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