From: aszlig <aszlig@nix.build>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
Graham Christensen <graham@grahamc.com>,
Samuel Dionne-Riel <samuel@dionne-riel.com>,
cleverca22@gmail.com
Subject: Re: Failure to execute file on overlayfs during switch_root/chroot
Date: Thu, 14 Mar 2019 11:37:58 +0100 [thread overview]
Message-ID: <20190314103757.GA4654@dnyarri> (raw)
In-Reply-To: <CAOQ4uxg_zS8XBTaDqdUKxRvzntF-_Pq=vqk1sYJGfhaPKsJRLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On Thu, Mar 14, 2019 at 09:47:23AM +0200, Amir Goldstein wrote:
> Overlayfs is not expected to modify the lower layer.
That is pretty clear, I mean that's the whole point of overlayfs, right? :-)
> OTOH, I can't really think anything that should break horribly if
> we allow overlayfs to update atime on a writable lower layer??
It wasn't using O_NOATIME prior to Linux 4.19 (which is where this was starting
to break our tooling), but the bisected commit I mentioned initially
(a6518f73e60e5044656d1ba587e7463479a9381a) was (implicitly) introducing
O_NOATIME, so to the contrary I'd say it would actually un-break networking
file systems with overlayfs.
a!
--
aszlig
Universal dilettante
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-03-14 10:37 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
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 [this message]
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=20190314103757.GA4654@dnyarri \
--to=aszlig@nix.build \
--cc=amir73il@gmail.com \
--cc=cleverca22@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;
as well as URLs for NNTP newsgroup(s).