stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: cantona@cantona.net, stable@vger.kernel.org, davem@davemloft.net,
	herbert@gondor.apana.org.au, stable-commits@vger.kernel.org
Subject: Re: Patch "crypto: talitos - fix ECB and CBC algs ivsize" has been added to the 4.9-stable tree
Date: Thu, 11 Jun 2020 13:30:30 +0200	[thread overview]
Message-ID: <20200611113030.GA731261@kroah.com> (raw)
In-Reply-To: <b639a842-5654-d719-d28c-9791f8f9cbac@csgroup.eu>

On Thu, Jun 11, 2020 at 01:27:34PM +0200, Christophe Leroy wrote:
> 
> 
> Le 11/06/2020 à 13:21, gregkh@linuxfoundation.org a écrit :
> > 
> > This is a note to let you know that I've just added the patch titled
> > 
> >      crypto: talitos - fix ECB and CBC algs ivsize
> > 
> > to the 4.9-stable tree which can be found at:
> >      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >       crypto-talitos-fix-ecb-and-cbc-algs-ivsize.patch
> > and it can be found in the queue-4.9 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> As far as I can see, the faulty commit e1de42fdfc6a ("crypto: talitos - fix
> ECB algs ivsize") only removed .ivsize = AES_BLOCK_SIZE at a wrong place.
> 
> The other changes (removal of .ivsize = DES_BLOCK_SIZE and .ivsize =
> DES3_EDE_BLOCK_SIZE) are not from the faulty patch.

Now dropped, sorry about that.

greg k-h

      reply	other threads:[~2020-06-11 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1591874497241120@kroah.com>
2020-06-11 11:27 ` Patch "crypto: talitos - fix ECB and CBC algs ivsize" has been added to the 4.9-stable tree Christophe Leroy
2020-06-11 11:30   ` Greg KH [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=20200611113030.GA731261@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cantona@cantona.net \
    --cc=christophe.leroy@csgroup.eu \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=stable-commits@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).