From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757189Ab2GQWnq (ORCPT ); Tue, 17 Jul 2012 18:43:46 -0400 Received: from terminus.zytor.com ([198.137.202.10]:51592 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751857Ab2GQWno (ORCPT ); Tue, 17 Jul 2012 18:43:44 -0400 Date: Tue, 17 Jul 2012 22:40:21 -0300 (BRT) Message-Id: <20120717.224021.707783566146599004.pcacjr@zytor.com> To: hch@infradead.org Cc: baozich@gmail.com, bpm@sgi.com, linux-kernel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: [PATCH] xfs: fix comment typo of struct xfs_da_blkinfo. From: Paulo Alcantara In-Reply-To: <20120717070643.GA4958@infradead.org> References: <20120716151038.GI29979@sgi.com> <5292013E-6FF3-47F6-BE9F-FD7BA2BB2AA9@gmail.com> <20120717070643.GA4958@infradead.org> X-Mailer: Mew version 6.5 on Emacs 24.0.97 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Christoph Hellwig Date: Tue, 17 Jul 2012 03:06:43 -0400 > Btw, if you need more reviers for the syslinus support feel free to pass > it by me (or the list). This is the branch I'm maintaing for the XFS readonly driver: git://zytor.com/users/pcacjr/syslinux.git (branch: xfs) The current status is: - We are able to find the root inode by reading rootino field from superblock (xfs_iget_root() function). - We are able to find inodes that have core's format set to "local" only at the moment, which is by reading leaf entries from inode btrees. The function that looks up for an inode is the xfs_iget() one. We're looking forward to implement the handling of keys in inode btrees (extents) also. Baoszi is currently working on the inode btree's key part (extents), and I'm working on the data part of the file inode, which is the xfs_next_extent() function. The xfs_next_extent() function must be able to read the inode (cast to the data fork) and populate a structure that stores physical starting number sector and number of consecutive sectors that contain the inode's data so that Syslinux will know where to read from. Thanks for the interest in helping us! Paulo