linux-kernel - Re: Strange hang on ia64 with CONFIG_PRINTK

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: <12c511ca0802131659u6e4407d9w96148fe72d6e11d7@mail.gmail.com>
Date:	Wed, 13 Feb 2008 16:59:30 -0800
From:	"Tony Luck" <tony.luck@...el.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	mingo@...e.hu, rdreier@...co.com, linux-kernel@...r.kernel.org
Subject: Re: Strange hang on ia64 with CONFIG_PRINTK_TIME=y

> It is legal to access per-cpu data as early as you like,
> it just evaluates to the static copy in the per-cpu section
> of the kernel image until the per-cpu areas are setup.

On ia64 per-cpu variables are mapped into the top 64K
of the address space.  Accessing them before the
resources to handle the access to that virtual address
have been set up would cause problems.

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