From: Al Viro <viro@zeniv.linux.org.uk>
To: Blake McBride <blake@mcbridemail.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Colby Wes McBride <colbym84@gmail.com>
Subject: Re: [RFC] View-Based File System Model with Program-Scoped Isolation
Date: Fri, 5 Sep 2025 00:08:46 +0100 [thread overview]
Message-ID: <20250904230846.GR39973@ZenIV> (raw)
In-Reply-To: <DHMURiMioUDX6Ggo4Qy8C43EUoC_ltjjS52i2kgC9tl6GhjGuJXOwyf9Nb-WkI__cM0NXECZw_HdKeIUmwShKkAmP7PwqZcmGz-vBrdWYL8=@mcbridemail.com>
On Thu, Sep 04, 2025 at 10:58:12PM +0000, Blake McBride wrote:
> Off the cuff, I'd say it is an mv option. It defaults to changing all occurrences, with an option to change it only in the current view.
Huh? mv(1) is userland; whatever it does, by definition it boils down
to a sequence of system calls.
If those "views" of yours are pasted together subtrees of the global
forest, you already can do all of that with namespaces; if they are not,
you get all kinds of interesting questions about coherency.
Which one it is? Before anyone can discuss possible implementations
and relative merits thereof, you need to define the semantics of
what you want to implement...
And frankly, if you are thinking in terms of userland programs (file
manglers, etc.) you are going the wrong way - description will have
to be on the syscall level.
next prev parent reply other threads:[~2025-09-04 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Oa1N9bTNjTvfRX39yqCcQGpl9FJVwfDT2fTq-9NXTT8HqTIqG2Y-Gy0f7QHKcp2-TIv7NZ3bu_YexmKiGuo9FBTeCtRnVzABBVnhx5EiShk=@mcbridemail.com>
2025-09-04 22:06 ` [RFC] View-Based File System Model with Program-Scoped Isolation Al Viro
2025-09-04 22:58 ` Blake McBride
2025-09-04 23:08 ` Al Viro [this message]
2025-09-04 23:41 ` Blake McBride
2025-09-04 23:57 ` Blake McBride
2025-09-05 0:06 ` Blake McBride
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=20250904230846.GR39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=blake@mcbridemail.com \
--cc=brauner@kernel.org \
--cc=colbym84@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.