linux-ext4 - Re: Exporting ext4-specific information through fsinfo attributes

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]

Date:   Wed, 1 Apr 2020 08:18:37 -0700
From:   "Darrick J. Wong" <darrick.wong@...cle.com>
To:     David Howells <dhowells@...hat.com>
Cc:     tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org
Subject: Re: Exporting ext4-specific information through fsinfo attributes

On Wed, Apr 01, 2020 at 08:39:07AM +0100, David Howells wrote:
> Hi Ted,
> 
> Whilst we were at Vault, I asked you if there was any live ext4 information
> that it could be useful to export through fsinfo().  I've implemented a patch
> that exports six superblock timestamps:
> 
> 	FSINFO_ATTR_EXT4_TIMESTAMPS: 
> 		mkfs    : 2016-02-26 00:37:03
> 		mount   : 2020-03-31 21:57:30
> 		write   : 2020-03-31 21:57:28
> 		fsck    : 2018-12-17 23:32:45
> 		1st-err : -
> 		last-err: -
> 
> but is there anything else that could be of interest?

The entire superblock as a binary blob? :)

This way we can begin moving dumpe2fs/tune2fs away from reading the raw
disk on live filesystems.

(I'd make the same noises about xfs, but less urgently since we already
have ioctls for that purpose.)

--D

> 
> Thanks,
> David
>