public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Toshi Kani <toshi.kani@hp.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / memhotplug: Fix a stale pointer in error path
Date: Fri, 12 Jul 2013 22:42:33 +0200	[thread overview]
Message-ID: <3723604.ey6eovWnzB@vostro.rjw.lan> (raw)
In-Reply-To: <1373640689.24916.15.camel@misato.fc.hp.com>

On Friday, July 12, 2013 08:51:29 AM Toshi Kani wrote:
> On Fri, 2013-07-12 at 09:24 +0900, Yasuaki Ishimatsu wrote:
> > (2013/07/11 1:47), Toshi Kani wrote:
> > > device->driver_data needs to be cleared when releasing its data,
> > > mem_device, in an error path of acpi_memory_device_add().
> > > 
> > > Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> > > ---
> > 
> > Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> 
> Thanks Yasuaki!

Queued up as a fix for 3.11.

Do we need that in -stable as well?

Rafael


> > 
> > >   drivers/acpi/acpi_memhotplug.c |    1 +
> > >   1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
> > > index c711d11..999adb5 100644
> > > --- a/drivers/acpi/acpi_memhotplug.c
> > > +++ b/drivers/acpi/acpi_memhotplug.c
> > > @@ -323,6 +323,7 @@ static int acpi_memory_device_add(struct acpi_device *device,
> > >   	/* Get the range from the _CRS */
> > >   	result = acpi_memory_get_device_resources(mem_device);
> > >   	if (result) {
> > > +		device->driver_data = NULL;
> > >   		kfree(mem_device);
> > >   		return result;
> > >   	}
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > 
> > 
> > 
> 
> 
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-07-12 20:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 16:47 [PATCH] ACPI / memhotplug: Fix a stale pointer in error path Toshi Kani
2013-07-12  0:24 ` Yasuaki Ishimatsu
2013-07-12 14:51   ` Toshi Kani
2013-07-12 20:42     ` Rafael J. Wysocki [this message]
2013-07-12 21:01       ` Toshi Kani
2013-07-12 21:13         ` Rafael J. Wysocki
2013-07-12 21:12           ` Toshi Kani
2013-07-12 21:40             ` Rafael J. Wysocki
2013-07-12 22:28               ` Toshi Kani
2013-07-12 23:53                 ` Rafael J. Wysocki
2013-07-15 16:11                   ` Toshi Kani

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=3723604.ey6eovWnzB@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toshi.kani@hp.com \
    /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