summaryrefslogtreecommitdiff
path: root/Documentation/i2c/gpio-fault-injection
diff options
context:
space:
mode:
authorDarrick J. Wong <darrick.wong@oracle.com>2018-10-30 10:41:49 +1100
committerDave Chinner <david@fromorbit.com>2018-10-30 10:41:49 +1100
commit42ec3d4c02187a18e27ff94b409ec27234bf2ffd (patch)
treec9db04db8187c370718a43e6067af0e5aa944500 /Documentation/i2c/gpio-fault-injection
parent8dde90bca6fca3736ea20109654bcf6dcf2ecf1d (diff)
downloadlinux-rpi-42ec3d4c02187a18e27ff94b409ec27234bf2ffd.tar.gz
linux-rpi-42ec3d4c02187a18e27ff94b409ec27234bf2ffd.tar.bz2
linux-rpi-42ec3d4c02187a18e27ff94b409ec27234bf2ffd.zip
vfs: make remap_file_range functions take and return bytes completed
Change the remap_file_range functions to take a number of bytes to operate upon and return the number of bytes they operated on. This is a requirement for allowing fs implementations to return short clone/dedupe results to the user, which will enable us to obey resource limits in a graceful manner. A subsequent patch will enable copy_file_range to signal to the ->clone_file_range implementation that it can handle a short length, which will be returned in the function's return value. For now the short return is not implemented anywhere so the behavior won't change -- either copy_file_range manages to clone the entire range or it tries an alternative. Neither clone ioctl can take advantage of this, alas. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'Documentation/i2c/gpio-fault-injection')
0 files changed, 0 insertions, 0 deletions