From: Christian Lamparter <chunkeey@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-crypto@vger.kernel.org, Kees Cook <keescook@chromium.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/4] crypto4xx: fix cfb and ofb "overran dst buffer" issues
Date: Mon, 22 Apr 2019 18:32:01 +0200 [thread overview]
Message-ID: <CAAd0S9D_29dG-70h-5C+F+h7QVppDKsa4rWDjRSR6ynBUss3+Q@mail.gmail.com> (raw)
In-Reply-To: <20190422131849.8548320693@mail.kernel.org>
On 4/22/19, Sasha Levin <sashal@kernel.org> wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v5.0.9, v4.19.36, v4.14.113,
> v4.9.170, v4.4.178, v3.18.138.
>
> v5.0.9: Build OK!
> v4.19.36: Build OK!
> v4.14.113: Failed to apply! Possible dependencies:
[...]
> f2a13e7cba9e ("crypto: crypto4xx - enable AES RFC3686, ECB, CFB and OFB
> offloads")
>
>
> How should we proceed with this patch?
>
Same as with the aes-ctr fix. I guess, I should have added
Fixes: f2a13e7cba9e ("crypto: crypto4xx - enable AES RFC3686, ECB, CFB
and OFB offloads")
Regards,
Christian
next prev parent reply other threads:[~2019-04-22 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 11:25 [PATCH 1/4] crypto4xx: fix ctr-aes missing output IV Christian Lamparter
2019-04-22 11:25 ` [PATCH 2/4] crypto4xx: fix cfb and ofb "overran dst buffer" issues Christian Lamparter
2019-04-22 11:26 ` [PATCH 3/4] crypto4xx: use sync skcipher for fallback Christian Lamparter
2019-04-22 11:26 ` [PATCH 4/4] crypto4xx: get rid of redundant using_sd variable Christian Lamparter
[not found] ` <20190422131849.8548320693@mail.kernel.org>
2019-04-22 16:32 ` Christian Lamparter [this message]
[not found] ` <20190422131848.3AD9A20693@mail.kernel.org>
2019-04-22 16:27 ` [PATCH 1/4] crypto4xx: fix ctr-aes missing output IV Christian Lamparter
2019-05-03 6:08 ` 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=CAAd0S9D_29dG-70h-5C+F+h7QVppDKsa4rWDjRSR6ynBUss3+Q@mail.gmail.com \
--to=chunkeey@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=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.