From: Al Viro <viro@zeniv.linux.org.uk>
To: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo.com>
Cc: Ian Kent <raven@themaw.net>, Matthew Wilcox <willy@infradead.org>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
Miklos Szeredi <mszeredi@redhat.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Ross Zwisler <zwisler@google.com>,
Aleksa Sarai <cyphar@cyphar.com>,
Eric Biggers <ebiggers@google.com>,
Mattias Nissler <mnissler@chromium.org>,
linux-fsdevel@vger.kernel.org, alexander@mihalicyn.com
Subject: Re: [RFC PATCH] autofs: find_autofs_mount overmounted parent support
Date: Mon, 8 Mar 2021 00:28:14 +0000 [thread overview]
Message-ID: <YEVvnvFNpfld7MXM@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <YEVr5jNlpu2jcdzs@zeniv-ca.linux.org.uk>
On Mon, Mar 08, 2021 at 12:12:22AM +0000, Al Viro wrote:
> Wait, so you have /proc overmounted, without anything autofs-related on
> /proc/sys/fs/binfmt_misc and still want to have the pathname resolved, just
> because it would've resolved with that overmount of /proc removed?
>
> I hope I'm misreading you; in case I'm not, the ABI is extremely
> tasteless and until you manage to document the exact semantics you want
> for param->path, consider it NAKed.
BTW, if that thing would be made to work, what's to stop somebody from
doing ...at() syscalls with the resulting fd as a starting point and pathnames
starting with ".."? "/foo is overmounted, but we can get to anything under
/foo/bar/ in the underlying tree since there's an autofs mount somewhere in
/foo/bar/splat/puke/*"?
IOW, the real question (aside of "WTF?") is what are you using the
resulting descriptor for and what do you need to be able to do with it.
Details, please.
next prev parent reply other threads:[~2021-03-08 0:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 15:28 [RFC PATCH] autofs: find_autofs_mount overmounted parent support Alexander Mikhalitsyn
2021-03-04 6:54 ` Ian Kent
2021-03-04 10:11 ` Alexander Mikhalitsyn
2021-03-05 10:10 ` Ian Kent
2021-03-05 11:55 ` Alexander Mikhalitsyn
2021-03-06 9:13 ` Ian Kent
2021-03-09 10:43 ` Alexander Mikhalitsyn
2021-03-23 8:44 ` Ian Kent
2021-03-24 14:20 ` Alexander Mihalicyn
2021-03-07 23:51 ` Al Viro
2021-03-08 0:12 ` Al Viro
2021-03-08 0:28 ` Al Viro [this message]
2021-03-09 11:31 ` Alexander Mikhalitsyn
2021-03-22 7:53 ` Alexander Mikhalitsyn
2021-03-03 16:17 Alexander Mikhalitsyn
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=YEVvnvFNpfld7MXM@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=alexander.mikhalitsyn@virtuozzo.com \
--cc=alexander@mihalicyn.com \
--cc=autofs@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=ebiggers@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnissler@chromium.org \
--cc=mszeredi@redhat.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=raven@themaw.net \
--cc=willy@infradead.org \
--cc=zwisler@google.com \
/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.