unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: [Patch v2] daemon: Set ownership of kept build directories to the calling user.
Date: Thu, 1 Dec 2016 01:01:10 +0100	[thread overview]
Message-ID: <20161201010110.2325efc9@scratchpost.org> (raw)
In-Reply-To: <cdbb9ea7-a6d0-8edf-715f-fd646b07f7a9@crazy-compilers.com>

Hi Hartmut,

On Mon, 28 Nov 2016 22:31:44 +0100
Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> I just need some C programming hint: uid_t is an unsigned int, so
> comparing with -1 raises a warning (which IMO is the same as en error).

The system call handler in the Linux kernel does this, among other things:

#define low2highuid(uid) ((uid) == (old_uid_t)-1 ? (uid_t)-1 : (uid_t)(uid))

So I'd say to compare with (uid_t)-1 would be fine

    if (settings.clientUid != (uid_t) -1) {
        ...
    }

... since they do something like it in Linux anyway - which is the one implementing the chown operation in the first place :)

> And casting uid_t to unisgned int might return the same uid as "nobody".

What do you mean? uid_t is __uid_t - which in turn is implementation-defined - but yes, it is unsigned. On Linux it changed size multiple time until now where it is 32 bit unsigned.

On GuixSD, user "nobody" has uid 65534. That's one less than the maximum value for 16 bit (!) uids (the maximum is hopefully invalid as uid since chown needs it as a flag).

(-1) in two-complement 16 bit integral encoding (which is technically not guaranteed to be used in C) would be 65535.

  reply	other threads:[~2016-12-01  0:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 11:30 [Patch v2] daemon: Set ownership of kept build directories to the calling user Hartmut Goebel
2016-11-21 14:13 ` Ludovic Courtès
2016-11-21 14:18   ` Hartmut Goebel
2016-11-27 21:04     ` Ludovic Courtès
2016-11-28 21:31       ` Hartmut Goebel
2016-12-01  0:01         ` Danny Milosavljevic [this message]
2016-12-05 20:46           ` [PATCH v3] " Hartmut Goebel
2016-12-06 15:08             ` Ludovic Courtès
2016-12-08 12:12               ` Hartmut Goebel
2016-12-08 12:14                 ` [PATCH v4] " Hartmut Goebel
2016-12-09 14:23                   ` Ludovic Courtès
2016-12-09 14:47                     ` Hartmut Goebel
2016-12-09 14:22                 ` [PATCH v3] " Ludovic Courtès
2016-12-09 15:50                   ` Guile-SSH found at configure-time but not at run-time Hartmut Goebel
2016-12-09 20:35                     ` Ludovic Courtès
2016-12-06 20:41             ` [PATCH v3] daemon: Set ownership of kept build directories to the calling user Danny Milosavljevic
2016-12-08 12:16               ` Hartmut Goebel
2016-12-05 20:51           ` [Patch v2] " Hartmut Goebel
2016-11-21 17:36   ` Hartmut Goebel
2016-11-21 18:29   ` Hartmut Goebel

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161201010110.2325efc9@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).