[lkml]   [2007]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: sys_chroot+sys_fchdir Fix
Bill Davidsen wrote: 
> It seems there are (at least) two parts to this, one regarding
> changing working directory which is clearly stated in the standards
> and must work as it does, and the various issues regarding getting out
> of the chroot after the cwd has entered that changed root. That second
> part seems to offer room for additional controls on getting out of the
> chroot which do not violate any of the obvious standards, and which
> therefore might be valid candidates for discussion on the basis of
> benefit rather than portability.

Correct. BSDs solved the problem by changing cwd on subsequent use of
chroot; I think there's a better way. I think the solution might be to
add a "previous root", and restrict the process there as well as the new
root. That is, once cwd is set within the new root, that new root is
the limit. Prior to setting cwd within the new root, the previous root
is the limit.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-09-28 03:09    [W:0.071 / U:6.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site