Messages in this thread | | | Subject | Re: RFC [patch 13/34] PID Virtualization Define new task_pid api | From | (Eric W. Biederman) | Date | Mon, 23 Jan 2006 11:48:06 -0700 |
| |
Hubertus Franke <frankeh@watson.ibm.com> writes:
> That's a good idea .. right now we simply did this through a flag left by the > call > to the /proc/container fs ... (awkward at best, but didn't break the API). > I have a concern wrt doing it in during fork namely the sharing of resources. > Whe obviously are looking at some constraints here wrt to sharing. We need to > ensure that this ain't a thread etc that will share resources > across "containers" (which then later aren't migratable due to that sharing). > So doing the fork_exec() atomically would avoid that problem.
Checking that we aren't sharing things to become a thread is fairly straight forward. do_fork already has similar checks in place.
This sounds like a classic case of if you don't want that don't do that then.
Eric
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |