netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: <jakub.kicinski@netronome.com>, <davem@davemloft.net>,
	<anna.schumaker@netapp.com>, <trond.myklebust@hammerspace.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ixgbe: Use memset_explicit directly in crypto cases
Date: Tue, 17 Sep 2019 21:41:15 +0800	[thread overview]
Message-ID: <5D80E27B.9050300@huawei.com> (raw)
In-Reply-To: <98a942fb-0c47-ffa6-4c9c-f30b5d6f750e@cogentembedded.com>

On 2019/9/17 17:59, Sergei Shtylyov wrote:
> Hello!
>
> On 17.09.2019 6:45, zhong jiang wrote:
>
>> It's better to use memset_explicit() to replace memset() in crypto cases.
>
>    But you're using memzero_explicit() below?
Sorry, stupid Oops. I will repost.  Thank for your reminder.

Sincerely,
zhong jiang
>
>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>> ---
>>   drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
>> index 31629fc..7e4f32f 100644
>> --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
>> +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c
>> @@ -960,10 +960,10 @@ int ixgbe_ipsec_vf_add_sa(struct ixgbe_adapter *adapter, u32 *msgbuf, u32 vf)
>>       return 0;
>>     err_aead:
>> -    memset(xs->aead, 0, sizeof(*xs->aead));
>> +    memzero_explicit(xs->aead, sizeof(*xs->aead));
>>       kfree(xs->aead);
>>   err_xs:
>> -    memset(xs, 0, sizeof(*xs));
>> +    memzero_explicit(xs, sizeof(*xs));
>>       kfree(xs);
>>   err_out:
>>       msgbuf[1] = err;
>> @@ -1049,7 +1049,7 @@ int ixgbe_ipsec_vf_del_sa(struct ixgbe_adapter *adapter, u32 *msgbuf, u32 vf)
>>       ixgbe_ipsec_del_sa(xs);
>>         /* remove the xs that was made-up in the add request */
>> -    memset(xs, 0, sizeof(*xs));
>> +    memzero_explicit(xs, sizeof(*xs));
>>       kfree(xs);
>>         return 0;
>
> MBR, Sergei
>
> .
>



      reply	other threads:[~2019-09-17 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17  3:45 [PATCH v2] ixgbe: Use memset_explicit directly in crypto cases zhong jiang
2019-09-17  9:59 ` Sergei Shtylyov
2019-09-17 13:41   ` zhong jiang [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=5D80E27B.9050300@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=anna.schumaker@netapp.com \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=trond.myklebust@hammerspace.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).