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]
Message-ID: <84144f020809040033h6872ecfdlfb7d7cdb57621b0d@mail.gmail.com>
Date:	Thu, 4 Sep 2008 10:33:54 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Steve VanDeBogart" <vandebo-lkml@...dbox.net>
Cc:	user-mode-linux-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	"Ingo Molnar" <mingo@...e.hu>, dkegel@...gle.com,
	jiayingz@...gle.com
Subject: Re: [uml-devel] [PATCH 5/6] slab: Annotate slab

Hi Steve,

On Wed, Sep 3, 2008 at 6:42 PM, Steve VanDeBogart
<vandebo-lkml@...dbox.net> wrote:
> But which bits of a slab object should be marked as initialized at
> kmem_cache_alloc() time?  We can't mark all of them as initialized
> because the constructor may not initialize all of them (in fact, I've
> programmatically confirmed that there are constructors that don't
> initialize all the bytes of an object).  The only place to get the
> information of interest is to mark all bytes uninitialized and then
> run the constructor on the memory region.

Aah, indeed. We should fix kmemcheck as well then.

                      Pekka
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ