From: David Weinehall <tao@acc.umu.se>
To: Jeff Dike <jdike@karaya.com>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] big stack variables
Date: Sat, 17 Mar 2001 12:39:45 +0100 [thread overview]
Message-ID: <20010317123945.D1962@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.GSO.4.21.0103161154060.12618-100000@weyl.math.psu.edu> <200103170601.BAA05503@ccure.karaya.com>
In-Reply-To: <200103170601.BAA05503@ccure.karaya.com>; from jdike@karaya.com on Sat, Mar 17, 2001 at 01:01:22AM -0500
On Sat, Mar 17, 2001 at 01:01:22AM -0500, Jeff Dike wrote:
> viro@math.psu.edu said:
> > ObUML: something fishy happens in UML with multiple exec() in PID 1.
> > Try to say "telinit u" (or just boot with init=/bin/sh and say exec /
> > sbin/init) and you've got a nice panic()...
>
> ObFix: This is fixed in my current CVS. If you're not so desperate for the
> fix, then it will be in my 2.4.3 release. Basically, the problem was that it
> assumed that the only exec done by pid 1 was the kernel thread execing init,
> and things got exciting when that turned out not to be true.
ObUML (again): Any estimated time of submission to Linus?! Is this
an early v2.5-thing, or are the changes minor enough to the rest of the
tree to allow for an v2.4-merge?
/David
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
next prev parent reply other threads:[~2001-03-17 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 2:34 [CHECKER] big stack variables Dawson Engler
2001-03-16 2:56 ` Jeff Dike
2001-03-16 3:06 ` Andrew Morton
2001-03-16 7:19 ` Dawson Engler
2001-03-16 8:23 ` Andrew Morton
2001-03-16 17:57 ` Jeff Dike
2001-03-16 16:58 ` Alexander Viro
2001-03-16 19:37 ` Jeff Dike
2001-03-17 6:01 ` Jeff Dike
2001-03-17 11:39 ` David Weinehall [this message]
2001-03-18 17:41 ` Jeff Dike
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=20010317123945.D1962@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.