From: Arjan van de Ven <arjan@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Brian Gerst <bgerst@didntduck.org>,
christoph <christoph@scalex86.org>,
Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Move some more structures into "mostly_readonly"
Date: Wed, 08 Jun 2005 12:35:33 +0200 [thread overview]
Message-ID: <1118226933.5655.19.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050608102053.GC331@wohnheim.fh-wedel.de>
On Wed, 2005-06-08 at 12:20 +0200, Jörn Engel wrote:
> On Wed, 8 June 2005 12:07:25 +0200, Arjan van de Ven wrote:
> > On Wed, 2005-06-08 at 12:00 +0200, Jörn Engel wrote:
> > > On Tue, 7 June 2005 17:31:19 -0400, 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.
> > >
> > > Can you confirm that for every architecture? Or just i386?
> >
> > does it matter? it's supposed to be read only, only sometimes that's not
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > enforced unfortunately.
>
> I agree. What I don't agree with is "It doesn't really matter" - not
> after debugging the occasional memory corruptions.
I agree, and it would be very useful to have a debug option in the
kernel that say checksums rodata (and probably the kernel text which is
also read only) periodically and raises an alarm if the checksum
changes.
next prev parent reply other threads:[~2005-06-08 10:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 18:30 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
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 [this message]
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=1118226933.5655.19.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=bgerst@didntduck.org \
--cc=christoph@scalex86.org \
--cc=hch@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--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
all inboxes | Powered by JetHome®