linux-kernel - [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-next>] [day] [month] [year] [list]

Message-ID: <op.thofmaaanwjy9v@titan.bintz-dev.net>
Date:	Thu, 19 Oct 2006 11:23:11 -0500
From:	mfbaustx <mfbaustx@...il.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [im]proper use of stack?

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?

Why use stack-based storage, you ask?  Let's pretend this is a  
high-frequency call and I don't want to incur the expense of kmalloc'ing  
and freeing on every call.  I know I have enough stack space, I just don't  
know if my stack is always available  :)

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