DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: sivaprasad.tummala@intel.com
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Bug 262] Error: Invalid memory for eth_virtio_dev_init()
Date: Tue, 30 Apr 2019 12:57:21 +0200	[thread overview]
Message-ID: <CAJFAV8zPBGRiUX+YoDHX3idkFdirRsCCg+_dfntEd9Mbguzaiw@mail.gmail.com> (raw)
Message-ID: <20190430105721.YMX4wxGhDCbX4LvrOmwn5nXV8l63Tcqe7I9NSzMRneA@z> (raw)
In-Reply-To: <bug-262-3@http.bugs.dpdk.org/>

On Tue, Apr 30, 2019 at 12:49 PM <bugzilla@dpdk.org> wrote:

> https://bugs.dpdk.org/show_bug.cgi?id=262
>
>             Bug ID: 262
>            Summary: Error: Invalid memory for eth_virtio_dev_init()
>            Product: DPDK
>            Version: 18.11
>           Hardware: x86
>                 OS: Linux
>             Status: CONFIRMED
>           Severity: normal
>           Priority: Normal
>          Component: vhost/virtio
>           Assignee: dev@dpdk.org
>           Reporter: sivaprasad.tummala@intel.com
>   Target Milestone: ---
>
> Error from EAL: `log_dpdk(): loglevel=4: EAL: Error: Invalid memory`
>
> Occurs: during rte_eal_init for non dpdk virtio interfaces
>
> Reason: double free for "mac_addrs" from `eth_virtio_dev_init()` and
> `virtio_user_eth_dev_free()/rte_eth_dev_release_port()`
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.


This problem should have been fixed in master with commit
https://git.dpdk.org/dpdk/commit/?id=7dee8c79483e370a346d68060b0b890b273e9a46
.


-- 
David Marchand

  parent reply	other threads:[~2019-04-30 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 10:49 bugzilla
2019-04-30 10:49 ` bugzilla
2019-04-30 10:57 ` David Marchand [this message]
2019-04-30 10:57   ` 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=CAJFAV8zPBGRiUX+YoDHX3idkFdirRsCCg+_dfntEd9Mbguzaiw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=sivaprasad.tummala@intel.com \
    /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).