From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, mkp@redhat.com, chenbo.xia@intel.com,
david.marchand@redhat.com
Subject: Re: [PATCH] vhost: fix madvise IOTLB entries pages overlap check
Date: Wed, 15 Mar 2023 12:37:14 +0100 [thread overview]
Message-ID: <7d212820-9b08-b111-5d2d-c2c9624d5634@redhat.com> (raw)
In-Reply-To: <20230315113158.442632-1-maxime.coquelin@redhat.com>
On 3/15/23 12:31, Maxime Coquelin wrote:
> At removal time, when testing whether the IOTLB entry has
> shared pages with the previous and next entries in the
> cache, it checks whether the start address of the entry to
> be removed is on the same page as the start address of the
> next entry in the cache.
>
> This is not correct, as an entry could cover several page
> so the end address of the entry to be remove should be
> used. This patch address this issue.
>
> Fixes: dea092d0addb ("vhost: fix madvise arguments alignment")
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> lib/vhost/iotlb.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/lib/vhost/iotlb.c b/lib/vhost/iotlb.c
> index 11785392ac..bfa04a0439 100644
> --- a/lib/vhost/iotlb.c
> +++ b/lib/vhost/iotlb.c
> @@ -182,8 +182,8 @@ vhost_user_iotlb_cache_random_evict(struct virtio_net *dev, struct vhost_virtque
> (node->uaddr & mask) != (prev_node->uaddr & mask)) {
> next_node = RTE_TAILQ_NEXT(node, next);
> /* Don't disable coredump if the next node is in the same page */
> - if (next_node == NULL ||
> - (node->uaddr & mask) != (next_node->uaddr & mask))
> + if (next_node == NULL || ((node->uaddr + node->size) & mask) !=
Oups, forgot to amend a change before generating the patch.
It should be (node->uaddr + node->size - 1) as we want the end address
of the entry.
> + (next_node->uaddr & mask))
> mem_set_dump((void *)(uintptr_t)node->uaddr, node->size,
> false, alignment);
> }
> @@ -287,8 +287,8 @@ vhost_user_iotlb_cache_remove(struct virtio_net *dev, struct vhost_virtqueue *vq
> (node->uaddr & mask) != (prev_node->uaddr & mask)) {
> next_node = RTE_TAILQ_NEXT(node, next);
> /* Don't disable coredump if the next node is in the same page */
> - if (next_node == NULL ||
> - (node->uaddr & mask) != (next_node->uaddr & mask))
> + if (next_node == NULL || ((node->uaddr + node->size) & mask) !=
Same here.
> + (next_node->uaddr & mask))
> mem_set_dump((void *)(uintptr_t)node->uaddr, node->size,
> false, alignment);
> }
Sending v2.
prev parent reply other threads:[~2023-03-15 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 11:31 Maxime Coquelin
2023-03-15 11:37 ` Maxime Coquelin [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=7d212820-9b08-b111-5d2d-c2c9624d5634@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mkp@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).