From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: system calls not intended for user space
Date: Mon, 17 May 2021 09:51:13 +0200 [thread overview]
Message-ID: <5cbacfde-8f54-1fef-77cc-6f45d4ae2bd3@gmail.com> (raw)
In-Reply-To: <c7dcc24d-3c7a-39cf-48a9-2357299e8b93@gmail.com>
Hi Michael,
On 5/17/21 9:47 AM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
>
> On 5/17/21 3:04 AM, Michael Kerrisk (man-pages) wrote:
>> Hi Alex,
>>
>> On Fri, 14 May 2021 at 07:25, Alejandro Colomar (man-pages)
>> <alx.manpages@gmail.com> wrote:
>>>
>>> Hello Michael,
>>>
>>> There are some syscalls that are not intended to be used from user
>>> space. See restart_syscall(2). Should I document those as
>>> syscall(SYS_...) or not?
>>
>> Yes, this function is an odd case. (Are there others? Perhaps
>> sigreturn(2) also.)
>
> rt_sigqueueinfo.2 maybe, for which, by the way, I sent a patch recently,
> so you may prefer to ingore it.
>
>>
>> I think I would just ignore these two. (That is, no changes.)
>
> Agree. I sent the patch for rt_sigqueueinfo.2 because in NOTES it
> already talked about syscall(2), and by the DESCRIPTION it looks like
> it's used by library writers (that's user space).
I see you've applied the patch (it was 2/8 that you applied today
(<https://lore.kernel.org/linux-man/20210515182027.186403-2-alx.manpages@gmail.com/T/#u>)).
Check this before pushing and decide :)
Cheers,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-05-17 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 19:25 system calls not intended for user space Alejandro Colomar (man-pages)
2021-05-17 1:04 ` Michael Kerrisk (man-pages)
2021-05-17 7:47 ` Alejandro Colomar (man-pages)
2021-05-17 7:51 ` Alejandro Colomar (man-pages) [this message]
2021-05-17 8:05 ` Michael Kerrisk (man-pages)
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=5cbacfde-8f54-1fef-77cc-6f45d4ae2bd3@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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