On Wed, 14 Oct 2015, Linus Torvalds wrote: > I don't think it's normally a problem. But mm/vmstat.c clearly *is* > confused, and uses both "schedule_delayed_work_on()" and > "schedule_delayed_work()" for the same work. Well yes the schedule_delayed_work_on() call is from another cpu and the schedule_delayed_work() from the same. No confusion there. vmstat_update() is run from the cpu where the diffs have to be updated and if it needs to reschedule itself it relies on schedule_delayed_work() to stay on the same cpu. The vmstat_shepherd needs to start work items on remote cpus and therefore uses xx_work_on(). And yes this relies on work items being executed on the same cpu unless the queue is decleared to be UNBOUND which is not the case here. -- 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>