On 01/04/2011 09:17 PM, Mike Heffner wrote: >> we use the following patch to get the pid of a task as seen from its >> pid namespace. It can be useful to identify tasks writing pids in files. >> > > Great, I'll try it out. Has there been any interest in getting this into > the mainline? hmm, it has been talked over a few years ago. I can't find the pointer anymore. > Are there negatives to advertising child vpid's? I don't think so but the issue is more on gathering clear requirements for it. The patch is simple enough to be discussed rapidly and eventually be accepted if it is considered useful enough. It does add a user/kernel API, which is always a concern. I'm not in favor of exposing too much of the pid stuff, already overly complex with the nested pid namespace, but the result of getpid() from a task pov sounds like a legitimate information to expose. Why do you need it ? C. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
