linux-kernel - Re: [im]proper use of stack?

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 19 Oct 2006 23:22:43 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	mfbaustx <mfbaustx@...il.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [im]proper use of stack?

Ar Iau, 2006-10-19 am 11:23 -0500, ysgrifennodd mfbaustx:
> So... I know that there is some small-ish amount of kernel stack space  
> available per-process, and the kernel uses this area when executing on a  
> process's behalf (system call, etc).  Let's say I allocate (via an  
> automatic/stack-based storage) some smallish structure which I want a  
> kernel thread to populate (or interrupt context... some context other than  
> my process's context).
> 
> If my process gets context swapped, is my kernel-based stack pointer  
> always valid?

Have a look how the kernel sleep/wakeup system work. We rely on the
property that the kernel stacks of tasks don't move nor do they get
swapped out.

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