From: "linwenkai (C)" <linwenkai6@hisilicon.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Chenghai Huang <huangchenghai2@huawei.com>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<linux-crypto@vger.kernel.org>, <liulongfang@huawei.com>,
<qianweili@huawei.com>, <wangzhou1@hisilicon.com>
Subject: Re: [PATCH v3 2/2] crypto: hisilicon/sec2 - fix for aead invalid authsize
Date: Thu, 14 Nov 2024 20:47:11 +0800 [thread overview]
Message-ID: <b67cecd0-e50c-40bd-99b7-b85482e55696@hisilicon.com> (raw)
In-Reply-To: <ZzAqQhiebKSuRzOm@gondor.apana.org.au>
在 2024/11/10 11:36, Herbert Xu 写道:
> On Sat, Nov 02, 2024 at 10:55:59AM +0800, Chenghai Huang wrote:
>> @@ -2226,15 +2236,15 @@ static int sec_aead_spec_check(struct sec_ctx *ctx, struct sec_req *sreq)
>> struct device *dev = ctx->dev;
>> int ret;
>>
>> - if (unlikely(req->cryptlen + req->assoclen > MAX_INPUT_DATA_LEN ||
>> - req->assoclen > SEC_MAX_AAD_LEN)) {
>> - dev_err(dev, "aead input spec error!\n");
>> + /* Hardware does not handle cases where authsize is less than 4 bytes */
>> + if (unlikely(sz < MIN_MAC_LEN)) {
>> + ctx->a_ctx.fallback = true;
> This is broken. sec_aead_spec_check is a per-request function,
> called without any locking. Therefore it must not modify any
> field in the tfm context (at least not without additional locking),
> because multiple requests can be issued on the same tfm at any time.
>
> I suppose for this field in particular you could move it to
> set_authsize and there it would be safe to change the tfm context.
>
> Cheers,
Hi,
I have found another setup for fallback in the sec_aead_param_check
function, so I need to fix it right too.
The orignal code:
static int sec_aead_param_check(struct sec_ctx *ctx, struct sec_req *sreq)
{
if (ctx->sec->qm.ver == QM_HW_V2) {
if (unlikely(!req->cryptlen || (!sreq->c_req.encrypt &&
req->cryptlen <= authsize))) {
ctx->a_ctx.fallback = true;
return -EINVAL;
}
}
}
After the modification, I used a temporary variable fallback to save the
state:
static int sec_aead_param_check(struct sec_ctx *ctx, struct sec_req
*sreq, bool *fallback)
{
if (ctx->sec->qm.ver == QM_HW_V2) {
if (unlikely(!req->cryptlen || (!sreq->c_req.encrypt &&
req->cryptlen <= authsize))) {
*fallback = true;
return -EINVAL;
}
}
}
Same with the sec_aead_spec_check function.
static int sec_aead_spec_check(struct sec_ctx *ctx, struct sec_req
*sreq, bool *fallback) {
/* Hardware does not handle cases where authsize is less than 4
bytes */
if (unlikely(sz < MIN_MAC_LEN)) {
*fallback = true;
return -EINVAL;
}
}
Do you think it is a better way?
Thanks,
next prev parent reply other threads:[~2024-11-14 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 2:55 [PATCH v3 0/2] crypto: hisilicon - fix the authsize and icv problems of aead in sec Chenghai Huang
2024-11-02 2:55 ` [PATCH v3 1/2] crypto: hisilicon/sec2 - fix for aead icv error Chenghai Huang
2024-11-02 2:55 ` [PATCH v3 2/2] crypto: hisilicon/sec2 - fix for aead invalid authsize Chenghai Huang
2024-11-10 3:36 ` Herbert Xu
2024-11-12 2:46 ` linwenkai (C)
2024-11-14 12:47 ` linwenkai (C) [this message]
2024-11-15 2:09 ` Herbert Xu
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=b67cecd0-e50c-40bd-99b7-b85482e55696@hisilicon.com \
--to=linwenkai6@hisilicon.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=huangchenghai2@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=wangzhou1@hisilicon.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