From 27b94a41736f6ffa1f212c531d3a3a57666d795a Mon Sep 17 00:00:00 2001
From: JMS55 <47158642+JMS55@users.noreply.github.com>
Date: Tue, 28 Jun 2022 10:27:00 -0700
Subject: [PATCH] Note that epoch-interrupts are safe against malicious guests
 (#4343)

* Note that epoch-interrupts are safe against malicious guests

* Remove implementation details from epoch deadline docs
---
 crates/wasmtime/src/config.rs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/crates/wasmtime/src/config.rs b/crates/wasmtime/src/config.rs
index ed01ec111c..b41ae9396f 100644
--- a/crates/wasmtime/src/config.rs
+++ b/crates/wasmtime/src/config.rs
@@ -425,6 +425,10 @@ impl Config {
     /// signal handler), then we can ensure that all async code will
     /// yield to the executor within a bounded time.
     ///
+    /// The deadline check cannot be avoided by malicious wasm code. It is safe
+    /// to use epoch deadlines to limit the execution time of untrusted
+    /// code.
+    ///
     /// The [`Store`](crate::Store) tracks the deadline, and controls
     /// what happens when the deadline is reached during
     /// execution. Several behaviors are possible: