From owner-freebsd-current@FreeBSD.ORG Tue Oct 10 14:11:12 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBDD116A40F; Tue, 10 Oct 2006 14:11:12 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C2DA43D46; Tue, 10 Oct 2006 14:11:11 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 7E775244C2C; Tue, 10 Oct 2006 23:11:08 +0900 (JST) Message-ID: <452BA9FB.3080401@freebsd.org> Date: Tue, 10 Oct 2006 23:11:07 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: Daichi GOTO 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> <452B750D.2020104@freebsd.org> In-Reply-To: <452B750D.2020104@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, ozawa@ongs.co.jp, Kris Kennaway Subject: Re: [ANN] unionfs patchset-16 release, it is ready for the merge X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 14:11:12 -0000 Daichi GOTO wrote: > 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? I updated new two dosuments: http://people.freebsd.org/~daichi/unionfs/reason-for-sys-uio-file.html http://people.freebsd.org/~daichi/unionfs/request-new-api-for-vfs.html Folks who have a interest in unionfs, read it please :) -- Daichi GOTO, http://people.freebsd.org/~daichi