From: Ulrich Drepper <drepper@redhat.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Rik van Riel <riel@redhat.com>,
Jamie Lokier <jamie@shareable.org>, Andi Kleen <ak@suse.de>,
johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch
Date: Fri, 06 Feb 2004 01:23:23 -0800 [thread overview]
Message-ID: <40235D0B.5090008@redhat.com> (raw)
In-Reply-To: <20040206042815.GO31926@dualathlon.random>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrea Arcangeli wrote:
> I don't think I was arguing against it completely, exactly because I'm
> just saying it should be optional.
And the result is that the current fast syscall handling on x86-64 is
completely unacceptable. If it's not change security enhancements are
not possible since the libc has to hardcode the address.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAI10P2ijCOnn/RHQRAuegAKCtk8W1cXWKlTWkDrmfJfykzvqATQCfRX4Q
cUVAR4+yIue/MFRL2xNbwfQ=
=VHoF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-06 9:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1075344395.1592.87.camel@cog.beaverton.ibm.com.suse.lists.linux.kernel>
[not found] ` <401894DA.7000609@redhat.com.suse.lists.linux.kernel>
[not found] ` <20040201012803.GN26076@dualathlon.random.suse.lists.linux.kernel>
[not found] ` <401F251C.2090300@redhat.com.suse.lists.linux.kernel>
[not found] ` <20040203085224.GA15738@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20040203162515.GY26076@dualathlon.random.suse.lists.linux.kernel>
[not found] ` <20040203173716.GC17895@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20040203181001.GA26076@dualathlon.random.suse.lists.linux.kernel>
[not found] ` <20040203182310.GA18326@mail.shareable.org.suse.lists.linux.kernel>
2004-02-04 2:27 ` [RFC][PATCH] linux-2.6.2-rc2_vsyscall-gtod_B1.patch Andi Kleen
2004-02-04 2:40 ` Andrea Arcangeli
2004-02-04 4:21 ` Jamie Lokier
2004-02-05 21:43 ` Andrea Arcangeli
2004-02-06 4:15 ` Rik van Riel
2004-02-06 4:28 ` Andrea Arcangeli
2004-02-06 9:23 ` Ulrich Drepper [this message]
2004-02-06 15:49 ` Andrea Arcangeli
2004-02-07 0:37 ` Ulrich Drepper
2004-02-07 2:19 ` Andrea Arcangeli
2004-02-07 3:37 ` Daniel Jacobowitz
2004-02-07 4:36 ` Andrea Arcangeli
2004-02-07 4:53 ` Jamie Lokier
2004-01-29 2:46 john stultz
2004-01-29 5:06 ` Ulrich Drepper
2004-01-29 13:26 ` Jamie Lokier
2004-01-29 18:05 ` Ulrich Drepper
2004-01-29 19:15 ` Jamie Lokier
2004-01-29 23:59 ` john stultz
2004-01-30 0:40 ` Ulrich Drepper
2004-01-30 0:31 ` Ulrich Drepper
2004-01-30 4:17 ` Jamie Lokier
2004-01-30 5:09 ` Ulrich Drepper
2004-01-30 9:29 ` Ingo Molnar
2004-02-03 4:38 ` Ulrich Drepper
2004-01-30 17:34 ` Jamie Lokier
2004-01-30 8:33 ` Jakub Jelinek
2004-01-30 17:21 ` Jamie Lokier
2004-01-31 0:10 ` Eric W. Biederman
2004-01-31 2:41 ` Jamie Lokier
2004-01-31 5:54 ` Eric W. Biederman
2004-02-01 1:28 ` Andrea Arcangeli
2004-02-03 4:35 ` Ulrich Drepper
2004-02-03 5:34 ` Andrea Arcangeli
2004-02-03 8:52 ` Jamie Lokier
2004-02-03 16:25 ` Andrea Arcangeli
2004-02-03 17:37 ` Jamie Lokier
2004-02-03 18:10 ` Andrea Arcangeli
2004-02-03 18:23 ` Jamie Lokier
2004-02-03 18:34 ` Andrea Arcangeli
2004-01-31 0:17 ` Eric W. Biederman
2004-01-31 2:20 ` john stultz
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=40235D0B.5090008@redhat.com \
--to=drepper@redhat.com \
--cc=ak@suse.de \
--cc=andrea@suse.de \
--cc=jamie@shareable.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@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 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.