From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mfbaustx <mfbaustx@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [im]proper use of stack?
Date: Thu, 19 Oct 2006 23:22:43 +0100 [thread overview]
Message-ID: <1161296563.17335.153.camel@localhost.localdomain> (raw)
In-Reply-To: <op.thofmaaanwjy9v@titan.bintz-dev.net>
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.
prev parent reply other threads:[~2006-10-19 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 16:23 [im]proper use of stack? mfbaustx
2006-10-19 22:22 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1161296563.17335.153.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mfbaustx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox