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] copy_file_range.2: SYNOPSIS: Fix prototype parameter types
Date: Wed, 30 Dec 2020 23:43:41 +0100 [thread overview]
Message-ID: <2b1cbbc7-a1f3-dbef-1d23-d96409e4490c@gmail.com> (raw)
In-Reply-To: <20201230214147.874671-5-alx.manpages@gmail.com>
Hi Alex,
On 12/30/20 10:41 PM, Alejandro Colomar wrote:
> Glibc uses 'off64_t' instead of 'loff_t'.
Okay.
> This patch doesn't change the types in the code example,
> because it uses the Linux syscall, and not the glibc wrapper.
I think the example probably also needs fixing then. There's
no longer a need for syscall(2) in this example, I think.
Thanks,
Michael
> ......
>
> $ syscall='copy_file_range';
> $ ret='ssize_t';
> $ find glibc/ -type f -name '*.h' \
> |xargs pcregrep -Mn "(?s)^[\w\s]*${ret}\s*${syscall}\s*\(.*?;";
> glibc/posix/unistd.h:1121:
> ssize_t copy_file_range (int __infd, __off64_t *__pinoff,
> int __outfd, __off64_t *__poutoff,
> size_t __length, unsigned int __flags);
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
> man2/copy_file_range.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/copy_file_range.2 b/man2/copy_file_range.2
> index 1692aa44a..6f4708c4b 100644
> --- a/man2/copy_file_range.2
> +++ b/man2/copy_file_range.2
> @@ -30,8 +30,8 @@ copy_file_range \- Copy a range of data from one file to another
> .B #define _GNU_SOURCE
> .B #include <unistd.h>
> .PP
> -.BI "ssize_t copy_file_range(int " fd_in ", loff_t *" off_in ,
> -.BI " int " fd_out ", loff_t *" off_out ,
> +.BI "ssize_t copy_file_range(int " fd_in ", off64_t *" off_in ,
> +.BI " int " fd_out ", off64_t *" off_out ,
> .BI " size_t " len ", unsigned int " flags );
> .fi
> .SH DESCRIPTION
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-12-30 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 21:41 [PATCH] copy_file_range.2: SYNOPSIS: Fix prototype parameter types Alejandro Colomar
2020-12-30 22:43 ` Michael Kerrisk (man-pages) [this message]
2020-12-30 23:20 ` Alejandro Colomar (man-pages)
2020-12-31 8:58 ` Michael Kerrisk (man-pages)
2020-12-31 12:46 ` Alejandro Colomar (man-pages)
2021-01-02 8:44 ` Michael Kerrisk (man-pages)
2020-12-31 13:01 ` [PATCH] Various pages: Consistently use 'unsigned int' Alejandro Colomar
2021-01-02 7:33 ` Michael Kerrisk (man-pages)
2020-12-31 13:24 ` [PATCH v2] copy_file_range.2: Document glibc wrapper instead of kernel syscall Alejandro Colomar
2021-01-01 21:23 ` 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=2b1cbbc7-a1f3-dbef-1d23-d96409e4490c@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