public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Issue in man page cgroup_namespaces.7
Date: Sun, 4 Dec 2022 21:07:45 +0100	[thread overview]
Message-ID: <08577b8c-950d-d090-4efb-7ebbd4114f11@gmail.com> (raw)
In-Reply-To: <20221204090718.GA877@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 2470 bytes --]

Hi Helge,

On 12/4/22 10:07, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    user ID → UID

IMO, (and I believe Branden will agree), user ID is more informative than UID. 
If any change, I'd apply some consistency in the other direction (don't know how 
much inconsistent the pages are regarding that): UID -> user ID.

So, WONTFIX.  Thanks for the reports!

Cheers,

Alex


> 
> "We have a cgroup directory, I</cg/1>, that is owned by user ID 9000." >
> "We have a process, I<X>, also owned by user ID 9000, that is namespaced"
> "under the cgroup I</cg/1/2> (i.e., I<X> was placed in a new cgroup namespace"
> "via B<clone>(2)  or B<unshare>(2)  with the B<CLONE_NEWCGROUP> flag)."
> 
> "In the absence of cgroup namespacing, because the cgroup directory I</cg/1>"
> "is owned (and writable) by UID 9000 and process I<X> is also owned by user"
> "ID 9000, process I<X> would be able to modify the contents of cgroups files"
> "(i.e., change cgroup settings) not only in I</cg/1/2> but also in the"
> "ancestor cgroup directory I</cg/1>.  Namespacing process I<X> under the"
> "cgroup directory I</cg/1/2>, in combination with suitable mount operations"
> "for the cgroup filesystem (as shown above), prevents it modifying files in"
> "I</cg/1>, since it cannot even see the contents of that directory (or of"
> "further removed cgroup ancestor directories).  Combined with correct"
> "enforcement of hierarchical limits, this prevents process I<X> from escaping"
> "the limits imposed by ancestor cgroups."
> 
> "In the absence of cgroup namespacing, because the cgroup directory I</cg/1>"
> "is owned (and writable) by UID 9000 and process I<X> is also owned by user"
> "ID 9000, then process I<X> would be able to modify the contents of cgroups"
> "files (i.e., change cgroup settings) not only in I</cg/1/2> but also in the"
> "ancestor cgroup directory I</cg/1>.  Namespacing process I<X> under the"
> "cgroup directory I</cg/1/2>, in combination with suitable mount operations"
> "for the cgroup filesystem (as shown above), prevents it modifying files in"
> "I</cg/1>, since it cannot even see the contents of that directory (or of"
> "further removed cgroup ancestor directories).  Combined with correct"
> "enforcement of hierarchical limits, this prevents process I<X> from escaping"
> "the limits imposed by ancestor cgroups."

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-04 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04  9:07 Issue in man page cgroup_namespaces.7 Helge Kreutzmann
2022-12-04 20:07 ` Alejandro Colomar [this message]
2022-12-04 20:11   ` Helge Kreutzmann
2022-12-04 21:22     ` Alejandro Colomar
2022-12-05 13:14   ` Jakub Wilk
  -- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-09-01 13:39 ` Alejandro Colomar
2022-03-13 12:34 Helge Kreutzmann

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=08577b8c-950d-d090-4efb-7ebbd4114f11@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /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