Date: Tue, 10 Oct 2006 19:25:17 +0900 From: Daichi GOTO <daichi@freebsd.org> To: Danny Braniss <danny@cs.huji.ac.il> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, ozawa@ongs.co.jp, Kris Kennaway <kris@obsecurity.org> Subject: Re: [ANN] unionfs patchset-16 release, it is ready for the merge Message-ID: <452B750D.2020104@freebsd.org> In-Reply-To: <E1GXERG-000BLK-2p@cs1.cs.huji.ac.il> References: <44B67340.1080405@freebsd.org> <44B74036.6060101@freebsd.org> <20060903170129.GA98917@xor.obsecurity.org> <20060903172033.GA99212@xor.obsecurity.org> <20060904184717.GA41475@xor.obsecurity.org> <44FD8B2B.60501@freebsd.org> <E1GXERG-000BLK-2p@cs1.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
Danny Braniss wrote: > [...] >> Yeah, we have a new patchset to solve above problem I think. > > any chance that the new unionfs will make it to 6.2? We cannot merger unionfs patch to 6.x branch. It'll just only for -current. For 6.x patchset is just a patchset. > I'm using it, and it's working just fine - as opposed to the unusable > one supplied. For under some heavy situation with mount_nullfs, it has a problem since the lock mechanism. To solve that problem, we need a new API(function) for VFS. We are discussing about it and need vfs-hackers help. Sorry for my slow response :( > If not, Daichi GOTO, will you have a new set of patches? > union_vfsops.c just changed, for example. > thanks, > danny uhmm... you need a new patchset if it is under construction? -- Daichi GOTO, http://people.freebsd.org/~daichi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?452B750D.2020104>