linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: chris.mason@oracle.com, david@fromorbit.com, hch@infradead.org,
	akpm@linux-foundation.org, jack@suse.cz,
	yanmin_zhang@linux.intel.com, richard@rsk.demon.co.uk,
	damien.wyart@free.fr, fweisbec@gmail.com, Alan.Brunelle@hp.com,
	Jens Axboe <jens.axboe@oracle.com>
Subject: [PATCH 09/10] writeback: check for registered bdi in flusher add and inode dirty
Date: Thu, 25 Jun 2009 12:42:02 +0200	[thread overview]
Message-ID: <1245926523-21959-10-git-send-email-jens.axboe@oracle.com> (raw)
In-Reply-To: <1245926523-21959-1-git-send-email-jens.axboe@oracle.com>

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>
---
 fs/fs-writeback.c           |    7 +++++++
 include/linux/backing-dev.h |    1 +
 mm/backing-dev.c            |    6 ++++++
 3 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index 796b243..dfb4767 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);
diff --git a/include/linux/backing-dev.h b/include/linux/backing-dev.h
index 9d2efc5..e623c57 100644
--- a/include/linux/backing-dev.h
+++ b/include/linux/backing-dev.h
@@ -31,6 +31,7 @@ enum bdi_state {
 	BDI_wblist_lock,	/* bdi->wb_list now needs locking */
 	BDI_async_congested,	/* The async (write) queue is getting full */
 	BDI_sync_congested,	/* The sync queue is getting full */
+	BDI_registered,		/* bdi_register() was done */
 	BDI_unused,		/* Available bits start here */
 };
 
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 6cdd9e5..75e6c47 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -569,6 +569,11 @@ static void bdi_add_one_flusher_task(struct backing_dev_info *bdi,
 	if (!bdi_cap_writeback_dirty(bdi))
 		return;
 
+	if (WARN_ON(!test_bit(BDI_registered, &bdi->state))) {
+		printk("bdi %p/%s is not registered!\n", bdi, bdi->name);
+		return;
+	}
+
 	/*
 	 * Check with the helper whether to proceed adding a task. Will only
 	 * abort if we two or more simultanous calls to
@@ -678,6 +683,7 @@ remove_err:
 	}
 
 	bdi_debug_register(bdi, dev_name(dev));
+	set_bit(BDI_registered, &bdi->state);
 exit:
 	return ret;
 }
-- 
1.6.3.rc0.1.gf800


  parent reply	other threads:[~2009-06-25 10:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 10:41 [PATCH 0/10] Per-bdi writeback flusher threads v12 Jens Axboe
2009-06-25 10:41 ` [PATCH 01/10] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-06-25 10:41 ` [PATCH 02/10] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-07-06 12:55   ` Artem Bityutskiy
2009-07-06 13:13     ` Jens Axboe
2009-07-06 13:26       ` Artem Bityutskiy
2009-07-07 15:27   ` Artem Bityutskiy
2009-07-08  0:57     ` Zhang, Yanmin
2009-07-08  4:47       ` Artem Bityutskiy
2009-06-25 10:41 ` [PATCH 03/10] writeback: get rid of pdflush completely Jens Axboe
2009-06-25 10:41 ` [PATCH 04/10] writeback: separate the flushing state/task from the bdi Jens Axboe
2009-06-25 10:41 ` [PATCH 05/10] writeback: support > 1 flusher thread per bdi Jens Axboe
2009-07-06 12:18   ` Artem Bityutskiy
2009-07-06 12:22     ` Jens Axboe
2009-07-06 13:37   ` Artem Bityutskiy
2009-07-06 13:49     ` Jamie Lokier
2009-07-06 14:11       ` Artem Bityutskiy
2009-07-06 15:43         ` Jens Axboe
2009-06-25 10:41 ` [PATCH 06/10] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-06-25 10:42 ` [PATCH 07/10] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-06-25 10:42 ` [PATCH 08/10] writeback: add name to backing_dev_info Jens Axboe
2009-06-25 10:42 ` Jens Axboe [this message]
2009-06-25 10:42 ` [PATCH 10/10] writeback: use spin_trylock() in bdi_writeback_all() for WB_SYNC_NONE Jens Axboe
2009-06-29  8:43 ` [PATCH 0/10] Per-bdi writeback flusher threads v12 Zhang, Yanmin
  -- strict thread matches above, loose matches on Subject: below --
2009-08-31 12:14 [PATCH 0/10] Per-bdi writeback flusher threads v14 Jens Axboe
2009-08-31 12:14 ` [PATCH 09/10] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-06-17 11:07 [PATCH 0/10] Per-bdi writeback flusher threads v11 Jens Axboe
2009-06-17 11:07 ` [PATCH 09/10] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1245926523-21959-10-git-send-email-jens.axboe@oracle.com \
    --to=jens.axboe@oracle.com \
    --cc=Alan.Brunelle@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=damien.wyart@free.fr \
    --cc=david@fromorbit.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@rsk.demon.co.uk \
    --cc=yanmin_zhang@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).