From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1089] mlx5 Windows crash creating flows in multiple threads
Date: Mon, 03 Oct 2022 17:51:07 +0000 [thread overview]
Message-ID: <bug-1089-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1089
Bug ID: 1089
Summary: mlx5 Windows crash creating flows in multiple threads
Product: DPDK
Version: 21.11
Hardware: All
OS: Windows
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: paul203948@gmail.com
Target Milestone: ---
Hi,
I am using release 21.11 on Windows with a ConnectX-4 card. My application is
crashing when calling rte_flow_create in two threads at the same time.
I tracked the issue down to mlx5_is_thread_alive() in
drivers/net/mlx5/windows/mlx5_flow_os.c. This is always returning false.
Changing the second return statement to return true fixes the crash.
I think one thread was destroying data structures still in use by another
thread.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-10-03 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 17:51 bugzilla [this message]
2022-10-30 10:11 ` [Bug 1089] mlx5 Windows crash creating flows in multiple threads 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-1089-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.