mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Arjan van de Ven <arjan@infradead.org>
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, 8 Jun 2005 13:08:44 +0200	[thread overview]
Message-ID: <20050608110844.GD331@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1118226933.5655.19.camel@laptopd505.fenrus.org>

On Wed, 8 June 2005 12:35:33 +0200, Arjan van de Ven wrote:
> 
> 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. 

Not really.  You want to catch the bad guy in the act.  A bit later
isn't much better than a lot later.

Lacking the mainframe key stores, I guess the best thing is to keep
.rodata under read-only tlbs.

Jörn

-- 
Sometimes, asking the right question is already the answer.
-- Unknown

  reply	other threads:[~2005-06-08 11:08 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
2005-06-08 11:08                 ` Jörn Engel [this message]
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=20050608110844.GD331@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=bgerst@didntduck.org \
    --cc=christoph@scalex86.org \
    --cc=hch@infradead.org \
    --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

Powered by JetHome