linux-ext4 - FIEMAP patches

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-next>] [day] [month] [year] [list]

Date:	Mon, 25 Aug 2008 14:22:50 -0600
From:	Andreas Dilger <adilger@....com>
To:	Mark Fasheh <mfasheh@...e.com>, Eric Sandeen <esandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: FIEMAP patches

I read through the entire previous FIEMAP thread (phew!) and it boils
down mostly to:

s/FIEMAP_FLAG_NO_DIRECT/FIEMAP_FLAG_NO_BYPASS/

> * FIEMAP_EXTENT_UNWRITTEN                                                    
> Unwritten extent - the extent is allocated but it's data has not been        
> initialized.  This indicates the extent's data will be all zero.             
                                                                               
This should say "will be all zero if read through the filesystem              
but the contents are undefined if read directly from the device."

There was also an update to the ext4 patch from Kalpak for handling
EA-in-inode at the same time as an external inode.

Eric, Mark,
could one of you please just submit the patches to Andrew for inclusion.
I think there was plenty of debate already, with very little significant
benefit except suggesting different names for some of the flags.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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