Messages in this thread | | | Date | Mon, 29 Apr 2013 19:54:38 +0400 | From | Glauber Costa <> | Subject | Re: [linux-next-20130422] Bug in SLAB? |
| |
On 04/29/2013 07:46 PM, Christoph Lameter wrote: > On Mon, 29 Apr 2013, Glauber Costa wrote: > >> On 04/29/2013 06:59 PM, Christoph Lameter wrote: >>> The code in kmalloc_index() creates a BUG() and preferentially should >>> create a compile time failure when a number that is too big is passed to it. >>> >>> What is MAX_ORDER on the architecture? >> >> Returning NULL is fine, but kmalloc_index currently does not check for >> MAX_ORDER at all. > > Could easily add that and BUG() on it? > We could, but now I am intrigued by the fact that the patch I sent does not fix Tetsuo's problem. 8M should be well within MAX_ORDER
| |