From: Pavel Machek <pavel@ucw.cz>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] AT_NO_JUMPS/LOOKUP_NO_JUMPS
Date: Tue, 2 May 2017 21:57:40 +0200 [thread overview]
Message-ID: <20170502195740.GA4427@amd> (raw)
In-Reply-To: <20170319172414.GT29622@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 534 bytes --]
On Sun 2017-03-19 17:24:15, Al Viro wrote:
> Bringing back an old conversation - what do you think about the
> potential usefulness of the following ...at() option:
> * no mountpoint crossings allowed (mount --bind included)
Returning error or returning the object that should be hidden by the
mount?
I believe the second option would be a bit dangerous...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-05-02 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 17:24 [RFC] AT_NO_JUMPS/LOOKUP_NO_JUMPS Al Viro
2017-03-20 1:46 ` Linus Torvalds
2017-03-20 14:22 ` Omar Sandoval
2017-05-02 19:57 ` Pavel Machek [this message]
2017-05-02 20:49 ` Al Viro
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=20170502195740.GA4427@amd \
--to=pavel@ucw.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).