Quoting David Newall (david@davidnewall.com ):
quoted text > Serge E. Hallyn wrote:
>> No reason for any new parameters to pivot_root. Just clone your mounts
>> namespace first.
>>
>> unshare(CLONE_NEWNS);
>> chdir(new_dir);
>> pivot_root(new_dir, oldroot);
>>
>> Since pivot_root actually fiddles with the vfsmnts, this is really the
>> only way to go about having it "work with just one process".
>
> I think the point is that, whereas we'd like to be able to pivot the root
> for a single process, in practice this causes startup issues to which the
> easy solution is to pivot the whole system. At least that's my reading of
> the man page.
>
> It might be tidy if pivot_root could be used (instead of a hack based on a
> chroot bug), but it'd still be unportable.
Oh. Yes, true, it is unportable.
-serge
-
unsubscribe notice 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/
Messages in current thread:
Re: sys_chroot+sys_fchdir Fix , Serge E. Hallyn , (Mon Sep 24, 7:02 pm)