From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Chow Subject: Re: inode->i_op->rename semantics . Date: Mon, 26 May 2003 01:54:35 +0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <3ED1035B.2080709@shaolinmicro.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: viro@parcelfarce.linux.theplanet.co.uk, linux-fsdevel@vger.kernel.org Return-path: Received: from [202.94.238.145] ([202.94.238.145]:18844 "EHLO mail.shaolinmicro.com") by vger.kernel.org with ESMTP id S263673AbTEYRj0 (ORCPT ); Sun, 25 May 2003 13:39:26 -0400 To: Nir Tzachar List-Id: linux-fsdevel.vger.kernel.org Nir Tzachar wrote: >hi AV. > >thank you for ur help, it solved my problems, >and thanks for clarifying some of the vfs code.... >( i rather wondered what d_move actually does. ) > >say, isnt it in order to publish some kind of a guide (more thorough than >the one in Documentation and anything i could find on the web + books... ) > Yes, I do have some notes on all i_ops, f_ops, a_ops for my own use (some still in my head). May be this should be further extend to form a book. Since the vfs.txt in the kernel doc written by Richard is pretty out-of-date and didn't have any examples. Especially for semantics from the Linux VFS. I thought of doing this for 2.4 but struggling for 2.5 as it worked a bit different in some cases. >to the vfs? even explaining execution paths will do.... >i think this kind of document, coming from the maintainer of >the vfs himself, will save us all much headaches...... > > > Al, I think you've been answering too many questions that I think it can be solved with an update-to-date simple doc. Do you have any plan on documenting the VFS api properly from i_ops, f_ops, a_ops and some detail explanation of those calls? Maybe something about 2.4 is quite good enough for a lot of people. If you have something, please do tell me so that I can collect them. regards, David Chow