From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
dev@dpdk.org, stable@dpdk.org, Chenbo Xia <chenbox@nvidia.com>,
Eelco Chaudron <echaudro@redhat.com>
Subject: Re: [PATCH] vhost: fix read vs write lock mismatch
Date: Mon, 25 Nov 2024 17:28:37 +0100 [thread overview]
Message-ID: <CAJFAV8wq+rmzKjBcth4KUWwLO1W1NnhdtCUdYNs-wY4U+iBprQ@mail.gmail.com> (raw)
In-Reply-To: <9ea5b1d6-bafa-44d5-bdb7-1eaeaa62a587@redhat.com>
On Mon, Nov 25, 2024 at 5:20 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
> On 11/25/24 12:14, David Marchand wrote:
> > On Mon, Nov 18, 2024 at 5:24 PM Stephen Hemminger
> > <stephen@networkplumber.org> wrote:
> >>
> >> If lock is acquired for write, it must be released for write
> >> or a deadlock is likely.
> >>
> >> Bugzilla ID: 1582
> >> Fixes: 9fc93a1e2320 ("vhost: fix virtqueue access check in datapath")
> >> Cc: david.marchand@redhat.com
> >> Cc: stable@dpdk.org
> >>
> >> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> >> ---
> >> lib/vhost/virtio_net.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/lib/vhost/virtio_net.c b/lib/vhost/virtio_net.c
> >> index 298a5dae74..d764d4bc6a 100644
> >> --- a/lib/vhost/virtio_net.c
> >> +++ b/lib/vhost/virtio_net.c
> >> @@ -2538,7 +2538,7 @@ virtio_dev_rx_async_submit(struct virtio_net *dev, struct vhost_virtqueue *vq,
> >>
> >> if (unlikely(!vq->access_ok)) {
> >> vhost_user_iotlb_rd_unlock(vq);
> >> - rte_rwlock_read_unlock(&vq->access_lock);
> >> + rte_rwlock_write_unlock(&vq->access_lock);
> >
> > A write lock is taken earlier, because virtio_dev_rx_async_submit_*
> > need it for access to vq->async (as opposed to the sync code that only
> > takes read lock).
> >
> > Here, no need to release/take again all locks.
> > A simpler fix is to directly call vring_translate(dev, vq).
> >
> >
>
> Ok, so both solutions are correct.
>
> David's one is more optimized, but this is a corner case in the async
> datapath so not really critical.
>
> On the other hand, Stephen's solution keeps the same pattern as the
> other datapaths.
Ok, it avoids having a special case, and I prefer limiting special cases too.
I'll send a RFC for new lock annotations (for catching such bug) for
the next release.
>
> I'd go with Stephen's solution, but would change the commit title to:
>
> vhost: fix deadlock in Rx async path
>
> With this change:
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Yes, the title needed some work.
--
David Marchand
next prev parent reply other threads:[~2024-11-25 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 16:24 Stephen Hemminger
2024-11-25 11:14 ` David Marchand
2024-11-25 16:20 ` Maxime Coquelin
2024-11-25 16:28 ` David Marchand [this message]
2024-11-25 16:31 ` Maxime Coquelin
2024-11-25 16:44 ` Stephen Hemminger
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=CAJFAV8wq+rmzKjBcth4KUWwLO1W1NnhdtCUdYNs-wY4U+iBprQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=echaudro@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).