From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [patch 6/6] mm: fsync livelock avoidance Date: Thu, 11 Dec 2008 14:41:09 -0800 Message-ID: <20081211144109.ee9c0410.akpm@linux-foundation.org> References: <20081210072454.GB27096@wotan.suse.de> <20081210074209.GG27096@wotan.suse.de> <20081211135111.cada5b8b.akpm@linux-foundation.org> <20081211223213.GC8294@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, mpatocka@redhat.com To: Nick Piggin Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:46636 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759587AbYLKWmv (ORCPT ); Thu, 11 Dec 2008 17:42:51 -0500 In-Reply-To: <20081211223213.GC8294@wotan.suse.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, 11 Dec 2008 23:32:13 +0100 Nick Piggin wrote: > > > + /* nothing tagged */ > > > + spin_unlock_irq(&mapping->tree_lock); > > > + return 0; > > > > Can we please avoid the deeply-nested-return hand grenade? > > Hmm, we could > > goto out; > ... > out: > return ret; > > But is that less hand grenadie than the plain return? yep. I've seen many many locking errors and resource leaks caused by the multiple-return-statements mistake.