On 2013/3/7 0:02, Sasha Levin wrote: > Hi all, > > While fuzzing with trinity inside a KVM tools guest running latest -next > kernel > I've stumbled on the following: > > [ 450.180599] =============================== > [ 450.181392] [ INFO: suspicious RCU usage. ] > [ 450.182101] 3.9.0-rc1-next-20130305-sasha-00048-g35e9ec5-dirty #1032 > Tainted: G W > [ 450.183482] ------------------------------- > [ 450.184343] include/linux/cgroup.h:429 suspicious rcu_dereference_check() > usage!
My fault. I didn't trigger a OOM to test my patch. I thought the caller of cpuset_print_task_mems_allowed() already acquired rcu_read_lock()... Thanks for the report. -- 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/
