lkml.org 
[lkml]   [2004]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kernel stack challenge
Thanks, Andi. That can be the case. Bad thing is that
stack size is hardcoded all over the kernel.

I wonder how it is possible to access task struct
having current stack pointer. %esp points at the
middle of the stack (when we are in the kernel) when
interrupt occures.

Serge.

--- Andi Kleen <ak@muc.de> wrote:
> Sergiy Lozovsky <serge_lozovsky@yahoo.com> 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
>


__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
-
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/

\
 
 \ /
  Last update: 2005-03-22 14:02    [W:0.033 / U:0.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site