On Sat, Oct 16, 2010 at 07:13:55PM +1100, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > 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@xxxxxxxxxx> Nice to see you and Christoph eliminated the need for that bdev:inode hack in my tree. Looks good. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
