From owner-freebsd-current@FreeBSD.ORG Tue Oct 10 14:06:00 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 A34E716A4E6; Tue, 10 Oct 2006 14:06:00 +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 AD92E43D58; Tue, 10 Oct 2006 14:05:59 +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 8D497244C2C; Tue, 10 Oct 2006 23:05:57 +0900 (JST) Message-ID: <452BA8C4.7040906@freebsd.org> Date: Tue, 10 Oct 2006 23:05:56 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org, rodrigc@crodrigues.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: daichi@freebsd.org, ozawa@ongs.co.jp Subject: [REQUEST] unionfs needs some guys can do implements new 2 APIs for VFS 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:06:00 -0000 Hi Guys! Now we need a man or a guy who can do implements new 2 APIs for VFS. Someone please help us!! http://people.freebsd.org/~daichi/unionfs/request-new-api-for-vfs.html ---- The FreeBSD new unionfs implementation: New API request for FreeBSD VFS ======================================================================= Daichi GOTO (daichi@freebsd.org) 1 Introduction We have always tried to keep changes just in unionfs segment only. But by accomplish nothing, we need change the other segment. 2 Problem Description Until now we have did many improvements for unionfs, but now we feel the limication arount the process of unionfs's "copied-up file". Additional thinking of future support for MAC extention, ADVLOCK lock infomation and somethinkg like those, all the more reason to be careful. 3 Impact It leads the confution of unionfs implementation and some problem around lock mechanism. We cannot solve those problem by just only changes in unionfs segument. 4 Solution Request We need new 2 APIs(functions) for VFS. Please some developer do implement new APIs like as follow: int VOP_GETALLATTR(struct vnode *vp, struct vnode_xxx *data, struct thread *td) { set the all attr to data from vp; ...; } int VOP_SETALLATTR(struct vnode *vp, struct vnode_xxx *data, struct thread *td) { set the all attr to vp from data; ...; } Above funtions can set/get vnode information(now those are attr, extattr and ADVLOCK) together if its type is VREG. We cannot do implement it caused by lack of vfs arcana. Please raise your hands and do it, please. 5 References http://people.freebsd.org/~daichi/unionfs/ http://people.freebsd.org/~daichi/unionfs/index-ja.html http://people.freebsd.org/~daichi/unionfs/reason-for-sys-uio-file.html ---- We need your help. Please help us. -- Daichi GOTO, http://people.freebsd.org/~daichi