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
-
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
On Sun, Apr 13, 2014 at 12:14 PM, wrote:
> Hi Andi,
>
> the module considers only the adress range between:
> kallsyms_lookup_name("_text") .. kallsyms_lookup_name("__end_rodata").
> this range has a typical size of 10..20 mb (depending on kernel-version and
> arch).
> see files: linux-3.*\arch
4 matches
Mail list logo
