DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org,
	"Phil Yang (Arm Technology China)" <Phil.Yang@arm.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"he.qiao17@zte.com.cn" <he.qiao17@zte.com.cn>,
	Igor Ryzhov <iryzhov@nfware.com>, Dan Gora <dg@adax.com>
Subject: Re: [dpdk-dev] [PATCH] examples/kni: fix crash while handling userspace request
Date: Thu, 17 Jan 2019 23:48:25 +0100	[thread overview]
Message-ID: <15486437.2BuXh0EO9Z@xps> (raw)
In-Reply-To: <DB7PR08MB33857C6D4F4085394775F9DCE9820@DB7PR08MB3385.eurprd08.prod.outlook.com>

> > When KNI interface receives RTE_KNI_REQ_CFG_NETWORK_IF request, it
> > stap/start the physical device which as a result of stop() can free all the mbufs in
> > its queue.
> > Meanwhile sample application continues to read from KNI interface queues and
> > push into device queues. This simultaneous access may cause a crash, crash log
> > can be found at defect description.
> >
> > As a solution KNI sample application can do the proper synchronization, and
> > stop transfer between KNI interface and physical interface while physical device
> > stop/started.
> >
> > Bugzilla ID: 116
> > Fixes: 3fc5ca2f6352 ("kni: initial import")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> 
> Acked-by: Phil Yang <phil.yang@arm.com>

Applied, thanks

      reply	other threads:[~2019-01-17 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 17:28 Ferruh Yigit
2019-01-16  6:34 ` Phil Yang (Arm Technology China)
2019-01-17 22:48   ` 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=15486437.2BuXh0EO9Z@xps \
    --to=thomas@monjalon.net \
    --cc=Phil.Yang@arm.com \
    --cc=dev@dpdk.org \
    --cc=dg@adax.com \
    --cc=ferruh.yigit@intel.com \
    --cc=he.qiao17@zte.com.cn \
    --cc=iryzhov@nfware.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 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).