On 04/25, Eric W. Biederman wrote: > > Oleg Nesterov <o...@redhat.com> writes: > > > Well. I _think_ that __fput() and ima_file_free() in particular should not > > depend on current and/or current->nsproxy. If nothing else, fput() can be > > called by the unrelated task which looks into /proc/pid/. > > > > But again, task_work_add() has more and more users, and it seems that even > > __fput() paths can do "everything", so perhaps it would be safer to allow > > to use ->nsproxy in task_work_run. > > Like I said, give me a clear motivating case.
I agree, we need a reason. Currently I do not see one. > Right now not allowing > nsproxy is turning up bugs in __fput. Which seems like a good thing. This is what I certainly agree with ;) Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/