From: Markus Elfring <Markus.Elfring@web.de>
To: Qiujun Huang <hqjagain@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Oliver O'Halloran <oohall@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Christophe Leroy <christophe.leroy@c-s.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] powerpc/powernv: add NULL check after kzalloc in opal_add_one_export
Date: Mon, 6 Apr 2020 14:00:12 +0200 [thread overview]
Message-ID: <b7d64d4a-74dd-ee21-db7b-018070f1295f@web.de> (raw)
In-Reply-To: <CAJRQjoeTYg6NnxwvXusU6fdOFOmOiceokYJZQ23-0YQo_yqZ5w@mail.gmail.com>
>>> Here needs a NULL check as kzalloc may fail returning NULL.
I find this wording potentially confusing.
* Such function calls will usually succeed to return a pointer.
* The desired memory allocation can fail.
* Please choose an imperative wording for the change description.
>>> Issue was found by coccinelle.
Please omit this line after the addition for the reference to the SmPL script.
>>> Generated by: scripts/coccinelle/null/kmerr.cocci
…
>>> Reviewed-by: Oliver O'Halloran <oohall@gmail.com>
I wonder about this tag because of requested changes for the shown patch approach.
I recommend to add the tag “Fixes”.
>> Thanks for putting up with all the review comments :)
This seems to become challenging here.
>> But I think this should actually be two patches now.
…
> Get that, I'll separate them.
I wonder why it was not directly tried in this patch version.
>>> v3->v4:
I suggest to apply a shorter version numbering format (without an arrow).
Regards,
Markus
prev parent reply other threads:[~2020-04-06 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 9:39 [PATCH v4] powerpc/powernv: add NULL check after kzalloc in opal_add_one_export Qiujun Huang
2020-04-06 10:30 ` Michael Ellerman
2020-04-06 10:43 ` Qiujun Huang
2020-04-06 12:00 ` Markus Elfring [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=b7d64d4a-74dd-ee21-db7b-018070f1295f@web.de \
--to=markus.elfring@web.de \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=hqjagain@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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