linux-kernel - Re: [PATCH] percpu,lockdep: implement and use is_static_percpu

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: <4B963513.1060508@kernel.org>
Date:	Tue, 09 Mar 2010 20:46:27 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Valdis.Kletnieks@...edu, Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] percpu,lockdep: implement and use is_static_percpu_address()

Hello,

On 03/09/2010 08:42 PM, Tejun Heo wrote:
>> So is_module_address() will only return true for static per-cpu module
>> storage, right?
> 
> Right, got confused there.  I'll update is_static_percpu_address() to
> test for reserved regions too.

Which I can't in straight forward manner because only the module code
knows the allocated address ranges on archs which don't require low
offset addresses for module static percpu symbols.  Seems like we'll
need to create is_module_percpu_address() or something.  I'll think
about it.

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/