Re: [PATCH] fscrypt: track master key presence separately from secret

2023-10-16 Thread Eric Biggers
On Mon, Oct 16, 2023 at 02:23:37PM -0400, Josef Bacik wrote: > On Sat, Oct 14, 2023 at 11:10:55PM -0700, Eric Biggers wrote: > > From: Eric Biggers > > > > Master keys can be in one of three states: present, incompletely > > removed, and absent (as per FSCRYPT_KEY_STATUS_* used in the UAPI). > >

Re: [PATCH] fscrypt: track master key presence separately from secret

2023-10-16 Thread Neal Gompa
On Sun, Oct 15, 2023 at 2:12 AM Eric Biggers wrote: > > From: Eric Biggers > > Master keys can be in one of three states: present, incompletely > removed, and absent (as per FSCRYPT_KEY_STATUS_* used in the UAPI). > Currently, the way that "present" is distinguished from "incompletely > removed"

Re: [PATCH] fscrypt: track master key presence separately from secret

2023-10-16 Thread Josef Bacik
On Sat, Oct 14, 2023 at 11:10:55PM -0700, Eric Biggers wrote: > From: Eric Biggers > > Master keys can be in one of three states: present, incompletely > removed, and absent (as per FSCRYPT_KEY_STATUS_* used in the UAPI). > Currently, the way that "present" is distinguished from "incompletely > r

[PATCH] fscrypt: track master key presence separately from secret

2023-10-14 Thread Eric Biggers
From: Eric Biggers Master keys can be in one of three states: present, incompletely removed, and absent (as per FSCRYPT_KEY_STATUS_* used in the UAPI). Currently, the way that "present" is distinguished from "incompletely removed" internally is by whether ->mk_secret exists or not. With extent-b