From: Snaipe <snaipe@arista.com>
To: hughd@google.com
Cc: ovt@google.com, corbet@lwn.net, akpm@linux-foundation.org,
brauner@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Snaipe <snaipe@arista.com>
Subject: Re: [PATCH] shmem: add support for user extended attributes
Date: Mon, 14 Aug 2023 10:23:39 +0200 [thread overview]
Message-ID: <20230814082339.2006418-1-snaipe@arista.com> (raw)
In-Reply-To: <9b8d38f0-fd22-3f98-d070-16baf976ecb5@google.com>
> Your sending this patch does help to raise the priority for my
> sending that patch: thank you; but I cannot promise when that will be.
Hey Hugh,
Just as an additional data point, if it helps with priority :)
The lack of support of user xattrs on tmpfs our last remaining blocker for
using unprivileged overlayfs mounts that use a tmpfs for the upper dir & work
dir. Not that it isn't possible to use unprivileged overlayfs mounts in general,
but not having this option means that use-cases for discardable upper layer
changes are harder to clean up correctly when not on an tmpfs mount whose
lifetime is bound to a mount namespace.
I don't think there's any rush; we can live with rmdir failing with EIO for now,
but it'd be great to see this fixed rather than having to implement expensive
cleanup routines that have to remove the upper+work dirs recursively with
CAP_DAC_OVERRIDE.
Cheers,
--
Snaipe
next prev parent reply other threads:[~2023-08-14 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 6:54 [PATCH] shmem: add support for user extended attributes Oleksandr Tymoshenko
2023-07-20 16:56 ` Hugh Dickins
2023-07-20 17:09 ` Oleksandr Tymoshenko
2023-07-20 17:42 ` Hugh Dickins
2023-08-14 8:23 ` Snaipe [this message]
2023-08-15 3:51 ` Hugh Dickins
2023-08-15 7:46 ` Franklin “Snaipe” Mathieu
2023-08-15 8:23 ` Christian Brauner
2023-08-21 17:52 ` Hugh Dickins
2023-08-22 9:01 ` Christian Brauner
2023-08-22 17:50 ` Oleksandr Tymoshenko
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=20230814082339.2006418-1-snaipe@arista.com \
--to=snaipe@arista.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=hughd@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ovt@google.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).