From: Dan Aloni <da-x@gmx.net>
To: dank@kegel.com
Cc: linux-kernel@vger.kernel.org
Subject: 32-bit process ids (was: Re: idea to enhance get_pid())
Date: 20 Apr 2002 22:12:14 +0300 [thread overview]
Message-ID: <1019329937.24728.111.camel@callisto.yi.org> (raw)
In-Reply-To: <3CC1AA5C.1DE5C69D@kegel.com>
On Sat, 2002-04-20 at 20:50, Dan Kegel wrote:
> I'd like to know more about that bash bug; do you have a URL for it?
> (Is there even a bug tracking system for bash?)
> I looked a bit on gnu.bash.bugs, and found two possibly related
> patches; do these have anything to do with the bug?
> http://groups.google.com/groups?selm=200104130734.AAA12931%40shade.twinsun.com
> http://groups.google.com/groups?selm=200104130854.BAA18368%40shade.twinsun.com
In a post by Linus from 2 years ago, concerning the bash bug
( http://lwn.net/2000/0120/a/lt-pid.html ), he also writes about
what holds from switching to 32 bit pids. and it's mainly
because it's unclear about the way pids should be handled in
a clustering environment.
According to the kernel patch made by the people at Cluster
Infrastructure ( http://ci-linux.sourceforge.net/ ), today
it is clear that the upper 16 bits of the pid are used for the node
number.
Linus should consider applying Andries Brouwer's patch from October:
( http://marc.theaimsgroup.com/?l=linux-kernel&m=100274734125520&w=2 )
This is really 2.5 material, but it slipped away for no apparent reason.
next prev parent reply other threads:[~2002-04-20 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 17:50 idea to enhance get_pid() Dan Kegel
2002-04-20 19:12 ` Dan Aloni [this message]
2002-04-20 20:00 ` 32-bit process ids (was: Re: idea to enhance get_pid()) Eric Brunner-Williams in Portland Maine
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=1019329937.24728.111.camel@callisto.yi.org \
--to=da-x@gmx.net \
--cc=dank@kegel.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
all inboxes | Powered by JetHome®