mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Ingo Molnar <mingo@elte.hu>,
	Richard Gooch <rgooch@ras.ucalgary.ca>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: MAX_PID changes in 2.5.31
Date: 22 Aug 2002 23:27:46 +0100	[thread overview]
Message-ID: <1030055266.3151.72.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020822221106.GB5471@win.tue.nl>

On Thu, 2002-08-22 at 23:11, Andries Brouwer wrote:
> Ha, Alan - I am a bit slow, and you are a bit brief, but let us see.
> 
> I interpreted your "throughout" as "also outside IPC", and hence asked
> for clarification. For the moment, let me assume that we are just talking
> about SYSV IPC. (You were not thinking about uids instead of pids?)

I don't think there are any other pid ones. I've no idea what libc4 used
but I don't think I actually care . 

On the kernel side I found a ushort pid in coda, but I can't actually
easily tell if thats a process id or a coda thingy. We have some other
sloppy pid users but they all appear to be int (eg vt_kern.h)


> Remains the question whether that is bad.
> With large pid_t, the four variables msg_lspid, msg_lrpid, shm_cpid,
> shm_lpid will be truncated.
> 
> Who uses these? Nobody, as far as I can see from a recent collection
> of RPMs.

I have to admit I've not looked. I know of one (older AberMUD) which did
it for security tricks but thats hardly relevant to this nor a reason to
worry.

Alan


  reply	other threads:[~2002-08-22 22:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 19:55 Ingo Molnar
2002-08-19 20:06 ` Linus Torvalds
2002-08-19 20:33   ` Ingo Molnar
2002-08-19 22:31 ` Richard Gooch
2002-08-19 22:34   ` Ingo Molnar
2002-08-19 22:36     ` Richard Gooch
2002-08-19 22:41       ` Robert Love
2002-08-19 22:44         ` Ingo Molnar
2002-08-19 22:47         ` Richard Gooch
2002-08-19 23:01           ` Ingo Molnar
2002-08-20 13:44           ` Thunder from the hill
2002-08-19 22:41       ` Ingo Molnar
2002-08-19 22:42         ` Richard Gooch
2002-08-19 22:46           ` Ingo Molnar
2002-08-19 22:51           ` H. Peter Anvin
2002-08-19 23:51             ` Alan Cox
2002-08-19 23:29     ` Alan Cox
2002-08-19 23:34       ` Ingo Molnar
2002-08-20  0:33       ` Andries Brouwer
2002-08-20  0:41         ` Alan Cox
2002-08-22 22:11           ` Andries Brouwer
2002-08-22 22:27             ` Alan Cox [this message]
2002-08-22 22:59               ` Jan Harkes

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=1030055266.3151.72.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rgooch@ras.ucalgary.ca \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®