[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55CDFA17.3090100@intel.com>
Date: Fri, 14 Aug 2015 07:24:23 -0700
From: Tadeusz Struk <tadeusz.struk@...el.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: keescook@...omium.org, jwboyer@...hat.com, smueller@...onox.de,
richard@....at, steved@...hat.com, linux-kernel@...r.kernel.org,
dhowells@...hat.com, linux-crypto@...r.kernel.org,
james.l.morris@...cle.com, jkosina@...e.cz,
zohar@...ux.vnet.ibm.com, davem@...emloft.net, vgoyal@...hat.com
Subject: Re: [PATCH 2/2] crypto: qat - Don't move data inside output buffer
On 08/13/2015 11:26 PM, Herbert Xu wrote:
> On Thu, Aug 13, 2015 at 11:14:11PM -0700, Tadeusz Struk wrote:
>>
>> Right, but we don't need that anymore.
>
> Why not? If you reduce the size without moving the buffer wouldn't
> it begin with a bunch of zeroes and wouldn't you lose the real bytes
> at the end?
>
If you don't like the first option then we still need this, as you pointed out.
---8<---
Change memcpy to memmove because the copy is done within the same buffer.
diff --git a/drivers/crypto/qat/qat_common/qat_asym_algs.c b/drivers/crypto/qat/qat_common/qat_asym_algs.c
index fe352a6..e87f510 100644
--- a/drivers/crypto/qat/qat_common/qat_asym_algs.c
+++ b/drivers/crypto/qat/qat_common/qat_asym_algs.c
@@ -145,7 +145,7 @@ static void qat_rsa_cb(struct icp_qat_fw_pke_resp *resp)
}
if (areq->dst_len != req->ctx->key_sz)
- memcpy(areq->dst, ptr, areq->dst_len);
+ memmove(areq->dst, ptr, areq->dst_len);
akcipher_request_complete(areq, err);
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists