From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 4.14.y] crypto: tcrypt - fix S/G table for test_aead_speed()
Date: Fri, 9 Feb 2018 08:16:05 +0100 [thread overview]
Message-ID: <20180209071605.GA7767@kroah.com> (raw)
In-Reply-To: <VI1PR0402MB334243FCF777BCD0F6B4C01C98F20@VI1PR0402MB3342.eurprd04.prod.outlook.com>
On Fri, Feb 09, 2018 at 06:11:59AM +0000, Horia Geantă wrote:
> On 2/8/2018 6:56 PM, Greg Kroah-Hartman wrote:
> > On Thu, Feb 08, 2018 at 09:28:31AM +0200, Horia Geantă wrote:
> >> From: Robert Baronescu <robert.baronescu@nxp.com>
> >>
> >> commit 5c6ac1d4f8fbdbed65dbeb8cf149d736409d16a1 upstream.
> >>
> >> In case buffer length is a multiple of PAGE_SIZE,
> >> the S/G table is incorrectly generated.
> >> Fix this by handling buflen = k * PAGE_SIZE separately.
> >>
> >> Signed-off-by: Robert Baronescu <robert.baronescu@nxp.com>
> >> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> >> Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
> >> ---
> >> crypto/tcrypt.c | 6 ++++--
> >> 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > Why just 4.14.y? I also queued this up for everything else (4.15.y,
> > 4.9.y, and 4.4.y).
> >
> The issue is not observed unless upstream commit
> 7aacbfcb331c ("crypto: tcrypt - fix buffer lengths in test_aead_speed()")
> is also applied.
Shouldn't that patch also be applied to all of the stable trees?
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-09 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 7:28 [PATCH 4.14.y] crypto: tcrypt - fix S/G table for test_aead_speed() Horia Geantă
2018-02-08 16:56 ` Greg Kroah-Hartman
2018-02-09 6:11 ` Horia Geantă
2018-02-09 7:16 ` Greg Kroah-Hartman [this message]
2018-02-09 7:39 ` Horia Geantă
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=20180209071605.GA7767@kroah.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox