From: Kyle Moffett <mrmacman_g4@mac.com>
To: Albert Cahalan <acahalan@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: anon unions are cool
Date: Tue, 24 Jan 2006 01:04:16 -0500 [thread overview]
Message-ID: <55FF6D56-A5F8-47E8-89F7-E51BB22B22FF@mac.com> (raw)
In-Reply-To: <787b0d920601231939x1cf519e1x540316c06973de58@mail.gmail.com>
On Jan 23, 2006, at 22:39, Albert Cahalan wrote:
>> Then there is the other weird side where only the leaders of
>> thread groups are placed in sessions and process groups.
>
> That's not at all weird. It fits perfectly with the use of the tgid
> as the POSIX PID and the use of the "pid" (ugh) as the POSIX thread
> ID.
>
> Aside from POSIX just being arguably weird, the only weird things
> here are:
>
> 1. kill() not returning errno=ESRCH when it should
> 2. the name "pid" being used oddly in the kernel
And actually, my use of the task->pid member was correct. The "pid
virtualization" patches are virtualizing not only the process IDs,
but the thread IDs as well (the whole point is to provide completely
unique PID/TID spaces, so everything needs to be virtualized). In
any case, it was just a poorly chosen example (because that
particular virtualization bit was not necessary). I agree with you
that the kernel's behavior is weird, but it has its reasons and a lot
of history. If you think it's that important, a cleanup patch
(assuming it's not too intrusive) would probably be welcomed.
Cheers,
Kyle Moffett
--
I lost interest in "blade servers" when I found they didn't throw
knives at people who weren't supposed to be in your machine room.
-- Anthony de Boer
prev parent reply other threads:[~2006-01-24 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 0:36 Albert Cahalan
2006-01-23 0:56 ` Kyle Moffett
2006-01-23 1:17 ` Albert Cahalan
2006-01-23 18:25 ` Eric W. Biederman
2006-01-24 3:39 ` Albert Cahalan
2006-01-24 6:04 ` Kyle Moffett [this message]
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=55FF6D56-A5F8-47E8-89F7-E51BB22B22FF@mac.com \
--to=mrmacman_g4@mac.com \
--cc=acahalan@gmail.com \
--cc=ebiederm@xmission.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®