Re: [PATCH v2 01/12] fs-verity: add a documentation file
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Theodore Y. Ts'o" <tytso@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-fscrypt@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-integrity@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Jaegeuk Kim <jaegeuk@xxxxxxxxxx>, Victor Hsieh <victorhsieh@xxxxxxxxxx>, Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [PATCH v2 01/12] fs-verity: add a documentation file
- From: Eric Biggers <ebiggers@xxxxxxxxxx>
- Date: Thu, 13 Dec 2018 21:39:06 -0800
- In-reply-to: <20181214051722.GF20880@thunk.org>
- References: <20181101225230.88058-1-ebiggers@kernel.org> <20181101225230.88058-2-ebiggers@kernel.org> <20181212091406.GA31723@infradead.org> <20181212202609.GA193967@gmail.com> <20181213202249.GA3797@infradead.org> <20181214051722.GF20880@thunk.org>
- User-agent: Mutt/1.11.0 (2018-11-25)
On Fri, Dec 14, 2018 at 12:17:22AM -0500, Theodore Y. Ts'o wrote:
> Furthermore, it would require extra complexity in the common fsverity code
> --- which looks for the Merkle tree at the end of file data --- for no real
> benefit.
To clarify, while this is technically true currently, as I mentioned it's been
kept flexible enough such that a filesystem *could* store the metadata elsewhere
with only some slight changes to the common fs/verity/ code which won't break
other filesystems. Though of course, keeping all filesystems using the
"metadata after EOF" approach does allow a couple simplifications.
- Eric
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite News]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]