linux-kernel - A problem with percpu variable cpu

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 PHC
Open Source and information security mailing list archives

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

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

Date:	Sun, 19 Feb 2012 20:20:31 +0800
From:	Tao Jiang <jiangtao.jit@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: A problem with percpu variable cpu_number

Hi:

I've asked the question on kernelnewbies, no replies.
So forward it here.
Thank you.


---------- Forwarded message ----------
From: tao jiang <jiangtao.jit@...il.com>
Date: 2012/2/16
Subject: A problem with percpu variable cpu_number
To: kernelnewbies <kernelnewbies@...nelnewbies.org>


Hi :

At the beginning of start_kernel() -- init/main.c
boot_cpu_init() is called

and in boot_cpu_init() will call smp_processor_id()
it's a macro
and it will be expanded as (percpu_read(cpu_number)) and so on

but i noticed that it's before setup_per_cpu_areas() in start_kernel()
is that mean the percpu areas hadn't be initialized yet
but why smp_processor_id() could be called before setup_per_cpu_areas()


Thank you.

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