From: Jan Kara <jack@suse.cz>
To: Curt Wohlgemuth <curtw@google.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes
Date: Wed, 20 Jun 2012 22:03:36 +0200 [thread overview]
Message-ID: <20120620200336.GF3435@quack.suse.cz> (raw)
In-Reply-To: <CAO81RMa6KQjHkHzjrU_VRC6dMpFgy=2xqO7VDot_6KBdV-ReLQ@mail.gmail.com>
Hi Curt,
On Wed 20-06-12 07:23:56, Curt Wohlgemuth wrote:
> Was there ever a resolution for this patch and the series? I looked
> for but found no ack/nack for V4 of your "Cleanup and improve sync"
> patch series.
>
> We've been carrying a crappy hack/patch to sync all block device
> inodes in order to allow lilo to not break, and it'd be nice to have a
> real fix for it upstream.
The patch set works, just I'm missing some final review and someone (Al?)
has to pick it up and merge it. Anyway I plan to repost the series soon to
hopefully get things moving again...
Honza
> On Thu, Jan 5, 2012 at 3:46 PM, Jan Kara <jack@suse.cz> wrote:
> > In case block device does not have filesystem mounted on it, sys_sync will just
> > ignore it and doesn't writeout its dirty pages. This is because writeback code
> > avoids writing inodes from superblock without backing device and
> > blockdev_superblock is such a superblock. Since it's unexpected that sync
> > doesn't writeout dirty data for block devices be nice to users and change the
> > behavior to do so. So now we iterate over all block devices on blockdev_super
> > instead of iterating over all superblocks when syncing block devices.
> >
> > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> > fs/sync.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++-------
> > 1 files changed, 51 insertions(+), 7 deletions(-)
> >
> > diff --git a/fs/sync.c b/fs/sync.c
> > index e62a57b..ccaaa1b 100644
> > --- a/fs/sync.c
> > +++ b/fs/sync.c
> > @@ -86,10 +86,54 @@ static void sync_fs_one_sb(struct super_block *sb, void *arg)
> > sb->s_op->sync_fs(sb, *(int *)arg);
> > }
> >
> > -static void sync_blkdev_one_sb(struct super_block *sb, void *arg)
> > +/*
> > + * We go through all existing block devices so that even devices without
> > + * filesystem mounted are synced.
> > + */
> > +static void sync_all_bdevs(int wait)
> > {
> > - if (!(sb->s_flags & MS_RDONLY))
> > - __sync_blockdev(sb->s_bdev, *(int *)arg);
> > + struct inode *inode, *old_inode = NULL;
> > +
> > + spin_lock(&inode_sb_list_lock);
> > + list_for_each_entry(inode, &blockdev_superblock->s_inodes, i_sb_list) {
> > + struct address_space *mapping = inode->i_mapping;
> > +
> > + spin_lock(&inode->i_lock);
> > + if (inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW) ||
> > + mapping->nrpages == 0) {
> > + spin_unlock(&inode->i_lock);
> > + continue;
> > + }
> > + __iget(inode);
> > + spin_unlock(&inode->i_lock);
> > + spin_unlock(&inode_sb_list_lock);
> > + /*
> > + * We hold a reference to 'inode' so it couldn't have been
> > + * removed from s_inodes list while we dropped the
> > + * inode_sb_list_lock. We cannot iput the inode now as we can
> > + * be holding the last reference and we cannot iput it under
> > + * inode_sb_list_lock. So we keep the reference and iput it
> > + * later.
> > + */
> > + iput(old_inode);
> > + old_inode = inode;
> > +
> > + __sync_blockdev(I_BDEV(inode), wait);
> > +
> > + spin_lock(&inode_sb_list_lock);
> > + }
> > + spin_unlock(&inode_sb_list_lock);
> > + iput(old_inode);
> > +}
> > +
> > +static void flush_one_bdev(struct block_device *bdev, void *arg)
> > +{
> > + __sync_blockdev(bdev, 0);
> > +}
> > +
> > +static void sync_one_bdev(struct block_device *bdev, void *arg)
> > +{
> > + sync_blockdev(bdev);
> > }
> >
> > /*
> > @@ -103,10 +147,10 @@ SYSCALL_DEFINE0(sync)
> > wakeup_flusher_threads(0, WB_REASON_SYNC);
> > iterate_supers(writeback_inodes_one_sb, NULL);
> > iterate_supers(sync_fs_one_sb, &nowait);
> > - iterate_supers(sync_blkdev_one_sb, &nowait);
> > + iterate_bdevs(flush_one_bdev, NULL);
> > iterate_supers(sync_inodes_one_sb, NULL);
> > iterate_supers(sync_fs_one_sb, &wait);
> > - iterate_supers(sync_blkdev_one_sb, &wait);
> > + iterate_bdevs(sync_one_bdev, NULL);
> > if (unlikely(laptop_mode))
> > laptop_sync_completion();
> > return 0;
> > @@ -122,10 +166,10 @@ static void do_sync_work(struct work_struct *work)
> > */
> > iterate_supers(sync_inodes_one_sb, &nowait);
> > iterate_supers(sync_fs_one_sb, &nowait);
> > - iterate_supers(sync_blkdev_one_sb, &nowait);
> > + sync_all_bdevs(nowait);
> > iterate_supers(sync_inodes_one_sb, &nowait);
> > iterate_supers(sync_fs_one_sb, &nowait);
> > - iterate_supers(sync_blkdev_one_sb, &nowait);
> > + sync_all_bdevs(nowait);
> > printk("Emergency Sync complete\n");
> > kfree(work);
> > }
> > --
> > 1.7.1
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-20 20:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 23:46 [PATCH 0/8 RESEND] Cleanup and improve sync (v4) Jan Kara
2012-01-05 23:46 ` [PATCH 1/8] vfs: Move noop_backing_dev_info check from sync into writeback Jan Kara
2012-01-05 23:46 ` [PATCH 2/8] quota: Split dquot_quota_sync() to writeback and cache flushing part Jan Kara
2012-01-05 23:46 ` [PATCH 3/8] quota: Move quota syncing to ->sync_fs method Jan Kara
2012-01-05 23:46 ` [PATCH 4/8] vfs: Reorder operations during sys_sync Jan Kara
2012-01-05 23:46 ` [PATCH 5/8] vfs: Create function for iterating over block devices Jan Kara
2012-01-05 23:46 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
2012-06-20 14:23 ` Curt Wohlgemuth
2012-06-20 20:03 ` Jan Kara [this message]
2012-06-22 10:30 ` Al Viro
2012-07-03 14:47 ` Jan Kara
2012-01-05 23:46 ` [PATCH 7/8] vfs: Remove unnecessary flushing of block devices Jan Kara
2012-01-05 23:46 ` [PATCH 8/8] vfs: Avoid unnecessary WB_SYNC_NONE writeback during sys_sync and reorder sync passes Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2012-07-03 14:45 [PATCH 0/8 v4] Flush all block devices on sync(2) and cleanup the code Jan Kara
2012-07-03 14:45 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
2012-07-17 6:27 ` Fengguang Wu
2012-07-20 2:21 ` Fengguang Wu
2011-11-09 17:44 [PATCH 0/8] Cleanup and improve sync (v4) Jan Kara
2011-11-09 17:45 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
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=20120620200336.GF3435@quack.suse.cz \
--to=jack@suse.cz \
--cc=curtw@google.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).