Date: Wed, 13 Nov 2002 06:33:31 -0000 From: "Cameron Grant" <gandalf@vilnya.demon.co.uk> To: "Matthew Dillon" <dillon@apollo.backplane.com>, "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: "Hans Zaunere" <zaunere@yahoo.com>, <freebsd-hackers@FreeBSD.ORG> Subject: Re: Shared files within a jail Message-ID: <011e01c28ade$95d1c280$4004020a@haveblue> References: <20021113034726.75787.qmail@web12801.mail.yahoo.com> <1037159767.66058.34.camel@chowder.localdomain> <200211130530.gAD5UxNt067928@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Try using null mounts. The warning is in there because making the
> null mount code work is a real hack and the authors aren't entirely
> sure that everything's gotten covered. That said, use of a null mount
> is certainly a lot safer if the stuff behind the mount is mostly
> static.
null mounts, in -stable at least, are broken for this purpose. on
connection, sshd revoke()s some device- its pty, i assume, and when this
hits the nullfs layer a null pointer is dereferenced. if i had vfs-clue i'd
have fixed it when i found the panic about two weeks ago. when i overcame
this by putting the jails /dev on an nfs loopback, i managed to produce two
more different panics.
-cg
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?011e01c28ade$95d1c280$4004020a>