From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] perf/x86/intel/pt: cleanup error handling in pt_pmu_hw_init()
Date: Thu, 09 Apr 2015 15:27:38 +0000 [thread overview]
Message-ID: <20150409152738.GD16501@mwanda> (raw)
In-Reply-To: <20150409090805.GG17605@mwanda>
On Thu, Apr 09, 2015 at 04:54:40PM +0200, Ingo Molnar wrote:
> > [...] If you unwind like:
> >
> > err_free_bar:
> > kfree(foo->bar);
> > err_free_foo:
> > kfree(foo);
> > return ret;
> >
> > That is less error prone.
>
> That's how I name and structure unwind labels as well, and my
> suggestion is to use something similar here in this code too, in
> arch/x86/kernel/cpu/perf_event_intel_pt.c.
>
> Agreed?
I don't understand what you want me to do here. I think you are saying
I should do this:
err_attrs:
kfree(attrs);
err:
return ret;
That's not the style that the rest of this file uses. Every function
uses direct returns where possible except pt_event_add() and that
function seems buggy.
arch/x86/kernel/cpu/perf_event_intel_pt.c
1000
1001 if (mode & PERF_EF_START) {
1002 pt_event_start(event, 0);
1003 if (hwc->state = PERF_HES_STOPPED) {
1004 pt_event_del(event, 0);
1005 ret = -EBUSY;
^^^^^^^^^^^^
We set "ret" here but then return zero.
1006 }
1007 } else {
1008 hwc->state = PERF_HES_STOPPED;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Shouldn't we set "ret" here?
1009 }
1010
1011 ret = 0;
1012 out:
1013
1014 if (ret)
1015 hwc->state = PERF_HES_STOPPED;
1016
1017 return ret;
1018 }
regards,
dan carpenter
next prev parent reply other threads:[~2015-04-09 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 9:08 [patch] perf/x86/intel/pt: cleanup error handling in pt_pmu_hw_init() Dan Carpenter
2015-04-09 12:02 ` Ingo Molnar
2015-04-09 12:33 ` Dan Carpenter
2015-04-09 12:45 ` Peter Zijlstra
2015-04-09 12:47 ` Alexander Shishkin
2015-04-09 13:30 ` Dan Carpenter
2015-04-09 14:54 ` Ingo Molnar
2015-04-09 15:27 ` Dan Carpenter [this message]
2015-04-11 8:37 ` Ingo Molnar
2015-04-11 11:03 ` Dan Carpenter
2015-04-12 9:38 ` Ingo Molnar
2015-04-12 9:51 ` Julia Lawall
2015-04-12 10:18 ` Ingo Molnar
2015-04-12 17:27 ` [tip:perf/core] perf/x86/intel/pt: Clean up the control flow " tip-bot for Ingo Molnar
2015-04-15 10:10 ` [patch] perf/x86/intel/pt: cleanup error handling " Alexander Shishkin
2015-04-15 10:27 ` Dan Carpenter
2015-04-15 10:50 ` Alexander Shishkin
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=20150409152738.GD16501@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.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 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.