From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] fscrypt: Update encryption policy version docs
Date: Mon, 20 Jul 2026 10:47:28 -0700 [thread overview]
Message-ID: <20260720174728.GF1865@quark> (raw)
In-Reply-To: <20260718212526.53943-1-ebiggers@kernel.org>
On Sat, Jul 18, 2026 at 02:25:26PM -0700, Eric Biggers wrote:
> Update the wording of the documentation to put v1 encryption policies a
> bit more firmly in the past, explicitly calling them "deprecated" (which
> is consistent with the warning message the kernel has printed ever since
> v5.4). Do the same for FS_IOC_GET_ENCRYPTION_POLICY which supports only
> v1 policies, and remove the explicit recommendation to fall back to it.
>
> Also clarify that reusing master keys across policies isn't the best
> practice or normal usage, even though it's technically allowed for v2.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
>
> This patch is targeting the fscrypt tree
Applied to https://git.kernel.org/pub/scm/fs/fscrypt/linux.git/log/?h=for-next
- Eric
prev parent reply other threads:[~2026-07-20 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 21:25 [PATCH] fscrypt: Update encryption policy version docs Eric Biggers
2026-07-20 17:47 ` Eric Biggers [this message]
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=20260720174728.GF1865@quark \
--to=ebiggers@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.