All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Ariel Rodriguez <arodriguez-Ze/REwZ+V9sqDJ6do+/SaQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: SEGMENTATION FAULT in kni example : kni_free_kni() call
Date: Wed, 29 Oct 2014 09:35:26 +0100	[thread overview]
Message-ID: <5223956.lFdNUbkl0D@xps13> (raw)
In-Reply-To: <CADoa0bbog5n7gsPU7013Jp8d584dCh_pT+w+pxCVtWMjnLkOGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi,

2014-10-28 23:07, Ariel Rodriguez:
> Hi, im trying the kni example. When i hit ctrl-c in the terminal  stopping
> the example, the os signals  with a segmentation fault.
[...]
> The following change fix that issue:
> 
> static int kni_free_kni(uint8_t port_id) {
> uint8_t i;
> struct kni_port_params **p = kni_port_params_array;
> 
> if (port_id >= RTE_MAX_ETHPORTS || !p[port_id])
> return -1;
> 
> ++ for (i = 0; i < p[port_id]->nb_kni; i++) {
> ++ rte_kni_release(p[port_id]->kni[i]);
> ++ p[port_id]->kni[i] = NULL;
> }
> rte_eth_dev_stop(port_id);
> 
> return 0;
> }
> 
> Sorry for the basic of my fix ... i dont know  the correct style to report
> this kind of issues... im just a user of the dpdk library ... but i meet
> this bug ...

Thank you for reporting it.
If you want to send an applicable patch, the procedure is described here:
	http://dpdk.org/dev#send

-- 
Thomas

  parent reply	other threads:[~2014-10-29  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  2:07 SEGMENTATION FAULT in kni example : kni_free_kni() call Ariel Rodriguez
     [not found] ` <CADoa0bbog5n7gsPU7013Jp8d584dCh_pT+w+pxCVtWMjnLkOGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-10-29  8:35   ` Thomas Monjalon [this message]
2014-10-29  8:42     ` Zhang, Helin

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=5223956.lFdNUbkl0D@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=arodriguez-Ze/REwZ+V9sqDJ6do+/SaQ@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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.