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 for Android: free password hash cracker in your pocket

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

Message-ID: <X0FicR_DkHDIm8QFrAKwaEcu5_rAQY4OUHYnA62zwbNXPxJJ6vk-e3zsNkoTaOFSXVwAaPom7WDhrnSauyUjtqvPYDQKIDwsHzY2TWnSuv8=@mcbridemail.com>
Date: Thu, 04 Sep 2025 23:57:58 +0000
From: Blake McBride <blake@...ridemail.com>
To: Blake McBride <blake@...ridemail.com>
Cc: Al Viro <viro@...iv.linux.org.uk>, "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

Let me be a little more clear about the application programmer-level API - nothing has to change. A context or view is selected by the user before a program is started (unless a program has a default or specific context). The API that the program uses is utterly unchanged. However, all of the calls are within the context of the view.

--blake





On Thursday, September 4th, 2025 at 6:41 PM, Blake McBride <blake@...ridemail.com> wrote:

> 
> 
> On Thursday, September 4th, 2025 at 6:09 PM, Al Viro viro@...iv.linux.org.uk wrote:
> 
> > 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.
> 
> 
> 
> Yes. This is what is intended. All of userland would just operate on the view the same as if that was your real hierarchy.
> 
> > 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.
> 
> 
> 
> These views are not pasted together subtrees. Each view can have utterly different layouts of the same set of files.
> 
> 
> 
> 
> > 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.
> 
> 
> I did not specify the implementation, just the user experience. All of userland would "appear" to function as it does now. The same with the syscalls that are made by the application code. They all effect the current view as if it was the real hierarchy.
> 
> --blake