From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
x86@kernel.org, Borislav Petkov <bp@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] x86/amd_nb: Use kmalloc_array() in amd_cache_gart()
Date: Sun, 04 Sep 2016 12:23:42 -0700 [thread overview]
Message-ID: <1473017022.5018.58.camel@perches.com> (raw)
In-Reply-To: <3b30d96b-9280-623d-2bcb-c24e2c94e425@users.sourceforge.net>
On Sun, 2016-09-04 at 21:08 +0200, SF Markus Elfring wrote:
> * A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the corresponding function "kmalloc_array".
>
> This issue was detected by using the Coccinelle software.
>
> * Replace the specification of a data type by a pointer dereference
> to make the corresponding size determination a bit safer according to
> the Linux coding style convention.
[]
> diff --git a/arch/x86/kernel/amd_nb.c b/arch/x86/kernel/amd_nb.c
[]
> @@ -226,7 +226,9 @@ static void amd_cache_gart(void)
> if (!amd_nb_has_feature(AMD_NB_GART))
> return;
>
> - flush_words = kmalloc(amd_nb_num() * sizeof(u32), GFP_KERNEL);
> + flush_words = kmalloc_array(amd_nb_num(),
> + sizeof(*flush_words),
> + GFP_KERNEL);
Markus, this sort of change really isn't very useful.
amd_nb_num is a u16 and is really just a count of
northbridges in the system.
It'll never be a particular high number that could
possibly overflow a size_t of num * sizeof(u32).
Detecting an inconsistency is different than an issue
that has any real significance.
Please stop blindly converting these from one form to
another. Please inspect these potential changes
first and find instances where this conversion could
actually matter before sending auto-generated patches.
prev parent reply other threads:[~2016-09-04 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 19:08 [PATCH] x86/amd_nb: Use kmalloc_array() in amd_cache_gart() SF Markus Elfring
2016-09-04 19:23 ` Joe Perches [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=1473017022.5018.58.camel@perches.com \
--to=joe@perches.com \
--cc=bp@suse.de \
--cc=elfring@users.sourceforge.net \
--cc=hpa@zytor.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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