I suspect that using BUG_ON here is not a good idea, because the tested called function looks pretty important. But I have forwarded it on in case someone thinks otherwise. julia On Sat, 9 Aug 2014, kbuild test robot wrote: > TO: Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> > CC: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > CC: Linux Memory Management List <linux-mm@xxxxxxxxx> > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: 6a062ecb62b37d6d36fa2e56052982565b0f5aac > commit: f9054025fb65d0802098f18b153e4d720acd126e [9660/12021] on demand vmstat: Do not open code alloc_cpumask_var > :::::: branch date: 27 hours ago > :::::: commit date: 9 days ago > > >> mm/vmstat.c:1343:2-5: WARNING: Use BUG_ON > > Please consider folding the attached diff :-) > > --- > 0-DAY kernel build testing backend Open Source Technology Center > http://lists.01.org/mailman/listinfo/kbuild Intel Corporation > -- 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>