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: <Pine.LNX.4.64.0706012057580.11358@schroedinger.engr.sgi.com>
Date:	Fri, 1 Jun 2007 21:01:09 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	jeremy@...p.org
Subject: Re: SLUB: Return ZERO_SIZE_PTR for kmalloc(0)

On Fri, 1 Jun 2007, Andrew Morton wrote:

> > On Fri, 1 Jun 2007 18:37:46 -0700 (PDT) Christoph Lameter <clameter@....com> wrote:
> >
> > +#define ZERO_SIZE_PTR ((void *)16)
> 
> Jeremy's point was a good one.  The kernel _does_ use address-comparison
> to determine object-inequality in an unknown but non-zero number of places.
> 
> It is of course unlikely that this will occur in conjunction with zero-sized
> objects, but who knows?

The zero sized objects are always the same and have the same content of 
nothingness. So the kernel would find that they are the same which they 
indeed are. Why could this be a problem?
-
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