linux-kernel - Re: [git pull] x86 updates

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:	Tue, 5 Feb 2008 22:18:54 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] x86 updates

On Tue, Feb 05, 2008 at 01:09:28PM -0800, H. Peter Anvin wrote:
> Ingo Molnar wrote:
> >
> >btw., what's the practical consequence of getting these section flags 
> >wrong - for example writable data can end up in executable section 
> >accidentally and be marked readonly by RODATA? Or can anything more 
> >serious happen? (they cannot get into any of the discarded sections, we 
> >filter for them explicitly in the linker scripts)
> >
> 
> The practical consequences are probably zero - *except* for getting the 
> "a" flag wrong, as !a sections will never be loaded.
> 
> Technically we should also specify @progbits or @nobits on sections, 
> however, I think @progbits is the default.

I have on my todo list to do so. But I wanted to investigate a bit
more since I do not yet fully understand the difference.

And we have to use %progbits and %nobits as ARM uses '"' to indicate
comments.

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