From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-multipath [PATCH] "better" return codes.
Date: Thu, 2 Mar 2006 11:44:57 +0100 [thread overview]
Message-ID: <20060302104457.GA14155@pundit> (raw)
In-Reply-To: <20060227211110.GB7357@ether.msp.redhat.com>
On Mon, Feb 27, 2006 at 03:11:10PM -0600, Benjamin Marzinski wrote:
> I think that these multipathd return codes make more sense (failing if the map
> is not a multipath map, and not failing if it has already been added).
>
> -Ben
> diff -urpN mp-devel-clean/multipathd/main.c mp-devel-patched/multipathd/main.c
> --- mp-devel-clean/multipathd/main.c 2006-02-27 15:09:55.000000000 -0600
> +++ mp-devel-patched/multipathd/main.c 2006-02-27 15:16:13.000000000 -0600
> @@ -569,7 +569,7 @@ ev_add_map (char * devname, struct vecto
> if (map_present && dm_type(alias, DEFAULT_TARGET) <= 0) {
> condlog(4, "%s: not a multipath map", alias);
> FREE(alias);
> - return 0;
> + return 1;
> }
>
Returning ok here means the event needs no treatment and it's ok.
Seems right to me.
> mpp = find_mp_by_alias(vecs->mpvec, alias);
> @@ -709,7 +709,7 @@ ev_add_path (char * devname, struct vect
> /*
> * allow reconfig of orphaned path here
> */
> - if (pp->mpp) return 1;
> + if (pp->mpp) return 0;
> }
> else {
> /*
Indeed, the comment looks wrong wrt actual code.
Regards,
cvaroqui
prev parent reply other threads:[~2006-03-02 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 21:11 dm-multipath [PATCH] "better" return codes Benjamin Marzinski
2006-03-02 10:44 ` Christophe Varoqui [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=20060302104457.GA14155@pundit \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.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.