linux-kernel - Re: [RFC] View-Based File System Model with Program-Scoped Isolation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250904230846.GR39973@ZenIV>
Date: Fri, 5 Sep 2025 00:08:46 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Blake McBride <blake@...ridemail.com>
Cc: "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"brauner@...nel.org" <brauner@...nel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	Colby Wes McBride <colbym84@...il.com>
Subject: Re: [RFC] View-Based File System Model with Program-Scoped Isolation

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.