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: Mon, 02 Mar 2020 16:37:45 +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: <20200302152458.hznqqssixhlpykgr@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:

> Now let's just hope no new syscalls need both AT_RECURSIVE and
> RESOLVE_NO_SYMLINKS

Ummm...  AT_RECURSIVE is used by open_tree() to determine whether to copy just
the mount it's looking at or the entire subtree from that point.

David

Follow-Ups:
- Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
  - From: David Howells

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

Prev by Date: Re: [PATCH v2] ext4: use non-movable memory for superblock readahead
Next by Date: Re: [PATCHv2] exec: Fix a deadlock in ptrace
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]