From: Jonathan Erb <jonathan.erb@threatblockr.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org, stable@dpdk.org,
Artemy Kovalyov <artemyko@nvidia.com>
Subject: Re: [PATCH] eal/linux: prevent deadlocks on rte init and cleanup
Date: Mon, 2 Oct 2023 10:34:55 -0400 [thread overview]
Message-ID: <eb787af6-028c-4fed-a307-56aceb6dae8e@threatblockr.com> (raw)
In-Reply-To: <CAJFAV8xStopC-TFY_NrSSCKK7-Z_8SY8H3Kqes4idQ4Ee27shQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
David,
Thanks for the follow-up. The proposed patch below from Artemy will work
for me.
Jonathan
On 9/29/23 10:32, David Marchand wrote:
> Hello Jonathan,
>
> On Thu, Jul 20, 2023 at 7:19 AM Jonathan Erb
> <jonathan.erb@threatblockr.com> wrote:
>> Resolves a deadlock that can occur when multiple secondary
>> processes are starting and stopping. A deadlock can occur because
>> eal_memalloc_init() is taking a second unnecessary read lock.
>> If another DPDK process that is terminating enters rte_eal_memory_detach()
>> and acquires a write lock wait state before the starting process can
>> acquire it's second read lock then no process will be able to proceed.
>>
>> Cc:stable@dpdk.org
>>
>> Signed-off-by: Jonathan Erb<jonathan.erb@threatblockr.com>
> Thanks for the report and fix and sorry for the late reply.
>
> Artemy came with a similar report and a more complete fix.
> Could you confirm it works for you?
>
> https://patchwork.dpdk.org/project/dpdk/list/?series=29463&state=%2A&archive=both
>
>
> Thanks,
>
--
Jonathan Erb
Software Engineer
*Phone:* 1.855.765.4925
jonathan.erb@threatblockr.com <mailto:name@swishdata.com>
threatblockr.com <https://threatblockr.com>
Threat Blockr Logo <https://threatblockr.com/>
[-- Attachment #2: Type: text/html, Size: 3712 bytes --]
prev parent reply other threads:[~2023-10-04 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 1:00 Jonathan Erb
2023-09-29 14:32 ` David Marchand
2023-10-02 14:34 ` Jonathan Erb [this message]
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=eb787af6-028c-4fed-a307-56aceb6dae8e@threatblockr.com \
--to=jonathan.erb@threatblockr.com \
--cc=anatoly.burakov@intel.com \
--cc=artemyko@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).