[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-man
Subject:    AW: [PATCH] copy_file_range.2: Kernel v5.12 updates
From:       Walter Harms <wharms () bfs ! de>
Date:       2021-02-25 15:29:02
Message-ID: 1420fad0d18843b29c8c97919ebcb421 () bfs ! de
[Download RAW message or body]

I would not mention crossfile support in 5.3.
It is more confusing than helping.

If the support works after 5.12 just say it. Nobody will write
a programm an claim "works for 5.3 and >5.12 ".

re,
 wh

________________________________________
Von: Luis Henriques <lhenriques@suse.de>
Gesendet: Donnerstag, 25. Februar 2021 11:21:04
An: Amir Goldstein
Cc: Alejandro Colomar; Michael Kerrisk; Jeff Layton; Steve French; Miklos S=
zeredi; Trond Myklebust; Anna Schumaker; Alexander Viro; Darrick J. Wong; D=
ave Chinner; Greg KH; Nicolas Boichat; Ian Lance Taylor; Luis Lozano; Andre=
as Dilger; Olga Kornievskaia; Christoph Hellwig; ceph-devel; linux-kernel; =
CIFS; samba-technical; linux-fsdevel; Linux NFS Mailing List; linux-man
Betreff: Re: [PATCH] copy_file_range.2: Kernel v5.12 updates

On Wed, Feb 24, 2021 at 06:10:45PM +0200, Amir Goldstein wrote:
> On Wed, Feb 24, 2021 at 4:22 PM Luis Henriques <lhenriques@suse.de> wrote=
:
> >
> > Update man-page with recent changes to this syscall.
> >
> > Signed-off-by: Luis Henriques <lhenriques@suse.de>
> > ---
> > Hi!
> >
> > Here's a suggestion for fixing the manpage for copy_file_range().  Note=
 that
> > I've assumed the fix will hit 5.12.
> >
> >  man2/copy_file_range.2 | 10 +++++++++-
> >  1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/man2/copy_file_range.2 b/man2/copy_file_range.2
> > index 611a39b8026b..b0fd85e2631e 100644
> > --- a/man2/copy_file_range.2
> > +++ b/man2/copy_file_range.2
> > @@ -169,6 +169,9 @@ Out of memory.
> >  .B ENOSPC
> >  There is not enough space on the target filesystem to complete the cop=
y.
> >  .TP
> > +.B EOPNOTSUPP
> > +The filesystem does not support this operation.
> > +.TP
> >  .B EOVERFLOW
> >  The requested source or destination range is too large to represent in=
 the
> >  specified data types.
> > @@ -187,7 +190,7 @@ refers to an active swap file.
> >  .B EXDEV
> >  The files referred to by
> >  .IR fd_in " and " fd_out
> > -are not on the same mounted filesystem (pre Linux 5.3).
> > +are not on the same mounted filesystem (pre Linux 5.3 and post Linux 5=
.12).
>
> I think you need to drop the (Linux range) altogether.
> What's missing here is the NFS cross server copy use case.
> Maybe:
>
> ...are not on the same mounted filesystem and the source and target files=
ystems
> do not support cross-filesystem copy.
>
> You may refer the reader to VERSIONS section where it will say which
> filesystems support cross-fs copy as of kernel version XXX (i.e. cifs and=
 nfs).
>
> >  .SH VERSIONS
> >  The
> >  .BR copy_file_range ()
> > @@ -202,6 +205,11 @@ Applications should target the behaviour and requi=
rements of 5.3 kernels.
> >  .PP
> >  First support for cross-filesystem copies was introduced in Linux 5.3.
> >  Older kernels will return -EXDEV when cross-filesystem copies are atte=
mpted.
> > +.PP
> > +After Linux 5.12, support for copies between different filesystems was=
 dropped.
> > +However, individual filesystems may still provide
> > +.BR copy_file_range ()
> > +implementations that allow copies across different devices.
>
> Again, this is not likely to stay uptodate for very long.
> The stable kernels are expected to apply your patch (because it fixes
> a regression)
> so this should be phrased differently.
> If it were me, I would provide all the details of the situation to
> Michael and ask him
> to write the best description for this section.

Thanks Amir.

Yeah, it's tricky.  Support was added and then dropped.   Since stable
kernels will be picking this patch,  maybe the best thing to do is to no
mention the generic cross-filesystem support at all...?  Or simply say
that 5.3 temporarily supported it but that support was later dropped.

Michael (or Alejandro), would you be OK handling this yourself as Amir
suggested?

Cheers,
--
Lu=EDs
[prev in list] [next in list] [prev in thread] [next in thread]