Re: kernel stack challenge

[Andi Kleen]

Sergiy Lozovsky <serge_lozovsky@xxxxxxxxx> writes:

> This function doesn't work in the kernel (system hungs
> instantly when my function is called). Does antbody
> have any idea what the reason can be? Some special
> alignment? Special memory segment? In what direction
> should I look?

The kernel puts some data about the current task at the bottom
of the stack and accesses that by referencing the stack pointer
in "current". This is even used by interrupts.

-Andi

-
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/