Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Gary R Hook <gary.hook@amd.com>
To: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] crypto: ccp - Fix XTS-AES-128 support on v5 CCPs
Date: Fri, 18 Aug 2017 11:41:04 -0500	[thread overview]
Message-ID: <32d0b50e-e5d5-6041-0ee9-f8384c7c79a3@amd.com> (raw)
In-Reply-To: <f5714d71-4e4a-b942-7e1e-58f478a5ff21@amd.com>

>On Tue, Jul 25, 2017 at 02:12:11PM -0500, Gary R Hook wrote:
> > Version 5 CCPs have some new requirements for XTS-AES: the type field
> > must be specified, and the key requires 512 bits, with each part
> > occupying 256 bits and padded with zeroes.
> >
> > cc: <stable@vger.kernel.org> # 4.9.x+
> >
> > Signed-off-by: Gary R Hook <ghook@amd.com>
>
> Patch applied.  Thanks.

Herbert,

*ping*

This is a bug fix, Could we push this into 4.13, please?

Gary

  parent reply	other threads:[~2017-08-18 16:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 20:08 [PATCH] crypto: ccp - Fix XTS-AES support on a version 5 CCP Gary R Hook
2017-07-17 21:48 ` Tom Lendacky
2017-07-21 15:48   ` Gary R Hook
2017-08-18 16:19   ` Gary R Hook
2017-08-18 16:38     ` Gary R Hook
2017-08-18 16:41     ` Gary R Hook [this message]
2017-08-19  4:02       ` [PATCH] crypto: ccp - Fix XTS-AES-128 support on v5 CCPs Herbert Xu
2017-08-22 18:24         ` Gary R Hook
2017-07-18  6:28 ` [PATCH] crypto: ccp - Fix XTS-AES support on a version 5 CCP Stephan Müller
2017-07-18 17:39   ` Gary R Hook
  -- strict thread matches above, loose matches on Subject: below --
2017-07-25 19:12 [PATCH] crypto: ccp - Fix XTS-AES-128 support on v5 CCPs Gary R Hook
2017-08-03  6:27 ` 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=32d0b50e-e5d5-6041-0ee9-f8384c7c79a3@amd.com \
    --to=gary.hook@amd.com \
    --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