linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yashpal Dutta <yashpal.dutta@freescale.com>
Cc: linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] crypto: caam - map src buffer before access
Date: Fri, 20 Sep 2013 08:18:45 -0700	[thread overview]
Message-ID: <20130920151845.GA4420@kroah.com> (raw)
In-Reply-To: <1379699647-10680-1-git-send-email-yashpal.dutta@freescale.com>

On Fri, Sep 20, 2013 at 11:24:07PM +0530, Yashpal Dutta wrote:
> KMap the buffers before copying trailing bytes during hmac into a session
> temporary buffer. This is required if pinned buffer from user-space is send
> during hmac and is safe even if hmac request is generated from within kernel.
> 
> Signed-off-by: Yashpal Dutta <yashpal.dutta@freescale.com>
> Reviewed-by: Vakul Garg <vakul@freescale.com>
> Reviewed-by: Horia Geanta <horia.geanta@freescale.com> 
> ---
> Patch covers review comments on first version of patch.
> ./scripts/checkpatch.pl --strict 0001-crypto-caam-map-src-buffer-before-access.patch 
> 
> total: 0 errors, 0 warnings, 0 checks, 62 lines checked
> 
> The patch fixes driver crashes when a pinned buffer from user-space is sent to CAAM driver
> for HMAC processing.
> 
>  drivers/crypto/caam/sg_sw_sec4.h |   34 +++++++++++++++++++++++++---------
>  1 file changed, 25 insertions(+), 9 deletions(-)


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

      reply	other threads:[~2013-09-20 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 17:54 [PATCH v3] crypto: caam - map src buffer before access Yashpal Dutta
2013-09-20 15:18 ` 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=20130920151845.GA4420@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yashpal.dutta@freescale.com \
    /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).