linux-kernel - Re: [patch 0/6][RFC] Cleanup FIBMAP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <472631FE.9070003@google.com>
Date:	Mon, 29 Oct 2007 12:18:22 -0700
From:	Mike Waychison <mikew@...gle.com>
To:	Zach Brown <zab@...bo.net>
CC:	Chris Mason <chris.mason@...cle.com>,
	Anton Altaparmakov <aia21@....ac.uk>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 0/6][RFC] Cleanup FIBMAP

Zach Brown wrote:
>>> And another of my pet peeves with ->bmap is that it uses 0 to mean  
>>> "sparse" which causes a conflict on NTFS at least as block zero is  
>>> part of the $Boot system file so it is a real, valid block...  NTFS  
>>> uses -1 to denote sparse blocks internally.
>> Reiserfs and Btrfs also use 0 to mean packed.  It would be nice if there
>> was a way to indicate your-data-is-here-but-isn't-alone.  But that's
>> more of a feature for the FIEMAP stuff.
> 
> And maybe we can step back and see what the callers of FIBMAP are doing
> with the results they're getting.
> 
> One use is to discover the order in which to read file data that will
> result in efficient IO.
> 
> If we had an interface specifically for this use case then perhaps a
> sparse block would be better reported as the position of the inode
> relative to other data blocks.  Maybe the inode block number in ext* land.
> 

Can you clarify what you mean above with an example?  I don't really follow.

Thanks,

Mike Waychison


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/