MIME-Version: 1.0
In-Reply-To: <20190422131849.8548320693@mail.kernel.org>
References: <4d8f4f483feb713126bbdb789b095936819d9804.1555932334.git.chunkeey@gmail.com>
 <20190422131849.8548320693@mail.kernel.org>
From:   Christian Lamparter <chunkeey@gmail.com>
Date:   Mon, 22 Apr 2019 18:32:01 +0200
Message-ID: <CAAd0S9D_29dG-70h-5C+F+h7QVppDKsa4rWDjRSR6ynBUss3+Q@mail.gmail.com>
Subject: Re: [PATCH 2/4] crypto4xx: fix cfb and ofb "overran dst buffer" issues
To:     Sasha Levin <sashal@kernel.org>
Cc:     linux-crypto@vger.kernel.org, Kees Cook <keescook@chromium.org>,
        stable@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

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