linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Changman Lee <cm224.lee@samsung.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: move put_gc_inode into gc_mutex
Date: Fri, 28 Nov 2014 15:08:37 +0900	[thread overview]
Message-ID: <20141128060837.GB2819@lcm> (raw)
In-Reply-To: <20141128035514.GA59415@jaegeuk-mac02.mot-mobility.com>

On Thu, Nov 27, 2014 at 07:55:14PM -0800, Jaegeuk Kim wrote:
> Hi Changman,
> 
> On Thu, Nov 27, 2014 at 06:42:54PM +0900, Changman Lee wrote:
> > There in no any lock to protect gc_inode list so let's move into
> > gc_mutex, otherwise it might be lost links of list.
> 
> Could you explain why the links can be lost?
> Cause the ilist is a local variable.

Hi Jaegeuk,

Oh, I missed ilist is a local variable.
Sorry, ignore this patch.

Thanks,

> 
> IIRC, the reason why put_gc_inode is called outside of gc_mutex is to avoid
> deadlock between f2fs_evict_inode and gc operations.
> I'm not sure it still has a problem, but it is unclear that we have to move
> put_gc_inode inside gc_mutex.
> 
> Are you facing with any bug on this?
> 
> Thanks,
> 
> > 
> > Signed-off-by: Changman Lee <cm224.lee@samsung.com>
> > ---
> >  fs/f2fs/gc.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> > index 657683c9..99e1720 100644
> > --- a/fs/f2fs/gc.c
> > +++ b/fs/f2fs/gc.c
> > @@ -733,9 +733,9 @@ gc_more:
> >  	if (gc_type == FG_GC)
> >  		write_checkpoint(sbi, &cpc);
> >  stop:
> > -	mutex_unlock(&sbi->gc_mutex);
> > -
> >  	put_gc_inode(&ilist);
> > +
> > +	mutex_unlock(&sbi->gc_mutex);
> >  	return ret;
> >  }
> >  
> > -- 
> > 1.9.1
> > 
> > 
> > ------------------------------------------------------------------------------
> > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> > from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> > with Interactivity, Sharing, Native Excel Exports, App Integration & more
> > Get technology previously reserved for billion-dollar corporations, FREE
> > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2014-11-28  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  9:42 [PATCH] f2fs: move put_gc_inode into gc_mutex Changman Lee
2014-11-28  3:55 ` [f2fs-dev] " Jaegeuk Kim
2014-11-28  6:08   ` Changman Lee [this message]

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=20141128060837.GB2819@lcm \
    --to=cm224.lee@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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).