linux-kernel - Re: const vs _

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 for Android: free password hash cracker in your pocket

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

Message-ID: <471E7151.8070805@garzik.org>
Date:	Tue, 23 Oct 2007 18:10:25 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
CC:	linux-kernel@...r.kernel.org,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Greg KH <greg@...ah.com>
Subject: Re: const vs __{dev}initdata

Bartlomiej Zolnierkiewicz wrote:
> Hi,
> 
> It seems that const cannot be (officialy) mixed with __{dev}initdata,
> 
> include/linux/init.h:
> ...
>  *
>  * Also note, that this data cannot be "const".
>  */
> ...
> 
> [ BTW Greg: this doesn't seem to be mentioned in LDD3. ]
> 
> Any reason for this limitation (other than not having .init.rodata section
> and __const__{dev}initdata tag)?  There are places where we really would like
> to have both, i.e. struct ide_port_info in drivers/ide.

Thank you for asking this question...  we really do need a solution for 
this.

As you point out, there are many valid cases for both const and initdata.

	Jeff



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