On Mon, Oct 29, 2007 at 11:37:40AM -0700, Linus Torvalds wrote: > > > On Mon, 29 Oct 2007, Greg KH wrote: > > > > I'll be glad to revert it in -stable, if it's also reverted in Linus's > > tree first :) > > We've had some changes since 2.6.23, and afaik, the > "alloc_bootmem_high_node()" code is alreadt effectively dead there. It's > only called if CONFIG_SPARSEMEM_VMEMMAP is *not* enabled, and I *think* we > enable it by force on x86-64 these days.
If so, we(Nanhai and myself) will take a look at VMEMMAP changes and see if the bug that the commit 2e1c49db4c640b35df13889b86b9d62215ade4b6 tries to fix is still open in the latest git. But I can't explain how 2e1c49db4c640b35df13889b86b9d62215ade4b6 can be the root cause of Dave's issue in 2.6.23. thanks, suresh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
