From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Joel Savitz <jsavitz@redhat.com>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: namespace: Tweak and reword resource control doc
Date: Sun, 20 Apr 2025 09:34:10 +0700 [thread overview]
Message-ID: <aARdIqU6Y7baKrSk@archie.me> (raw)
In-Reply-To: <20250419150428.1129352-1-jsavitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
On Sat, Apr 19, 2025 at 11:04:28AM -0400, Joel Savitz wrote:
> -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...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-20 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 15:04 Joel Savitz
2025-04-20 2:34 ` Bagas Sanjaya [this message]
2025-04-21 16:14 ` Joel Savitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aARdIqU6Y7baKrSk@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jsavitz@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®