All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Renzo Davoli <renzo@cs.unibo.it>
Cc: linux-man@vger.kernel.org
Subject: Re: utimensat(2) and faccessat(2): man pages do not mention AT_EMPTY_PATH flag
Date: Sat, 9 Dec 2023 13:00:08 +0100	[thread overview]
Message-ID: <ZXRWyMQh2_uV_U_1@debian> (raw)
In-Reply-To: <ZXBVJ5phq4tK1fWq@cs.unibo.it>

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Dear Renzo,

On Wed, Dec 06, 2023 at 12:04:07PM +0100, Renzo Davoli wrote:
> Dear Alejandro,
> 
> utimensat and faccessat support the flag AT_EMPTY_PATH since Linux 5.8 but
> this option is still missing in the man pages.
> 
> (actually Linux 5.8 added faccessat2: glibc wrapper for faccessat
>  uses faccessat2, and faccessat2 does support AT_EMPTY_PATH).
> 
> I think the standard text used in many other -at man page could fit
> for these system calls, too.
> 
> AT_EMPTY_PATH (since Linux 5.8)
> 	If  pathname is an empty string, operate on the file referred to
> 	by dirfd (which may have been obtained using the open(2)  O_PATH
> 	flag).   In  this case, dirfd can refer to any type of file, not
> 	just a directory.  If dirfd is AT_FDCWD, the  call  operates  on
> 	the current working directory.  This flag is Linux-specific;
> 	define _GNU_SOURCE to obtain its definition.

Thanks for reporting that.  Would you mind preparing a patch updating
the page?  If you need any help, just ask for it.

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-09 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 11:04 utimensat(2) and faccessat(2): man pages do not mention AT_EMPTY_PATH flag Renzo Davoli
2023-12-09 12:00 ` Alejandro Colomar [this message]
2023-12-09 16:38   ` Renzo Davoli
2023-12-09 21:36     ` Alejandro Colomar
2023-12-10  8:07       ` Renzo Davoli
     [not found]   ` <ZXSXwZMWbojebpH1@cs.unibo.it>
2024-01-01 11:43     ` Alejandro Colomar
2024-01-01 15:48       ` Renzo Davoli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZXRWyMQh2_uV_U_1@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=renzo@cs.unibo.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.