linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Victor Porton" <porton@ex-code.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New reliability technique
Date: Sat, 25 Feb 2006 14:27:20 +0100	[thread overview]
Message-ID: <9a8748490602250527l78e057ecvcd2e656b8ff5c9f2@mail.gmail.com> (raw)
In-Reply-To: <9a8748490602250526p2187e04ej9a680e6b2b948e7d@mail.gmail.com>

On 2/25/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 2/25/06, Victor Porton <porton@ex-code.com> wrote:
> > A minute ago I invented a new reliability enhancing technique.
> >
> > In idle cycles (or periodically in expense of some performance) Linux can
> > calculate MD5 or CRC sums of _unused_ (free) memory areas and compare these
> > sums with previously calculated sums.
> >
> > Additionally it can be done for allocated memory, if it will be write
> > protected before the first actual write. Moreover, all memory may be made
> > write-protected if it is not written e.g. more than a second. (When it
> > is written kernel would unlock it and allow to write, by a techniqie like
> > to how swap works.) If write-protected memory appears to be modified by
> > a check sum, this likewise indicates a bug.
> >
> > If a sum is inequal, it would notice a bug in kernel or in hardware.
> >
> > I suggest to add "Check free memory control sums" in config.
> >
>
> Implement it then and send a patch.
>

But, doesn't slab poisoning and the like already cover this ground somewhat?


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-02-25 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25 13:21 New reliability technique Victor Porton
2006-02-25 13:26 ` Jesper Juhl
2006-02-25 13:27   ` Jesper Juhl [this message]
2006-02-25 19:52     ` Avi Kivity
2006-02-25 19:56       ` Jesper Juhl
2006-02-25 22:44         ` Janos Farkas
2006-02-26 11:34       ` Victor Porton
2006-02-26 12:25         ` Pekka Enberg
2006-02-26 12:30           ` Nick Piggin

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=9a8748490602250527l78e057ecvcd2e656b8ff5c9f2@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=porton@ex-code.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).