From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-fsdevel@vger.kernel.org, mpatocka@redhat.com
Subject: Re: [patch 6/6] mm: fsync livelock avoidance
Date: Thu, 11 Dec 2008 14:41:09 -0800 [thread overview]
Message-ID: <20081211144109.ee9c0410.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081211223213.GC8294@wotan.suse.de>
On Thu, 11 Dec 2008 23:32:13 +0100
Nick Piggin <npiggin@suse.de> 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.
next prev parent reply other threads:[~2008-12-11 22:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 7:24 [patch 1/6] mm: direct IO starvation improvement Nick Piggin
2008-12-10 7:25 ` [patch 2/6] fs: remove WB_SYNC_HOLD Nick Piggin
2008-12-10 7:27 ` [patch 3/6] fs: sync_sb_inodes fix Nick Piggin
2008-12-11 21:51 ` Andrew Morton
2008-12-11 22:34 ` Nick Piggin
2008-12-10 7:27 ` [patch 4/6] fs: sys_sync fix Nick Piggin
2008-12-10 7:28 ` [patch 5/6] radix-tree: gang set if tagged operation Nick Piggin
2008-12-11 21:20 ` Andrew Morton
2008-12-11 22:10 ` Nick Piggin
2008-12-10 7:42 ` [patch 6/6] mm: fsync livelock avoidance Nick Piggin
2008-12-10 9:15 ` steve
2008-12-11 21:51 ` Andrew Morton
2008-12-11 22:32 ` Nick Piggin
2008-12-11 22:41 ` Andrew Morton [this message]
2008-12-11 22:45 ` Andrew Morton
2008-12-11 22:59 ` Nick Piggin
2008-12-11 21:51 ` Andrew Morton
2008-12-11 22:23 ` Andrew Morton
2008-12-11 22:45 ` Nick Piggin
2008-12-11 23:14 ` Andrew Morton
2008-12-11 23:43 ` Nick Piggin
2008-12-12 0:39 ` Andrew Morton
2008-12-12 4:01 ` Nick Piggin
2008-12-12 16:04 ` [patch 1/6] mm: direct IO starvation improvement Jeff Moyer
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=20081211144109.ee9c0410.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.