From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH 0/4] fscrypt: logging improvements, and use ENOPKG
Date: Wed, 14 Aug 2019 15:31:45 -0700 [thread overview]
Message-ID: <20190814223144.GD101319@gmail.com> (raw)
In-Reply-To: <20190724195422.42495-1-ebiggers@kernel.org>
On Wed, Jul 24, 2019 at 12:54:18PM -0700, Eric Biggers wrote:
> Patches 1-3 make some small improvements to warning and error messages
> in fs/crypto/, including logging all types of unsupported encryption
> contexts rather than just ones where the encryption modes are invalid.
>
> Patch 4 changes the error code for "missing crypto API support" from
> ENOENT to ENOPKG, to avoid an ambiguity. This is a logically separate
> change, but it's in this series to avoid conflicts.
>
> Eric Biggers (4):
> fscrypt: make fscrypt_msg() take inode instead of super_block
> fscrypt: improve warning messages for unsupported encryption contexts
> fscrypt: improve warnings for missing crypto API support
> fscrypt: use ENOPKG when crypto API support missing
>
> fs/crypto/crypto.c | 13 ++++----
> fs/crypto/fname.c | 8 ++---
> fs/crypto/fscrypt_private.h | 10 +++---
> fs/crypto/hooks.c | 6 ++--
> fs/crypto/keyinfo.c | 61 +++++++++++++++++++++++++------------
> 5 files changed, 57 insertions(+), 41 deletions(-)
>
> --
> 2.22.0.657.g960e92d24f-goog
>
All applied to fscrypt tree for 5.4.
- Eric
prev parent reply other threads:[~2019-08-14 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 19:54 [PATCH 0/4] fscrypt: logging improvements, and use ENOPKG Eric Biggers
2019-07-24 19:54 ` [PATCH 1/4] fscrypt: make fscrypt_msg() take inode instead of super_block Eric Biggers
2019-07-24 19:54 ` [PATCH 2/4] fscrypt: improve warning messages for unsupported encryption contexts Eric Biggers
2019-07-24 19:54 ` [PATCH 3/4] fscrypt: improve warnings for missing crypto API support Eric Biggers
2019-07-24 19:54 ` [PATCH 4/4] fscrypt: use ENOPKG when crypto API support missing Eric Biggers
2019-08-14 22:31 ` 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=20190814223144.GD101319@gmail.com \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@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 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).