On 03/05/2010 03:08 PM, Tejun Heo wrote: > Hmmm... this means that on one of the chunks, chunk->list.next was > NULL (BTW, the disassembly is from unlinked object, right?). The main > allocation code hasn't seen much change lately. The only changes are, > > 22b737f4c75197372d64afc6ed1bccd58c00e549 : just refactoring > 833af8427be4b217b5bc522f61afdbd3f1d282c2 : possible but isn't very new Can you also please try reverting the above two commits? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
