linux-kernel - Re: [RFC][PATCH] Mark AT_* path flags as deprecated and add missing RESOLVE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 05 Mar 2020 20:35:07 +0000
From:   David Howells <dhowells@...hat.com>
To:     Stefan Metzmacher <metze@...ba.org>
Cc:     dhowells@...hat.com, linux-api@...r.kernel.org,
        viro@...iv.linux.org.uk, torvalds@...ux-foundation.org,
        cyphar@...har.com, christian.brauner@...ntu.com,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] Mark AT_* path flags as deprecated and add missing RESOLVE_ flags

Stefan Metzmacher <metze@...ba.org> wrote:

> Where's the RESOLVE_NO_TERMINAL_AUTOMOUNTS check?

See:

      (3) Make openat2() support RESOLVE_NO_TERMINAL_SYMLINKS.  LOOKUP_OPEN
          internally implies LOOKUP_AUTOMOUNT, and AT_EMPTY_PATH is probably not
          worth supporting (maybe use dup2() instead?).

As things currently stand, automount following is explicitly forced on for
open and create.  We can make it error out instead if this is desirable if
RESOLVE_NO_TERMINAL_AUTOMOUNTS in such a case.

David