From: Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>
To: Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH v10] xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE
Date: Sun, 10 Jul 2022 22:11:45 +0000 [thread overview]
Message-ID: <ccf6557a-2fab-3e7a-e986-41a4e35eaa78@epam.com> (raw)
In-Reply-To: <20220710215437.1351-1-demi@invisiblethingslab.com>
On 11.07.22 00:54, Demi Marie Obenour wrote:
Hello Demi Marie
> The error paths of gntdev_mmap() can call unmap_grant_pages() even
> though not all of the pages have been successfully mapped. This will
> trigger the WARN_ON()s in __unmap_grant_pages_done(). The number of
> warnings can be very large; I have observed thousands of lines of
> warnings in the systemd journal.
>
> Avoid this problem by only warning on unmapping failure if the handle
> being unmapped is not INVALID_GRANT_HANDLE. The handle field of any
> page that was not successfully mapped will be INVALID_GRANT_HANDLE, so
> this catches all cases where unmapping can legitimately fail.
>
> Suggested-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Demi Marie Obenour <demi@invisiblethingslab.com>
> Fixes: dbe97cff7dd9 ("xen/gntdev: Avoid blocking in unmap_grant_pages()")
Next time please add a changelog, also I assume current patch ought to
be v2 instead of v10)
> ---
> drivers/xen/gntdev.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c
> index 4b56c39f766d4da68570d08d963f6ef40c8d9c37..44a1078da21b8a2333b4432900a8dbdfb8e13c53 100644
> --- a/drivers/xen/gntdev.c
> +++ b/drivers/xen/gntdev.c
> @@ -396,13 +396,15 @@ static void __unmap_grant_pages_done(int result,
> unsigned int offset = data->unmap_ops - map->unmap_ops;
>
> for (i = 0; i < data->count; i++) {
> - WARN_ON(map->unmap_ops[offset+i].status);
> + WARN_ON(map->kunmap_ops[offset + i].status != GNTST_okay &&
> + map->kunmap_ops[offset + i].handle != INVALID_GRANT_HANDLE);
s/kunmap_ops/unmap_ops
[snip]
--
Regards,
Oleksandr Tyshchenko
prev parent reply other threads:[~2022-07-10 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 21:54 [PATCH v10] xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE Demi Marie Obenour
2022-07-10 22:11 ` Oleksandr Tyshchenko [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=ccf6557a-2fab-3e7a-e986-41a4e35eaa78@epam.com \
--to=oleksandr_tyshchenko@epam.com \
--cc=demi@invisiblethingslab.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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