From: "liaochang (A)" <liaochang1@huawei.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Joe Perches <joe@perches.com>, <apw@canonical.com>,
<dwaipayanray1@gmail.com>, <lukas.bulwahn@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <bagasdotme@gmail.com>,
<pbonzini@redhat.com>
Subject: Re: [PATCH -next v2] checkpatch: Add check for array allocator family argument order
Date: Mon, 7 Nov 2022 09:25:58 +0800 [thread overview]
Message-ID: <017634f7-fa60-64d3-6c4f-e82f4d5e4cbd@huawei.com> (raw)
In-Reply-To: <e22ecdd4-5a46-b573-6a41-f0c980722f0b@wanadoo.fr>
在 2022/11/6 5:36, Christophe JAILLET 写道:
>
> Le 05/11/2022 à 18:24, Joe Perches a écrit :
>> On Fri, 2022-11-04 at 18:08 +0100, Christophe JAILLET wrote:
>>> Le 04/11/2022 à 08:05, Liao Chang a écrit :
>>>> These array allocator family are sometimes misused with the first and
>>>> second arguments switchted.
>>>>
>>>> Same issue with calloc, kvcalloc, kvmalloc_array etc.
>>>>
>>>> Bleat if sizeof is the first argument.
>>>>
>>>> Link: https://lore.kernel.org/lkml/5374345c-7973-6a3c-d559-73bf4ac15079@redhat.com/
>>>> Signed-off-by: Liao Chang <liaochang1@huawei.com>
>>>> Acked-by: Joe Perches <joe@perches.com>
>>>> ---
>>>> v2:
>>>> 1. Acked-by Joe Perches.
>>>> 2. Use lore links in Link tag.
>>>>
>>>> ---
>>>> scripts/checkpatch.pl | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>>>> index 1e5e66ae5a52..a9a9dc277cff 100755
>>>> --- a/scripts/checkpatch.pl
>>>> +++ b/scripts/checkpatch.pl
>>>> @@ -7128,7 +7128,7 @@ sub process {
>>>> }
>>>> # check for alloc argument mismatch
>>>> - if ($line =~ /\b((?:devm_)?(?:kcalloc|kmalloc_array))\s*\(\s*sizeof\b/) {
>>>> + if ($line =~ /\b((?:devm_)?((?:k|kv)?(calloc|malloc_array)(?:_node)?))\s*\(\s*sizeof\b/) {
>>>> WARN("ALLOC_ARRAY_ARGS",
>>>> "$1 uses number as first arg, sizeof is generally wrong\n" . $herecurr);
>>>> }
>>> Hi,
>>>
>>> Should the devm_ and not devm_ cases be separated?
>>>
>>> In the devm_case, sizeof will never be just after the first '('.
>> Right.
>>
>> Likely this works better:
>> ---
>> scripts/checkpatch.pl | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index 7be93c3df2bcb..7f37976a9f8b5 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -7145,12 +7145,18 @@ sub process {
>> "Reusing the krealloc arg is almost always a bug\n" . $herecurr);
>> }
>> -# check for alloc argument mismatch
>> - if ($line =~ /\b((?:devm_)?(?:kcalloc|kmalloc_array))\s*\(\s*sizeof\b/) {
>> +# check for alloc argument mismatch in alloc functions
>> + if ($line =~ /\b(((?:k|kv)?(calloc|malloc_array)(?:_node)?))\s*\(\s*sizeof\b/) {
>> WARN("ALLOC_ARRAY_ARGS",
>> "$1 uses number as first arg, sizeof is generally wrong\n" . $herecurr);
>> }
>> +# check for alloc argument mismatch in devm_ alloc functions
>> + if ($line =~ /\b(devm_((?:k|kv)?(calloc|malloc_array)(?:_node)?))\s*\(\s*$FuncArg\s*,\s*sizeof\b/) {
>> + WARN("ALLOC_ARRAY_ARGS",
>> + "$1 uses number as second arg, sizeof is generally wrong\n" . $herecurr);
>> + }
>> +
>> # check for multiple semicolons
>> if ($line =~ /;\s*;\s*$/) {
>> if (WARN("ONE_SEMICOLON",
>>
> +1
>
+1, thanks.
BTW, i find the v2 has been added to the -mm mm-nonmm-unstable branch,
do i need to submit new version includes above change?
>
> .
--
BR,
Liao, Chang
prev parent reply other threads:[~2022-11-07 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 7:05 Liao Chang
2022-11-04 8:35 ` Lukas Bulwahn
2022-11-04 14:33 ` Joe Perches
2022-11-07 1:25 ` liaochang (A)
2022-11-04 17:08 ` Christophe JAILLET
2022-11-05 17:24 ` Joe Perches
2022-11-05 21:36 ` Christophe JAILLET
2022-11-07 1:25 ` liaochang (A) [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=017634f7-fa60-64d3-6c4f-e82f4d5e4cbd@huawei.com \
--to=liaochang1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=bagasdotme@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pbonzini@redhat.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
all inboxes | Powered by JetHome®