linux-kernel - Re: [PATCH 1/2] kmemcheck v3

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:	Thu, 7 Feb 2008 15:32:29 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Vegard Nossum <vegard.nossum@...il.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Andi Kleen <andi@...stfloor.org>,
	Richard Knutsson <ricknu-0@...dent.ltu.se>
Subject: Re: [PATCH 1/2] kmemcheck v3

On Fri, 8 Feb 2008, Vegard Nossum wrote:

> The tracking that kmemcheck does is actually a byte-for-byte tracking
> of whether memory has been initialized or not. Think of it as valgrind
> for the kernel. We do this by "hiding" pages (marking them non-present
> for for MMU) and taking the page faults, which effectively tells us
> what memory is being attempted to be read from or written to.

Ahh. Okay. But ZONE_DMA pages are exempt from that scheme? You know 
that ZONE_NORMAL pages can undergo dma?

> I chose to implement this in the slab layer because this is probably
> where most of the interesting allocations are coming from, and this
> gives us a better control over what most users/callers care about,
> namely the specific objects.

But the slab layer allocates pages < PAGE_SIZE. You need to take a fault 
right? So each object would need its own page?
--
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/