From: Jan Kara <jack@suse.cz>
To: Jens Axboe <axboe@kernel.dk>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
linux-fsdevel@vger.kernel.org,
Bert De Jonghe <Bert.DeJonghe@amplidata.com>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] writeback: Fix periodic writeback after fs mount
Date: Thu, 27 Jun 2013 19:01:33 +0200 [thread overview]
Message-ID: <20130627170133.GA28935@quack.suse.cz> (raw)
In-Reply-To: <1369903459-10295-1-git-send-email-jack@suse.cz>
On Thu 30-05-13 10:44:19, Jan Kara wrote:
> Code in blkdev.c moves a device inode to default_backing_dev_info when
> the last reference to the device is put and moves the device inode back
> to its bdi when the first reference is acquired. This includes moving to
> wb.b_dirty list if the device inode is dirty. The code however doesn't
> setup timer to wake corresponding flusher thread and while wb.b_dirty
> list is non-empty __mark_inode_dirty() will not set it up either. Thus
> periodic writeback is effectively disabled until a sync(2) call which can
> lead to unexpected data loss in case of crash or power failure.
>
> Fix the problem by setting up a timer for periodic writeback in case we
> add the first dirty inode to wb.b_dirty list in bdev_inode_switch_bdi().
>
> Reported-by: Bert De Jonghe <Bert.DeJonghe@amplidata.com>
> CC: stable@vger.kernel.org # >= 3.0
> Signed-off-by: Jan Kara <jack@suse.cz>
Jens, I'm going over my submitted patches and I don't think you've merged
this patch. Did you?
Honza
> ---
> fs/block_dev.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index 2091db8..85f5c85 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c
> @@ -58,17 +58,24 @@ static void bdev_inode_switch_bdi(struct inode *inode,
> struct backing_dev_info *dst)
> {
> struct backing_dev_info *old = inode->i_data.backing_dev_info;
> + bool wakeup_bdi = false;
>
> if (unlikely(dst == old)) /* deadlock avoidance */
> return;
> bdi_lock_two(&old->wb, &dst->wb);
> spin_lock(&inode->i_lock);
> inode->i_data.backing_dev_info = dst;
> - if (inode->i_state & I_DIRTY)
> + if (inode->i_state & I_DIRTY) {
> + if (bdi_cap_writeback_dirty(dst) && !wb_has_dirty_io(&dst->wb))
> + wakeup_bdi = true;
> list_move(&inode->i_wb_list, &dst->wb.b_dirty);
> + }
> spin_unlock(&inode->i_lock);
> spin_unlock(&old->wb.list_lock);
> spin_unlock(&dst->wb.list_lock);
> +
> + if (wakeup_bdi)
> + bdi_wakeup_thread_delayed(dst);
> }
>
> /* Kill _all_ buffers and pagecache , dirty or not.. */
> --
> 1.8.1.4
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-06-27 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 8:44 [PATCH] writeback: Fix periodic writeback after fs mount Jan Kara
2013-06-27 17:01 ` Jan Kara [this message]
2013-06-28 14:02 ` 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=20130627170133.GA28935@quack.suse.cz \
--to=jack@suse.cz \
--cc=Bert.DeJonghe@amplidata.com \
--cc=axboe@kernel.dk \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).