From: aszlig <aszlig@nix.build>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
graham@grahamc.com, samuel@dionne-riel.com
Subject: Re: Failure to execute file on overlayfs during switch_root/chroot
Date: Sun, 3 Feb 2019 11:13:41 +0100 [thread overview]
Message-ID: <20190203101340.GA6934@dnyarri> (raw)
In-Reply-To: <CAOQ4uxh0L_u-UzJAcQ=QO+D-9VkoSy2HHofXig4=AqDo0vWTmg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Sun, Feb 03, 2019 at 07:37:55AM +0200, Amir Goldstein wrote:
> Any access? or just execute? Can you share pr_debug output of access
> to file that is not execute?
Sure, same result (EPERM) there, here is the output and the changed Nix
expression (in case you want to reproduce it):
https://gist.github.com/aszlig/0b5ae4b03208a117b6f737772ff0eed8
I also added a stat on these files to check whether it happens there as well,
but it only occurs when reading them.
Here is the relevant pr_debug output:
open(000000007ee735e6[/regular_top/l], 0100000) -> (0000000080f3d7f9, 00)
open(00000000f7778f73[somesubdir/regular_sub/l], 0100000) -> (0000000080f3d7f9, 00)
> FWIW, I ran unionmount-testsuite (tweaked) with 9p as lower as it passed,
> so no obvious regressions with 9p as lower.
Okay, one other thing that I can think of is that might be triggering the issue
is that the Nix build process (on the host side) runs in a chroot with a few
separate namespaces[1], including a mount namespace.
a!
[1]: https://github.com/NixOS/nix/blob/92d08c02c84be34ec0df56ed718526c382845d1a/src/libstore/build.cc#L2216-L2218
--
aszlig
Universal dilettante
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-02-03 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181207121027.GA5996@dnyarri>
[not found] ` <CAJfpegsu6DUHVVac2PSyGoFW4pAKm3UH0XLg5+SMvN5XZmNzFw@mail.gmail.com>
2019-01-29 19:41 ` Failure to execute file on overlayfs during switch_root/chroot aszlig
2019-02-02 17:29 ` aszlig
2019-02-03 5:37 ` Amir Goldstein
2019-02-03 10:13 ` aszlig [this message]
2019-02-03 13:51 ` Amir Goldstein
2019-03-14 1:09 ` aszlig
2019-03-14 1:20 ` aszlig
2019-03-14 7:47 ` Amir Goldstein
2019-03-14 10:37 ` aszlig
2019-03-14 19:38 ` Amir Goldstein
2019-03-14 19:45 ` aszlig
2019-03-16 3:21 ` [PATCH] ovl: Don't open files with O_NOATIME in lowerdir aszlig
2019-03-16 9:09 ` Amir Goldstein
2019-03-16 11:17 ` aszlig
2019-03-14 10:40 ` Failure to execute file on overlayfs during switch_root/chroot Amir Goldstein
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=20190203101340.GA6934@dnyarri \
--to=aszlig@nix.build \
--cc=amir73il@gmail.com \
--cc=graham@grahamc.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=samuel@dionne-riel.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