All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Antill <jantill@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [patch] libselinux:  access per-thread proc pid attr nodes, unify code
Date: Sat, 12 Aug 2006 01:34:45 -0400	[thread overview]
Message-ID: <1155360886.2496.29.camel@code.and.org> (raw)
In-Reply-To: <1155324042.30078.100.camel@moss-spartans.epoch.ncsc.mil>

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

On Fri, 2006-08-11 at 15:20 -0400, Stephen Smalley wrote:
> Rework the libselinux functions that access /proc/pid/attr to access the
> per-thread nodes, and unify the code to simplify maintenance.

 The main glibc author has stated[1] that gettid() isn't a public
function because he reserves the right to not have the user space thread
tied to the kernel space thread, which would really confuse anyone using
these functions...

On Thu, 2006-06-08 at 09:02 -0700, Ulrich Drepper wrote:
>  And currently we use the same TID (for the kernel: the PID) for the
> lifetime of the thread.  But this could change at any time.  It's an
> implementation detail and if there are advantages to do some userlevel
> scheduling (i.e., swap the underlying process of two threads) I'll
> implement this and it'll break all code depending on the fixed
> relationship.
> 
> If they don't care and don't blame us they can use
> 
>   syscall (__NR_gettid)
> 
> after including <sys/syscall.h>.  But get it in writing that they
> won't put it in production code. 


[1] This is from a semi-private mail, so I can't provide a link ...
however I'm sure Ulrich will publicly state something resembling the
above if you ask him.

-- 
James Antill <jantill@redhat.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-08-12  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 19:20 [patch] libselinux: access per-thread proc pid attr nodes, unify code Stephen Smalley
2006-08-12  5:34 ` James Antill [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=1155360886.2496.29.camel@code.and.org \
    --to=jantill@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.