* David Miller <davem@xxxxxxxxxxxxx> wrote: > From: Ingo Molnar <mingo@xxxxxxx> > Date: Mon, 3 Aug 2009 07:56:08 +0200 > > > I'm wondering how sparc32 handles core_kernel_text() & friends? > > > > Those functions already assume that the bits between _stext and > > _etext are all core kernel text and not generic pages freed back > > to the buddy. > > They won't work for such pages obviously. Shows how many sparc32 > users who trigger this case of actually freeing those pages and > using such facilities there actually are :-) :) I suspect the other bit is probably that core_kernel_text() really didnt use to have any critical use at all - just debugging/lockdep mostly. So no functionality broke for people to report. Such bugs often have years of latency on x86 too - we recently fixed one that was there for over a year and nobody noticed: 4a44bac: symbols, stacktrace: look up init symbols after module symbols Ingo -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
