From: Florian Weimer <fw@deneb.enyo.de>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Askar Safin <safinaskar@mail.ru>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: What about adding AT_NO_AUTOMOUNT analogue to openat2?
Date: Sat, 11 Apr 2020 12:51:31 +0200 [thread overview]
Message-ID: <87a73i9txo.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20200411070750.goak63tlej37wkbj@yavin.dot.cyphar.com> (Aleksa Sarai's message of "Sat, 11 Apr 2020 17:07:50 +1000")
* Aleksa Sarai:
> It would just give you -EXDEV (or perhaps -EREMOTE) if you walk into an
> automount (the same logic as with the other RESOLVE_NO_* flags). We
> could make it -ENOENT if you prefer, but that means userspace can't tell
> the difference between it hitting an automount and the target actually
> not existing.
Maybe there's a better way to show the difference to userspace
involving something related to O_PATH?
prev parent reply other threads:[~2020-04-11 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 22:41 What about adding AT_NO_AUTOMOUNT analogue to openat2? Askar Safin
2020-04-11 6:02 ` Aleksa Sarai
2020-04-11 6:45 ` Al Viro
2020-04-11 7:07 ` Aleksa Sarai
2020-04-11 10:51 ` Florian Weimer [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=87a73i9txo.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=cyphar@cyphar.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=safinaskar@mail.ru \
--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 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.