Linux Manual Pages development
 help / color / mirror / Atom feed
From: Dorjoy Chowdhury <dorjoychy111@gmail.com>
To: linux-man@vger.kernel.org
Cc: alx@kernel.org, brauner@kernel.org, jlayton@kernel.org
Subject: [PATCH 1/1] man/man2/openat2.2: Document OPENAT2_REGULAR flag
Date: Sat, 25 Apr 2026 19:39:28 +0600	[thread overview]
Message-ID: <20260425134048.62616-2-dorjoychy111@gmail.com> (raw)
In-Reply-To: <20260425134048.62616-1-dorjoychy111@gmail.com>

Signed-off-by: Dorjoy Chowdhury <dorjoychy111@gmail.com>
---
 man/man2/openat2.2 | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/man/man2/openat2.2 b/man/man2/openat2.2
index f0770f3a0..42ebf22ea 100644
--- a/man/man2/openat2.2
+++ b/man/man2/openat2.2
@@ -133,6 +133,19 @@ argument,
 .BR openat2 ()
 returns an error if unknown or conflicting flags are specified in
 .IR how.flags .
+.IP
+.BR openat2 ()
+also supports the below additional flags:
+.RS
+.TP
+.BR OPENAT2_REGULAR " (since Linux 7.2)"
+Only open the file specified by
+.I path
+if it is a regular file. If it is not a regular file,
+.BR openat2 ()
+fails with the error
+.BR EFTYPE .
+.RE
 .TP
 .I mode
 This field specifies the
@@ -471,6 +484,12 @@ and an escape from the root during path resolution was detected.
 contains
 .BR RESOLVE_NO_XDEV ,
 and a path component crosses a mount point.
+.TP
+.B EFTYPE
+.I how.flags
+contains
+.BR OPENAT2_REGULAR
+flag and the path is not a regular file.
 .SH STANDARDS
 Linux.
 .SH HISTORY
-- 
2.53.0


  reply	other threads:[~2026-04-25 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25 13:39 [PATCH 0/1] OPENAT2_REGULAR flag documentation Dorjoy Chowdhury
2026-04-25 13:39 ` Dorjoy Chowdhury [this message]
2026-04-25 14:58   ` [PATCH 1/1] man/man2/openat2.2: Document OPENAT2_REGULAR flag Alejandro Colomar
2026-04-25 15:07     ` Dorjoy Chowdhury
2026-04-25 17:39       ` Alejandro Colomar

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=20260425134048.62616-2-dorjoychy111@gmail.com \
    --to=dorjoychy111@gmail.com \
    --cc=alx@kernel.org \
    --cc=brauner@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox