sukadev@xxxxxxxxxx writes: > > My patch refers to this function as pid_active_pid_ns() - I have > been meaning to send that out on top of your signals patch. > Since a pid has many namespaces, we have been using 'active pid ns' > to refer to this ns. Currently we don't ask for any of the others, and the namespace the pid came from is special. That fundamentally is the namespace of the pid. The rest byproducts of being in that pid namespace, as we could derive them by walking the namespace's parent list. > Even your next patch modifies task_active_pid_ns() to use this. > So can we rename this functio to pid_active_pid_ns() ? I'd be more inclined to rename task_active_pid_ns to task_pid_ns. And to rename pid_in_pid_ns that Pavel has issues with to pid_in_ns. When I read active_pid_ns I wonder what the other namespaces are that we are distinguishing this from. They do exist in the implementation but so far it is a complete don't care. So I expect being as terse as we can while still conveying all of the relevant information is the most maintainable long term. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
