Date: Sat, 9 Feb 2008 10:33:43 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Pekka Enberg <penberg@cs.helsinki.fi>,
       Richard Knutsson <ricknu-0@student.ltu.se>,
       Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1/2] kmemcheck v3
Message-ID: <20080209093343.GA23004@elte.hu>
References: <47AB79D4.2070605@gmail.com> <20080208115542.GD4745@one.firstfloor.org> <19f34abd0802080418o75969480v3286da7a83ebc178@mail.gmail.com> <20080208132032.GA6115@one.firstfloor.org> <19f34abd0802080459t4630c251q2a7cb3680e207e7a@mail.gmail.com> <20080208134823.GB6115@one.firstfloor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080208134823.GB6115@one.firstfloor.org>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1016
Lines: 23


* Andi Kleen <andi@firstfloor.org> wrote:

> > Yes, this is true. Then our task is to make sure that this memory is 
> > never allocated from tracked caches. We do have some changes in this 
> > area, for instance we never track task structs. Keep in mind that 
> > only slab objects are tracked currently, so things like stacks never 
> > catch page faults. I am not sure if this is exactly what you had in 
> > mind, but I don't know other kernel code very well enough to come up 
> > with perhaps more relevant examples :-)
> 
> Given that you don't seem to handle networking yet I wonder how many 
> cases you really tested so far.

you are wrong about no networking support: i have booted up a full 
distro config on real hardware with full networking, etc.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/