From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com, jaltman@auristor.com,
Al Viro <viro@zeniv.linux.org.uk>,
coda@cs.cmu.edu, linux-afs@lists.infradead.org,
CIFS <linux-cifs@vger.kernel.org>,
"open list:NFS, SUNRPC, AND..." <linux-nfs@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] vfs: syscalls: Add create_automount() and remove_automount()
Date: Wed, 19 Feb 2020 21:39:53 +0000 [thread overview]
Message-ID: <260918.1582148393@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAHk-=wgtAEvD6J_zVPKXHDjZ7rNe3piRzD_bX2HcVgY3AMGhjw@mail.gmail.com>
Linus Torvalds <torvalds@linux-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
prev parent reply other threads:[~2020-02-19 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:35 [RFC PATCH] vfs: syscalls: Add create_automount() and remove_automount() David Howells
2020-02-19 14:43 ` Geert Uytterhoeven
2020-02-19 15:08 ` David Howells
2020-02-19 17:00 ` Linus Torvalds
2020-02-19 17:55 ` David Howells
2020-02-19 18:55 ` Linus Torvalds
2020-02-19 19:07 ` Linus Torvalds
2020-02-19 19:26 ` Linus Torvalds
2020-02-19 19:58 ` David Howells
2020-02-19 20:12 ` Linus Torvalds
2020-02-19 21:39 ` David Howells [this message]
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=260918.1582148393@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=coda@cs.cmu.edu \
--cc=jaltman@auristor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).