Re: [RFC PATCH 0/3] xfstests: test adding filesystem-level fscrypt key via key_id
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Eric Biggers <ebiggers@xxxxxxxxxx>, dhowells@xxxxxxxxxx
- Subject: Re: [RFC PATCH 0/3] xfstests: test adding filesystem-level fscrypt key via key_id
- From: Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxxxxxxxx>
- Date: Wed, 11 Dec 2019 11:50:19 +0200
- In-reply-to: <20191127225759.GA303989@sol.localdomain>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20191119223130.228341-1-ebiggers@kernel.org> <20191127204536.GA12520@linux.intel.com> <20191127225759.GA303989@sol.localdomain>
- User-agent: Mutt/1.10.1 (2018-07-13)
On Wed, Nov 27, 2019 at 02:57:59PM -0800, Eric Biggers wrote:
> You could manually do what the xfstest does, which is more or less the following
> (requires xfs_io patched with https://patchwork.kernel.org/patch/11252795/):
I postpone testing/reviewing this patch up until its depedencies are in
the mainline.
I'll add these to my tree as soon as we have addressed a critical bug
in tpm_tis:
1. KEYS: remove CONFIG_KEYS_COMPAT
2. KEYS: asymmetric: return ENOMEM if akcipher_request_alloc() fails
Just mentioning that I haven't forgotten them.
/Jarkko
[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]