All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 548] net/pcap rx_infinite freeing from unallocated ring
Date: Fri, 09 Oct 2020 15:18:03 +0000	[thread overview]
Message-ID: <bug-548-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 548
           Summary: net/pcap rx_infinite freeing from unallocated ring
           Product: DPDK
           Version: 20.08
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: rchibois@gmail.com
  Target Milestone: ---

- create a new pcap with:

    rte_eal_hotplug_add(
        "vdev",
        "net_pcap_0",
        "rx_pcap=file.pcap,infinite_rx=1"
    );

- remove it:

    rte_eal_hotplug_remove("vdev", "net_pcap_0");

- problem:

    eth_rx_queue_setup was not called so not ring was created
    eth_dev_close is called and tries to dequeue everything

    segfault happens at rte_eth_pcap.c:743 because pcap_q->pkts is NULL

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

                 reply	other threads:[~2020-10-09 15:18 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=bug-548-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.