Ok - I understand. My point was not to put the _stack_ at a constant
address, but to put _current_ on a constant address by having one
"kernel" page mapped differently in each task.
ummm...
int wait4(...)
{
struct wait_queue wait { current, NULL };
sleep_on(&wait);
}
It's the same exact problem. Some event happening in the context of
another task will want to wake up people on this wait queue, and
they'll see this "constant current" in there, which would cause the
waker to wake himself up, instead the sleeping task ;-)
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html