summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorJens Axboe <jens.axboe@oracle.com>2009-05-25 09:06:49 +0200
committerJens Axboe <jens.axboe@oracle.com>2009-06-25 12:36:37 +0200
commit32d714aeb0a2eb7c121b67038c5a86cb98d1372d (patch)
tree5411dc235816ad6b368b9a5dd90fa6d59110d30c /fs
parent0faf574f6b00dfd5a4f2d34a0a43d29e0da22f69 (diff)
writeback: check for registered bdi in flusher add and inode dirty
Also a debugging aid. We want to catch dirty inodes being added to backing devices that don't do writeback. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'fs')
-rw-r--r--fs/fs-writeback.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index 796b24389485..dfb4767d7ca4 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -643,6 +643,13 @@ void __mark_inode_dirty(struct inode *inode, int flags)
*/
if (!was_dirty) {
struct bdi_writeback *wb = inode_get_wb(inode);
+ struct backing_dev_info *bdi = wb->bdi;
+
+ if (bdi_cap_writeback_dirty(bdi) &&
+ !test_bit(BDI_registered, &bdi->state)) {
+ WARN_ON(1);
+ printk("bdi-%s not registered\n", bdi->name);
+ }
inode->dirtied_when = jiffies;
list_move(&inode->i_list, &wb->b_dirty);