linux-kernel - Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <25389.1479458901@warthog.procyon.org.uk>
Date:   Fri, 18 Nov 2016 08:48:21 +0000
From:   David Howells <dhowells@...hat.com>
To:     Jeff Layton <jlayton@...hat.com>
Cc:     dhowells@...hat.com, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] statx: Add a system call to make enhanced file info available

Jeff Layton <jlayton@...hat.com> wrote:

> > If neither AT_STATX_*_SYNC flag is set, the behaviour is the default for
> > stat() on that filesystem.
> > 
> 
> We also need to specify here what happens if both bits are set. Should
> that be -EINVAL?

Makes sense.

This leads to another thought: should fstatat() be allowed to take AT_STATX_*
flags?

David