about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2023-08-14 09:16:08 +0200
committerRalf Jung <post@ralfj.de>2023-08-14 09:16:08 +0200
commit4da08115132c55289905e9304d202464bd46f059 (patch)
treec89635c6cb8401688cbc416294654a42ad8fb819
parent55f18beddd8a74034a402fae173eb74e046cedaa (diff)
downloadrust-4da08115132c55289905e9304d202464bd46f059.tar.gz
rust-4da08115132c55289905e9304d202464bd46f059.zip
mention /proc/self/fd with /proc/self/mem
-rw-r--r--library/std/src/os/unix/io/mod.rs6
1 files changed, 3 insertions, 3 deletions
diff --git a/library/std/src/os/unix/io/mod.rs b/library/std/src/os/unix/io/mod.rs
index f49aebefd20..c12d89ed637 100644
--- a/library/std/src/os/unix/io/mod.rs
+++ b/library/std/src/os/unix/io/mod.rs
@@ -65,9 +65,9 @@
 //! to be opened and read from or written must be `unsafe`. Rust's safety guarantees
 //! only cover what the program itself can do, and not what entities outside
 //! the program can do to it. `/proc/self/mem` is considered to be such an
-//! external entity, along with debugging interfaces, and people with physical access to
-//! the hardware. This is true even in cases where the program is controlling
-//! the external entity.
+//! external entity, along with `/proc/self/fd/*`, debugging interfaces, and people with physical
+//! access to the hardware. This is true even in cases where the program is controlling the external
+//! entity.
 //!
 //! If you desire to comprehensively prevent programs from reaching out and
 //! causing external entities to reach back in and violate memory safety, it's