From: Ulrich Drepper <drepper@redhat.com>
To: bmark@us.ibm.com
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: LinuxThreads future
Date: Sat, 22 Mar 2003 06:13:00 -0000 [thread overview]
Message-ID: <3E7BB4B2.3020707@redhat.com> (raw)
In-Reply-To: <OFE7202B82.38FB75F5-ON86256CF0.00511793-86256CF0.0051968F@us.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mark Brown wrote:
> While NPTL is
> the future, many users and developers have invested a lot of time
...and found no severe problem.
> and
> money making things that work with Linuxthreads, and will be depending
> on it for a while to come.
Nobody takes away existing binaries and the current sources.
There is hardly the possibility for security problems. No unchecked
arrays exist, no string operations happen etc. In the entire almost 8
years there hasn't been any such instance.
> but we should be
> honest and plan for the movement being slow, and not a light-switch.
I am honest which is why I say that I'll not work on that code again.
If it makes you happy I say that severe security problems willbe fixed
but only because I cannot imagine there being any such thing. I don't
want to weaken the wording more since then people will try to argue what
qualifies as severe. The current code is it, it's the best LT will be.
People areliving with it now. Code which exists today lives with it.
If new code shows problems the way out is to not use LT.
- --
- --------------. ,-. 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+e7S32ijCOnn/RHQRAq+vAJ4lnjNnT6m89ltFwYgOwkUGhQJNOgCfZiM7
T2Y4AVs4wDHws7r9p7r2xfo=
=MWke
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-03-22 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 9:49 Ulrich Drepper
2003-03-21 15:33 ` Mark Brown
2003-03-22 6:13 ` Ulrich Drepper [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=3E7BB4B2.3020707@redhat.com \
--to=drepper@redhat.com \
--cc=bmark@us.ibm.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).