linux-ext4 - Re: [PATCH] filefrag: Lustre changes to filefrag FIEMAP handling

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

Message-ID: <20180702213311.GA19410@thunk.org>
Date:   Mon, 2 Jul 2018 17:33:12 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     c17828 <artem.blagodarenko@...il.com>
Cc:     linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca,
        alexey.lyashkov@...il.com,
        Andreas Dilger <andreas.dilger@...el.com>
Subject: Re: [PATCH] filefrag: Lustre changes to filefrag FIEMAP handling

On Wed, Jun 27, 2018 at 06:57:31PM +0300, c17828 wrote:
> From: Andreas Dilger <andreas.dilger@...el.com>
> 
> Add support for multiple-device filesystems by defining a new
> fe_device field in the fiemap_extent structure.  This allows
> printing the filesystem-relative or linux block device number
> associated with each extent of a file.  If a single filesystem
> extent is mirrored to multiple block devices, the fe_device
> field can be used to disambiguate the multiple copies.
> 
> If the "-l" (device-logical) option is given to filefrag, then
> all extents for a particular device of a file are returned
> before returning extents for the next device.  This makes it
> easier to see if extent allocation within a single device is
> contiguous, instead of returning all of the blocks of a file
> interleaved in file-logical-offset order.
> 
> Change-Id: Icdefe4dbc319e6652c3d6641e1500f2cfaf63605
> Signed-off-by: Andreas Dilger <andreas.dilger@...el.com>
> Signed-off-by: Artem Blagodarenko <artem.blagodarenko@...il.com>

The kernel-side change for this needs to be accepted first --- if for
no other reason than to make sure code point assignment for the FIEMAP
flag is the one that gets settled on in the kernel.

Please resend when that is accomplished.

	     	    	     	  	  - Ted