dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Bug 285] rte_table unit test crashes in ipv6
Date: Tue, 18 Jun 2019 12:45:54 +0200	[thread overview]
Message-ID: <CAJFAV8x7itAiB-n0TMrFdMvV7_ySc7PE6rxVHpj3QPWA_0xDkw@mail.gmail.com> (raw)
In-Reply-To: <bug-285-3@http.bugs.dpdk.org/>

Hello Christian,

Could you have a look at this?
Is there someone working on it?
We will have to disable the table unit tests in CI otherwise.


Thanks.

-- 
David Marchand

On Mon, May 27, 2019 at 6:50 PM <bugzilla@dpdk.org> wrote:

> https://bugs.dpdk.org/show_bug.cgi?id=285
>
>             Bug ID: 285
>            Summary: rte_table unit test crashes in ipv6
>            Product: DPDK
>            Version: unspecified
>           Hardware: All
>                 OS: All
>             Status: CONFIRMED
>           Severity: major
>           Priority: Normal
>          Component: other
>           Assignee: dev@dpdk.org
>           Reporter: david.marchand@redhat.com
>                 CC: cristian.dumitrescu@intel.com
>   Target Milestone: ---
>
> Starting the table_autotest ut on current master, with 2048 hugepages
> available
> and 8 cores triggers a crash in librte_table:
>
> (gdb) run -c 0xff
> Starting program: /home/dmarchan/git/pub/dpdk/./master/app/test -c 0xff
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> EAL: Detected 8 lcore(s)
> EAL: Detected 1 NUMA nodes
> [New Thread 0x7ffff6cc1700 (LWP 28387)]
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> [New Thread 0x7ffff64c0700 (LWP 28388)]
> EAL: No available hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> [New Thread 0x7ffff5cbf700 (LWP 28389)]
> [New Thread 0x7ffff54be700 (LWP 28390)]
> [New Thread 0x7ffff4cbd700 (LWP 28391)]
> [New Thread 0x7ffff44bc700 (LWP 28392)]
> [New Thread 0x7ffff3cbb700 (LWP 28394)]
> [New Thread 0x7ffff34ba700 (LWP 28395)]
> [New Thread 0x7ffff2cb9700 (LWP 28396)]
> EAL: PCI device 0000:00:1f.6 on NUMA socket -1
> EAL:   Invalid NUMA socket, default to 0
> EAL:   probe driver: 8086:15d7 net_e1000_em
> APP: HPET is not enabled, using TSC as default timer
> RTE>>table_autotest
> Getting/Creating the mempool ...
>
> [...]
>
> ************Table tests************
> --------------
> RUNNING TEST - test_table_lpm_combined
> --------------
> Expected 50, got 50
> Expected 0, got 0
> Expected 25, got 25
> Expected 1, got 1
> Expected 0, got 0
> Change entry action
> Expected 0, got 0
> Expected 50, got 50
> delete entry
> TABLE: rte_table_lpm_create: Invalid n_rules
> PIPELINE: rte_pipeline_table_create: Table creation failed
> TABLE: rte_table_lpm_entry_add: invalid depth (0)
> TABLE: rte_table_lpm_entry_add: invalid depth (33)
> --------------
> RUNNING TEST - test_table_lpm_ipv6_combined
> --------------
>
> Program received signal SIGSEGV, Segmentation fault.
> rte_table_lpm_ipv6_entry_add (table=0x100215e40, key=0x7fffffff76a0,
> entry=0x7fffffff7520, key_found=0x7fffffff74dc, entry_ptr=0x7fffffff7530)
>     at
> /home/dmarchan/git/pub/dpdk/lib/librte_table/rte_table_lpm_ipv6.c:236
> 236             lpm->nht_users[nht_pos0] -= nht_pos0_valid;
>
> (gdb) bt
> #0  rte_table_lpm_ipv6_entry_add (table=0x100215e40, key=0x7fffffff76a0,
> entry=0x7fffffff7520, key_found=0x7fffffff74dc, entry_ptr=0x7fffffff7530)
>     at
> /home/dmarchan/git/pub/dpdk/lib/librte_table/rte_table_lpm_ipv6.c:236
> #1  0x00000000004ac437 in test_table_type (table_ops=0xfb4dc0
> <rte_table_lpm_ipv6_ops>, table_args=table_args@entry=0x7fffffff76c0,
> key=<optimized out>, table_packets=table_packets@entry=0x7fffffff76e0,
>     n_ops=0, manage_ops=0x0) at
> /home/dmarchan/git/pub/dpdk/app/test/test_table_combined.c:150
> #2  0x00000000004af476 in test_table_lpm_ipv6_combined () at
> /home/dmarchan/git/pub/dpdk/app/test/test_table_combined.c:379
> #3  0x00000000004a2090 in test_table () at
> /home/dmarchan/git/pub/dpdk/app/test/test_table.c:174
> #4  0x000000000048a05b in cmd_autotest_parsed
> (parsed_result=0x7fffffff7c20,
> cl=<optimized out>, data=<optimized out>) at
> /home/dmarchan/git/pub/dpdk/app/test/commands.c:76
> #5  0x0000000000682f0d in cmdline_parse (cl=cl@entry=0x95b4690,
> buf=0x95b46d8
> "table_autotest \n") at
> /home/dmarchan/git/pub/dpdk/lib/librte_cmdline/cmdline_parse.c:295
> #6  0x0000000000681eb0 in cmdline_valid_buffer (rdl=<optimized out>,
> buf=<optimized out>, size=<optimized out>) at
> /home/dmarchan/git/pub/dpdk/lib/librte_cmdline/cmdline.c:31
> #7  0x0000000000684dc4 in rdline_char_in (rdl=rdl@entry=0x95b46a0, c=10
> '\n')
> at /home/dmarchan/git/pub/dpdk/lib/librte_cmdline/cmdline_rdline.c:421
> #8  0x0000000000681bcc in cmdline_in (cl=cl@entry=0x95b4690,
> buf=buf@entry=0x7fffffffdd20 "\n\377", size=1) at
> /home/dmarchan/git/pub/dpdk/lib/librte_cmdline/cmdline.c:148
> #9  0x000000000068215b in cmdline_interact (cl=cl@entry=0x95b4690) at
> /home/dmarchan/git/pub/dpdk/lib/librte_cmdline/cmdline.c:227
> #10 0x00000000004806cc in main (argc=<optimized out>, argv=<optimized
> out>) at
> /home/dmarchan/git/pub/dpdk/app/test/test.c:184
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

  reply	other threads:[~2019-06-18 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 16:50 [dpdk-dev] [Bug 285] rte_table unit test crashes in ipv6 bugzilla
2019-06-18 10:45 ` David Marchand [this message]
2019-06-28 14:29   ` David Marchand
2019-06-28 14:37     ` Dumitrescu, Cristian
2019-06-28 14:42       ` Pattan, Reshma
2019-06-28 14:45         ` David Marchand

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=CAJFAV8x7itAiB-n0TMrFdMvV7_ySc7PE6rxVHpj3QPWA_0xDkw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=cristian.dumitrescu@intel.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).