From: Andi Kleen <andi@firstfloor.org>
To: Alexander.Kleinsorge@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: new module to check constant memory for corruption
Date: Sat, 12 Apr 2014 20:00:30 -0700 [thread overview]
Message-ID: <87eh12hr1t.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <trinity-aef9715a-72d2-4824-a3d8-306d5850c633-1397352790457@3capp-gmx-bs18> (Alexander Kleinsorge's message of "Sun, 13 Apr 2014 03:33:10 +0200")
Alexander.Kleinsorge@gmx.de writes:
> ramcheck kernel module
> new module to check constant memory for corruption
>
> detect corruption of constant kernel memory (text and data) periodically.
> runtime costs about 1..2 ms per sec (about 10 mb with 5 mb/ms),
> which is distributed over 8 (BLOCKS) time partitions (less than half
> ms per sec).
> in case of checksum (xor) error, an kernel log is posted.
> manual trigger via /proc/ramcheck is possible.
> range: kallsyms_lookup_name("_text") .. kallsyms_lookup_name("__end_rodata")
Can you explain how this works? How does it handle legal writes?
If it just checks its own memory it could be done in user space.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-04-13 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 1:33 new module to check constant memory for corruption Alexander.Kleinsorge
2014-04-13 3:00 ` Andi Kleen [this message]
2014-04-13 10:14 ` Aw: " Alexander.Kleinsorge
2014-04-13 10:26 ` Richard Weinberger
[not found] ` <trinity-99a290b9-30fa-464e-b67b-b8555d48011b-1397406377024@3capp-gmx-bs45>
2014-04-13 16:43 ` Richard Weinberger
2014-04-14 14:14 ` Jiri Kosina
2014-04-13 17:20 ` Aw: Re: " Alexander.Kleinsorge
2014-04-13 15:55 ` Andi Kleen
2014-04-13 16:22 ` Aw: " Alexander.Kleinsorge
2014-04-14 8:03 ` Aw: " Alexander.Kleinsorge
2014-04-13 3:08 ` Valdis.Kletnieks
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=87eh12hr1t.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=Alexander.Kleinsorge@gmx.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