VMCI: Use set_page_dirty_lock() when unregistering guest memory
authorJorgen Hansen <jhansen@vmware.com>
Wed, 20 Jan 2021 16:32:40 +0000 (08:32 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 26 Jan 2021 18:18:46 +0000 (19:18 +0100)
commit5a16c535409f8dcb7568e20737309e3027ae3e49
tree1977dc0a09678b34651a6f3004e646ba07bc4e6e
parente8266c4c3307d2a64f8ebcb22323347be8854742
VMCI: Use set_page_dirty_lock() when unregistering guest memory

When the VMCI host support releases guest memory in the case where
the VM was killed, the pinned guest pages aren't locked. Use
set_page_dirty_lock() instead of set_page_dirty().

Testing done: Killed VM while having an active VMCI based vSocket
connection and observed warning from ext4. With this fix, no
warning was observed. Ran various vSocket tests without issues.

Fixes: 06164d2b72aa ("VMCI: queue pairs implementation.")
Reviewed-by: Vishnu Dasa <vdasa@vmware.com>
Signed-off-by: Jorgen Hansen <jhansen@vmware.com>
Link: https://lore.kernel.org/r/1611160360-30299-1-git-send-email-jhansen@vmware.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/misc/vmw_vmci/vmci_queue_pair.c