All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: andrei.botila@nxp.com, herbert@gondor.apana.org.au,
	horia.geanta@nxp.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] crypto: caam - update xts sector size for large input length" failed to apply to 4.9-stable tree
Date: Wed, 15 Apr 2020 21:13:38 -0400	[thread overview]
Message-ID: <20200416011338.GR1068@sasha-vm> (raw)
In-Reply-To: <1586948775110154@kroah.com>

On Wed, Apr 15, 2020 at 01:06:15PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 3f142b6a7b573bde6cff926f246da05652c61eb4 Mon Sep 17 00:00:00 2001
>From: Andrei Botila <andrei.botila@nxp.com>
>Date: Fri, 28 Feb 2020 12:46:48 +0200
>Subject: [PATCH] crypto: caam - update xts sector size for large input length
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>Since in the software implementation of XTS-AES there is
>no notion of sector every input length is processed the same way.
>CAAM implementation has the notion of sector which causes different
>results between the software implementation and the one in CAAM
>for input lengths bigger than 512 bytes.
>Increase sector size to maximum value on 16 bits.
>
>Fixes: c6415a6016bf ("crypto: caam - add support for acipher xts(aes)")
>Cc: <stable@vger.kernel.org> # v4.12+
>Signed-off-by: Andrei Botila <andrei.botila@nxp.com>
>Reviewed-by: Horia Geantă <horia.geanta@nxp.com>
>Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Function names were different due to 9dbe3072c6b1 ("crypto: caam/qi -
ablkcipher -> skcipher conversion") - queued up for 4.19 and 4.14.

I don't think that it's needed on anything older.

-- 
Thanks,
Sasha

      reply	other threads:[~2020-04-16  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 11:06 FAILED: patch "[PATCH] crypto: caam - update xts sector size for large input length" failed to apply to 4.9-stable tree gregkh
2020-04-16  1:13 ` Sasha Levin [this message]

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=20200416011338.GR1068@sasha-vm \
    --to=sashal@kernel.org \
    --cc=andrei.botila@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --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.