mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>
To: Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: Linux kernel regressions <regressions@lists.linux.dev>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Xen developer discussion <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH master] Ignore failure to unmap INVALID_GRANT_HANDLE
Date: Sun, 10 Jul 2022 19:19:50 +0000	[thread overview]
Message-ID: <45234f29-49f9-6089-1c97-7d2c6f29e70f@epam.com> (raw)
In-Reply-To: <20220708163750.2005-8-demi@invisiblethingslab.com>


On 08.07.22 19:37, Demi Marie Obenour wrote:

Hello Demi Marie


Please add subsystem to the commit subject, for example "xen/gntdev:".


> 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>
> Cc: stable@vger.kernel.org
> Signed-off-by: Demi Marie Obenour <demi@invisiblethingslab.com>
> Fixes: dbe97cff7dd9 ("xen/gntdev: Avoid blocking in unmap_grant_pages()")
> ---
>   drivers/xen/gntdev.c | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c
> index 4b56c39f766d4da68570d08d963f6ef40c8d9c37..22fcd503f4a4487d0aed147c94f432683dad8c73 100644
> --- a/drivers/xen/gntdev.c
> +++ b/drivers/xen/gntdev.c
> @@ -396,13 +396,17 @@ 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->unmap_ops[offset+i].status &&
> +			map->unmap_ops[offset+i].handle !=
> +			INVALID_GRANT_HANDLE);


Nit: While extending the check I would clarify the first half of it: 
"map->unmap_ops[offset+i].status != GNTST_okay"


>   		pr_debug("unmap handle=%d st=%d\n",
>   			map->unmap_ops[offset+i].handle,
>   			map->unmap_ops[offset+i].status);
>   		map->unmap_ops[offset+i].handle = INVALID_GRANT_HANDLE;
>   		if (use_ptemod) {
> -			WARN_ON(map->kunmap_ops[offset+i].status);
> +			WARN_ON(map->kunmap_ops[offset+i].status &&
> +				map->kunmap_ops[offset+i].handle !=
> +				INVALID_GRANT_HANDLE);

ditto



With updated subject:

Reviewed-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>


>   			pr_debug("kunmap handle=%u st=%d\n",
>   				 map->kunmap_ops[offset+i].handle,
>   				 map->kunmap_ops[offset+i].status);

-- 
Regards,

Oleksandr Tyshchenko

  reply	other threads:[~2022-07-11  4:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 16:37 gntdev warning fixes Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 4.19] Ignore failure to unmap -1 Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 4.14] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.4] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.10] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.15] Ignore failure to unmap INVALID_GRANT_HANDLE Demi Marie Obenour
2022-07-08 16:37 ` [PATCH 5.18] " Demi Marie Obenour
2022-07-08 16:37 ` [PATCH master] " Demi Marie Obenour
2022-07-10 19:19   ` Oleksandr Tyshchenko [this message]
2022-07-09  6:34 ` gntdev warning fixes Greg KH

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=45234f29-49f9-6089-1c97-7d2c6f29e70f@epam.com \
    --to=oleksandr_tyshchenko@epam.com \
    --cc=demi@invisiblethingslab.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --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

all inboxes | Powered by JetHome®