From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, Lin Ming <ming.m.lin@intel.com>,
Bob Moore <robert.moore@intel.com>,
Gary Hade <garyhade@us.ibm.com>
Subject: Re: [PATCH] ACPICA: fixup after acpi_get_object_info() change
Date: Mon, 31 Aug 2009 16:22:19 -0600 [thread overview]
Message-ID: <200908311622.20201.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20090831222000.11461.52371.stgit@bob.kio>
Oops, I meant to CC you guys, but forgot. 15b8dd53f5ffa is in
acpi-test, but not upstream yet.
On Monday 31 August 2009 04:20:00 pm Bjorn Helgaas wrote:
> Commit 15b8dd53f5ffa changed info->hardware_id from a static array to
> a pointer. If hardware_id is non-NULL, it points to a NULL-terminated
> string, so we don't need to terminate it explicitly. However, it may
> be NULL; in that case, we *can't* add a NULL terminator.
>
> This causes a NULL pointer dereference oops for devices without _HID.
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> CC: Lin Ming <ming.m.lin@intel.com>
> CC: Bob Moore <robert.moore@intel.com>
> CC: Gary Hade <garyhade@us.ibm.com>
> ---
> drivers/pci/hotplug/acpiphp_ibm.c | 1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> 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) ||
>
>
prev parent reply other threads:[~2009-08-31 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 22:20 [PATCH] ACPICA: fixup after acpi_get_object_info() change Bjorn Helgaas
2009-08-31 22:22 ` Bjorn Helgaas [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=200908311622.20201.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=garyhade@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.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