Btrfs: always copy scrub arguments back to user space
PATCH 1/1 Btrfs: always copy scrub arguments back to user space
From: Filipe Manana <[email protected]>
If scrub returns an error we are not copying back the scrub arguments structure to user space. This prevents user space to know how much progress scrub has done if an error happened - this includes -ECANCELED which is returned when users ask for scrub to stop. A particular use case, which is used in btrfs-progs, is to resume scrub after it is canceled, in that case it relies on checking the progress from the scrub arguments structure and then use that progress in a call to resume scrub.
So fix this by always copying the scrub arguments structure to user space, overwriting the value returned to user space with -EFAULT only if copying the structure failed to let user space know that either that copying did not happen, and therefore the structure is stale, or it happened partially and the structure is probably not valid and corrupt due to the partial copy.
--- fs/btrfs/ioctl.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
fs/btrfs/ioctl.c +13 -1
@@ -4253,7 +4253,19 @@ static long btrfs_ioctl_scrub(struct file *file, void __user *arg) &sa->progress, sa->flags &BTRFS_SCRUB_READONLY , 0); -if (ret ==0 &©_to_user (arg, sa,sizeof (*sa))) +/* +* Copy scrub args to user space even if btrfs_scrub_dev() returned an +* error. This is important as it allows user space to know how much +* progress scrub has done. For example, if scrub is canceled we get +* -ECANCELED from btrfs_scrub_dev() and return that error back to user +* space. Later user space can inspect the progress from the structure +* btrfs_ioctl_scrub_args and resume scrub from where it left off +* previously (btrfs-progs does this). +* If we fail to copy the btrfs_ioctl_scrub_args structure to user space +* then return -EFAULT to signal the structure was not copied or it may +* be corrupt and unreliable due to a partial copy. +*/ +if (copy_to_user (arg, sa,sizeof (*sa))) ret = -EFAULT ;if (!(sa->flags &BTRFS_SCRUB_READONLY ))
Signature · 1 line
2.11.0
Looks good,
Quoted 17 lines · On 2020/1/16 下午7:29, [email protected] wrote:
From: Filipe Manana <[email protected]>
If scrub returns an error we are not copying back the scrub arguments structure to user space. This prevents user space to know how much progress scrub has done if an error happened - this includes
-ECANCELEDwhich is returned when users ask for scrub to stop. A particular use case, which is used in btrfs-progs, is to resume scrub after it is canceled, in that case it relies on checking the progress from the scrub arguments structure and then use that progress in a call to resume scrub.So fix this by always copying the scrub arguments structure to user space, overwriting the value returned to user space with
-EFAULTonly if copying the structure failed to let user space know that either that copying did not happen, and therefore the structure is stale, or it happened partially and the structure is probably not valid and corrupt due to the partial copy.
Quoted 4 lines
Reported-by Graham Cobb <[email protected]>Fixes 06fe39ab15a6a4 ("Btrfs: do not overwrite scrub error with fault error in scrub ioctl")Signed-off-by Filipe Manana <[email protected]>
Thanks,
Qu
Quoted 30 lines
--- fs/btrfs/ioctl.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)fs/btrfs/ioctl.c +13
-1@@ -4253,7 +4253,19 @@ static long btrfs_ioctl_scrub(struct file *file, void __user *arg) &sa->progress, sa->flags &BTRFS_SCRUB_READONLY , 0); -if (ret ==0 &©_to_user (arg, sa,sizeof (*sa))) +/* +* Copy scrub args to user space even if btrfs_scrub_dev() returned an +* error. This is important as it allows user space to know how much +* progress scrub has done. For example, if scrub is canceled we get +* -ECANCELED from btrfs_scrub_dev() and return that error back to user +* space. Later user space can inspect the progress from the structure +* btrfs_ioctl_scrub_args and resume scrub from where it left off +* previously (btrfs-progs does this). +* If we fail to copy the btrfs_ioctl_scrub_args structure to user space +* then return -EFAULT to signal the structure was not copied or it may +* be corrupt and unreliable due to a partial copy. +*/ +if (copy_to_user (arg, sa,sizeof (*sa))) ret = -EFAULT ;if (!(sa->flags &BTRFS_SCRUB_READONLY ))
Quoted 17 lines · On Thu, Jan 16, 2020 at 11:29:20AM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
If scrub returns an error we are not copying back the scrub arguments structure to user space. This prevents user space to know how much progress scrub has done if an error happened - this includes
-ECANCELEDwhich is returned when users ask for scrub to stop. A particular use case, which is used in btrfs-progs, is to resume scrub after it is canceled, in that case it relies on checking the progress from the scrub arguments structure and then use that progress in a call to resume scrub.So fix this by always copying the scrub arguments structure to user space, overwriting the value returned to user space with
-EFAULTonly if copying the structure failed to let user space know that either that copying did not happen, and therefore the structure is stale, or it happened partially and the structure is probably not valid and corrupt due to the partial copy.
Quoted 4 lines
Reported-by Graham Cobb <[email protected]>Fixes 06fe39ab15a6a4 ("Btrfs: do not overwrite scrub error with fault error in scrub ioctl")Signed-off-by Filipe Manana <[email protected]>
Added to 5.5-rc queue, thanks.
Graham Cobb
Tested-byQuoted 18 lines · David Sterba
Quoted 17 lines · On Thu, Jan 16, 2020 at 11:29:20AM +0000, [email protected] wrote:
From: Filipe Manana <[email protected]>
If scrub returns an error we are not copying back the scrub arguments structure to user space. This prevents user space to know how much progress scrub has done if an error happened - this includes
-ECANCELEDwhich is returned when users ask for scrub to stop. A particular use case, which is used in btrfs-progs, is to resume scrub after it is canceled, in that case it relies on checking the progress from the scrub arguments structure and then use that progress in a call to resume scrub.So fix this by always copying the scrub arguments structure to user space, overwriting the value returned to user space with
-EFAULTonly if copying the structure failed to let user space know that either that copying did not happen, and therefore the structure is stale, or it happened partially and the structure is probably not valid and corrupt due to the partial copy.
Quoted 6 lines
Quoted 4 lines
Reported-by Graham Cobb <[email protected]>Fixes 06fe39ab15a6a4 ("Btrfs: do not overwrite scrub error with fault error in scrub ioctl")Signed-off-by Filipe Manana <[email protected]>Added to 5.5-rc queue, thanks.
Just to let you know... As promised I have built a Debian Testing kernel (5.3) with this patch applied. My btrfs-scrub-slowly script has now run successfully to completion with 32 cancel/resume cycles (runs for 30 mins then takes 10 min break).
If it is useful, feel free to add:
Thanks Felipe!