The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: dhowells@redhat.com, mszeredi@redhat.com,
	linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to support directory opacity in a filesystem for overlayfs to use?
Date: Tue, 14 Jan 2025 15:56:33 +0000	[thread overview]
Message-ID: <112184.1736870193@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAJfpegsUbvMB_tFbV283_JmK+wzFAECaLZgYAbmcBbBxWX=Ctw@mail.gmail.com>

Miklos Szeredi <miklos@szeredi.hu> wrote:

> On Tue, 14 Jan 2025 at 16:15, David Howells <dhowells@redhat.com> wrote:
> 
> > What's the best way for a network filesystem to make a native
> > directory-is-opaque flag available to the system?  Is it best to catch
> > setxattr/getxattr/removexattr("overlay.opaque") and translate these into the
> > RPCs to wrangle the flag?
> 
> I don't know.  Out of curiosity, which filesystem is it?

One of the varieties of AFS.  Unfortunately, xattrs aren't a thing and can't
easily be added because of the volume transfer and backup protocols and
formats.

> There's "trusted.overlay.opaque" and "user.overlay.opaque" and are
> used in different scenarios.   There was also talk of making the
> "trusted." namespace nest inside user namespaces, but apparently it's
> not so important.
> 
> Which one would you like to emulate?

Um - I don't know the difference to answer that question.

David


  reply	other threads:[~2025-01-14 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 15:15 How to support directory opacity in a filesystem for overlayfs to use? David Howells
2025-01-14 15:32 ` Miklos Szeredi
2025-01-14 15:56   ` David Howells [this message]
2025-01-14 16:23     ` Miklos Szeredi

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=112184.1736870193@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.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