From: Greg KH <gregkh@linuxfoundation.org>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
stable@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [STABLE PATCH 0/2] crypto: ccree: fixes backport to 4.19
Date: Mon, 20 May 2019 14:07:13 +0200 [thread overview]
Message-ID: <20190520120713.GA13524@kroah.com> (raw)
In-Reply-To: <20190520115025.16457-1-gilad@benyossef.com>
On Mon, May 20, 2019 at 02:50:22PM +0300, Gilad Ben-Yossef wrote:
> Backport of upstream fixes to 4.19.y, which also applies to 5.0.y
> and 5.1.y.
>
> Gilad Ben-Yossef (2):
> crypto: ccree: zap entire sg on aead request unmap
> crypto: ccree: fix backlog notifications
>
> drivers/crypto/ccree/cc_aead.c | 4 ++++
> drivers/crypto/ccree/cc_buffer_mgr.c | 18 ++---------------
> drivers/crypto/ccree/cc_cipher.c | 4 ++++
> drivers/crypto/ccree/cc_hash.c | 28 +++++++++++++++++++--------
> drivers/crypto/ccree/cc_request_mgr.c | 11 ++++++++---
> 5 files changed, 38 insertions(+), 27 deletions(-)
As the "FAILED:" emails said, I need these for 5.1 and 5.0 as well,
can't just move from 4.19 to a newer kernel and have regressions. I'll
go see if these apply there too.
Also, giving me the git commit ids of the original patches in Linus's
tree is necessary, so I don't have to go dig it up by hand. I'll do it
this time...
let me see how this goes...
greg k-h
prev parent reply other threads:[~2019-05-20 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 11:50 [STABLE PATCH 0/2] crypto: ccree: fixes backport to 4.19 Gilad Ben-Yossef
2019-05-20 11:50 ` [STABLE PATCH 1/2] crypto: ccree: zap entire sg on aead request unmap Gilad Ben-Yossef
2019-05-20 12:09 ` Greg KH
2019-05-20 12:17 ` Gilad Ben-Yossef
2019-05-20 11:50 ` [STABLE PATCH 2/2] crypto: ccree: fix backlog notifications Gilad Ben-Yossef
2019-05-20 12:07 ` 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=20190520120713.GA13524@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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).