DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/4] bnxt: Fix a segfault encountered during KNI exit
Date: Mon, 10 Oct 2016 13:41:27 -0500	[thread overview]
Message-ID: <CACZ4nhvibTB3FiLZsoFS7SpBu57nwrzxzUCXN736X7d68Dwh8g@mail.gmail.com> (raw)
In-Reply-To: <91ebdd13-b556-dc9b-5488-a38483b16733@intel.com>

On Mon, Oct 10, 2016 at 10:24 AM, Ferruh Yigit <ferruh.yigit@intel.com>
wrote:

> On 9/29/2016 8:06 PM, Ajit Khaparde wrote:
> > On Thu, Sep 29, 2016 at 12:41 PM, Ferruh Yigit <ferruh.yigit@intel.com
> > <mailto:ferruh.yigit@intel.com>>wrote:
> >
> >     On 9/29/2016 6:03 PM, Ajit Khaparde wrote:
> >     > The bnxt PMD is running into a segfault when exiting out of KNI
> >
> >     KNI?
> >
> > examples/kni
> >
> > ​On closing the kni app, I am seeing a segfault.​ because of improper
> > cleanup of resources
> > in the dev_uninit path.
>
> So this is mainly related to driver exit, KNI app is just a way to
> reproduce it.
>
> Are you OK with following update in commit log:
>
> "
> net/bnxt: fix a segfault encountered during PMD exit
>
> This patch fixes segfault encountered during dev_uninit/close routine.
> KNI sample app can be used to reproduce the issue.
> "
>
​I am OK with this Ferruh.

Thanks​

      reply	other threads:[~2016-10-10 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 17:03 Ajit Khaparde
2016-09-29 17:41 ` Ferruh Yigit
2016-09-29 19:06   ` Ajit Khaparde
2016-10-10 15:24     ` Ferruh Yigit
2016-10-10 18:41       ` Ajit Khaparde [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=CACZ4nhvibTB3FiLZsoFS7SpBu57nwrzxzUCXN736X7d68Dwh8g@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /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).