On Wed, 14 Nov 2012, Dave Jones wrote: > On Tue, Nov 13, 2012 at 07:50:25PM -0800, Hugh Dickins wrote: > > > Originally I was waiting to hear further from Dave; but his test > > machine was giving trouble, and it occurred to me that, never mind > > whether he says he has hit it again, or he has not hit it again, > > the answer is the same: don't send that VM_BUG_ON upstream. > > Sorry, I'm supposedly on vacation. Sorry for breaking in upon that, and thank you for responding even so. > That said, a replacement test box has been running tests since last Friday > without hitting that case. Maybe it was the last death throes of > that other machine before it gave up the ghost completely. > > Does sound like an awful coincidence though. I'm still clinging to your 0.1% possibility that it was not the intended kernel running. Anyway, I'm not going to worry about it further, until we see another hit - please do keep the VM_BUG_ON in your test kernel (i.e. resist that temptation to race in from your vacation to apply today's patch!), even though the right thing for 3.7 was to remove it. Thanks, Hugh -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>