From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: copy_thread preserves kernel stack
Date: Thu, 03 Jul 2003 02:02:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105719797219701@msgid-missing> (raw)
The ia64 version of copy_thread() preserves the parent kernel stack
which takes stack space away from the child thread, increasing the risk
of stack overflow. The i386 version of copy_thread() creates a
pristine stack for the new thread.
ia64 has a comment "Note: if we get called through kernel_thread() then
the memory above "(highest addr)" is valid kernel stack memory that
needs to be copied as well". i386 kernel threads work fine without the
extra stack wastage, so there is no generic reason to save the parent
backtrace. Apart from unwind problems, I can see no reason for ia64 to
preserve the parent's task in kernel threads. Any objections to me
doing a patch that constructs an empty stack for ia64 kernel threads?
next reply other threads:[~2003-07-03 2:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 2:02 Keith Owens [this message]
2003-07-07 21:13 ` copy_thread preserves kernel stack David Mosberger
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=marc-linux-ia64-105719797219701@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.org \
/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