From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] cman: improve cman/qdisk interactions
Date: Wed, 7 Sep 2011 14:07:45 -0400 [thread overview]
Message-ID: <20110907180745.GA5988@redhat.com> (raw)
In-Reply-To: <1315401025-10670-1-git-send-email-fdinitto@redhat.com>
Hi,
Good design -- couple of things...
On Wed, Sep 07, 2011 at 03:10:25PM +0200, Fabio M. Di Nitto wrote:
> - cman: use strdup instead of malloc+strcpy (code is more readable)
* Not really a necessary change, but ok.
> - libcman: perform better error checking in register_quorum_device/update_quorum_device
>
> - Allow qdisk to update device name in cman using a new libcman quorum API call
> - Perform slight better error checking of some update opertaions
>
> Resolves: rhbz#735917
* All in all, this seems like a lot of patch for a very tiny problem or
set of problems in a very narrow use case (renaming quorum device).
> + if (quorum_device->name)
> + free(quorum_device->name);
> +
> + free(quorum_device);
> +
> + quorum_device = NULL;
> +
> + return;
* return is implied in functions returning void (no big deal; stylistic
stuff)
> +static void quorum_device_update_votes(int votes)
> +{
> + int oldvotes;
> +
> + /* Update votes even if it existed before */
> + oldvotes = quorum_device->votes;
> + quorum_device->votes = votes;
> +
> + /* If it is a member and votes decreased, recalculate quorum */
> + if (quorum_device->state == NODESTATE_MEMBER &&
> + oldvotes != votes) {
> + recalculate_quorum(1, 0);
> + }
> +}
* Code does not match comments; 'oldvotes != votes' is not a check
for decrease, and recalculate_quorum(1, 0) allows both increases and
decreases to votes. Is the comment wrong or the code? (I think the
comment is wrong...)
> + if (errno == EBUSY) {
> + logt_print(LOG_NOTICE, "quorum device is already registered, updating\n");
> + ret = update_device(&ctx);
> + if (ret) {
> + logt_print(LOG_ERR, "DEBUG: unable to update quorum device info\n");
> + goto out;
> + }
* Is this a debug or an error message? An error message with DEBUG: in
it is confusing; can we have one or the other?
--
Lon Hohberger - Red Hat, Inc.
next prev parent reply other threads:[~2011-09-07 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 13:10 [Cluster-devel] [PATCH] cman: improve cman/qdisk interactions Fabio M. Di Nitto
2011-09-07 18:07 ` Lon Hohberger [this message]
2011-09-08 6:39 ` Fabio M. Di Nitto
2011-09-08 7:45 ` Christine Caulfield
-- strict thread matches above, loose matches on Subject: below --
2011-09-08 6:59 Fabio M. Di Nitto
2011-09-08 7:02 ` Fabio M. Di Nitto
2011-09-08 14:04 ` Lon Hohberger
2011-09-07 12:40 Fabio M. Di Nitto
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=20110907180745.GA5988@redhat.com \
--to=lhh@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.