linux-kernel - Re: [PATCH 3/4] x86: corruption check: run the corruption checks from a work queue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 5 Oct 2008 21:35:57 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Arjan van de Ven" <arjan@...radead.org>
Cc:	mingo@...e.hu, "Jeremy Fitzhardinge" <jeremy@...p.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] x86: corruption check: run the corruption checks from a work queue

On Sun, Oct 5, 2008 at 9:09 PM, Arjan van de Ven <arjan@...radead.org> wrote:
>
> From: Arjan van de Ven <arjan@...ux.intel.com>
> Date: Mon, 22 Sep 2008 13:42:15 -0700
> Subject: [PATCH] x86: corruption check: run the corruption checks from a work queue
>
> the periodic corruption checks are better off run from a work queue; there's
> nothing time critical about them and this way the amount of
> interrupt-context work is reduced.
>
> Signed-off-by: Arjan van de Ven <arjan@...ux.intel.com>

Hi,

Did you figure out what's causing these corruptions yet?

Can't you do so by simply reserving the memory area in question,
clearing the present bit for those pages, and letting the page fault
handler catch whatever code is accessing it?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/