public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@osdl.org>,
	kuznet@ms2.inr.ac.ru, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Allow either tid or pid in SCM_CREDENTIALS struct ucred
Date: Fri, 22 Aug 2003 10:03:32 -0700	[thread overview]
Message-ID: <3F464CE4.8040704@redhat.com> (raw)
In-Reply-To: <1061451559.4386.13.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeremy Fitzhardinge wrote:

> This patch also makes it accept tgid in the SCM_CREDENTIALS pid field. 
> That is, a threaded program can either supply the ID of the whole
> process (tgid) or a particular thread (pid).  

I don't think ->pid should be tested.  Just replace it with ->tgid.
It's really not intended for the user to have any contact with the TID
(i.e., ->pid).  This is how it's done in other place.  What this shows
is that more searches for ->pid are needed which need to be replaced
with ->tgid.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/Rkzk2ijCOnn/RHQRAi7PAKCT+l2NCmoDzpHgq/yqFcqXmBArKQCgkxzW
wy2BYybK6yXrJRpNd6957tA=
=IW8f
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-08-22 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21  7:39 [PATCH] Allow either tid or pid in SCM_CREDENTIALS struct ucred Jeremy Fitzhardinge
2003-08-22 17:03 ` Ulrich Drepper [this message]
2003-08-22 18:02   ` Trond Myklebust

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=3F464CE4.8040704@redhat.com \
    --to=drepper@redhat.com \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --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