提交 e765a997 编写于 作者: N Nitesh Konkar 提交者: Ján Tomko

docs: Fix typo in memory backing section

Signed-off-by: NNitesh Konkar <nitkon12@linux.vnet.ibm.com>
Signed-off-by: NJán Tomko <jtomko@redhat.com>
上级 5df1d0d4
...@@ -964,7 +964,7 @@ ...@@ -964,7 +964,7 @@
option opens up to a potential security risk: the host will be unable 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 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 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 Because of this, using this option is discouraged unless your workload
demands it; even then, it's highly recommended to set an demands it; even then, it's highly recommended to set an
<code>hard_limit</code> (see <code>hard_limit</code> (see
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册