xfs
[Top] [All Lists]

Re: [PATCH] xfs: fix comment typo of struct xfs_da_blkinfo.

To: hch@xxxxxxxxxxxxx
Subject: Re: [PATCH] xfs: fix comment typo of struct xfs_da_blkinfo.
From: Paulo Alcantara <pcacjr@xxxxxxxxx>
Date: Tue, 17 Jul 2012 22:40:21 -0300 (BRT)
Cc: baozich@xxxxxxxxx, bpm@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20120717070643.GA4958@xxxxxxxxxxxxx>
References: <20120716151038.GI29979@xxxxxxx> <5292013E-6FF3-47F6-BE9F-FD7BA2BB2AA9@xxxxxxxxx> <20120717070643.GA4958@xxxxxxxxxxxxx>
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
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

<Prev in Thread] Current Thread [Next in Thread>