summaryrefslogtreecommitdiffstats
path: root/fs/inode.c
diff options
context:
space:
mode:
authorDave Chinner <dchinner@redhat.com>2010-10-21 11:49:26 +1100
committerAl Viro <viro@zeniv.linux.org.uk>2010-10-25 21:26:14 -0400
commita5491e0c7bb7387e3e6ff9994d6dc2efc78af56c (patch)
tree7573138ef2350fbf0ea02e237d5acebcdaea2780 /fs/inode.c
parent99a38919241fd051b8d93b2e4d0c05ef0556d795 (diff)
downloadop-kernel-dev-a5491e0c7bb7387e3e6ff9994d6dc2efc78af56c.zip
op-kernel-dev-a5491e0c7bb7387e3e6ff9994d6dc2efc78af56c.tar.gz
fs: switch bdev inode bdi's correctly
bdev inodes can remain dirty even after their last close. Hence the BDI associated with the bdev->inode gets modified duringthe last close to point to the default BDI. However, the bdev inode still needs to be moved to the dirty lists of the new BDI, otherwise it will corrupt the writeback list is was left on. Add a new function bdev_inode_switch_bdi() to move all the bdi state from the old bdi to the new one safely. This is only a temporary measure until the bdev inode<->bdi lifecycle problems are sorted out. Signed-off-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/inode.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud