Skip to contentSkip to conversation

docs: namespace: Tweak and reword resource control doc

PATCH Superseded Joel Savitz 2 participants 3 messages Apr 19, 2025 – Apr 21, 2025 Documentation

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 docs: namespace: Tweak and reword resource control doc

Fix the document title and reword the phrasing to active voice.

---
Changes since v1:
- Fix spelling of resource

 .../namespaces/resource-control.rst           | 24 +++++++++----------
 1 file changed, 12 insertions(+), 12 deletions(-)
Documentation/admin-guide/namespaces/resource-control.rst +12 -12
index 369556e00f0c..350134c26a98 100644
@@ -1,17 +1,17 @@
-===========================
-Namespaces research control
-===========================
+====================================
+User namespaces and resource control
+====================================
 
-There are a lot of kinds of objects in the kernel that don't have
-individual limits or that have limits that are ineffective when a set
-of processes is allowed to switch user ids.  With user namespaces
-enabled in a kernel for people who don't trust their users or their
-users programs to play nice this problems becomes more acute.
+The kernel contains many kinds of objects that either don't have
+individual limits or that have limits which are ineffective when
+a set of processes is allowed to switch their UID. On a system
+where there admins don't trust their users or their users' programs,
+user namespaces expose the system to potential misuse of resources.
 
-Therefore it is recommended that memory control groups be enabled in
-kernels that enable user namespaces, and it is further recommended
-that userspace configure memory control groups to limit how much
-memory user's they don't trust to play nice can use.
+In order to mitigate this, we recommend that admins enable memory
+control groups on any system that enables user namespaces.
+Furthermore, we recommend that admins configure the memory control
+groups to limit the maximum memory usable by any untrusted user.
 
 Memory control groups can be configured by installing the libcgroup
 package present on most distros editing /etc/cgrules.conf,
Signature · 1 line
2.45.2
#1 lore raw

Documentation/admin-guide/namespaces/resource-control.rst line 9

Quoted 10 lines · Joel Savitz
Documentation/admin-guide/namespaces/resource-control.rst +5 -5
-There are a lot of kinds of objects in the kernel that don't have
-individual limits or that have limits that are ineffective when a set
-of processes is allowed to switch user ids.  With user namespaces
-enabled in a kernel for people who don't trust their users or their
-users programs to play nice this problems becomes more acute.
+The kernel contains many kinds of objects that either don't have
+individual limits or that have limits which are ineffective when
+a set of processes is allowed to switch their UID. On a system
+where there admins don't trust their users or their users' programs,
+user namespaces expose the system to potential misuse of resources.

Do you mean "when there are admins who don't trust ..." or "where admins don't trust ..."?

Confused...

Signature · 1 line
An old man doll... just what I always wanted! - Clara
#2 lore raw
Quoted 15 lines · Bagas Sanjaya

Documentation/admin-guide/namespaces/resource-control.rst line 9

Quoted 10 lines · Joel Savitz
Documentation/admin-guide/namespaces/resource-control.rst +5 -5
-There are a lot of kinds of objects in the kernel that don't have
-individual limits or that have limits that are ineffective when a set
-of processes is allowed to switch user ids.  With user namespaces
-enabled in a kernel for people who don't trust their users or their
-users programs to play nice this problems becomes more acute.
+The kernel contains many kinds of objects that either don't have
+individual limits or that have limits which are ineffective when
+a set of processes is allowed to switch their UID. On a system
+where there admins don't trust their users or their users' programs,
+user namespaces expose the system to potential misuse of resources.

Do you mean "when there are admins who don't trust ..." or "where admins don't trust ..."?

I meant to write "the admins", my bad.

Quoted 5 lines

Confused...

--
An old man doll... just what I always wanted! - Clara