[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070924230008.GA3160@vino.hallyn.com>
Date: Mon, 24 Sep 2007 18:00:08 -0500
From: "Serge E. Hallyn" <serge@...lyn.com>
To: David Newall <david@...idnewall.com>
Cc: "Serge E. Hallyn" <serge@...lyn.com>,
Bill Davidsen <davidsen@....com>,
Philipp Marek <philipp@...ek.priv.at>, 7eggert@....de,
Alan Cox <alan@...rguk.ukuu.org.uk>,
majkls <majkls@...pere.com>, bunk@...tum.de,
linux-kernel@...r.kernel.org
Subject: Re: sys_chroot+sys_fchdir Fix
Quoting David Newall (david@...idnewall.com):
> 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.
It can.
Please re-read my previous msg.
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists