[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120425.183121.1283820821646106475.davem@davemloft.net>
Date: Wed, 25 Apr 2012 18:31:21 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: hpa@...ux.intel.com
Cc: tj@...nel.org, htmldeveloper@...il.com,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
mingo@...e.hu, linux-mm@...ck.org
Subject: Re: [BUG]memblock: fix overflow of array index
From: "H. Peter Anvin" <hpa@...ux.intel.com>
Date: Wed, 25 Apr 2012 15:29:31 -0700
> On 04/25/2012 03:28 PM, Tejun Heo wrote:
>>
>> All indexes in memblock are integers. Changing that particular one to
>> unsigned int doesn't fix anything. I think it just makes things more
>> confusing. If there ever are cases w/ more then 2G memblocks, we're
>> going for 64bit not unsigned.
>>
>
> I would expect there to be plenty of memblocks larger than 2G?
Yes, but not the array indexes into those memblock entries, which is
what this patch is about.
--
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