memory: don't implicitly unpin for decrease-reservation

It very likely was a mistake (copy-and-paste from domain cleanup code)
to implicitly unpin here: The caller should really unpin itself before
(or after, if they so wish) requesting the page to be removed.

This is XSA-252.

Reported-by: Jann Horn <jannh@google.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
master commit: d798a09529
master date: 2018-02-27 14:03:27 +0100
This commit is contained in:
Jan Beulich committed 2018-02-27 14:36:46 +01:00
1 parent 0fbf30a7f8
commit c9c1bb658c
1 file changed
-3
-3
View File
@@ -316,9 +316,6 @@ int guest_remove_page(struct domain *d, unsigned long gmfn)
rc = guest_physmap_remove_page(d, gmfn, mfn, 0);
if ( !rc && test_and_clear_bit(_PGT_pinned, &page->u.inuse.type_info) )
put_page_and_type(page);
if ( !rc && test_and_clear_bit(_PGC_allocated, &page->count_info) )
put_page(page);
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.