Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Dorjoy Chowdhury <dorjoychy111@gmail.com>
Cc: linux-man@vger.kernel.org, brauner@kernel.org, jlayton@kernel.org
Subject: Re: [PATCH 1/1] man/man2/openat2.2: Document OPENAT2_REGULAR flag
Date: Sat, 25 Apr 2026 19:39:36 +0200	[thread overview]
Message-ID: <aez7bEeb7eceg5rI@devuan> (raw)
In-Reply-To: <CAFfO_h7eZdMUdgYhYc3pEYnYCWK=q6qFis0UmuK=4oh90ADRDQ@mail.gmail.com>

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

Hey Dorjoy,

On 2026-04-25T21:07:04+0600, Dorjoy Chowdhury wrote:
> > > +.BR openat2 ()
> > > +fails with the error
> > > +.BR EFTYPE .
> >
> > Hmmm, this error code is new to me.
> >
> >         alx@devuan:~$ errno EFTYPE
> >         alx@devuan:~$ echo $?
> >         1
> >         alx@devuan:~$ man 3 errno | grep EFTYPE
> >         alx@devuan:~$ grepc EFTYPE /usr/include/
> >         alx@devuan:~$
> >
> > I don't see it documented, nor defined under </usr/include>.
> > Is this error code available in user space?
> > Is it a new error code?
> >
> 
> Yes. This is a new error code added in the patch series i.e., if the
> path is not a regular file, then this new error code is returned from
> the system call. Does the new error code need to be included anywhere
> else for man pages?

Yes, it should be documented in the errno(3) manual page.

It should also be added to glibc's <errno.h>, of course.

However, that can be done after the code has been merged to Linus's
tree.  But you could write the documentation for errno(3) already.


Cheers,
Alex

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

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

      reply	other threads:[~2026-04-25 17:39 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 ` [PATCH 1/1] man/man2/openat2.2: Document OPENAT2_REGULAR flag Dorjoy Chowdhury
2026-04-25 14:58   ` Alejandro Colomar
2026-04-25 15:07     ` Dorjoy Chowdhury
2026-04-25 17:39       ` Alejandro Colomar [this message]

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=aez7bEeb7eceg5rI@devuan \
    --to=alx@kernel.org \
    --cc=brauner@kernel.org \
    --cc=dorjoychy111@gmail.com \
    --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