RE: access call not calling faccessat correctly

[Michael Morrell <mmorrell at tachyum dot com>]

Rats!  I didn't see that at the bottom of the manpage.  Never mind.  The bug must be elsewhere.

-----Original Message-----
From: Florian Weimer <fweimer@redhat.com> 
Sent: Monday, October 21, 2019 11:34 AM
To: Michael Morrell <mmorrell@tachyum.com>
Cc: libc-help@sourceware.org
Subject: Re: access call not calling faccessat correctly

* Michael Morrell:

> The manpage for "access" says it takes 4 arguments.
>
> ACCESS(2)                                                Linux Programmer's Manual                                                ACCESS(2)
>
> NAME
>        access, faccessat - check user's permissions for a file
>
> SYNOPSIS
>        #include <unistd.h>
>
>        int access(const char *pathname, int mode);
>
>        #include <fcntl.h>           /* Definition of AT_* constants */
>        #include <unistd.h>
>
>        int faccessat(int dirfd, const char *pathname, int mode, int 
> flags);

For the system call?  No it does not.  You need to scroll down for userspace/kernel difference.

Thanks,
Florian