From: William Lee Irwin III <wli@holomorphy.com>
To: Robert Picco <Robert.Picco@hp.com>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc4-mm1
Date: Tue, 10 Aug 2004 16:15:07 -0700 [thread overview]
Message-ID: <20040810231507.GF11200@holomorphy.com> (raw)
In-Reply-To: <41194EA5.80706@hp.com>
On Tue, Aug 10, 2004 at 06:39:33PM -0400, Robert Picco wrote:
> copy_thread expects a switch_stack below pt_regs on the stack. the
> switch_stack would have the parent's bspstore value for computing how
> much register backing store to copy into child. there isn't a
> switch_stack and the resultant bspstore size computed is enormous
> (depends on what there is on stack). i suspect printk has changed stack
> and the code layout changed too.
[...]
> * For SMP idle threads, fork_by_hand() calls do_fork with
> * NULL regs.
> */
> - if (!regs)
> + if (clone_flags & CLONE_IDLETASK)
> return 0;
> #endif
It may not be immediately obvious, but since all the checks for
CLONE_IDLETASK were ripped out in patches prior to this, respecting
CLONE_IDLETASK anywhere means that userspace can create idle threads(!).
So the alternative fixes I've been posting are very necessary.
-- wli
next prev parent reply other threads:[~2004-08-10 23:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 7:21 2.6.8-rc4-mm1 Andrew Morton
2004-08-10 15:09 ` 2.6.8-rc4-mm1 doesn't boot Adrian Bunk
2004-08-10 15:59 ` Bjorn Helgaas
2004-08-10 17:32 ` Adrian Bunk
2004-08-10 22:46 ` Bjorn Helgaas
2004-08-10 23:56 ` Adrian Bunk
2004-08-11 20:33 ` Bjorn Helgaas
2004-08-11 23:23 ` Adrian Bunk
2004-08-11 9:56 ` Alan Cox
2004-08-10 16:37 ` 2.6.8-rc4-mm1 Jesse Barnes
2004-08-10 21:20 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-10 22:39 ` 2.6.8-rc4-mm1 Robert Picco
2004-08-10 22:28 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-10 22:30 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-10 22:43 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-10 22:45 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-10 23:03 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-10 23:38 ` 2.6.8-rc4-mm1 William Lee Irwin III
2004-08-11 2:01 ` 2.6.8-rc4-mm1 Jesse Barnes
2004-08-10 23:15 ` William Lee Irwin III [this message]
2004-08-10 19:43 ` 2.6.8-rc4-mm1 (compile stats) John Cherry
2004-08-11 0:12 ` 2.6.8-rc4-mm1 Tom Vier
2004-08-11 11:35 ` [patch] 2.6.8-rc4-mm1: i2c-keywest.c compile error Adrian Bunk
2004-08-11 22:14 ` [patch] 2.6.8-rc4-mm1: NMI changes don't compile with SYSCTL=n Adrian Bunk
2004-08-11 22:18 ` 2.6.8-rc4-mm1: legacy_va_layout compile error " Adrian Bunk
2004-08-11 22:33 ` William Lee Irwin III
2004-08-11 22:42 ` William Lee Irwin III
2004-08-11 22:46 ` William Lee Irwin III
2004-08-11 23:02 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 18:38 2.6.8-rc4-mm1 Diffie
2004-08-11 3:33 2.6.8-rc4-mm1 Diffie
2004-08-11 15:36 ` 2.6.8-rc4-mm1 Randy.Dunlap
2004-08-11 22:57 ` 2.6.8-rc4-mm1 Bjorn Helgaas
2004-08-12 5:48 ` 2.6.8-rc4-mm1 Paul Blazejowski
2004-08-12 18:49 2.6.8-rc4-mm1 Paul Blazejowski
2004-08-12 23:21 ` 2.6.8-rc4-mm1 Bjorn Helgaas
2004-08-13 8:15 ` 2.6.8-rc4-mm1 Paul Blazejowski
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=20040810231507.GF11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Robert.Picco@hp.com \
--cc=akpm@osdl.org \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@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