From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] socketcall.2: Add note about missing glibc wrapper
Date: Mon, 15 Feb 2021 20:56:15 +0100 [thread overview]
Message-ID: <8d9fa5cf-b2e8-1588-5ac0-d871decb1690@gmail.com> (raw)
In-Reply-To: <20210215131522.450666-3-alx.manpages@gmail.com>
Hi Alex,
On 2/15/21 2:15 PM, Alejandro Colomar wrote:
> ......
>
> .../glibc$ grep_glibc_prototype socketcall
> .../glibc$
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks! Patch applied.
Cheers,
Michael
> ---
> man2/socketcall.2 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man2/socketcall.2 b/man2/socketcall.2
> index a3012d4c7..d1803d906 100644
> --- a/man2/socketcall.2
> +++ b/man2/socketcall.2
> @@ -31,6 +31,9 @@ socketcall \- socket system calls
> .PP
> .BI "int socketcall(int " call ", unsigned long *" args );
> .fi
> +.PP
> +.IR Note :
> +There is no glibc wrapper for this system call; see NOTES.
> .SH DESCRIPTION
> .BR socketcall ()
> is a common kernel entry point for the socket system calls.
> @@ -153,6 +156,9 @@ T}
> This call is specific to Linux, and should not be used in programs
> intended to be portable.
> .SH NOTES
> +Glibc does not provide a wrapper for this system call; call it using
> +.BR syscall (2).
> +.PP
> On a some architectures\(emfor example, x86-64 and ARM\(emthere is no
> .BR socketcall ()
> system call; instead
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-02-15 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:15 [PATCH] socketcall.2: Add note about missing glibc wrapper Alejandro Colomar
2021-02-15 19:56 ` Michael Kerrisk (man-pages) [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=8d9fa5cf-b2e8-1588-5ac0-d871decb1690@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--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