From: "J. Bruce Fields" <bfields@fieldses.org>
To: roel <roel.kluin@gmail.com>
Cc: Neil Brown <neilb@suse.de>,
linux-nfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SUNRPC: svc_register error overwritten in next iteration
Date: Mon, 14 Mar 2011 18:36:45 -0400 [thread overview]
Message-ID: <20110314223645.GL25442@fieldses.org> (raw)
In-Reply-To: <4D7B74C7.7060506@gmail.com>
On Sat, Mar 12, 2011 at 02:27:35PM +0100, roel wrote:
> The break is in the inner loop, the svc_register() error is overwritten
> in the next iteration. Only the error in the last iteration is returned.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> net/sunrpc/svc.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> Is this needed?
>
> diff --git a/net/sunrpc/svc.c b/net/sunrpc/svc.c
> index 08e05a8..5fd08c0 100644
> --- a/net/sunrpc/svc.c
> +++ b/net/sunrpc/svc.c
> @@ -889,6 +889,8 @@ int svc_register(const struct svc_serv *serv, const int family,
> if (error < 0)
> break;
May as well just "goto out" or "return error" here?
But: aren't we missing some cleanup? If we succesfully register one
program then fail at a second one, don't we need to unregister the
first?
--b.
> }
> + if (error < 0)
> + break;
> }
>
> return error;
next prev parent reply other threads:[~2011-03-14 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 13:27 [PATCH] SUNRPC: svc_register error overwritten in next iteration roel
2011-03-14 12:47 ` Chuck Lever
2011-03-14 22:36 ` J. Bruce Fields [this message]
2011-03-15 15:43 ` Chuck Lever
2011-03-15 16:13 ` J. Bruce Fields
2011-03-15 16:54 ` Chuck Lever
2011-03-15 16:57 ` J. Bruce Fields
2011-03-15 21:34 ` J. Bruce Fields
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=20110314223645.GL25442@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=roel.kluin@gmail.com \
/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.