From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: setXid
Date: Mon, 20 Sep 2004 19:50:00 -0000 [thread overview]
Message-ID: <200409201950.i8KJoIJb015512@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Monday, 20 September 2004 12:29:28 -0700 <414F2F98.9020905@redhat.com>
> > I have never been in favor of a per-thread ID extension.
>
> They definitely want to preserve this and therefore any kernel solution
> is as nonatomic as the userlevel implementation. (not my analysis).
Like I said, they haven't been presented with an implementation yet. What
I would propose would allow such an extension and also implement correct
semantics when you are not using it. It's pointless to speculate about
what others would or wouldn't say in circumstances that don't exist yet.
> I think this is as good as we'll get it any time soon (or ever).
Assuming you are talking about the simulation of almost correct semantics,
that may be. My point about that was that we should make sure that people
are aware of the "almost" and what it means.
You did not respond at all to my objection to your glibc extension
functions. Please say something about how you intend these to be
acceptable features. As they stand, it's necessary for me to absolutely
refuse to cooperate with their inclusion in glibc, and warn people away
from using nscd as it is. Let's talk about what features we really do
want, and about getting them fully specified and securely implemented.
Thanks,
Roland
next prev parent reply other threads:[~2004-09-20 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 0:27 setXid Ulrich Drepper
2004-09-20 19:20 ` setXid Roland McGrath
2004-09-20 19:29 ` setXid Ulrich Drepper
2004-09-20 19:50 ` Roland McGrath [this message]
2004-09-20 20:19 ` setXid Ulrich Drepper
2004-09-20 20:26 ` setXid Roland McGrath
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=200409201950.i8KJoIJb015512@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).