linux-kernel - Re: lockdep: access percpu variable too early

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: <20130306103406.GB16827@gmail.com>
Date:	Wed, 6 Mar 2013 11:34:06 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Ming Lei <ming.lei@...onical.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: lockdep: access percpu variable too early


* Ming Lei <ming.lei@...onical.com> wrote:

> On Wed, Mar 6, 2013 at 6:20 PM, Ingo Molnar <mingo@...nel.org> wrote:
> >
> > What's the practical effect of it? Do we copy the value from the boot CPU and 
> > thus the secondary CPUs start with slightly increased stats?
> 
> Yes, it is the major effect.
> 
> Also the arch dependent __my_cpu_offset might be initialized a bit late.

I suspect we could try to fix it - post-initializing it after percpu setup sounds 
like a viable option, if it does not get too ugly.

Thanks,

	Ingo
--
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/