On Sun, 13 Apr 2014, Richard Weinberger wrote:
> > Hi Richard,
> >
> > I updated my code and check for ftrace (cat /proc/sys/kernel/ftrace_enabled
> > > 0).
> > http://tauruz.homeip.net/ramcheck.tgz
> >
> > On a 24/7 server ftrace is not a common thing anyway.
>
> I disagree with you.
> perf,
linux-kernel@vger.kernel.org
Betreff: Re: new module to check constant memory for corruption
alexander.kleinso...@gmx.de writes:
> ramcheck kernel module
> new module to check constant memory for corruption
>
> detect corruption of constant kernel memory (text and data) periodically.
&
hat percent of single, double, triple, and
other error syndromes your xor detects (hint - what is the behavior of a
dead row or column of bits?).
Gesendet: Sonntag, 13. April 2014 um 12:26 Uhr
Von: "Richard Weinberger"
An: alexander.kleinso...@gmx.de
Cc: "Andi Kleen" , LKML
Betr
pril 2014 um 12:26 Uhr
> Von: "Richard Weinberger"
> An: alexander.kleinso...@gmx.de
> Cc: "Andi Kleen" , LKML
> Betreff: Re: Re: new module to check constant memory for corruption
> On Sun, Apr 13, 2014 at 12:14 PM, wrote:
>> Hi Andi,
>>
>>
-
Gesendet: Sonntag, 13. April 2014 um 17:55 Uhr
Von: "Andi Kleen"
An: alexander.kleinso...@gmx.de
Cc: "Andi Kleen" , linux-kernel@vger.kernel.org
Betreff: Re: Re: new module to check constant memory for corruption
> your question:
> your question: there are no writes in this write protected adress range (e.g.
> kernel code).
It's actually not true, Linux changes r/o code. But you could
handle that by hooking into the right places.
> my idea is to calculate a checksum (xor is fastest) over this range and check
> later (pe
ged.
> see source code download (5 KB): http://tauruz.homeip.net/ramcheck.tgz
> the code is working fine and the checksum is (as expected) constant (at least
> for many hours).
>
> regards, Alexander
>
>
> Gesendet: Sonntag, 13. April 2014 um 05:00 Uhr
> Von: "Andi
April 2014 um 05:00 Uhr
Von: "Andi Kleen"
An: alexander.kleinso...@gmx.de
Cc: linux-kernel@vger.kernel.org
Betreff: Re: new module to check constant memory for corruption
alexander.kleinso...@gmx.de writes:
> ramcheck kernel module
> new module to check constant memory for corruption
&
On Sun, 13 Apr 2014 03:33:10 +0200, alexander.kleinso...@gmx.de said:
> printk(KERN_EMERG MODNAME "error: const kernel memory is broken
> (%08lx != 0), please reboot!", g_SumLast);
Make a list of all the things that can dynamically modify kernel text while
it's running, starting wi
alexander.kleinso...@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) t
10 matches
Mail list logo
