On Wed, 25 Apr 2007, Hugh Dickins wrote: > But, surely you wouldn't have expected it to stay on the processor > throughout the waiting page allocation?? I think you're misremembering > your expectations, and this was just a simple, understandable, oversight.
You do not know my fuzzy brain... Some thoughts go wrong once and twice and then are stuck in there and I need people like you to straighten me out. > Quite a serious one, though: it got caught in my case by the NULL > dereference, but it's probably been switching cpu there much more > often - one cpu diddling with what's private to another, with > unpredictable results. Right. Thanks for catching it. - 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/
