unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 35662@debbugs.gnu.org
Subject: bug#35662: Really relocatable binaries crash with Permission denied
Date: Wed, 15 May 2019 18:15:19 +0200	[thread overview]
Message-ID: <87d0kju220.fsf@gnu.org> (raw)
In-Reply-To: <20190514210453.2p7x3ibpgohwaxot@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Tue, 14 May 2019 23:04:53 +0200")

Hi,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

> Do I understand correctly that user namespaces are not really disabled
> (?) but fail on ZFS?

Correct.  Specifically, read-only bind mounts of (and to?) files that
reside on ZFS fail with EACCESS, which is normally “impossible.”

It would be great if you could ask the admins specifically what they did
in relation to user namespaces.

>> I don’t have any great option to offer.  You could perhaps modify
>> run-in-namespace.c so that it doesn’t even try user namespaces and
>> instead goes directly to the PRoot option?
>>
>> However working around this behavior of ZFS it not completely trivial
>> and I’m not sure we should put much energy to paper over non-standard
>> file system behavior.
>> 
>> Thoughts?
>>
>
> If ZFS makes user namespaces fail, then could run-un-namespace.c fall
> back to PRoot when detecting ZFS, somehow?

It’s code, so everything is possible :-), but like I wrote it’s a bit of
work, and it’s something that cannot happen (AFAIK) with file systems
that are part of Linux.

Thanks,
Ludo’.

  reply	other threads:[~2019-05-15 16:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 22:01 bug#35662: Really relocatable binaries crash with Permission denied pelzflorian (Florian Pelz)
2019-05-10  5:54 ` pelzflorian (Florian Pelz)
2019-05-10 21:50 ` Ludovic Courtès
2019-05-11  5:05   ` pelzflorian (Florian Pelz)
2019-05-13  7:49     ` Ludovic Courtès
2019-05-13 10:34       ` pelzflorian (Florian Pelz)
2019-05-13 13:54         ` Ludovic Courtès
2019-05-13 15:17           ` pelzflorian (Florian Pelz)
2019-05-13 20:39             ` Ludovic Courtès
2019-05-13 20:45               ` pelzflorian (Florian Pelz)
2019-05-14  8:05                 ` pelzflorian (Florian Pelz)
2019-05-14 20:43                   ` Ludovic Courtès
2019-05-14 21:04                     ` pelzflorian (Florian Pelz)
2019-05-15 16:15                       ` Ludovic Courtès [this message]
2019-05-15 15:20                     ` Giovanni Biscuolo
2019-05-16 11:02                       ` pelzflorian (Florian Pelz)
2019-05-16 11:10                         ` Ludovic Courtès

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=87d0kju220.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35662@debbugs.gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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).