From: Alejandro Colomar Date: Tue, 25 Mar 2025 00:45:01 +0000 (+0100) Subject: man/man2/posix_fadvise.2: Consistency fix (len => size) X-Git-Tag: man-pages-6.14~42 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=04ac8a314716e162a8503a3256a7ede3062d402f;p=thirdparty%2Fman-pages.git man/man2/posix_fadvise.2: Consistency fix (len => size) Fixes: 18e7c4597c4e (2024-11-17; "man/: Terminology consistency reforms (n, size, length)") Closes: Reported-by: Paul Pluzhnikov Signed-off-by: Alejandro Colomar --- diff --git a/man/man2/posix_fadvise.2 b/man/man2/posix_fadvise.2 index c7a42baa9..0c7209a5d 100644 --- a/man/man2/posix_fadvise.2 +++ b/man/man2/posix_fadvise.2 @@ -38,8 +38,8 @@ file data in a specific pattern in the future, thus allowing the kernel to perform appropriate optimizations. .P The \fIadvice\fP applies to a (not necessarily existent) region starting -at \fIoffset\fP and extending for \fIlen\fP bytes (or until the end of -the file if \fIlen\fP is 0) within the file referred to by \fIfd\fP. +at \fIoffset\fP and extending for \fIsize\fP bytes (or until the end of +the file if \fIsize\fP is 0) within the file referred to by \fIfd\fP. The \fIadvice\fP is not binding; it merely constitutes an expectation on behalf of the application. @@ -148,7 +148,7 @@ The underlying system call is called (or, on some architectures, .BR fadvise64_64 ()); the difference between the two is that the former system call -assumes that the type of the \fIlen\fP argument is \fIsize_t\fP, +assumes that the type of the \fIsize\fP argument is \fIsize_t\fP, while the latter expects \fIloff_t\fP there. .SS Architecture-specific variants Some architectures require