[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160905075239.GR10153@twins.programming.kicks-ass.net>
Date: Mon, 5 Sep 2016 09:52:39 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: x86@...nel.org, Borislav Petkov <bp@...e.de>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Richard Cochran <rcochran@...utronix.de>,
Stephane Eranian <eranian@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tony Luck <tony.luck@...el.com>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Julia Lawall <julia.lawall@...6.fr>,
Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [PATCH 1/4] perf/x86/cqm: Use kmalloc_array() in intel_mbm_init()
On Sun, Sep 04, 2016 at 07:54:47PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring <elfring@...rs.sourceforge.net>
> Date: Sun, 4 Sep 2016 17:28:13 +0200
>
> * 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 structure by a pointer dereference
> to make the corresponding size determination a bit safer according to
> the Linux coding style convention.
Again, lack of actual reason..
Powered by blists - more mailing lists