Date: Tue, 05 Sep 2006 23:35:23 +0900 From: Daichi GOTO <daichi@freebsd.org> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: [ANN] unionfs patchset-16 release, it is ready for the merge Message-ID: <44FD8B2B.60501@freebsd.org> In-Reply-To: <20060904184717.GA41475@xor.obsecurity.org> References: <44B67340.1080405@freebsd.org> <44B74036.6060101@freebsd.org> <20060903170129.GA98917@xor.obsecurity.org> <20060903172033.GA99212@xor.obsecurity.org> <20060904184717.GA41475@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Sun, Sep 03, 2006 at 01:20:33PM -0400, Kris Kennaway wrote: >> 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 >>>>> >>>>> For 6.x >>>>> http://people.freebsd.org/~daichi/unionfs/unionfs6-p16.diff >>>> I'm sorry, how silly of me. I updated miss edited things. >>>> I updated correct things now. Please check it :) >>> Dear Goto-san, >>> >>> 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. > > Another panic from mount_unionfs -b when just running 'vi' on a file. > By the way, I recommend you run with DEBUG_LOCKS and DEBUG_VFS_LOCKS > if you're not already doing so, because it looks like there are still > a number of locking problems. Oops ;-X Yeah, we have a new patchset to solve above problem I think. -- Daichi GOTO, http://people.freebsd.org/~daichi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44FD8B2B.60501>