* [PATCH v2] xfs_io: Improvements to copy_range return code handling
@ 2016-12-14 21:28 Anna Schumaker
2016-12-15 11:26 ` Carlos Maiolino
0 siblings, 1 reply; 2+ messages in thread
From: Anna Schumaker @ 2016-12-14 21:28 UTC (permalink / raw)
To: linux-xfs; +Cc: david
If copy_file_range() returns 0, then that means no data was copied. We
should break out of the loop in this case to prevent looping
indefinitely.
Additionally, if an error is returned by copy_file_range() then we need
to print out the string form to be used by error checking tests in
xfstests.
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
---
v2:
- Use perror() instead of fprintf()
---
io/copy_file_range.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/io/copy_file_range.c b/io/copy_file_range.c
index 88203e9..249c649 100644
--- a/io/copy_file_range.c
+++ b/io/copy_file_range.c
@@ -49,8 +49,11 @@ copy_file_range(int fd, loff_t *src, loff_t *dst, size_t len)
do {
ret = syscall(__NR_copy_file_range, fd, src, file->fd, dst, len, 0);
- if (ret == -1)
+ if (ret == -1) {
+ perror("copy_range");
return errno;
+ } else if (ret == 0)
+ break;
len -= ret;
} while (len > 0);
--
2.10.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2] xfs_io: Improvements to copy_range return code handling
2016-12-14 21:28 [PATCH v2] xfs_io: Improvements to copy_range return code handling Anna Schumaker
@ 2016-12-15 11:26 ` Carlos Maiolino
0 siblings, 0 replies; 2+ messages in thread
From: Carlos Maiolino @ 2016-12-15 11:26 UTC (permalink / raw)
To: Anna Schumaker; +Cc: linux-xfs, david
On Wed, Dec 14, 2016 at 04:28:46PM -0500, Anna Schumaker wrote:
> If copy_file_range() returns 0, then that means no data was copied. We
> should break out of the loop in this case to prevent looping
> indefinitely.
>
looks good for me, you can add
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> Additionally, if an error is returned by copy_file_range() then we need
> to print out the string form to be used by error checking tests in
> xfstests.
>
> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
> ---
> v2:
> - Use perror() instead of fprintf()
> ---
> io/copy_file_range.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/io/copy_file_range.c b/io/copy_file_range.c
> index 88203e9..249c649 100644
> --- a/io/copy_file_range.c
> +++ b/io/copy_file_range.c
> @@ -49,8 +49,11 @@ copy_file_range(int fd, loff_t *src, loff_t *dst, size_t len)
>
> do {
> ret = syscall(__NR_copy_file_range, fd, src, file->fd, dst, len, 0);
> - if (ret == -1)
> + if (ret == -1) {
> + perror("copy_range");
> return errno;
> + } else if (ret == 0)
> + break;
> len -= ret;
> } while (len > 0);
>
> --
> 2.10.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Carlos
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-12-15 11:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-12-14 21:28 [PATCH v2] xfs_io: Improvements to copy_range return code handling Anna Schumaker
2016-12-15 11:26 ` Carlos Maiolino
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).