linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>
To: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Eric Biggers <ebiggers@kernel.org>
Subject: Interesting crypto manager behavior
Date: Tue, 10 Sep 2019 12:50:04 +0000	[thread overview]
Message-ID: <MN2PR20MB2973C378D06E1694AE061983CAB60@MN2PR20MB2973.namprd20.prod.outlook.com> (raw)

Herbert, Eric,

I noticed some interesting behavior from the crypto manager when 
dealing with a fallback cipher situation.

I'm allocating a fallback (AEAD) cipher to handle some corner cases
my HW cannot handle, but I noticed that the fallback itself is being
tested when I allocate it (or so it seems) and if the fallback itself
fails on some testvector, it is not replaced by an alternative while
such an alternative should be available. So I have to fail my entire
init because the fallback could not be allocated.

i.e. while requesting a fallback for rfc7539(chacha20, poly1305), it
attempts rfc7539(safexcel-chacha20,poly1305-simd), which fails, but
it could still fall back to e.g. rfc7539(chacha20-simd, poly1305-simd),
which should work.

Actually, I really do not want the fallback to hit another algorithm
of my own driver. Is there some way to prevent that from happening?
(without actually referencing hard cra_driver_name's ...)

Regards,
Pascal van Leeuwen
Silicon IP Architect, Multi-Protocol Engines @ Verimatrix
www.insidesecure.com


             reply	other threads:[~2019-09-10 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 12:50 Pascal Van Leeuwen [this message]
2019-09-10 12:59 ` Interesting crypto manager behavior Herbert Xu
2019-09-10 13:10   ` Pascal Van Leeuwen
2019-09-10 13:37     ` Pascal Van Leeuwen

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=MN2PR20MB2973C378D06E1694AE061983CAB60@MN2PR20MB2973.namprd20.prod.outlook.com \
    --to=pvanleeuwen@verimatrix.com \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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).