ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Arseny Maslennikov <arseny@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] I: brp-verify-unit: "... assumes overflowugid credentials"
Date: Mon, 12 Feb 2024 16:16:41 +0300
Message-ID: <ZcoaObn8aA94Z1KF@cello> (raw)
In-Reply-To: <a522c44e-34cd-4023-bb7b-63b4a46e498b@basealt.ru>

[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]

On Mon, Feb 12, 2024 at 01:50:27PM +0300, Anton Farygin wrote:
> On 12.02.2024 13:34, Dmitry V. Levin wrote:
> > Всё обстоит несколько иначе.
> 
> Ну да, но смысл от этого особо не меняется.
> 
> sysctl этот, судя по документации, для каких-то старых файловых систем
> нужен:
> 
> https://docs.kernel.org/admin-guide/sysctl/fs.html#overflowgid-overflowuid

NFS с его логикой ремаппинга рута трудно назвать старой файловой
системой. :)

Более того, письмо Димы с цитатой git grep по ядру меня сподвигло узнать
вот об этом:

user_namespaces(7):
   Unmapped user and group IDs
       There  are various places where an unmapped user ID (group ID) may be exposed to user
       space.  For example, the first process in a new user namespace may call getuid(2) be‐
       fore a user ID mapping has been defined for the namespace.  In most  such  cases,  an
       unmapped  user  ID is converted to the overflow user ID (group ID); the default value
       for the overflow user ID (group ID) is 65534.  See the descriptions of /proc/sys/ker‐
       nel/overflowuid and /proc/sys/kernel/overflowgid in proc(5).

       The cases where unmapped IDs are mapped in this fashion include system calls that re‐
       turn user IDs (getuid(2), getgid(2), and similar), credentials passed over a UNIX do‐
       main socket, credentials returned by stat(2), waitid(2), and the System V  IPC  "ctl"
       IPC_STAT  operations,  credentials  exposed  by  /proc/pid/status  and  the  files in
       /proc/sysvipc/*, credentials returned via the si_uid field in the siginfo_t  received
       with  a signal (see sigaction(2)), credentials written to the process accounting file
       (see acct(5)), and credentials returned with POSIX message queue  notifications  (see
       mq_notify(3)).

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

  reply	other threads:[~2024-02-12 13:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10 11:37 Arseny Maslennikov
2024-02-10 14:06 ` Anton Farygin
2024-02-10 15:23   ` Arseny Maslennikov
2024-02-11 22:12     ` Dmitry V. Levin
2024-02-12  5:58       ` Anton Farygin
2024-02-12 10:34         ` Dmitry V. Levin
2024-02-12 10:50           ` Anton Farygin
2024-02-12 13:16             ` Arseny Maslennikov [this message]
2024-02-12  5:44     ` Anton Farygin
2024-02-12  7:45       ` [devel] I: brp-verify-unit: "... assumes overflowugid Alexey V. Vissarionov
2024-02-12  7:52         ` Anton Farygin
2024-02-12  8:04           ` Alexey V. Vissarionov
2024-02-12 14:23       ` [devel] I: brp-verify-unit: "... assumes overflowugid credentials" Arseny Maslennikov
2024-02-12 14:33         ` Arseny Maslennikov
2024-02-12 14:48           ` Anton Farygin
2024-02-18 13:35 ` Vitaly Lipatov

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=ZcoaObn8aA94Z1KF@cello \
    --to=arseny@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git