[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090916134346.GM26030@duck.suse.cz>
Date: Wed, 16 Sep 2009 15:43:46 +0200
From: Jan Kara <jack@...e.cz>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
chris.mason@...cle.com, hch@...radead.org, tytso@....edu,
akpm@...ux-foundation.org, jack@...e.cz, trond.myklebust@....uio.no
Subject: Re: [PATCH 10/16] writeback: splice dirty inode entries to default
bdi on bdi_destroy()
On Wed 16-09-09 15:24:48, Jens Axboe wrote:
> We cannot safely ensure that the inodes are all gone at this point
> in time, and we must not destroy this bdi with inodes having off it.
> So just splice our entries to the default bdi since that one will
> always persist.
I'd at least add a comment like
"XXX: This is probably a bug but let's workaround it for now."
And either remove the code or update the comment when this gets resolved.
Honza
>
> Signed-off-by: Jens Axboe <jens.axboe@...cle.com>
> ---
> mm/backing-dev.c | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
> index fd93566..3d3accb 100644
> --- a/mm/backing-dev.c
> +++ b/mm/backing-dev.c
> @@ -668,7 +668,19 @@ void bdi_destroy(struct backing_dev_info *bdi)
> {
> int i;
>
> - WARN_ON(bdi_has_dirty_io(bdi));
> + /*
> + * Splice our entries to the default_backing_dev_info, if this
> + * bdi disappears
> + */
> + if (bdi_has_dirty_io(bdi)) {
> + struct bdi_writeback *dst = &default_backing_dev_info.wb;
> +
> + spin_lock(&inode_lock);
> + list_splice(&bdi->wb.b_dirty, &dst->b_dirty);
> + list_splice(&bdi->wb.b_io, &dst->b_io);
> + list_splice(&bdi->wb.b_more_io, &dst->b_more_io);
> + spin_unlock(&inode_lock);
> + }
>
> bdi_unregister(bdi);
>
> --
> 1.6.4.1.207.g68ea
>
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists