From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 320] mlx4: info get fails in secondary process
Date: Fri, 12 Jul 2019 14:03:58 -0700 [thread overview]
Message-ID: <20190712140358.6761361a@hermes.lan> (raw)
In-Reply-To: <bug-320-3@http.bugs.dpdk.org/>
On Fri, 12 Jul 2019 20:04:26 +0000
bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=320
>
> Bug ID: 320
> Summary: mlx4: info get fails in secondary process
> Product: DPDK
> Version: 19.08
> Hardware: All
> OS: All
> Status: UNCONFIRMED
> Severity: normal
> Priority: Normal
> Component: other
> Assignee: dev@dpdk.org
> Reporter: stephen@networkplumber.org
> Target Milestone: ---
>
> Attempts to do dev_info_get in secondary process fail because the driver handle
> to infiniband (priv->ctx) is not valid in secondary process. This leads to:
>
> #0 0x00007ffff5d06ab4 in _IO_vfprintf_internal (s=s@entry=0x7fffffffe3c0,
> format=<optimized out>, format@entry=0x7ffff496a605 "%s/device/net",
> ap=ap@entry=0x7fffffffe528) at vfprintf.c:1635
> #1 0x00007ffff5d32599 in _IO_vsnprintf (string=0x7fffffffe4b0 "",
> maxlen=<optimized out>, format=0x7ffff496a605 "%s/device/net",
> args=args@entry=0x7fffffffe528) at vsnprintf.c:119
> #2 0x00007ffff5d0fd32 in __snprintf (s=s@entry=0x0, maxlen=maxlen@entry=0,
> format=format@entry=0x7ffff496a605 "%s/device/net") at snprintf.c:34
> #3 0x00007ffff4720b8b in mlx4_get_ifname (priv=priv@entry=0xc0137e93c0,
> ifname=ifname@entry=0x7fffffffe690) at
> /usr/src/redhat/BUILD/dpdk-18.11/drivers/net/mlx4/mlx4_ethdev.c:71
> #4 0x00007ffff47214e4 in mlx4_dev_infos_get (dev=<optimized out>,
> info=0x7fffffffe6e0) at
> /usr/src/redhat/BUILD/dpdk-18.11/drivers/net/mlx4/mlx4_ethdev.c:583
> #5 0x00007ffff44b896c in rte_eth_dev_info_get (port_id=port_id@entry=0,
> dev_info=dev_info@entry=0x7fffffffe6e0) at
> /usr/src/redhat/BUILD/dpdk-18.11/lib/librte_ethdev/rte_ethdev.c:2532
>
I am testing a patch for this.
next prev parent reply other threads:[~2019-07-12 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 20:04 bugzilla
2019-07-12 21:03 ` Stephen Hemminger [this message]
2019-07-19 5:55 ` Slava Ovsiienko
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=20190712140358.6761361a@hermes.lan \
--to=stephen@networkplumber.org \
--cc=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 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).