xfs: mark all internal workqueues as freezable
authorBrian Foster <bfoster@redhat.com>
Tue, 9 Sep 2014 01:44:46 +0000 (11:44 +1000)
committerDave Chinner <david@fromorbit.com>
Tue, 9 Sep 2014 01:44:46 +0000 (11:44 +1000)
commit8018ec083c72443cc74fd2d08eb7c5dddc13af53
tree762b2d1693ff71f4b61e17f73b90eb9b345d3198
parent52addcf9d6669fa439387610bc65c92fa0980cef
xfs: mark all internal workqueues as freezable

Workqueues must be explicitly set as freezable to ensure they are frozen
in the assocated part of the hibernation/suspend sequence. Freezing of
workqueues and kernel threads is important to ensure that modifications
are not made on-disk after the hibernation image has been created.
Otherwise, the in-memory state can become inconsistent with what is on
disk and eventually lead to filesystem corruption. We have reports of
free space btree corruptions that occur immediately after restore from
hibernate that suggest the xfs-eofblocks workqueue could be causing
such problems if it races with hibernation.

Mark all of the internal XFS workqueues as freezable to ensure nothing
changes on-disk once the freezer infrastructure freezes kernel threads
and creates the hibernation image.

Signed-off-by: Brian Foster <bfoster@redhat.com>
Reported-by: Carlos E. R. <carlos.e.r@opensuse.org>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_buf.c
fs/xfs/xfs_mru_cache.c
fs/xfs/xfs_super.c