From: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] fix segfault seen with performance-thread example
Date: Mon, 15 Jul 2019 10:39:30 -0500 [thread overview]
Message-ID: <1563205172-352-1-git-send-email-erik.g.carrillo@intel.com> (raw)
A crash occurs in the examples/performance-thread/l3fwd-thread when it calls
into rte_timer_manage() from the LThread library it utilizes. This happens
because the application omitted a call to rte_timer_subsystem_init(), which
leaves a pointer set to null in the timer library. This pointer is
dereferenced in a check for validity of a timer data object, resulting in
the segfault. This series fixes the validity check in the timer library,
and adds the missing call to rte_timer_subsystem_init in the application.
Erik Gabriel Carrillo (2):
timer: fix null pointer dereference
examples/performance-thread: init timer subsystem
examples/performance-thread/l3fwd-thread/main.c | 5 +++++
lib/librte_timer/rte_timer.c | 3 ++-
2 files changed, 7 insertions(+), 1 deletion(-)
--
2.6.4
next reply other threads:[~2019-07-15 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 15:39 Erik Gabriel Carrillo [this message]
2019-07-15 15:39 ` [dpdk-dev] [PATCH 1/2] timer: fix null pointer dereference Erik Gabriel Carrillo
2019-07-15 15:48 ` Stephen Hemminger
2019-07-15 16:04 ` Carrillo, Erik G
2019-07-15 19:48 ` Carrillo, Erik G
2019-07-16 8:31 ` Bruce Richardson
2019-07-16 14:58 ` Carrillo, Erik G
2019-07-15 15:39 ` [dpdk-dev] [PATCH 2/2] examples/performance-thread: init timer subsystem Erik Gabriel Carrillo
2019-07-18 21:20 ` [dpdk-dev] [PATCH 0/2] fix segfault seen with performance-thread example Thomas Monjalon
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=1563205172-352-1-git-send-email-erik.g.carrillo@intel.com \
--to=erik.g.carrillo@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).