From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
Cc: Yevgeny Kliteynik
<kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm/osm_console.c: fix memory and file descriptor leaks
Date: Tue, 07 Sep 2010 18:32:55 +0300 [thread overview]
Message-ID: <4C865B27.1000904@dev.mellanox.co.il> (raw)
In-Reply-To: <20100907082047.3b6be681.weiny2-i2BcT+NCU+M@public.gmane.org>
On 07-Sep-10 6:20 PM, Ira Weiny wrote:
> Hi Yevgeny,
>
> On Tue, 7 Sep 2010 08:12:58 -0700
> Yevgeny Kliteynik<kliteyn-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org> wrote:
>
>>
>> Signed-off-by: Yevgeny Kliteynik<kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
>> ---
>> opensm/opensm/osm_console.c | 9 ++++++---
>> 1 files changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/opensm/opensm/osm_console.c b/opensm/opensm/osm_console.c
>> index bc7bea3..29a6c83 100644
>> --- a/opensm/opensm/osm_console.c
>> +++ b/opensm/opensm/osm_console.c
>> @@ -1302,12 +1302,13 @@ static void dump_portguid_parse(char **p_last, osm_opensm_t * p_osm, FILE * out)
>> /* Check we have at least one expression to match */
>> if (p_head_regexp == NULL) {
>> fprintf(out, "No valid expression provided. Aborting\n");
>> + goto Exit;
>> return;
>
> While you are at it, shouldn't you remove the return here as well?
Yep :)
-- Yevgeny
> Ira
>
>> }
>>
>> if (p_osm->sm.p_subn->need_update != 0) {
>> fprintf(out, "Subnet is not ready yet. Try again later\n");
>> - return;
>> + goto Free_and_exit;
>> }
>>
>> /* Subnet doesn't need to be updated so we can carry on */
>> @@ -1333,14 +1334,16 @@ static void dump_portguid_parse(char **p_last, osm_opensm_t * p_osm, FILE * out)
>> }
>>
>> CL_PLOCK_RELEASE(p_osm->sm.p_lock);
>> - if (output != out)
>> - fclose(output);
>>
>> +Free_and_exit:
>> for (; p_head_regexp; p_head_regexp = p_regexp) {
>> p_regexp = p_head_regexp->next;
>> regfree(&p_head_regexp->exp);
>> free(p_head_regexp);
>> }
>> +Exit:
>> + if (output != out)
>> + fclose(output);
>> }
>>
>> static void help_dump_portguid(FILE * out, int detail)
>> --
>> 1.6.2.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at http://*vger.kernel.org/majordomo-info.html
>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-07 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 15:12 [PATCH] opensm/osm_console.c: fix memory and file descriptor leaks Yevgeny Kliteynik
[not found] ` <4C86567A.5060400-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2010-09-07 15:20 ` Ira Weiny
[not found] ` <20100907082047.3b6be681.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-09-07 15:32 ` Yevgeny Kliteynik [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=4C865B27.1000904@dev.mellanox.co.il \
--to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=weiny2-i2BcT+NCU+M@public.gmane.org \
/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