From: Andi Kleen <ak@suse.de>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: Tom Duffy <tduffy@sun.com>, Andi Kleen <ak@suse.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [OOPS] powernow on smp dual core amd64
Date: Fri, 10 Jun 2005 22:01:54 +0200 [thread overview]
Message-ID: <20050610200153.GO23831@wotan.suse.de> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84301CFC134@SAUSEXMB1.amd.com>
On Fri, Jun 10, 2005 at 02:48:58PM -0500, Langsdorf, Mark wrote:
> It looks like the crash is caused by an invalid
> pointer dereference in
> query_current_values_with_pending_wait(), which
> implies that powernowk8_get() was called with an
> invalid CPU number.
>
> Andi, what will happen if you do
> set_cpus_allowed(current, cpumask_of_cpu(cpu)) when
> cpu isn't in the range of online CPUs? There's
It just returns with -EINVAL.
Also it really shouldnt happen.
> supposed to be a check to prevent an invalid
> pointer access from happening but it's failing for
> some reason.
-Andi
next prev parent reply other threads:[~2005-06-10 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 19:48 Langsdorf, Mark
2005-06-10 20:01 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-13 22:44 Langsdorf, Mark
2005-06-13 22:47 ` Andi Kleen
2005-06-13 22:58 ` Tom Duffy
2005-06-13 23:35 ` Andi Kleen
2005-06-14 18:19 ` Tom Duffy
2005-06-13 21:47 Langsdorf, Mark
2005-06-13 22:20 ` Tom Duffy
2005-06-13 22:38 ` Andi Kleen
2005-06-13 23:17 ` Zachary Amsden
2005-06-13 23:34 ` Andi Kleen
[not found] <84EA05E2CA77634C82730353CBE3A84301CFC14B@SAUSEXMB1.amd.com>
2005-06-13 21:27 ` Tom Duffy
2005-06-09 23:46 Tom Duffy
2005-06-10 16:53 ` [discuss] " Andi Kleen
2005-06-10 18:46 ` Tom Duffy
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=20050610200153.GO23831@wotan.suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=tduffy@sun.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®