All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] acpi: fix null pointer deference of hardware_id string
Date: Sun, 27 Sep 2009 09:49:58 +0800	[thread overview]
Message-ID: <1254016198.17697.19.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1253903053.26639.3.camel@localhost>

On Sat, 2009-09-26 at 02:24 +0800, Thomas Meyer wrote:
> Am Donnerstag, den 13.08.2009, 11:12 +0800 schrieb Lin Ming:
> > From: Lin Ming <ming.m.lin@intel.com>
> > Date: Thu, 13 Aug 2009 11:04:47 +0800
> 
> Another month, another git repository...
> 
> Are there any reasons why the patch below didn't land in linus' git
> tree?

A similar patch from Bjorn Helgaas is in Linus' tree.

ACPICA: fixup after acpi_get_object_info() change
b24715027aab5e586c4ab1d035f3e543307dea69

Lin Ming

> 
> > Subject: [PATCH] acpi: fix null pointer deference of hardware_id string
> > 
> > This regression was caused by commit ed44482
> > "ACPICA: Major update for acpi_get_object_info external interface"
> > 
> > Don't need to set hardware_id string \0 terminated here,
> > acpi_get_object_info already handles it.
> > 
> > Tested-by: Thomas Meyer <thomas@m3y3r.de>
> > Signed-off-by: Lin Ming <ming.m.lin@intel.com>
> > ---
> >  drivers/char/agp/hp-agp.c         |    6 ++++--
> >  drivers/pci/hotplug/acpiphp_ibm.c |    1 -
> >  2 files changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/char/agp/hp-agp.c b/drivers/char/agp/hp-agp.c
> > index 7bead4c..d83c4a8 100644
> > --- a/drivers/char/agp/hp-agp.c
> > +++ b/drivers/char/agp/hp-agp.c
> > @@ -492,8 +492,10 @@ zx1_gart_probe (acpi_handle obj, u32 depth, void *context, void **ret)
> >  		status = acpi_get_object_info(handle, &info);
> >  		if (ACPI_SUCCESS(status)) {
> >  			/* TBD check _CID also */
> > -			info->hardware_id.string[sizeof(info->hardware_id.length)-1] = '\0';
> > -			match = (strcmp(info->hardware_id.string, "HWP0001") == 0);
> > +			if (info->valid & ACPI_VALID_HID)
> > +				match = !strcmp(info->hardware_id.string, "HWP0001");
> > +			else
> > +				match = 0;
> >  			kfree(info);
> >  			if (match) {
> >  				status = hp_acpi_csr_space(handle, &sba_hpa, &length);
> > diff --git a/drivers/pci/hotplug/acpiphp_ibm.c b/drivers/pci/hotplug/acpiphp_ibm.c
> > index a9d926b..e7be66d 100644
> > --- a/drivers/pci/hotplug/acpiphp_ibm.c
> > +++ b/drivers/pci/hotplug/acpiphp_ibm.c
> > @@ -406,7 +406,6 @@ static acpi_status __init ibm_find_acpi_device(acpi_handle handle,
> >  			__func__, status);
> >  		return retval;
> >  	}
> > -	info->hardware_id.string[sizeof(info->hardware_id.length) - 1] = '\0';
> >  
> >  	if (info->current_status && (info->valid & ACPI_VALID_HID) &&
> >  			(!strcmp(info->hardware_id.string, IBM_HARDWARE_ID1) ||
> > 
> > 
> 


      reply	other threads:[~2009-09-27  1:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  3:12 [PATCH] acpi: fix null pointer deference of hardware_id string Lin Ming
2009-09-25 18:24 ` Thomas Meyer
2009-09-27  1:49   ` Lin Ming [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=1254016198.17697.19.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    /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.