From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [UST PATCH] Make the error handling in open_channel more readable
Date: Tue, 22 Feb 2011 23:06:40 -0500 [thread overview]
Message-ID: <BLU0-SMTP5230E23DFB91AF98DED9CE96DB0@phx.gbl> (raw)
In-Reply-To: <1298307312-22272-1-git-send-email-yannick.brosseau@gmail.com>
* Yannick Brosseau (yannick.brosseau at gmail.com) wrote:
> Signed-off-by: Yannick Brosseau <yannick.brosseau at gmail.com>
> ---
> libust/buffers.c | 9 ++++-----
> 1 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/libust/buffers.c b/libust/buffers.c
> index 4e8004c..534d0ef 100644
> --- a/libust/buffers.c
> +++ b/libust/buffers.c
> @@ -319,12 +319,11 @@ static int open_channel(struct ust_channel *chan, size_t subbuf_size,
>
> return 0;
>
> - /* Jump directly inside the loop to close the buffers that were already
> - * opened. */
> - for(; i>=0; i--) {
> - close_buf(chan->buf[i]);
> error:
> - do {} while(0);
> + /* Loop through the opened buffers and close them. Skip the current i,
> + since it's the one that did not open. */
> + for(i--; i>=0; i--) {
> + close_buf(chan->buf[i]);
Not sure I see how this is more readable. You seem to be changing the
code behavior too.
Mathieu
> }
>
> pthread_mutex_unlock(&ust_buffers_channels_mutex);
> --
> 1.7.2.3
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-02-23 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 16:55 Yannick Brosseau
2011-02-23 4:06 ` Mathieu Desnoyers [this message]
[not found] ` <BLU0-SMTP9165A2945ADE5682920AC096DB0@phx.gbl>
2011-02-23 4:13 ` Yannick Brosseau
2011-02-23 4:23 ` Mathieu Desnoyers
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=BLU0-SMTP5230E23DFB91AF98DED9CE96DB0@phx.gbl \
--to=compudj@krystal.dyndns.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