From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 701] mlx5: reading xstats smashes stack
Date: Tue, 11 May 2021 07:50:47 +0000 [thread overview]
Message-ID: <bug-701-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=701
Bug ID: 701
Summary: mlx5: reading xstats smashes stack
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: viktorin@cesnet.cz
Target Milestone: ---
When reading xstats via mlx5 driver *before the port* is started, such
application crashes with "stack smashing detected". After the port is started
(and then stoped), it does not happen anymore.
Terminal 1:
# dpdk-testpmd -a 0000:04:00.0 -- -i --disable-device-start
...
EAL: RTE Version: 'DPDK 20.11.1'
...
EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:04:00.0 (socket 0)
...
testpmd>
Terminal 2:
# dpdk-proc-info -- --xstats
Device 0000:04:00.1 is not driven by the primary process
mlx5_pci: can not attach rte ethdev
mlx5_pci: probe of PCI device 0000:04:00.1 aborted after encountering an error:
Cannot allocate memory
common_mlx5: Failed to load driver = mlx5_pci.
EAL: Requested device 0000:04:00.1 cannot be used
EAL: Cannot find resource for device
EAL: No legacy callbacks, legacy socket not created
...
*** stack smashing detected ***: dpdk-proc-info terminated
======= Backtrace: =========
/lib64/libc.so.6(__fortify_fail+0x37)[0x7fd76cdf9697]
/lib64/libc.so.6(+0x118652)[0x7fd76cdf9652]
/usr/lib64/dpdk/pmds-21.0/librte_net_mlx5.so.21.0(+0x1b41e4)[0x7fd7602271e4]
======= Memory map: ========
...
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-11 7:50 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-701-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.