summaryrefslogtreecommitdiffstats
path: root/block/blk-tag.c
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2013-06-28 16:04:02 +0200
committerJens Axboe <axboe@kernel.dk>2013-06-28 16:04:02 +0200
commita5faeaf9109578e65e1a32e2a3e76c8b47e7dcb6 (patch)
tree9082ec395e98ad41ec046786234cf7669a95bc05 /block/blk-tag.c
parent9138125beabbb76b4a373d4a619870f6f5d86fc5 (diff)
downloadlinux-0-day-a5faeaf9109578e65e1a32e2a3e76c8b47e7dcb6.tar.gz
linux-0-day-a5faeaf9109578e65e1a32e2a3e76c8b47e7dcb6.tar.xz
writeback: Fix periodic writeback after fs mount
Code in blkdev.c moves a device inode to default_backing_dev_info when the last reference to the device is put and moves the device inode back to its bdi when the first reference is acquired. This includes moving to wb.b_dirty list if the device inode is dirty. The code however doesn't setup timer to wake corresponding flusher thread and while wb.b_dirty list is non-empty __mark_inode_dirty() will not set it up either. Thus periodic writeback is effectively disabled until a sync(2) call which can lead to unexpected data loss in case of crash or power failure. Fix the problem by setting up a timer for periodic writeback in case we add the first dirty inode to wb.b_dirty list in bdev_inode_switch_bdi(). Reported-by: Bert De Jonghe <Bert.DeJonghe@amplidata.com> CC: stable@vger.kernel.org # >= 3.0 Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-tag.c')
0 files changed, 0 insertions, 0 deletions