linux-kernel - Re: Tree sweep to fix up initconst

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]

Date:	Fri, 16 Sep 2011 01:33:54 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andi Kleen <andi@...stfloor.org>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Tree sweep to fix up initconst

On Thu, 15 Sep 2011, Andi Kleen wrote:

> This is a global tree sweep to fix up initconst section problems.
> 
> Any variable const in initdata must be marked __initconst, not initdata.
> const __read_mostly is not allowed.
> 
> Otherwise the global sections can get a read only marking and in some
> circumstances the compiler/and or the linker will detect conflicts.

In some circumstances?  Care to explain that in detail?
 
> This patchkit aims to fix it up everywhere.

Aims? How did you generate these patches? [grep|compile+look] and hack
or did you actually use something sensible like coccinelle?
 
> Also available in git://github.com/andikleen/linux-misc.git const-sections
> 
> Note I plan to ask Linus to pull this directly.

You can plan what you want, but unless you provide substantial
information please target your plan towards /dev/null

Thanks,

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