All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1465] rte_bpf_load() hangs with six IPv6 addresses in the filter causing dumpcap to fail
Date: Wed, 19 Jun 2024 08:42:30 +0000	[thread overview]
Message-ID: <bug-1465-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1465

            Bug ID: 1465
           Summary: rte_bpf_load() hangs with six IPv6 addresses in the
                    filter causing dumpcap to fail
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: iboukris@gmail.com
  Target Milestone: ---

Original thread on the users list (with all the dumpcap related details):
https://mails.dpdk.org/archives/users/2024-June/007702.html

Example filter causing the problem:
"host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1"

The simplest way to reproduce is by using the test-suite, by adding the filter
above to the 'sample_filters' in 'test_bpf.c' and invoke the test:

time sudo build/app/dpdk-test bpf_convert_autotest

This causes the test to take ~25 seconds instead of 2 seconds (btw, adding
--log-level=lib.bpf:debug gives tons of output).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3159 bytes --]

             reply	other threads:[~2024-06-19  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  8:42 bugzilla [this message]
2024-07-05  8:56 ` [DPDK/other Bug 1465] rte_bpf_load() hangs with six IPv6 addresses in the filter causing dumpcap to fail bugzilla

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=bug-1465-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 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.