From: Gil Fruchter <gilf@ezchip.com>
To: <rostedt@goodmis.org>, <mingo@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <giladb@ezchip.com>,
<cmetcalf@ezchip.com>, <noamc@ezchip.com>,
Gil Fruchter <gilf@ezchip.com>
Subject: [PATCH v2 0/2] Fix tracing with non-continuous cpu ids
Date: Tue, 9 Jun 2015 10:32:33 +0300 [thread overview]
Message-ID: <1433835155-6894-1-git-send-email-gilf@ezchip.com> (raw)
In-Reply-To: <1433251589-21013-1-git-send-email-gilf@ezchip.com>
Currently exception occures due to access beyond buffer_iter
range while using index of cpu bigger than num_possible_cpus().
In order to fix buffer allocation size for non-continuous cpu ids
we allocate according to the max cpu id and not according to the
amount of possible cpus.
This series also includes a checkpatch warning fix for using
kzalloc with multiply instead of kcalloc.
Happy tracing,
Gil
v2:
Update commit description for patch 1/2.
Gil Fruchter (2):
tracing: Prefer kcalloc over kzalloc with multiply
tracing: Fix for non-continuous cpu ids
kernel/trace/trace.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next prev parent reply other threads:[~2015-06-09 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:26 [PATCH 0/2] Fix tracing with non-continuous cpu ids Gil Fruchter
2015-06-02 13:26 ` [PATCH 1/2] tracing: Prefer kcalloc over kzalloc with multiply Gil Fruchter
2015-06-02 14:15 ` Steven Rostedt
2015-06-03 11:53 ` Gil Fruchter
2015-06-08 15:21 ` Steven Rostedt
2015-06-02 13:26 ` [PATCH 2/2] tracing: Fix for non-continuous cpu ids Gil Fruchter
2015-06-02 14:26 ` Steven Rostedt
2015-06-02 15:47 ` Gilad Ben-Yossef
2015-06-09 7:32 ` Gil Fruchter [this message]
2015-06-09 7:32 ` [PATCH v2 1/2] tracing: Prefer kcalloc over kzalloc with multiply Gil Fruchter
2015-06-09 7:32 ` [PATCH v2 2/2] tracing: Fix for non-continuous cpu ids Gil Fruchter
2015-07-13 16:12 ` Steven Rostedt
2015-07-14 10:12 ` Gil Fruchter
2015-07-14 13:22 ` 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=1433835155-6894-1-git-send-email-gilf@ezchip.com \
--to=gilf@ezchip.com \
--cc=cmetcalf@ezchip.com \
--cc=giladb@ezchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=noamc@ezchip.com \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.