Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Aleksa Sarai <cyphar@xxxxxxxxxx>
Subject: Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
From: David Howells <dhowells@xxxxxxxxxx>
Date: Fri, 06 Mar 2020 14:48:50 +0000
Cc: dhowells@xxxxxxxxxx, Christian Brauner <christian.brauner@xxxxxxxxxx>, Florian Weimer <fweimer@xxxxxxxxxx>, linux-api@xxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, metze@xxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20200306140032.tpwfytofaeuazalo@yavin>
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903

Aleksa Sarai <cyphar@xxxxxxxxxx> wrote:

> Right, but open_tree() doesn't need RESOLVE_ flags (nor can you add them
> without an open_tree2()). Instead you can pass an O_PATH file descriptor
> with AT_EMPTY_PATH which you could've safely resolved with openat2().

Note that openat2() is not a substitute for open_tree(). See the effect of
the OPEN_TREE_CLONE flag.

David

References:
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: Aleksa Sarai
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: Christian Brauner
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: Christian Brauner
- Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: David Howells
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: Christian Brauner
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: Florian Weimer
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: David Howells
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: David Howells
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: Christian Brauner
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: David Howells

Prev by Date: Re: [RFC][PATCH] Mark AT_* path flags as deprecated and add missing RESOLVE_ flags
Next by Date: Re: [RFC][PATCH] Mark AT_* path flags as deprecated and add missing RESOLVE_ flags
Previous by thread: Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
Next by thread: Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]