From: "Ariel Otilibili-Anieli" <otilibil@eurecom.fr>
To: "Maxime Coquelin" <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Subject: Re: [PATCH] vhost: fix VDUSE devices registration
Date: Thu, 06 Feb 2025 22:05:59 +0100 [thread overview]
Message-ID: <786c0-67a52400-aef-318b4ec@175281925> (raw)
In-Reply-To: <f80bf8d7-b57a-4816-b207-65bf22e436f5@redhat.com>
Hi Maxime,
On Wednesday, February 05, 2025 22:18 CET, Maxime Coquelin <maxime.coquelin@redhat.com> wrote:
> Hi Ariel,
>
>
> Not really :)
> Without your patch, ret was assigned by the pthread_mutex_init() return,
> so always 0. With your patch, this assignment is removed so ret will
> always be -1 for VDUSE devices.
>
> So before your patch, VDUSE devices registration was functional, with
> your patch it breaks systematically.
>
> We don't want to backport my patch to LTS that aren't imapcted, so
> tagging your patch as the one introducing the regression is the right
> thing to do.
:) Gotcha; it is now clearer to me.
>
> > :) For my understanding; now that 4d2aa150769b ("vhost: remove check around mutex init") needs a fix, is there a way by which I could have detect the regression?
>
> It could have been detected by testing VDUSE, that's how I noticed it.
> But VDUSE is still fairly recent, and it is not yet tested by the CI.
>
> Now that it is supported in at least Fedora without any kernel change,
> we should work on adding CI testing for it.
>
> > Your help will be much appreciated,
> > Ariel
> >
>
> Thanks for your contribution,
> Maxime
Thanks for having put some of your time into the explanation.
Have a good day,
Ariel
>
next prev parent reply other threads:[~2025-02-06 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 17:34 Ariel Otilibili-Anieli
2025-02-05 21:18 ` Maxime Coquelin
2025-02-06 21:05 ` Ariel Otilibili-Anieli [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-31 13:09 Maxime Coquelin
2025-02-06 8:35 ` Chenbo Xia
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=786c0-67a52400-aef-318b4ec@175281925 \
--to=otilibil@eurecom.fr \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).