KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> wrote: > > KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> wrote: > > > > > dump_tasks() can call __task_cred() safely because we are holding > > > tasklist_lock. but rcu lock validator don't have enough knowledge and > > > it makes following annoying warning. > > > > No, it can't. The tasklist_lock is not protection against the creds > > changing on another CPU. > > Thank you for correction. > > I suppose you mean I missed CONFIG_TREE_PREEMPT_RCU, right? > As far as my grepping, other rcu implementation and spinlock use > preempt_disable(). In other word, Can I assume usual distro user > don't hit this issue? No. The paths by which a process changes its credentials don't normally take tasklist_lock, so holding tasklist_lock doesn't prevent the process you're looking at from replacing its cred and discarding the ones you're looking at. Further, unless you're holding the RCU read lock, there's nothing theoretically stopping the system from deleting the discarded credentials. David -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>