From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] xen/gntdev: Fix partial gntdev_mmap() cleanup
Date: Wed, 10 Jan 2018 09:11:17 +0000 [thread overview]
Message-ID: <7b27b9ee-2c38-356c-14bd-b21db3a96960@citrix.com> (raw)
In-Reply-To: <e2686907-2715-15e8-4cdf-3165903db3ee@oracle.com>
On 01/10/2018 01:22 AM, Boris Ostrovsky wrote:
>
>
> On 01/09/2018 07:10 AM, Ross Lagerwall wrote:
>> When cleaning up after a partially successful gntdev_mmap(), unmap the
>> successfully mapped grant pages otherwise Xen will kill the domain if
>> in debug mode (Attempt to implicitly unmap a granted PTE) or Linux will
>> kill the process and emit "BUG: Bad page map in process" if Xen is in
>> release mode.
>>
>> This is only needed when use_ptemod is true because gntdev_put_map()
>> will unmap grant pages itself when use_ptemod is false.
>>
>> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>
> although I wonder whether it may be possible to have gntdev_put_map()
> figure whether to unmap the pages if use_ptemod is set.
It was a while since I wrote this patch, but IIRC when use_ptemod is
set, successfully mmapped pages are unmapped via the mmu_notifier
release callback. So doing it in gntdev_put_map() isn't possible without
further changes.
--
Ross Lagerwall
next prev parent reply other threads:[~2018-01-10 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:10 [PATCH 1/2] xen/gntdev: Fix off-by-one error when unmapping with holes Ross Lagerwall
2018-01-09 12:10 ` [PATCH 2/2] xen/gntdev: Fix partial gntdev_mmap() cleanup Ross Lagerwall
2018-01-10 1:22 ` Boris Ostrovsky
2018-01-10 9:11 ` Ross Lagerwall [this message]
2018-01-10 1:16 ` [PATCH 1/2] xen/gntdev: Fix off-by-one error when unmapping with holes Boris Ostrovsky
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=7b27b9ee-2c38-356c-14bd-b21db3a96960@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@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®