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

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

Date:	Tue, 5 Feb 2008 13:32:01 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Sam Ravnborg <sam@...nborg.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] x86 updates



On Tue, 5 Feb 2008, H. Peter Anvin wrote:
> 
> The difference is quite simple:
> 
> 	a		- this section occupies address space
> 	w		- this section is writable
> 	x		- this section is executable
> 	progbits	- this section has data in the file
> 
> In contrast, a nobits section is implicitly zero-filled.

Well, the real question is "what are the defaults"

> By default:
> 
> .bss 	is (aw,nobits).
> .data 	is (aw,progbits).
> .rodata	is (a,progbits).
> .text	is (ax,progbits).

But what about something like ".init.data"?

I'd assume the defaults for unrecognized segments would have to be 
something sane like (aw,progbits) (ie my patch shouldn't make any 
difference), but where do we find that out?

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