mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: Jonghwan Choi <jhbird.choi@samsung.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	"'Wei Yongjun'" <yongjun_wei@trendmicro.com.cn>,
	"'Peter Zijlstra'" <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 3.8-stable] perf: Fix error return code
Date: Fri, 10 May 2013 03:08:42 +0100	[thread overview]
Message-ID: <1368151722.17344.1.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20130423105659.GE3471@hercules>

[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]

On Tue, 2013-04-23 at 11:56 +0100, Luis Henriques wrote:
> On Tue, Apr 23, 2013 at 11:57:51AM +0900, Jonghwan Choi wrote:
> > 3.8-stable review patch.  If anyone has any objections, please let me know.
> 
> Thanks, I believe this is also applicable to 3.2.y, 3.4.y and 3.5.y.

I agree; I've queued this up for 3.2.y, thanks.

Ben.

> Cheers,
> --
> Luis
> 
> > 
> > ------------------
> > 
> > From: "Wei Yongjun <yongjun_wei@trendmicro.com.cn>"
> > 
> > commit c481420248c6730246d2a1b1773d5d7007ae0835 upstream.
> > 
> > Fix to return -ENOMEM in the allocation error case instead of 0
> > (if pmu_bus_running == 1), as done elsewhere in this function.
> > 
> > Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
> > Cc: a.p.zijlstra@chello.nl
> > Cc: paulus@samba.org
> > Cc: acme@ghostprotocols.net
> > Link:
> > http://lkml.kernel.org/r/CAPgLHd8j_fWcgqe%3DKLWjpBj%2B%3Do0Pw6Z-SEq%3DNTPU08
> > c2w1tngQ@mail.gmail.com
> > [ Tweaked the error code setting placement and the changelog. ]
> > Signed-off-by: Ingo Molnar <mingo@kernel.org>
> > Signed-off-by: Jonghwan Choi <jhbird.choi@samsung.com>
> > ---
> >  kernel/events/core.c |    1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index 7b6646a..f6eba58 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -5988,6 +5988,7 @@ skip_type:
> >  	if (pmu->pmu_cpu_context)
> >  		goto got_cpu_context;
> >  
> > +	ret = -ENOMEM;
> >  	pmu->pmu_cpu_context = alloc_percpu(struct perf_cpu_context);
> >  	if (!pmu->pmu_cpu_context)
> >  		goto free_dev;
> > -- 
> > 1.7.9.5
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe stable" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2013-05-10  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  2:57 Jonghwan Choi
2013-04-23 10:56 ` Luis Henriques
2013-05-10  2:08   ` Ben Hutchings [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=1368151722.17344.1.camel@deadeye.wl.decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=a.p.zijlstra@chello.nl \
    --cc=jhbird.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=stable@vger.kernel.org \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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

all inboxes | Powered by JetHome®