From: Jeremy Maitin-Shepard <jbms@cmu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Read only syscall tables for x86_64 and i386
Date: Tue, 28 Jun 2005 15:52:50 -0400 [thread overview]
Message-ID: <87vf3y2qzz.fsf@jbms.ath.cx> (raw)
In-Reply-To: <20050628194215.GB32240@infradead.org> (Christoph Hellwig's message of "Tue, 28 Jun 2005 20:42:15 +0100")
Christoph Hellwig <hch@infradead.org> writes:
> On Tue, Jun 28, 2005 at 12:31:33PM -0700, Christoph Lameter wrote:
>> On Tue, 28 Jun 2005, Jeremy Maitin-Shepard wrote:
>>
>> > It would probably be better implemented with a more generic mechanism,
>> > but I don't believe anyone is working on that now, so it looks like AFS
>> > will continue to use a special syscall.
>>
>> We could put an #ifdef CONFIG_AFS into the syscall table definition?
>> That makes it explicit.
> No. AFS is utterly wrong, and the sooner we make it fail to work the
> better.
Heh, well that is nice, but breaking it will only mean that I and every
other AFS user will have to revert the patch that breaks it;
furthermore, many distributions that provide binary kernels will
probably also have to revert the patch because many of their users will
want to use AFS.
--
Jeremy Maitin-Shepard
next prev parent reply other threads:[~2005-06-28 19:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 18:47 [PATCH] Read only syscall tables for x86_64 and i386 Christoph Lameter
2005-06-28 18:56 ` Arjan van de Ven
2005-06-28 19:26 ` Christoph Lameter
2005-06-28 19:41 ` Christoph Hellwig
[not found] ` <87oe9q70no.fsf@jbms.ath.cx>
[not found] ` <Pine.LNX.4.62.0506281218030.1454@graphe.net>
2005-06-28 19:27 ` Jeremy Maitin-Shepard
2005-06-28 19:31 ` Christoph Lameter
2005-06-28 19:41 ` Jeremy Maitin-Shepard
2005-06-28 19:42 ` Christoph Hellwig
2005-06-28 19:52 ` Jeremy Maitin-Shepard [this message]
2005-06-28 20:11 ` Arjan van de Ven
2005-06-28 20:23 ` Jeremy Maitin-Shepard
2005-06-28 19:47 ` Arjan van de Ven
2005-06-28 20:00 ` Jeremy Maitin-Shepard
[not found] <Pine.LNX.4.62.0506281141050.959@graphe.net.suse.lists.linux.kernel>
2005-06-28 19:33 ` Andi Kleen
2005-06-28 19:41 ` Christoph Lameter
2005-06-29 0:06 ` Arnd Bergmann
2005-06-29 2:49 ` Andi Kleen
2005-07-01 20:10 ` Christoph Lameter
2005-07-01 20:28 ` Andi Kleen
2005-07-01 20:47 ` Richard B. Johnson
2005-07-01 21:13 ` Alan Cox
2005-07-01 20:34 ` Richard B. Johnson
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=87vf3y2qzz.fsf@jbms.ath.cx \
--to=jbms@cmu.edu \
--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 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.