From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Lin Ming" <ming.m.lin@intel.com>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>,
"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: Thu, 8 May 2008 08:05:27 +0200 [thread overview]
Message-ID: <19f34abd0805072305i19dc37bn3e13fbca4b6981e3@mail.gmail.com> (raw)
In-Reply-To: <1210224923.22503.8.camel@minggr.sh.intel.com>
Hello,
On Thu, May 8, 2008 at 7:35 AM, Lin Ming <ming.m.lin@intel.com> wrote:
> Here comes a simple patch that fixes the warning in my machine.
>
> Vegard, would you please help to test it in your machine?
>
Thanks for the try, but unfortunately this does not solve the problem.
Please note that kmemcheck is an patch to the kernel; without it you
will never see the warning. You can pull it from
git://git.kernel.org/pub/scm/linux/kernel/git/vegard/kmemcheck.git current
though it is unlikely that it will help you more than looking at the
code (or the report) will do.
> Thanks,
> Lin Ming
>
> Signed-off-by: Lin Ming <ming.m.lin@intel.com>
> ---
> diff --git a/drivers/acpi/parser/psargs.c b/drivers/acpi/parser/psargs.c
> index f1e8bf6..ef55d24 100644
> --- a/drivers/acpi/parser/psargs.c
> +++ b/drivers/acpi/parser/psargs.c
> @@ -268,7 +268,7 @@ acpi_ps_get_next_namepath(struct acpi_walk_state
> *walk_state,
> */
> if (ACPI_SUCCESS(status) &&
> possible_method_call && (node->type == ACPI_TYPE_METHOD)) {
> - if (walk_state->op->common.aml_opcode == AML_UNLOAD_OP) {
> + if (walk_state->op && walk_state->op->common.aml_opcode ==
> AML_UNLOAD_OP) {
> /*
> * acpi_ps_get_next_namestring has increased the AML pointer,
> * so we need to restore the saved AML pointer for method call.
Also, noticing your change, I can see why it makes no difference:
Pekka already found that it is walk_state->op that has the value of
0xf7c12ec6 (e.g. the pointer being dereferenced), so the test will
still succeed.
On the other hand, I have discovered what seems to be a deficiency in
kmemcheck (i.e. it might be my fault entirely), so it is possible that
the warning is bogus. Will send an update shortly.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-05-08 6:05 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
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 [this message]
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=19f34abd0805072305i19dc37bn3e13fbca4b6981e3@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--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=penberg@cs.helsinki.fi \
--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
all inboxes | Powered by JetHome®