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] splice.2: Use 'off64_t' instead of 'loff_t'
Date: Mon, 15 Feb 2021 20:59:25 +0100 [thread overview]
Message-ID: <7b2aba11-c93f-0e90-c518-a17cd4059a0b@gmail.com> (raw)
In-Reply-To: <20210215131522.450666-5-alx.manpages@gmail.com>
Hi Alex,
On 2/15/21 2:15 PM, Alejandro Colomar wrote:
> The kernel syscall uses 'loff_t', but the glibc wrapper uses 'off64_t'.
> Let's document the wrapper prototype, as in other pages.
>
> ......
>
> .../glibc$ grep_glibc_prototype splice
> sysdeps/unix/sysv/linux/bits/fcntl-linux.h:398:
> extern __ssize_t splice (int __fdin, __off64_t *__offin, int __fdout,
> __off64_t *__offout, size_t __len,
> unsigned int __flags);
> .../glibc$
>
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
Thanks! Patch applied.
Cheers,
Michael
> ---
> man2/splice.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/splice.2 b/man2/splice.2
> index 6e9029281..d07639810 100644
> --- a/man2/splice.2
> +++ b/man2/splice.2
> @@ -31,8 +31,8 @@ splice \- splice data to/from a pipe
> .BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
> .B #include <fcntl.h>
> .PP
> -.BI "ssize_t splice(int " fd_in ", loff_t *" off_in ", int " fd_out ,
> -.BI " loff_t *" off_out ", size_t " len \
> +.BI "ssize_t splice(int " fd_in ", off64_t *" off_in ", int " fd_out ,
> +.BI " off64_t *" off_out ", size_t " len \
> ", unsigned int " flags );
> .\" Return type was long before glibc 2.7
> .fi
>
--
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 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:15 [PATCH] splice.2: Use 'off64_t' instead of 'loff_t' Alejandro Colomar
2021-02-15 19:59 ` 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=7b2aba11-c93f-0e90-c518-a17cd4059a0b@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