linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Stroetmann <stroetmann@ontolinux.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 3/4] fs: skip I_FREEING inodes in writeback_sb_inodes
Date: Sun, 24 Oct 2010 23:46:04 +0200	[thread overview]
Message-ID: <4CC4A91C.3040401@ontolinux.com> (raw)
In-Reply-To: <20101024174046.GC2718@lst.de>

  little typos

On the 24.10.2010 19:40, Christoph Hellwig wrote:
> Skip I_FREEING inodes just like I_WILL_FREE and I_NEW when walking the
> writeback lists.  Currenly this can't happen, but once we move from
> inode_lock to more fine grained locking we can have an inode that's
> still on the writeback lists but has I_FREEING set, and we absolutely
> need to skip it here, just like we do for all other inode list walks.
>
> Based on a patch from Dave Chinner.
>
> Signed-off-by: Christoph Hellwig<hch@lst.de>
>
> Index: linux-2.6/fs/fs-writeback.c
> ===================================================================
> --- linux-2.6.orig/fs/fs-writeback.c	2010-10-24 13:21:18.282010741 +0200
> +++ linux-2.6/fs/fs-writeback.c	2010-10-24 13:21:35.456004735 +0200
> @@ -487,10 +487,16 @@ static int writeback_sb_inodes(struct su
>   			return 0;
>   		}
>
> -		if (inode->i_state&  (I_NEW | I_WILL_FREE)) {
> +		/*
> +		 * Don't bother with new inodes or inodes beeing freed, first
being
> +		 * kind does not need peridic writeout yet, and for the latter
> +		 * kind writeout is handled by the freer.
don't know:
freer inode
or
releaser

[...]

  reply	other threads:[~2010-10-24 21:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24 17:40 [PATCH 1/4] fs: do not drop inode_lock in dispose_list Christoph Hellwig
2010-10-24 17:40 ` [PATCH 2/4] fs: fold invalidate_list into invalidate_inodes Christoph Hellwig
2010-10-24 21:45   ` Christian Stroetmann
2010-10-24 17:40 ` [PATCH 3/4] fs: skip I_FREEING inodes in writeback_sb_inodes Christoph Hellwig
2010-10-24 21:46   ` Christian Stroetmann [this message]
2010-10-24 17:40 ` [PATCH 4/4] fs: kill I_WILL_FREE Christoph Hellwig
2010-10-24 21:46   ` Christian Stroetmann
2010-10-24 21:50     ` Christian Stroetmann
2010-10-26  1:28   ` Al Viro
2010-10-26 19:18   ` Al Viro
2010-10-25  5:33 ` [PATCH 1/4] fs: do not drop inode_lock in dispose_list Dave Chinner
2010-10-25  5:46   ` Dave Chinner
2010-10-25  9:20     ` Dave Chinner
2010-10-25 10:07     ` Christoph Hellwig
2010-10-25 23:07       ` Dave Chinner

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=4CC4A91C.3040401@ontolinux.com \
    --to=stroetmann@ontolinux.com \
    --cc=hch@lst.de \
    --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).