docs: Fix typo in memory backing section

Signed-off-by: Nitesh Konkar <nitkon12@linux.vnet.ibm.com>
Signed-off-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
Nitesh Konkar
2017-07-26 16:48:21 +02:00
committed by Ján Tomko
parent 5df1d0d417
commit e765a9972b
+1 -1
View File
@@ -964,7 +964,7 @@
option opens up to a potential security risk: the host will be unable
to reclaim the locked memory back from the guest when it's running out
of memory, which means a malicious guest allocating large amounts of
locked memory could cause a denial-of-service attach on the host.
locked memory could cause a denial-of-service attack on the host.
Because of this, using this option is discouraged unless your workload
demands it; even then, it's highly recommended to set an
<code>hard_limit</code> (see