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] process_madvise.2: Add note about missing glibc wrapper
Date: Sat, 13 Feb 2021 16:46:27 +0100 [thread overview]
Message-ID: <03db241c-5b1a-94df-5dc0-9ae574183ebf@gmail.com> (raw)
In-Reply-To: <20210211174454.48112-2-alx.manpages@gmail.com>
Hi Alex,
On 2/11/21 6:44 PM, Alejandro Colomar wrote:
> Glibc bug: <https://sourceware.org/bugzilla/show_bug.cgi?id=27380>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks. Patch applied.
Cheers,
Michael
> ---
> man2/process_madvise.2 | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/man2/process_madvise.2 b/man2/process_madvise.2
> index d33c32f63..9dc90ced1 100644
> --- a/man2/process_madvise.2
> +++ b/man2/process_madvise.2
> @@ -36,6 +36,10 @@ process_madvise \- give advice about use of memory to a process
> .BI " unsigned long " vlen ", int " advice ,
> .BI " unsigned int " flags ");"
> .fi
> +.PP
> +.IR Note :
> +There is no glibc wrapper for this system call; see NOTES.
> +.\" FIXME: See <https://sourceware.org/bugzilla/show_bug.cgi?id=27380>
> .SH DESCRIPTION
> The
> .BR process_madvise()
> @@ -218,6 +222,9 @@ Support for this system call is optional,
> depending on the setting of the
> .B CONFIG_ADVISE_SYSCALLS
> configuration option.
> +.SH NOTES
> +Glibc does not provide a wrapper for this system call; call it using
> +.BR syscall (2).
> .SH SEE ALSO
> .BR madvise (2),
> .BR pidfd_open (2),
>
--
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-13 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 17:44 [PATCH] process_madvise.2: Add note about missing glibc wrapper Alejandro Colomar
2021-02-13 15:46 ` 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=03db241c-5b1a-94df-5dc0-9ae574183ebf@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