> If "other means" means knowing that its located in a certain place on
> the stack, that's actually bogus. Any user space task started via exec
> from a kernel thread has extra junk on the kernel stack. Been there
> already. ;(
no, i've added it to the irq descriptor structure, where it can be
accessed in normal ways by the driver. [the stack position thing doesnt
fly with vm86 tasks either.]
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/