From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Gil Fruchter <gilf@ezchip.com>
Subject: [for-next][PATCH 01/13] tracing: Prefer kcalloc over kzalloc with multiply
Date: Tue, 21 Jul 2015 15:14:19 -0400 [thread overview]
Message-ID: <20150721191436.332302326@goodmis.org> (raw)
In-Reply-To: <20150721191418.772796260@goodmis.org>
[-- Attachment #1: 0001-tracing-Prefer-kcalloc-over-kzalloc-with-multiply.patch --]
[-- Type: text/plain, Size: 951 bytes --]
From: Gil Fruchter <gilf@ezchip.com>
Use kcalloc for allocating an array instead of kzalloc with multiply,
as that is what kcalloc is used for.
Found with checkpatch.
Link: http://lkml.kernel.org/r/1433835155-6894-2-git-send-email-gilf@ezchip.com
Signed-off-by: Gil Fruchter <gilf@ezchip.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/trace/trace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index abcbf7ff8743..5d219384b4d1 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -3035,7 +3035,7 @@ __tracing_open(struct inode *inode, struct file *file, bool snapshot)
if (!iter)
return ERR_PTR(-ENOMEM);
- iter->buffer_iter = kzalloc(sizeof(*iter->buffer_iter) * num_possible_cpus(),
+ iter->buffer_iter = kcalloc(num_possible_cpus(), sizeof(*iter->buffer_iter),
GFP_KERNEL);
if (!iter->buffer_iter)
goto release;
--
2.1.4
next prev parent reply other threads:[~2015-07-21 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 19:14 [for-next][PATCH 00/13] tracing: Updates for 4.3 Steven Rostedt
2015-07-21 19:14 ` Steven Rostedt [this message]
2015-07-21 19:14 ` [for-next][PATCH 02/13] tracing: Fix for non-continuous cpu ids Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 03/13] ftrace: correct the counter increment for trace_buffer data Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 04/13] ring-buffer: Add event descriptor to simplify passing data Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 05/13] ring-buffer: Move the adding of the extended timestamp out of line Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 06/13] ring-buffer: Get timestamp after event is allocated Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 07/13] ring-buffer: Make sure event has enough room for extend and padding Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 08/13] ring-buffer: Reorganize function locations Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 09/13] tracing: Clean up stack tracing and fix fentry updates Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 10/13] ftrace: add tracing_thresh to function profile Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 11/13] ftrace: Fix function_graph duration spacing with 7-digits Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 12/13] tracing: Introduce two additional marks for delay Steven Rostedt
2015-07-21 19:14 ` [for-next][PATCH 13/13] ftrace: Format MCOUNT_ADDR address as type unsigned long Steven Rostedt
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=20150721191436.332302326@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=gilf@ezchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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®