public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Maitin-Shepard <jbms@cmu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move some more structures into "mostly_readonly"
Date: Tue, 07 Jun 2005 18:54:57 -0400	[thread overview]
Message-ID: <87hdg9eq0u.fsf@jbms.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.62.0506071519470.19659@ScMPusgw> (christoph@scalex86.org's message of "Tue, 7 Jun 2005 15:23:01 -0700 (PDT)")

christoph <christoph@scalex86.org> writes:

> On Tue, 7 Jun 2005, Brian Gerst wrote:
>> It doesn't really matter.  .rodata isn't actually mapped read-only. Doing so
>> would break up the large pages used to map the kernel.

> In that case.... here is a patch that moves the table into rodata.

AFS writes to the system call table.  If as Brian says, .rodata isn't
actually mapped read-only, then users of AFS could use this syscall
table patch without problems, but it is nonetheless pointless and
misleading.

-- 
Jeremy Maitin-Shepard

  reply	other threads:[~2005-06-07 22:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 18:30 [PATCH] Move some more structures into "mostly_readonly" christoph
2005-06-07 19:41 ` Christoph Hellwig
2005-06-07 19:59   ` christoph
2005-06-07 20:59     ` Arjan van de Ven
2005-06-07 21:31       ` Brian Gerst
2005-06-07 22:23         ` christoph
2005-06-07 22:54           ` Jeremy Maitin-Shepard [this message]
2005-06-08  6:29             ` Arjan van de Ven
2005-06-08 17:56               ` Jeremy Maitin-Shepard
2005-06-08 10:00         ` Jörn Engel
2005-06-08 10:07           ` Arjan van de Ven
2005-06-08 10:20             ` Jörn Engel
2005-06-08 10:35               ` Arjan van de Ven
2005-06-08 11:08                 ` Jörn Engel
2005-06-08 14:24         ` Arnd Bergmann
2005-06-08 12:16 ` Pavel Machek

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=87hdg9eq0u.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox