Date: Sun, 3 Sep 2006 13:20:33 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-fs@freebsd.org, Daichi GOTO <daichi@freebsd.org>, freebsd-current@freebsd.org Subject: Re: [ANN] unionfs patchset-16 release, it is ready for the merge Message-ID: <20060903172033.GA99212@xor.obsecurity.org> In-Reply-To: <20060903170129.GA98917@xor.obsecurity.org> References: <44B67340.1080405@freebsd.org> <44B74036.6060101@freebsd.org> <20060903170129.GA98917@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 03, 2006 at 01:01:29PM -0400, Kris Kennaway wrote: > On Fri, Jul 14, 2006 at 03:56:54PM +0900, Daichi GOTO wrote: > > Daichi GOTO wrote: > > > Patchset-16: > > > For 7-current > > > http://people.freebsd.org/~daichi/unionfs/unionfs-p16.diff > > >=20 > > > For 6.x > > > http://people.freebsd.org/~daichi/unionfs/unionfs6-p16.diff > >=20 > > I'm sorry, how silly of me. I updated miss edited things. > > I updated correct things now. Please check it :) >=20 > Dear Goto-san, >=20 > The panic I was previously seeing (with chrooting into the unionfs) > appears to be fixed, but after a bit of load I got the following > locking assertion on a unionfs (default mount options) stacked over a > nullfs mount of a local ufs filesystem: I got the same panic from a mount_unionfs -b mount with no nullfs involved. Kris --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE+w7gWry0BWjoQKURAradAJoCf+YpfBmsECfH4mPVNsZvtOUdkwCg0vqO VVdAH6zqTn9/uVuPS+70GNo= =wXky -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060903172033.GA99212>