All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	stable@dpdk.org,
	"pbhagavatula@caviumnetworks.com"
	<pbhagavatula@caviumnetworks.com>,
	"Zhou, JunX W" <junx.w.zhou@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] examples/eventdev_pipeline: fix segfault on exit
Date: Mon, 11 May 2020 18:39:21 +0200	[thread overview]
Message-ID: <1711809.BzM5BlMlMQ@thomas> (raw)
In-Reply-To: <EDA4914C4BAB5848BD29F696B5FE612D0441A3A6@CDSMSX102.ccr.corp.intel.com>

07/05/2020 12:07, Zhou, JunX W:
> From: Van Haaren, Harry 
> > This commit fixes a segfault on exit by using Ctrl^C if the master lcore
> > was also being used as a worker core. The root cause of the issue was
> > that the interrupt handler was cleaning up resources such as the ethdev
> > and eventdev ports, and once the interrupt handler would return, that
> > thread would continue working as an eventdev worker, and dereference the
> > memory which just had free() called on it.
> > 
> > Fixed by moving the cleanup code from the interrupt handler to the cleanup
> > stage of main(), which the master thread will execute once it has
> > returned from its worker() functionality.
> > 
> > Fixes: 085edac2ca38 ("examples/eventdev_pipeline: support Tx adapter")
> > 
> > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> Tested-by: Zhou, JunX W <junx.w.zhou@intel.com>

Applied, thanks



      reply	other threads:[~2020-05-11 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05  9:39 [dpdk-dev] [PATCH] examples/eventdev_pipeline: fix segfault on exit Harry van Haaren
2020-05-07 10:07 ` Zhou, JunX W
2020-05-11 16:39   ` Thomas Monjalon [this message]

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=1711809.BzM5BlMlMQ@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=harry.van.haaren@intel.com \
    --cc=junx.w.zhou@intel.com \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=stable@dpdk.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.