From: Andi Kleen <ak@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
robert.moore@intel.com, Alex Chiang <achiang@hp.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] acpi: fix crash in core ACPI code, triggered by CONFIG_ACPI_PCI_SLOT=y
Date: Mon, 21 Jul 2008 20:38:27 +0200 [thread overview]
Message-ID: <4884D7A3.6010802@linux.intel.com> (raw)
In-Reply-To: <20080721135745.GA22748@elte.hu>
Ingo Molnar wrote:
[For acpica issues please always put robert.moore@intel.com into Cc. Thanks]
[Bob, will need to resync this into ACPICA]
> I.e. when we called acpi_ns_handle_to_pathname(), we got required_size
> of 0 due to an error condition, but this is passed to the ACPI allocator
> unconditionally:
>
> required_size = acpi_ns_get_pathname_length(node);
>
> /* Validate/Allocate/Clear caller buffer */
>
> status = acpi_ut_initialize_buffer(buffer, required_size);
> if (ACPI_FAILURE(status)) {
> return_ACPI_STATUS(status);
> }
>
> Where acpi_ut_initialize_buffer(), through many (unnecessary) layers,
> ends up calling kzalloc(0). Which returns 0x10 and that then causes the
> crash later on.
>
> So fix both callers of acpi_ns_get_pathname_length(), which can return 0
> in case of an invalid node.
>
> Also add a WARN_ON() against zero sized allocations in
> acpi_ut_initialize_buffer() to make it easier to find similar instances
> of this bug.
>
> I have tested this patch for the past 24 hours and the crash has not
> reappeared.
Thanks for the detailed analysis and the patch. Patch looks mostly good,
except that the error message could be a little clearer ("Invalid zero
length node string" perhaps?). It'll need to be backmerged into
the ACPICA code base, but that can be done in parallel without
delaying fixing this bug.
I can add it to my next batch your or you can add it one of yours
if you prefer.
-Andi
prev parent reply other threads:[~2008-07-21 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 23:39 [git pull] PCI pull request for 2.6.27 Jesse Barnes
2008-07-16 23:50 ` Linus Torvalds
2008-07-16 23:54 ` Jesse Barnes
2008-07-17 0:23 ` Maciej W. Rozycki
2008-07-17 0:38 ` Linus Torvalds
2008-07-17 0:28 ` Linus Torvalds
2008-07-21 13:57 ` [patch] acpi: fix crash in core ACPI code, triggered by CONFIG_ACPI_PCI_SLOT=y Ingo Molnar
2008-07-21 18:38 ` Andi Kleen [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=4884D7A3.6010802@linux.intel.com \
--to=ak@linux.intel.com \
--cc=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=robert.moore@intel.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox