From: Stefano Garzarella <sgarzare@redhat.com>
To: virtualization@lists.linux-foundation.org
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Stefano Garzarella <sgarzare@redhat.com>
Subject: [PATCH v2 0/2] vhost: fix ranges when call vhost_iotlb_itree_first()
Date: Wed, 9 Nov 2022 11:25:01 +0100 [thread overview]
Message-ID: <20221109102503.18816-1-sgarzare@redhat.com> (raw)
v2:
- Patch 2: Replaced Fixes tag with the right one [Jason]
v1: https://lore.kernel.org/virtualization/20221108103437.105327-1-sgarzare@redhat.com/
While I was working on vringh to support VA in vringh_*_iotlb()
I saw that the range we use in iotlb_translate() when we call
vhost_iotlb_itree_first() was not correct IIUC.
So I looked at all the calls and found that in vhost.c as well.
I didn't observe a failure and I don't have a reproducer because
I noticed the problem by looking at the code.
Maybe we didn't have a problem, because a shorter range was being
returned anyway and the loop stopped taking into account the total
amount of bytes translated, but I think it's better to fix.
Thanks,
Stefano
Stefano Garzarella (2):
vringh: fix range used in iotlb_translate()
vhost: fix range used in translate_desc()
drivers/vhost/vhost.c | 4 ++--
drivers/vhost/vringh.c | 5 ++---
2 files changed, 4 insertions(+), 5 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-09 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 10:25 Stefano Garzarella [this message]
2022-11-09 10:25 ` [PATCH v2 1/2] vringh: fix range used in iotlb_translate() Stefano Garzarella
2022-11-09 10:25 ` [PATCH v2 2/2] vhost: fix range used in translate_desc() Stefano Garzarella
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=20221109102503.18816-1-sgarzare@redhat.com \
--to=sgarzare@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®