mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 张轶群 <zhangyiqun@phytium.com.cn>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] crypto: all - alloc and init all req alloc as zero
Date: Fri, 28 Jul 2023 17:06:21 +0800 (GMT+08:00)	[thread overview]
Message-ID: <6c3f5deb.197.1899bbfbd6f.Coremail.zhangyiqun@phytium.com.cn> (raw)
In-Reply-To: <ZMIl1vSitJBU3UJS@gondor.apana.org.au>

Actually, I met a problem in my own development. Because some members in req
struct is not intialized, they cause some errors in test. If we change kmalloc
to kzalloc, it can facilitate all developers to care about inialized all 
members. I hope my idea can convince you. But I think you have other
important consideration.

Thanks,

> -----Original Messages-----
> From: "Herbert Xu" <herbert@gondor.apana.org.au>
> Send time:Thursday, 07/27/2023 16:07:50
> To: "Zhang Yiqun" <zhangyiqun@phytium.com.cn>
> Cc: davem@davemloft.net, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] crypto: all - alloc and init all req alloc as zero
> 
> On Thu, Jul 27, 2023 at 04:05:48PM +0800, Zhang Yiqun wrote:
> > This patch is to change all req struct alloc function from kmalloc
> > to kzalloc. Sometimes, it will incur some errors without initialized
> > zero.
> > 
> > Signed-off-by: Zhang Yiqun <zhangyiqun@phytium.com.cn>
> > ---
> >  include/crypto/akcipher.h | 2 +-
> >  include/crypto/hash.h     | 2 +-
> >  include/crypto/kpp.h      | 2 +-
> >  include/crypto/skcipher.h | 2 +-
> >  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> Nack.  Unless you have a specific issue please don't submit vague
> patches like this.  You should always state what issue led you to
> make a change like this.
> 
> Thanks,
> -- 
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt



信息安全声明:本邮件包含信息归发件人所在组织所有,发件人所在组织对该邮件拥有所有权利。请接收者注意保密,未经发件人书面许可,不得向任何第三方组织和个人透露本邮件所含信息。
Information Security Notice: The information contained in this mail is solely property of the sender's organization.This mail communication is confidential.Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.

      reply	other threads:[~2023-07-28  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  8:05 Zhang Yiqun
2023-07-27  8:07 ` Herbert Xu
2023-07-28  9:06   ` 张轶群 [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=6c3f5deb.197.1899bbfbd6f.Coremail.zhangyiqun@phytium.com.cn \
    --to=zhangyiqun@phytium.com.cn \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®