From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andy Lutomirski <luto@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Linux API <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: new ...at() flag: AT_NO_JUMPS
Date: Mon, 1 May 2017 06:15:06 +0100 [thread overview]
Message-ID: <20170501051506.GY29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CALCETrX0dx3d6OQQ+1GJ_xgSz3iNVeRn+8o6b-+3f7awVOWdQg@mail.gmail.com>
On Sun, Apr 30, 2017 at 09:52:37PM -0700, Andy Lutomirski wrote:
> On Sun, Apr 30, 2017 at 9:10 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Sat, Apr 29, 2017 at 09:38:22PM -0700, Matthew Wilcox wrote:
> >
> >> It sounds more like AT_NO_ESCAPE ... or AT_BELOW, or something.
> >
> > I considered AT_ROACH_MOTEL at one point... Another interesting
> > question is whether EXDEV would've been better than ELOOP.
> > Opinions?
>
> In support of my homeland, I propose AT_HOTEL_CALIFORNIA.
>
> How about EXDEV for crossing a mountpoint and ELOOP for absolute
> symlinks or invalid ..? (Is there a technical reason why the same AT_
> flag should trigger both cases?)
You do realize that mount --bind can do everything absolute symlinks could,
right? And absolute symlinks most likely do lead to (or at least through)
a different fs...
next prev parent reply other threads:[~2017-05-01 5:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 22:04 new ...at() flag: AT_NO_JUMPS Al Viro
2017-04-29 23:17 ` Andy Lutomirski
2017-04-29 23:25 ` Al Viro
2017-04-30 1:13 ` Andy Lutomirski
2017-04-30 4:38 ` Matthew Wilcox
2017-04-30 16:10 ` Al Viro
2017-05-01 4:52 ` Andy Lutomirski
2017-05-01 5:15 ` Al Viro [this message]
2017-05-01 17:36 ` Jann Horn
2017-05-01 19:37 ` Andy Lutomirski
2017-05-05 0:30 ` Al Viro
2017-05-05 0:44 ` Andy Lutomirski
2017-05-05 1:06 ` Al Viro
2017-05-05 1:27 ` Linus Torvalds
2017-05-05 3:00 ` Al Viro
2017-05-05 4:01 ` Linus Torvalds
2017-05-05 4:31 ` Andy Lutomirski
2017-05-05 2:47 ` Jann Horn
2017-05-05 3:46 ` Linus Torvalds
2017-05-05 4:39 ` Al Viro
2017-05-05 4:44 ` Andy Lutomirski
2017-05-05 20:04 ` Eric W. Biederman
2017-05-05 20:28 ` Eric W. Biederman
2017-05-08 19:34 ` Mickaël Salaün
2017-05-18 8:50 ` David Drysdale
2017-09-10 20:26 Jürg Billeter
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=20170501051506.GY29622@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=willy@infradead.org \
/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).