diff options
author | Benjamin Marzinski <bmarzins@redhat.com> | 2014-11-13 20:42:04 -0600 |
---|---|---|
committer | Steven Whitehouse <swhiteho@redhat.com> | 2014-11-17 10:36:39 +0000 |
commit | 2e60d7683c8d2ea21317f6d9f4cd3bf5428ce162 (patch) | |
tree | fc7900ad18814d1ea46879f93eab063ff5754d1e /include/uapi | |
parent | 48b6bca6b7b8309697fc8a101793befe92d249d9 (diff) | |
download | linux-2e60d7683c8d2ea21317f6d9f4cd3bf5428ce162.tar.bz2 |
GFS2: update freeze code to use freeze/thaw_super on all nodes
The current gfs2 freezing code is considerably more complicated than it
should be because it doesn't use the vfs freezing code on any node except
the one that begins the freeze. This is because it needs to acquire a
cluster glock before calling the vfs code to prevent a deadlock, and
without the new freeze_super and thaw_super hooks, that was impossible. To
deal with the issue, gfs2 had to do some hacky locking tricks to make sure
that a frozen node couldn't be holding on a lock it needed to do the
unfreeze ioctl.
This patch makes use of the new hooks to simply the gfs2 locking code. Now,
all the nodes in the cluster freeze and thaw in exactly the same way. Every
node in the cluster caches the freeze glock in the shared state. The new
freeze_super hook allows the freezing node to grab this freeze glock in
the exclusive state without first calling the vfs freeze_super function.
All the nodes in the cluster see this lock change, and call the vfs
freeze_super function. The vfs locking code guarantees that the nodes can't
get stuck holding the glocks necessary to unfreeze the system. To
unfreeze, the freezing node uses the new thaw_super hook to drop the freeze
glock. Again, all the nodes notice this, reacquire the glock in shared mode
and call the vfs thaw_super function.
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'include/uapi')
0 files changed, 0 insertions, 0 deletions