From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan 9 (in)security
In-Reply-To: <20010526230234.611F9199EB@mail.cse.psu.edu>
Message-ID: <Pine.GSO.4.21.0105261906390.1945-100000@weyl.math.psu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Date: Sat, 26 May 2001 19:22:59 -0400
Topicbox-Message-UUID: a917e8e8-eac9-11e9-9e20-41e7f4b1d025



On Sat, 26 May 2001 jmk@plan9.bell-labs.com wrote:

> On Sat May 26 18:48:27 EDT 2001, viro@math.psu.edu wrote:
> ...
> > Furrfu... It's not like that was something new. malloc(foo*sizeof(bar))
> > can return non-NULL and allocate less than array of foo elements - just
> > have the product slightly above the UINT_MAX.
> > 
> 
> Furrfu?

Look at the context. Or rot13 if you are curious about etimology.

> UINT_MAX? What are those?
/sys/include/ape/limits.h:#define UINT_MAX   0xffffffffU

In other words, maximal possible value of unsigned int. Actually, ULONG_MAX
might be more accurate.