diff options
author | Benjamin Marzinski <bmarzins@redhat.com> | 2014-11-14 05:42:03 +0300 |
---|---|---|
committer | Steven Whitehouse <swhiteho@redhat.com> | 2014-11-17 13:35:17 +0300 |
commit | 48b6bca6b7b8309697fc8a101793befe92d249d9 (patch) | |
tree | 2cec8b867e5058c6672e425e2ac9a0d25ae60cf1 /fs/gfs2/ops_fstype.c | |
parent | 98f1a696a1b2f6cf0c1ce6850b1516beda9c1269 (diff) | |
download | linux-48b6bca6b7b8309697fc8a101793befe92d249d9.tar.xz |
fs: add freeze_super/thaw_super fs hooks
Currently, freezing a filesystem involves calling freeze_super, which locks
sb->s_umount and then calls the fs-specific freeze_fs hook. This makes it
hard for gfs2 (and potentially other cluster filesystems) to use the vfs
freezing code to do freezes on all the cluster nodes.
In order to communicate that a freeze has been requested, and to make sure
that only one node is trying to freeze at a time, gfs2 uses a glock
(sd_freeze_gl). The problem is that there is no hook for gfs2 to acquire
this lock before calling freeze_super. This means that two nodes can
attempt to freeze the filesystem by both calling freeze_super, acquiring
the sb->s_umount lock, and then attempting to grab the cluster glock
sd_freeze_gl. Only one will succeed, and the other will be stuck in
freeze_super, making it impossible to finish freezing the node.
To solve this problem, this patch adds the freeze_super and thaw_super
hooks. If a filesystem implements these hooks, they are called instead of
the vfs freeze_super and thaw_super functions. This means that every
filesystem that implements these hooks must call the vfs freeze_super and
thaw_super functions itself within the hook function to make use of the vfs
freezing code.
Reviewed-by: Jan Kara <jack@suse.cz>
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'fs/gfs2/ops_fstype.c')
0 files changed, 0 insertions, 0 deletions