DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jan Sacha <Jan.Sacha@alcatel-lucent.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] rte_lpm_add in librte_lpm
Date: Fri, 5 Sep 2014 17:14:50 -0700	[thread overview]
Message-ID: <540A51FA.3070905@alcatel-lucent.com> (raw)


Hi,

I've been playing with DPDK and I got some crashes in the LPM module. As 
far as I know, this problem has not been reported yet. These crashes 
happened in DPDK 1.7.0 and 1.6.0r2 (I didn't check other versions) when 
I added new LPM routes.

In the lib/librte_lpm/rte_lpm.c file, line 399 (add_depth_small 
function), there is the following condition:

if (!lpm->tbl24[i].valid || (lpm->tbl24[i].ext_entry == 0 && 
lpm->tbl24[i].depth <= depth))

If the new route has a lower depth than an existing non-extended entry, 
this condition is not met. We then skip to line 418, where we assume the 
entry is extended and use an uninitialized index. Is this a bug?

Thanks,
Jan

                 reply	other threads:[~2014-09-06  0:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=540A51FA.3070905@alcatel-lucent.com \
    --to=jan.sacha@alcatel-lucent.com \
    --cc=dev@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).