From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
To: Eric Biggers <ebiggers@google.com>
To: linux-crypto@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v2 5/7] crypto: gcm - fix incompatibility between "gcm" and "gcm_base"
Date: Wed, 10 Apr 2019 19:18:06 +0000 [thread overview]
Message-ID: <20190410191807.7C9D320820@mail.kernel.org> (raw)
In-Reply-To: <20190410064635.11813-6-ebiggers@kernel.org>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d00aa19b507b [CRYPTO] gcm: Allow block cipher parameter.
The bot has tested the following trees: v5.0.7, v4.19.34, v4.14.111, v4.9.168, v4.4.178, v3.18.138.
v5.0.7: Build OK!
v4.19.34: Build OK!
v4.14.111: Build OK!
v4.9.168: Failed to apply! Possible dependencies:
9b40f79c08e8 ("crypto: gcm - Fix error return code in crypto_gcm_create_common()")
v4.4.178: Failed to apply! Possible dependencies:
16f37ecdd068 ("crypto: gcm - Use skcipher")
9b40f79c08e8 ("crypto: gcm - Fix error return code in crypto_gcm_create_common()")
v3.18.138: Failed to apply! Possible dependencies:
16f37ecdd068 ("crypto: gcm - Use skcipher")
17db85469970 ("crypto: gcm - Use default null skcipher")
5d72336f1b2c ("crypto: gcm - Use crypto_aead_set_reqsize helper")
9b40f79c08e8 ("crypto: gcm - Fix error return code in crypto_gcm_create_common()")
adcbc688fe2f ("crypto: gcm - Convert to new AEAD interface")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-04-10 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 6:46 [PATCH v2 0/7] crypto: fixes in preparation of new fuzz tests Eric Biggers
2019-04-10 6:46 ` [PATCH v2 1/7] crypto: lrw - don't access already-freed walk.iv Eric Biggers
2019-04-10 6:46 ` [PATCH v2 2/7] crypto: salsa20 " Eric Biggers
2019-04-10 19:18 ` Sasha Levin
2019-04-10 6:46 ` [PATCH v2 3/7] crypto: arm/aes-neonbs " Eric Biggers
2019-04-10 19:18 ` Sasha Levin
2019-04-10 6:46 ` [PATCH v2 4/7] crypto: arm64/aes-neonbs " Eric Biggers
2019-04-10 19:18 ` Sasha Levin
2019-04-10 6:46 ` [PATCH v2 5/7] crypto: gcm - fix incompatibility between "gcm" and "gcm_base" Eric Biggers
2019-04-10 19:18 ` Sasha Levin [this message]
2019-04-18 14:00 ` Herbert Xu
2019-04-18 18:41 ` Eric Biggers
2019-04-19 5:52 ` Herbert Xu
2019-04-10 6:46 ` [PATCH v2 6/7] crypto: ccm - fix incompatibility between "ccm" and "ccm_base" Eric Biggers
2019-04-10 19:18 ` Sasha Levin
2019-04-18 14:03 ` Herbert Xu
2019-04-10 6:46 ` [PATCH v2 7/7] crypto: vmx - return correct error code on failed setkey Eric Biggers
2019-04-10 18:08 ` [PATCH v2 0/7] crypto: fixes in preparation of new fuzz tests Ard Biesheuvel
2019-04-18 14:24 ` Herbert Xu
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=20190410191807.7C9D320820@mail.kernel.org \
--to=sashal@kernel.org \
--cc=stable@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.