From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35662: Really relocatable binaries crash with Permission denied Date: Mon, 13 May 2019 22:39:21 +0200 Message-ID: <87tvdyozra.fsf@gnu.org> References: <20190509220136.tli7um2heocifrpq@pelzflorian.localdomain> <87o94ax9lw.fsf@gnu.org> <20190511050518.ozmvhsov6meg6g5f@pelzflorian.localdomain> <87ftpivlnv.fsf@gnu.org> <20190513103440.xkri3uk2oxtk4rn6@pelzflorian.localdomain> <87r292qx30.fsf@gnu.org> <20190513151736.ffbuofr3vmyqaoov@pelzflorian.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:44550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQHjv-0000Wz-D6 for bug-guix@gnu.org; Mon, 13 May 2019 16:40:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hQHju-0005eq-C5 for bug-guix@gnu.org; Mon, 13 May 2019 16:40:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:32898) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hQHju-0005el-96 for bug-guix@gnu.org; Mon, 13 May 2019 16:40:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hQHju-0006lK-4X for bug-guix@gnu.org; Mon, 13 May 2019 16:40:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190513151736.ffbuofr3vmyqaoov@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Mon, 13 May 2019 17:17:36 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: "pelzflorian (Florian Pelz)" Cc: 35662@debbugs.gnu.org "pelzflorian (Florian Pelz)" skribis: > On Mon, May 13, 2019 at 03:54:11PM +0200, Ludovic Court=C3=A8s wrote: >> Can you show the mount options of you root file system? >>=20 >> mount | grep 'on / ' >>=20 > > [f_pelz12@tux6 ~]$ mount | grep 'on / ' > rpool/data/subvol-161199-disk-0 on / type zfs (rw,noatime,xattr,posixacl) I suspect ZFS-on-Linux (right?) is doing something unusual here: mount(2) specifies the following reasons for EACCESS, and I don=E2=80=99t s= ee anything that would apply: --8<---------------cut here---------------start------------->8--- EACCES A component of a path was not searchable. (See also path_resolution= (7).) EACCES Mounting a read-only filesystem was attempted without giving the MS_RDONLY flag. The file system may be read-only for various reasons, including: it resides on a read-only optical disk; it is resides on a device with a physical switch that has been set to mark the device read- only; the filesystem implementation was compiled with read-only support; or errors were detected when initially mounting the filesystem, so that it was marked read-only and can't be remounted as read-write (until the errors are fixed). Some filesystems instead return the error EROFS on an attempt to mount a read-only filesystem. EACCES The block device source is located on a filesystem mounted with the MS_NODEV option. --8<---------------cut here---------------end--------------->8--- What do the following commands do on this system? --8<---------------cut here---------------start------------->8--- $ mkdir -p /tmp/test/lib $ unshare -mrf mount /lib /tmp/test/lib -o bind,readonly --8<---------------cut here---------------end--------------->8--- Thanks, Ludo=E2=80=99.