linux-kernel - Re: per_cpu_ptr_to_phys() failure on UV x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C1A5679.8010907@kernel.org>
Date:	Thu, 17 Jun 2010 19:08:09 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Cliff Wickman <cpw@....com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: per_cpu_ptr_to_phys() failure on UV x86_64

Hello,

On 06/17/2010 06:20 PM, Cliff Wickman wrote:
>  phys_addr_t per_cpu_ptr_to_phys(void *addr)
>  {
> +	if ((unsigned long)addr < VMALLOC_START ||
> +	    (unsigned long)addr >= VMALLOC_END)
> +		return __pa(addr);
>  	if (pcpu_addr_in_first_chunk(addr)) {
> -		if ((unsigned long)addr < VMALLOC_START ||
> -		    (unsigned long)addr >= VMALLOC_END)
> -			return __pa(addr);
> -		else
> -			return page_to_phys(vmalloc_to_page(addr));
> +		return page_to_phys(vmalloc_to_page(addr));
>  	} else
>  		return page_to_phys(pcpu_addr_to_page(addr));
>  }

(scratching head...) So, that means it's given an address for which
!pcpu_addr_in_first_chunk() but outside of vmalloc area.  Strange.
I'll find out what's going on.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/