From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikola Pajkovsky Subject: Re: [f2fs-dev] [PATCH] f2fs: use list_for_each rather than list_for_each_safe, in remove_orphan_inode() Date: Mon, 22 Jul 2013 17:36:45 +0200 Message-ID: References: <51E8F7A6.7030708@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V1IAh-0002o2-3z for linux-f2fs-devel@lists.sourceforge.net; Mon, 22 Jul 2013 15:37:11 +0000 Received: from mx1.redhat.com ([209.132.183.28]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1V1IAd-0002w2-Ra for linux-f2fs-devel@lists.sourceforge.net; Mon, 22 Jul 2013 15:37:11 +0000 In-Reply-To: <51E8F7A6.7030708@cn.fujitsu.com> (Gu Zheng's message of "Fri, 19 Jul 2013 16:24:06 +0800") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net To: Gu Zheng Cc: linux-kernel , f2fs Gu Zheng writes: > As we remove the target single node, so list_for_each is enought, in order to > clean up, we use list_for_each_entry instead. > > Signed-off-by: Gu Zheng > --- > fs/f2fs/checkpoint.c | 5 ++--- > 1 files changed, 2 insertions(+), 3 deletions(-) > > diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c > index 290db04..87f7bc2 100644 > --- a/fs/f2fs/checkpoint.c > +++ b/fs/f2fs/checkpoint.c > @@ -237,13 +237,12 @@ out: > > void remove_orphan_inode(struct f2fs_sb_info *sbi, nid_t ino) > { > - struct list_head *this, *next, *head; > + struct list_head *head; > struct orphan_inode_entry *orphan; > > mutex_lock(&sbi->orphan_inode_mutex); > head = &sbi->orphan_inode_list; > - list_for_each_safe(this, next, head) { > - orphan = list_entry(this, struct orphan_inode_entry, list); > + list_for_each_entry(orphan, head, list) { > if (orphan->ino == ino) { > list_del(&orphan->list); > kmem_cache_free(orphan_entry_slab, orphan); you have meant list_for_each_entry_safe, haven't you? -- Nikola ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk