From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: dan.carpenter@oracle.com, linux-kernel@vger.kernel.org,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/2] A couple hist trigger fixes
Date: Mon, 25 Apr 2016 14:01:26 -0500 [thread overview]
Message-ID: <cover.1461610073.git.tom.zanussi@linux.intel.com> (raw)
These are a couple of small fixes for problems pointed out by Dan
Carpenter.
patch 1, pointed out by Smatch though not actually a bug, cleans up
the code to explicitly check for something that was implied. Thanks
to Steve Rostedt for suggesting the fix.
patch 2 fixes a PTR_ERR problem similar to the one previously
reported by Dan.
The following changes since commit d50c744ecde7ee3ba4d7ffb0e1c55e7a2f6bbc8e:
tracing: Fix unsigned comparison to zero in hist trigger code (2016-04-19 18:56:05 -0400)
are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/hist-trigger-err-fixes
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/hist-trigger-err-fixes
Tom Zanussi (2):
tracing: Add check for NULL event field when creating hist field
tracing: Handle tracing_map_alloc_elts() error path correctly
kernel/trace/trace_events_hist.c | 3 +++
kernel/trace/tracing_map.c | 8 ++++++--
2 files changed, 9 insertions(+), 2 deletions(-)
--
1.9.3
next reply other threads:[~2016-04-25 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 19:01 Tom Zanussi [this message]
2016-04-25 19:01 ` [PATCH 1/2] tracing: Add check for NULL event field when creating hist field Tom Zanussi
2016-04-25 19:01 ` [PATCH 2/2] tracing: Handle tracing_map_alloc_elts() error path correctly Tom Zanussi
2016-04-26 13:41 ` [PATCH 0/2] A couple hist trigger fixes 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=cover.1461610073.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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.