linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Luis Henriques <lhenriques@suse.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-fsdevel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH] copy_file_range.2: Fix wrong kernel version information
Date: Wed, 14 Dec 2022 00:18:08 +0100	[thread overview]
Message-ID: <0c932ff1-1b5f-3a3b-1b81-1bbe710e1994@gmail.com> (raw)
In-Reply-To: <20221213120834.948163-1-amir73il@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2887 bytes --]

Hi Amir,

On 12/13/22 13:08, Amir Goldstein wrote:
> commit d7ba612d0 ("copy_file_range.2: Update cross-filesystem support
> for 5.12") prematurely documented kernel 5.12 as the version that
> changes the cross-fs copy_file_range() behavior, but that behavior
> change was only merged in kernel version 5.19.
> 
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>

Thanks!  Patch applied.

Cheers,

Alex

> ---
>   man2/copy_file_range.2 | 17 +++++++++++------
>   1 file changed, 11 insertions(+), 6 deletions(-)
> 
> diff --git a/man2/copy_file_range.2 b/man2/copy_file_range.2
> index ac74d9a07..25146a1dd 100644
> --- a/man2/copy_file_range.2
> +++ b/man2/copy_file_range.2
> @@ -152,7 +152,8 @@ Out of memory.
>   .B ENOSPC
>   There is not enough space on the target filesystem to complete the copy.
>   .TP
> -.BR EOPNOTSUPP " (since Linux 5.12)"
> +.BR EOPNOTSUPP " (since Linux 5.19)"
> +.\" commit 868f9f2f8e004bfe0d3935b1976f625b2924893b
>   The filesystem does not support this operation.
>   .TP
>   .B EOVERFLOW
> @@ -171,11 +172,13 @@ or
>   refers to an active swap file.
>   .TP
>   .BR EXDEV " (before Linux 5.3)"
> +.\" commit 5dae222a5ff0c269730393018a5539cc970a4726
>   The files referred to by
>   .IR fd_in " and " fd_out
>   are not on the same filesystem.
>   .TP
> -.BR EXDEV " (since Linux 5.12)"
> +.BR EXDEV " (since Linux 5.19)"
> +.\" commit 868f9f2f8e004bfe0d3935b1976f625b2924893b
>   The files referred to by
>   .IR fd_in " and " fd_out
>   are not on the same filesystem,
> @@ -191,13 +194,15 @@ emulation when it is not available.
>   A major rework of the kernel implementation occurred in Linux 5.3.
>   Areas of the API that weren't clearly defined were clarified and the API bounds
>   are much more strictly checked than on earlier kernels.
> -Applications should target the behaviour and requirements of 5.3 kernels.
>   .PP
> -Since Linux 5.12,
> +Since Linux 5.19,
>   cross-filesystem copies can be achieved
>   when both filesystems are of the same type,
>   and that filesystem implements support for it.
> -See BUGS for behavior prior to Linux 5.12.
> +See BUGS for behavior prior to Linux 5.19.
> +.PP
> +Applications should target the behaviour and requirements of 5.19 kernels,
> +that was also backported to earlier stable kernels.
>   .SH STANDARDS
>   The
>   .BR copy_file_range ()
> @@ -223,7 +228,7 @@ such as the use of reflinks (i.e., two or more inodes that share
>   pointers to the same copy-on-write disk blocks)
>   or server-side-copy (in the case of NFS).
>   .SH BUGS
> -In Linux 5.3 to Linux 5.11,
> +In Linux 5.3 to Linux 5.18,
>   cross-filesystem copies were implemented by the kernel,
>   if the operation was not supported by individual filesystems.
>   However, on some virtual filesystems,

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-12-13 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 12:08 [PATCH] copy_file_range.2: Fix wrong kernel version information Amir Goldstein
2022-12-13 23:18 ` Alejandro Colomar [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=0c932ff1-1b5f-3a3b-1b81-1bbe710e1994@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lhenriques@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).