From: Ulrich Drepper <drepper@redhat.com>
To: miquels@cistron-office.nl (Miquel van Smoorenburg)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status
Date: 20 Aug 2001 12:15:50 -0700 [thread overview]
Message-ID: <m3snem8rvd.fsf@otr.mynet> (raw)
In-Reply-To: <E15Yrlh-0006JF-00@the-village.bc.nu> <26210000.998324773@baldur> <9lrn8s$t23$1@ncc1701.cistron.net>
In-Reply-To: miquels@cistron-office.nl's message of "Mon, 20 Aug 2001 19:09:16 +0000 (UTC)"
miquels@cistron-office.nl (Miquel van Smoorenburg) writes:
> Switching pid and tgid is something that the LinuxThreads library
> should probably do, but not the kernel. IMHO.
Not possible until the signal handling in the kernel is thread group
aware. Grab Linus' patch from ten months os so ago, fix it, and get
it into the kernel. Then we can rewrite the signal handling and make
getpid behave correctly.
Having said this, since this is a known deficiency no program should
use getpid for some critical unless it's absolutely necessary.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
next prev parent reply other threads:[~2001-08-20 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 15:39 [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status Dave McCracken
2001-08-20 16:19 ` Alan Cox
2001-08-20 16:26 ` Dave McCracken
2001-08-20 18:50 ` [PATCH] 2.4.9 Make thread group id visible in/proc/<pid>/status george anzinger
2001-08-20 18:59 ` Dave McCracken
2001-08-20 19:52 ` george anzinger
2001-08-20 20:03 ` Dave McCracken
2001-08-20 19:09 ` [PATCH] 2.4.9 Make thread group id visible in /proc/<pid>/status Miquel van Smoorenburg
2001-08-20 19:15 ` Ulrich Drepper [this message]
2001-08-20 19:30 ` Dave McCracken
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=m3snem8rvd.fsf@otr.mynet \
--to=drepper@redhat.com \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
/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