From: Eric Biggers <ebiggers3@gmail.com>
To: Michael Halcrow <mhalcrow@google.com>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-crypto@vger.kernel.org,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Alex Cope <alexcope@google.com>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH 5/6] fscrypt: cache the HMAC transform for each master key
Date: Wed, 19 Jul 2017 10:37:44 -0700 [thread overview]
Message-ID: <20170719173744.GB78811@gmail.com> (raw)
In-Reply-To: <20170717174551.GA32282@google.com>
On Mon, Jul 17, 2017 at 10:45:51AM -0700, Michael Halcrow wrote:
> > +/*
> > + * Get the fscrypt_master_key identified by the specified v2+ encryption
> > + * context, or create it if not found.
> > + *
> > + * Returns the fscrypt_master_key with a reference taken, or an ERR_PTR().
> > + */
> > +static struct fscrypt_master_key *
> > +find_or_create_master_key(const struct inode *inode,
> > + const struct fscrypt_context *ctx,
> > + unsigned int min_keysize)
> > +{
> > + struct fscrypt_master_key *master_key;
> > +
> > + if (WARN_ON(ctx->version < FSCRYPT_CONTEXT_V2))
> > + return ERR_PTR(-EINVAL);
>
> Isn't this a programming error? If so, consider either BUG_ON() or
> omit the check.
>
Yes, but BUG_ON() is discouraged in cases where there is a straightforward way
to recover from the error. checkpatch actually warns about using it these days.
Eric
next prev parent reply other threads:[~2017-07-19 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 21:00 [PATCH 0/6] fscrypt: key verification and KDF improvement Eric Biggers
2017-07-12 21:00 ` [PATCH 1/6] fscrypt: add v2 encryption context and policy Eric Biggers
2017-07-13 22:29 ` Michael Halcrow
2017-07-13 22:58 ` Eric Biggers
2017-07-14 20:08 ` Andreas Dilger
2017-07-12 21:00 ` [PATCH 2/6] fscrypt: rename ->ci_master_key to ->ci_master_key_descriptor Eric Biggers
2017-07-14 15:36 ` Michael Halcrow
2017-07-12 21:00 ` [PATCH 3/6] fscrypt: use HKDF-SHA512 to derive the per-inode encryption keys Eric Biggers
2017-07-13 14:54 ` Stephan Müller
2017-07-13 16:07 ` Herbert Xu
2017-07-13 16:18 ` Stephan Müller
2017-07-13 18:10 ` Eric Biggers
2017-07-14 15:50 ` Stephan Müller
2017-07-14 16:24 ` Michael Halcrow
2017-07-14 17:11 ` Michael Halcrow
2017-07-19 17:32 ` Eric Biggers
2017-07-12 21:00 ` [PATCH 4/6] fscrypt: verify that the correct master key was supplied Eric Biggers
2017-07-14 16:40 ` Michael Halcrow
2017-07-14 17:34 ` Jeffrey Walton
2017-07-15 0:52 ` Eric Biggers
2017-07-12 21:00 ` [PATCH 5/6] fscrypt: cache the HMAC transform for each master key Eric Biggers
2017-07-17 17:45 ` Michael Halcrow
2017-07-19 17:37 ` Eric Biggers [this message]
2017-07-12 21:00 ` [PATCH 6/6] fscrypt: for v2 policies, support "fscrypt:" key prefix only Eric Biggers
2017-07-17 17:54 ` Michael Halcrow
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=20170719173744.GB78811@gmail.com \
--to=ebiggers3@gmail.com \
--cc=alexcope@google.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mhalcrow@google.com \
--cc=tytso@mit.edu \
/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).