diff options
author | Aleksa Sarai <asarai@suse.de> | 2017-07-04 21:49:06 +1000 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2017-11-26 13:50:20 +0000 |
commit | 7c3274b3c4131299a459216e55821f0e54a4686e (patch) | |
tree | 1e59a0d0df543c3083fbb36769c9d320a50d0828 /tools/perf/scripts | |
parent | c23c045d17003108600173074da08c70bd5c78a0 (diff) | |
download | linux-stable-7c3274b3c4131299a459216e55821f0e54a4686e.tar.gz linux-stable-7c3274b3c4131299a459216e55821f0e54a4686e.tar.bz2 linux-stable-7c3274b3c4131299a459216e55821f0e54a4686e.zip |
btrfs: resume qgroup rescan on rw remount
commit 6c6b5a39c4bf3dbd8cf629c9f5450e983c19dbb9 upstream.
Several distributions mount the "proper root" as ro during initrd and
then remount it as rw before pivot_root(2). Thus, if a rescan had been
aborted by a previous shutdown, the rescan would never be resumed.
This issue would manifest itself as several btrfs ioctl(2)s causing the
entire machine to hang when btrfs_qgroup_wait_for_completion was hit
(due to the fs_info->qgroup_rescan_running flag being set but the rescan
itself not being resumed). Notably, Docker's btrfs storage driver makes
regular use of BTRFS_QUOTA_CTL_DISABLE and BTRFS_IOC_QUOTA_RESCAN_WAIT
(causing this problem to be manifested on boot for some machines).
Cc: Jeff Mahoney <jeffm@suse.com>
Fixes: b382a324b60f ("Btrfs: fix qgroup rescan resume on mount")
Signed-off-by: Aleksa Sarai <asarai@suse.de>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Tested-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
[bwh: Backported to 3.16: add #include "qgroup.h"]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'tools/perf/scripts')
0 files changed, 0 insertions, 0 deletions