Messages in this thread | | | Date | Wed, 26 Sep 2007 20:52:27 +0930 | From | David Newall <> | Subject | Re: sys_chroot+sys_fchdir Fix |
| |
Alan Cox wrote: > On Wed, 26 Sep 2007 20:04:14 +0930 > David Newall <david@davidnewall.com> wrote: > >> Al Viro wrote: >> >>> Oh, for fsck sake... Folks, it's standard-required behaviour. Ability >>> to chroot() implies the ability to break out of it. Could we please >>> add that (along with reference to SuS) to l-k FAQ and be done with that >>> nonsense? >>> >> I'm pretty confident that it's only standard behavior for Linux. Every >> other unix says it's not allowed. >> > > Go try them, then come back and admit your error >
I've made no error. The documentation says what it says, and what it doesn't say, other than for Linux, is that there is an unspecified way of breaking out.
If you're so keen on trying things, then I challenge you to try it on, oh, say, BSD, and then admit your error. (Such hostile words.) - 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/
| |