From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Lin Ming" <ming.m.lin@intel.com>,
"Bob Moore" <robert.moore@intel.com>,
"Alexey Starikovskiy" <astarikovskiy@suse.de>,
"Len Brown" <len.brown@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ACPI: kmemcheck: Caught 16-bit read from freed memory (f7c12ec6)
Date: Tue, 6 May 2008 23:38:51 +0300 [thread overview]
Message-ID: <84144f020805061338yd6e3declaf5ff9ca344c28ba@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0805060909q635d2d43j9414e5f179c9e22f@mail.gmail.com>
On Tue, May 6, 2008 at 7:09 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Running kmemcheck on top of v2.6.26-rc1 gives the following (never
> before seen) warning:
>
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI init
> ACPI: bus type pnp registered
> kmemcheck: Caught 16-bit read from freed memory (f7c12ec6)
>
> Pid: 1, comm: swapper Not tainted (2.6.26-rc1-00010-g7966e04 #2)
> EIP: 0060:[<c027ecaa>] EFLAGS: 00010286 CPU: 0
> EIP is at acpi_ps_get_next_arg+0x1b8/0x262
> EAX: f7c12ec0 EBX: f7d20428 ECX: f7ca1b00 EDX: 00000001
> ESI: 00000049 EDI: f7d20400 EBP: f7c61e38 ESP: c06c9dc8
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> CR0: 8005003b CR2: f7c46456 CR3: 006ba000 CR4: 000006c0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff4ff0 DR7: 00000400
> [<c0119192>] kmemcheck_read+0xe2/0x140
> [<c0119326>] kmemcheck_access+0x136/0x1a0
> [<c04bd286>] do_page_fault+0x5e6/0x690
> [<c04bb2da>] error_code+0x72/0x78
> [<c027f991>] acpi_ps_parse_loop+0x4dd/0x7f8
> [<c027ee36>] acpi_ps_parse_aml+0xb4/0x332
> [<c02802c0>] acpi_ps_execute_method+0x13d/0x20d
> [<c027c8a2>] acpi_ns_evaluate+0x10e/0x1b0
> [<c0283210>] acpi_ut_evaluate_object+0x51/0x18d
> [<c0283406>] acpi_ut_execute_STA+0x22/0x7b
> [<c027c18b>] acpi_ns_get_device_callback+0x5a/0x121
> [<c027e410>] acpi_ns_walk_namespace+0xf0/0x10c
> [<c027c0b5>] acpi_get_devices+0x47/0x5d
> [<c068db45>] pnpacpi_init+0x65/0xa0
> [<c06735c7>] kernel_init+0x127/0x290
> [<c0104cc7>] kernel_thread_helper+0x7/0x10
> [<ffffffff>] 0xffffffff
> pnp: PnP ACPI: found 17 devices
> ACPI: ACPI bus type pnp unregistered
>
> This faulting instruction comes from
>
> $ addr2line -e vmlinux -i c027ecaa
> drivers/acpi/parser/psargs.c:694
(That's some seriously hairy code in ACPI btw.)
Vegard, can you do disassembly for the faulting instruction? I *think*
it's the "walk_state->op" bit that is hanging to an object that was
already deleted in the strange loop in acpi_ps_parse_loop() but it
would be good to have some more data on this.
Pekka
next prev parent reply other threads:[~2008-05-06 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 16:09 Vegard Nossum
2008-05-06 20:38 ` Pekka Enberg [this message]
2008-05-06 20:46 ` Vegard Nossum
2008-05-06 20:54 ` Pekka Enberg
2008-05-07 19:21 ` Vegard Nossum
2008-05-08 1:38 ` Lin Ming
2008-05-08 5:35 ` Lin Ming
2008-05-08 6:05 ` Vegard Nossum
2008-05-08 6:12 ` Lin Ming
2008-05-08 6:31 ` Vegard Nossum
2008-05-08 6:56 ` Lin Ming
2008-05-08 7:29 ` Vegard Nossum
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=84144f020805061338yd6e3declaf5ff9ca344c28ba@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=astarikovskiy@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
--cc=vegard.nossum@gmail.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
all inboxes | Powered by JetHome®