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 for Android: free password hash cracker in your pocket

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

Message-ID: <4040642.1583505822@warthog.procyon.org.uk>
Date:   Fri, 06 Mar 2020 14:43:42 +0000
From:   David Howells <dhowells@...hat.com>
To:     Christian Brauner <christian.brauner@...ntu.com>
Cc:     dhowells@...hat.com, linux-api@...r.kernel.org,
        viro@...iv.linux.org.uk, torvalds@...ux-foundation.org,
        metze@...ba.org, cyphar@...har.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

Christian Brauner <christian.brauner@...ntu.com> wrote:

> > +	if (flags & O_NOFOLLOW)
> > +		lookup_flags &= ~LOOKUP_FOLLOW;
> 
> Odd change. But I guess you're doing it for the sake of consistency
> because of how you treat NO_TERMINAL_SYMLINKS below.

Not really.  The default is to follow.  Both remove the LOOKUP_FOLLOW flag and
neither set it.

David