All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] percpu: fix first chunk match in per_cpu_ptr_to_phys()
Date: Fri, 18 Jun 2010 15:07:10 +0200	[thread overview]
Message-ID: <4C1B6F7E.5040802@kernel.org> (raw)
In-Reply-To: <20100618123002.GA15931@sgi.com>

On 06/18/2010 02:30 PM, Cliff Wickman wrote:
> On Fri, Jun 18, 2010 at 11:56:16AM +0200, Tejun Heo wrote:
>> per_cpu_ptr_to_phys() determines whether the passed in @addr belongs
>> to the first_chunk or not by just matching the address against the
>> address range of the base unit (unit0, used by cpu0).  When an adress
>> from another cpu was passed in, it will always determine that the
>> address doesn't belong to the first chunk even when it does.  This
>> makes the function return a bogus physical address which may lead to
>> crash.
>>
>> This problem was discovered by Cliff Wickman while investigating a
>> crash during kdump on a SGI UV system.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>> Reported-by: Cliff Wickman <cpw@sgi.com>
>> ---
>> Can you please verify this one?  I added a small optimization so that
>> it doesn't suck too bad on large machines and it works fine here but
>> it would be great to have your Tested-by:.
> 
> Yep.  Works fine on 32p UV.
> 
> Tested-by: Cliff Wickman <cpw@sgi.com>

Great, thanks.  Will push it to mainline and -stable.

-- 
tejun

      reply	other threads:[~2010-06-18 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 16:20 per_cpu_ptr_to_phys() failure on UV x86_64 Cliff Wickman
2010-06-17 17:08 ` Tejun Heo
2010-06-17 17:35   ` Tejun Heo
2010-06-17 18:24     ` Cliff Wickman
2010-06-18  9:56       ` [PATCH] percpu: fix first chunk match in per_cpu_ptr_to_phys() Tejun Heo
2010-06-18 12:30         ` Cliff Wickman
2010-06-18 13:07           ` Tejun Heo [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=4C1B6F7E.5040802@kernel.org \
    --to=tj@kernel.org \
    --cc=cpw@sgi.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.