linux-kernel - Re: Please include const-sections into linux-next

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: <3ede57fd7fb0eff1aebed4ed9cb08301.squirrel@www.firstfloor.org>
Date:	Wed, 19 Oct 2011 22:11:17 +0200
From:	"Andi Kleen" <andi@...stfloor.org>
To:	"James Bottomley" <James.Bottomley@...senPartnership.com>
Cc:	"Andi Kleen" <andi@...stfloor.org>,
	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: Please include const-sections into linux-next

> On Wed, 2011-10-19 at 15:04 -0500, James Bottomley wrote:
>> this is probably something to do with writeable strings?
>
> Bingo!  If I add -fno-writeable-strings to the compiler directives, it
> works.

Cool thanks. I assume the resulting kernel works.

This means the pa compiler defaults to -fwritable-strings? Odd.

Are you handling that or should I add a patch to the tree?

-Andi


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