From: Kim Phillips <kim.phillips@linaro.org>
To: yashpal.dutta@freescale.com
Cc: linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4] crypto: caam - map src buffer before access
Date: Mon, 23 Sep 2013 13:51:34 -0500 [thread overview]
Message-ID: <20130923135134.23a7462d143b8e2a1f0cc165@linaro.org> (raw)
In-Reply-To: <1379753795-14949-1-git-send-email-yashpal.dutta@freescale.com>
On Sat, 21 Sep 2013 14:26:35 +0530
Yashpal Dutta <yashpal.dutta@freescale.com> 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.
it may be "safe" but it adversely affects performance for AF_ALG users,
no?
why does ocf-linux need this, and not AF_ALG? Is a patch to ocf-linux
more appropriate here?
> Cc:stable@vger.kernel.org
fyi, this violates the following rule in
Documentation/stable_kernel_rules.txt:
- It or an equivalent fix must already exist in Linus' tree (upstream).
Kim
next prev parent reply other threads:[~2013-09-23 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 8:56 [PATCH v4] crypto: caam - map src buffer before access Yashpal Dutta
2013-09-23 18:51 ` Kim Phillips [this message]
2013-09-24 9:07 ` 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=20130923135134.23a7462d143b8e2a1f0cc165@linaro.org \
--to=kim.phillips@linaro.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).