From: David Howells <dhowells@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: dhowells@redhat.com, Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH v2] fs: rename S_KERNEL_FILE
Date: Fri, 28 Jan 2022 11:35:59 +0000 [thread overview]
Message-ID: <922909.1643369759@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAOQ4uxhRS3MGEnCUDcsB1RL0d1Oy0g0Rzm75hVFAJw2dJ7uKSA@mail.gmail.com>
Amir Goldstein <amir73il@gmail.com> wrote:
> Good idea, but then the helpers to set the flag should not be internal
> to cachefiles and the locking semantics should be clear.
I could move them out, at least partially. They do log some information
that's private to cachefiles through the tracepoint, but it's just one number
and could be passed in as a parameter. I could move the tracepoint to
somewhere more generic.
> FYI, overlayfs already takes an "exclusive lock" on upper/work dir
> among all ovl instances.
>
> How do you feel about hoisting ovl_inuse_* helpers to fs.h
> and rename s/I_OVL_INUSE/I_EXCL_INUSE?
Fine by me. Sharing a cache with or through an overlay would make for very
fun coherency management.
> Whether deny rmdir should have its own flag or not I don't know,
> but from ovl POV I *think* it should not be a problem to deny rmdir
> for the ovl upper/work dirs as long as ovl is mounted(?).
What's the consequence of someone rearranging the directories directly in the
contributing dirs whilst there's an overlay over them?
> Another problem with generic deny of rmdir is that users getting
> EBUSY have no way to figure out the reason.
> At least for a specific subsystem (i.e. cachefiles) users should be able
> to check if the denied dir is in the subsystem's inventory(?)
I could add a tracepoint for that. It could form a set with the cachefiles
tracepoints if I move those out too.
David
next prev parent reply other threads:[~2022-01-28 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 7:47 [PATCH v2] fs: rename S_KERNEL_FILE Christoph Hellwig
2022-01-28 9:01 ` Chaitanya Kulkarni
2022-01-28 10:12 ` David Howells
2022-01-28 11:09 ` Amir Goldstein
2022-01-28 11:35 ` David Howells [this message]
2022-01-28 13:17 ` Al Viro
2022-01-28 15:24 ` 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=922909.1643369759@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=amir73il@gmail.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.