Hi, It seems that Corosync is segfaulting whenever I restart the network using yast in SLES11SP1. This is in reference to http://www.mail-archive.com/openais@xxxxxxxxxxxxxxxxxxxxxxxxxx/msg06233.html version info: Corosync Cluster Engine, version '1.4.3' Copyright (c) 2006-2009 Red Hat, Inc. Could you send a copy of your patch to me? I would like to try it out. Regards, Kashif Jawed Siddiqui Senior Software Engineer Huawei Technologies India Pvt. Ltd. Level 3,4 &5 Leela Galleria, The Leela Palce 23, Airport Road, Bangalore - 560008 080 41117676 kashifjs@xxxxxxxxxx www.huawei.com *************************************************************************************** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ________________________________________ From: discuss-bounces@xxxxxxxxxxxx [discuss-bounces@xxxxxxxxxxxx] on behalf of Jan Friesse [jfriesse@xxxxxxxxxx] Sent: Tuesday, April 24, 2012 12:52 PM To: Fabio M. Di Nitto Cc: discuss@xxxxxxxxxxxx Subject: Re: [PATCH 2/2] icmap: don't leak memory when changing ro/rw status on a key ACK Fabio M. Di Nitto napsal(a): > From: "Fabio M. Di Nitto" <fdinitto@xxxxxxxxxx> > > Signed-off-by: Fabio M. Di Nitto <fdinitto@xxxxxxxxxx> > --- > exec/icmap.c | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/exec/icmap.c b/exec/icmap.c > index 2743959..eb9f0c9 100644 > --- a/exec/icmap.c > +++ b/exec/icmap.c > @@ -950,6 +950,7 @@ cs_error_t icmap_set_ro_access(const char *key_name, int prefix, int ro_access) > return (CS_ERR_EXIST); > } else { > list_del(&icmap_ro_ai->list); > + free(icmap_ro_ai->key_name); > free(icmap_ro_ai); > > return (CS_OK); _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
