From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org
Subject: Re: Exporting ext4-specific information through fsinfo attributes
Date: Wed, 1 Apr 2020 12:05:53 -0700 [thread overview]
Message-ID: <20200401190553.GC56931@magnolia> (raw)
In-Reply-To: <20200401162744.GB201933@gmail.com>
On Wed, Apr 01, 2020 at 09:27:44AM -0700, Eric Biggers wrote:
> 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?
> >
> > Thanks,
> > David
> >
>
> FWIW, the filesystem UUID would be useful for testing ext4 and f2fs encryption
> (since it's now sometimes used in the derivation of encryption keys). But I see
> you already included it as FSINFO_ATTR_VOLUME_UUID.
It is?? What happens if you tune2fs -U if csum_seed isn't enabled?
--D
>
> - Eric
next prev parent reply other threads:[~2020-04-01 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 7:39 Exporting ext4-specific information through fsinfo attributes David Howells
2020-04-01 15:18 ` Darrick J. Wong
2020-04-01 16:27 ` Eric Biggers
2020-04-01 19:05 ` Darrick J. Wong [this message]
2020-04-01 19:28 ` Eric Biggers
2020-04-01 20:36 ` Eric Biggers
2020-04-21 16:17 ` David Howells
2020-04-21 22:07 ` Andreas Dilger
2020-04-22 16:12 ` Darrick J. Wong
2020-07-21 9:20 ` David Howells
2020-07-21 15:37 ` Darrick J. Wong
2020-04-22 14:27 ` David Howells
2020-07-21 15:42 ` Darrick J. Wong
2020-07-22 8:53 ` David Howells
2020-07-22 15:25 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200401190553.GC56931@magnolia \
--to=darrick.wong@oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).