[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <260918.1582148393@warthog.procyon.org.uk>
Date: Wed, 19 Feb 2020 21:39:53 +0000
From: David Howells <dhowells@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: dhowells@...hat.com, jaltman@...istor.com,
Al Viro <viro@...iv.linux.org.uk>, coda@...cmu.edu,
linux-afs@...ts.infradead.org, CIFS <linux-cifs@...r.kernel.org>,
"open list:NFS, SUNRPC, AND..." <linux-nfs@...r.kernel.org>,
linux-btrfs <linux-btrfs@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] vfs: syscalls: Add create_automount() and remove_automount()
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> so you _could_ actually just make the rule be something simple like
>
> symlink(target, "//datagoeshere")
>
> being the "create magic autolink directory using "datagoeshere".
Interesting. I'll ask around to see if this is feasible. Some applications
(emacs being one maybe) sometimes appear to store information in symlink
bodies - I'm not sure if any of those could be a problem.
Since the mountpoint body is formulaic:
[%#](<cellname>:)?<volumename>(.readonly|.backup)?.
maybe I can use that pattern.
symlink() would be returning a dentry that appears to be a directory, but it
doesn't look like that should be a problem.
> So then you could again script things with
>
> mknod dirname c X Y
> echo "datagoeshere" > dirname
This would be tricky to get right as it's not atomic and the second part could
fail to happen. For extra fun, another client could interfere between the
steps (setxattr would be safer than write here).
David
Powered by blists - more mailing lists