Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] handle some malloc failures
Date: Tue, 21 Oct 2008 13:56:30 +0200	[thread overview]
Message-ID: <87ljwiyxe9.fsf@rho.meyering.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0810211316010.9830@trider-g7> (Fabio M. Di Nitto's message of "Tue, 21 Oct 2008 13:17:03 +0200 (CEST)")

"Fabio M. Di Nitto" <fabbione@fabbione.net> wrote:
> Merged into master branch. I had some issues to get them in the tree
> so the SHA1 are different from your original posting but it's all
> there.

Thanks, Fabio.
Here's a tiny adjustment:

From 01c30afac0bf97d84df11cc32773304a99613a08 Mon Sep 17 00:00:00 2001
From: Jim Meyering <meyering@redhat.com>
Date: Mon, 13 Oct 2008 15:22:55 +0200
Subject: [PATCH] adjust a diagnostic

* group/dlm_controld/deadlock.c (add_waitfor): Tweak diagnostic.
---
 group/dlm_controld/deadlock.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/group/dlm_controld/deadlock.c b/group/dlm_controld/deadlock.c
index cdedb87..9eccaae 100644
--- a/group/dlm_controld/deadlock.c
+++ b/group/dlm_controld/deadlock.c
@@ -1340,7 +1340,7 @@ static void add_waitfor(struct lockspace *ls, struct dlm_lkb *waiting_lkb,
 		new_waitfor = realloc(tr->waitfor,
 				      tr->waitfor_alloc * sizeof(*tr->waitfor));
 		if (new_waitfor == NULL) {
-			log_group(ls, "failed to allocate ...");
+			log_group(ls, "failed to allocate internal buffer");
 			free (tr->waitfor);
 			return;
 		}
--
1.6.0.2.588.g3102



  reply	other threads:[~2008-10-21 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 16:38 [Cluster-devel] handle some malloc failures Jim Meyering
2008-10-21 11:17 ` Fabio M. Di Nitto
2008-10-21 11:56   ` Jim Meyering [this message]
2008-10-22  7:32     ` 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=87ljwiyxe9.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox