From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] virtio_ring: aovid reading flag from the descriptor ring
Date: Wed, 23 Feb 2022 02:08:33 -0500 [thread overview]
Message-ID: <20220223020452-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEucnZPt_dhaSXCegeFE0gs=dSDfv7CJSq4HCW_4a4XfGg@mail.gmail.com>
On Wed, Feb 23, 2022 at 11:19:03AM +0800, Jason Wang wrote:
> On Mon, Nov 8, 2021 at 4:13 PM Jason Wang <jasowang@redhat.com> wrote:
> >
> > Commit 72b5e8958738 ("virtio-ring: store DMA metadata in desc_extra
> > for split virtqueue") tries to make it possible for the driver to not
> > read from the descriptor ring to prevent the device from corrupting
> > the descriptor ring. But it still read the descriptor flag from the
> > descriptor ring during buffer detach.
> >
> > This patch fixes by always store the descriptor flag no matter whether
> > DMA API is used and then we can avoid reading descriptor flag from the
> > descriptor ring. This eliminates the possibly of unexpected next
> > descriptor caused by the wrong flag (e.g the next flag).
> >
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
>
> Michael, any comment for this?
>
> Thanks
I don't exactly see why we should care without DMA API, it seems
cleaner not to poke at the array one extra time.
> > ---
> > drivers/virtio/virtio_ring.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> > index 00f64f2f8b72..28734f4e57d3 100644
> > --- a/drivers/virtio/virtio_ring.c
> > +++ b/drivers/virtio/virtio_ring.c
> > @@ -583,7 +583,7 @@ static inline int virtqueue_add_split(struct virtqueue *_vq,
> > }
> > /* Last one doesn't continue. */
> > desc[prev].flags &= cpu_to_virtio16(_vq->vdev, ~VRING_DESC_F_NEXT);
> > - if (!indirect && vq->use_dma_api)
> > + if (!indirect)
> > vq->split.desc_extra[prev & (vq->split.vring.num - 1)].flags &=
> > ~VRING_DESC_F_NEXT;
> >
> > @@ -713,7 +713,7 @@ static void detach_buf_split(struct vring_virtqueue *vq, unsigned int head,
> > /* Put back on free list: unmap first-level descriptors and find end */
> > i = head;
> >
> > - while (vq->split.vring.desc[i].flags & nextflag) {
> > + while (vq->split.desc_extra[i].flags & nextflag) {
> > vring_unmap_one_split(vq, i);
> > i = vq->split.desc_extra[i].next;
> > vq->vq.num_free++;
> > --
> > 2.25.1
> >
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: virtualization <virtualization@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio_ring: aovid reading flag from the descriptor ring
Date: Wed, 23 Feb 2022 02:08:33 -0500 [thread overview]
Message-ID: <20220223020452-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEucnZPt_dhaSXCegeFE0gs=dSDfv7CJSq4HCW_4a4XfGg@mail.gmail.com>
On Wed, Feb 23, 2022 at 11:19:03AM +0800, Jason Wang wrote:
> On Mon, Nov 8, 2021 at 4:13 PM Jason Wang <jasowang@redhat.com> wrote:
> >
> > Commit 72b5e8958738 ("virtio-ring: store DMA metadata in desc_extra
> > for split virtqueue") tries to make it possible for the driver to not
> > read from the descriptor ring to prevent the device from corrupting
> > the descriptor ring. But it still read the descriptor flag from the
> > descriptor ring during buffer detach.
> >
> > This patch fixes by always store the descriptor flag no matter whether
> > DMA API is used and then we can avoid reading descriptor flag from the
> > descriptor ring. This eliminates the possibly of unexpected next
> > descriptor caused by the wrong flag (e.g the next flag).
> >
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
>
> Michael, any comment for this?
>
> Thanks
I don't exactly see why we should care without DMA API, it seems
cleaner not to poke at the array one extra time.
> > ---
> > drivers/virtio/virtio_ring.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> > index 00f64f2f8b72..28734f4e57d3 100644
> > --- a/drivers/virtio/virtio_ring.c
> > +++ b/drivers/virtio/virtio_ring.c
> > @@ -583,7 +583,7 @@ static inline int virtqueue_add_split(struct virtqueue *_vq,
> > }
> > /* Last one doesn't continue. */
> > desc[prev].flags &= cpu_to_virtio16(_vq->vdev, ~VRING_DESC_F_NEXT);
> > - if (!indirect && vq->use_dma_api)
> > + if (!indirect)
> > vq->split.desc_extra[prev & (vq->split.vring.num - 1)].flags &=
> > ~VRING_DESC_F_NEXT;
> >
> > @@ -713,7 +713,7 @@ static void detach_buf_split(struct vring_virtqueue *vq, unsigned int head,
> > /* Put back on free list: unmap first-level descriptors and find end */
> > i = head;
> >
> > - while (vq->split.vring.desc[i].flags & nextflag) {
> > + while (vq->split.desc_extra[i].flags & nextflag) {
> > vring_unmap_one_split(vq, i);
> > i = vq->split.desc_extra[i].next;
> > vq->vq.num_free++;
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2022-02-23 7:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 8:13 [PATCH] virtio_ring: aovid reading flag from the descriptor ring Jason Wang
2021-11-08 8:13 ` Jason Wang
2022-02-23 3:19 ` Jason Wang
2022-02-23 3:19 ` Jason Wang
2022-02-23 7:08 ` Michael S. Tsirkin [this message]
2022-02-23 7:08 ` Michael S. Tsirkin
2022-02-23 7:34 ` Jason Wang
2022-02-23 7:34 ` Jason Wang
2022-02-23 7:50 ` Jason Wang
2022-02-23 7:50 ` Jason Wang
2022-02-24 17:26 ` Michael S. Tsirkin
2022-02-24 17:26 ` Michael S. Tsirkin
2022-02-25 2:39 ` Jason Wang
2022-02-25 2:39 ` Jason Wang
2022-02-24 17:55 ` Michael S. Tsirkin
2022-02-24 17:55 ` Michael S. Tsirkin
2022-02-25 2:35 ` Jason Wang
2022-02-25 2:35 ` Jason Wang
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=20220223020452-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.