summaryrefslogtreecommitdiff
path: root/.gitattributes
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2017-04-05 15:09:48 +0300
committerJan Kara <jack@suse.cz>2017-04-05 15:24:16 +0300
commit71b0576bdb862e964a82c73327cdd1a249c53e67 (patch)
tree172df641c17c0d88efb755bbc7e8ff35d619ec40 /.gitattributes
parent65547661500885dde26ca4a75d4d7f7df587c88e (diff)
downloadlinux-71b0576bdb862e964a82c73327cdd1a249c53e67.tar.xz
reiserfs: Make cancel_old_flush() reliable
Currently canceling of delayed work that flushes old data using cancel_old_flush() does not prevent work from being requeued. Thus in theory new work can be queued after cancel_old_flush() from reiserfs_freeze() has run. This will become larger problem once flush_old_commits() can requeue the work itself. Fix the problem by recording in sbi->work_queue that flushing work is canceled and should not be requeued. Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions