On Tue, Jul 17, 2012 at 10:40:21PM -0300, Paulo Alcantara wrote:
> 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
> 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)
> 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()
> The xfs_next_extent() function must be able to read the inode (cast to the
> 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.
As we discussed on #xfs, I'm still not convinced that parsing the
filesystem metadata in the bootloader is the way to go. Far better,
IMO, is simply to supply the bootloader with a list of extents for
the blocks it needs to read to get the files it needs. You can get
them via fiemap(), and it'll work for XFS, btrfs, ext3, ext4, etc
without needing to write code to parse the on-disk format of every
Especially as we are in the process of making major changes to the
XFS on-disk format, which means you'll have to make significant
changes to support a second XFS disk format in the not-to-distant
> Thanks for the interest in helping us!
We want it to work! ;)