Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
From
: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date
: Tue, 4 Dec 2018 07:16:29 -0800
Cc
: linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, olga.kornievskaia@xxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-unionfs@xxxxxxxxxxxxxxx, ceph-devel@xxxxxxxxxxxxxxx, linux-cifs@xxxxxxxxxxxxxxx
In-reply-to
: <
20181203083416.28978-4-david@fromorbit.com
>
User-agent
: Mutt/1.9.2 (2017-12-15)
Looks fine, Reviewed-by: Christoph Hellwig <hch@xxxxxx>
References
:
[PATCH 0/11] fs: fixes for major copy_file_range() issues
From:
Dave Chinner
[PATCH 03/11] vfs: no fallback for ->copy_file_range
From:
Dave Chinner
Prev by Date:
Re: overlayfs access checks on underlying layers
Next by Date:
Re: [PATCH 04/11] vfs: add missing checks to copy_file_range
Previous by thread:
Re: [PATCH 03/11] vfs: no fallback for ->copy_file_range
Next by thread:
[PATCH 06/11] vfs: copy_file_range needs to strip setuid bits
Index(es):
Date
Thread
[Index of Archives]
[Linux Filesystems Devel]
[Linux NFS]
[Linux NILFS]
[Linux USB Devel]
[Linux Audio Users]
[Yosemite News]
[Linux Kernel]
[Linux SCSI]
