Skip to contentSkip to conversation

IA64/x86-64 and execution protection support?

DISCUSSION Joseph Pingenot 3 participants 3 messages Nov 3, 2003

lore
Share & tools
lore
#0 lore raw

Hello.

I was reading El Reg this morning when they discussed "execution protection"
on the new Intel (IA64) and AMD (K8 and above) chips.
Does the Linux kernel have support for preventing execution of certain
memory regions on those architectures?
Also, I know that some implementations of x86 stack protection are out there;
I've not seen them in the vanilla kernels; is there any plan to implement them?

Thank you!
-Joseph

Signature · 7 lines
Joseph===============================================trelane@digitasaru.net
"Asked by CollabNet CTO Brian Behlendorf whether Microsoft will enforce its
 patents against open source projects, Mundie replied, 'Yes, absolutely.'
 An audience member pointed out that many open source projects aren't
 funded and so can't afford legal representation to rival Microsoft's. 'Oh
 well,' said Mundie. 'Get your money, and let's go to court.' 
Microsoft's patents only defensive? http://swpat.ffii.org/players/microsoft
#1 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line · Joseph Pingenot

Joseph> Hello. I was reading El Reg this morning when they Joseph> discussed "execution protection" on the new Intel (IA64) and Joseph> AMD (K8 and above) chips. Does the Linux kernel have Joseph> support for preventing execution of certain memory regions Joseph> on those architectures?

Yes, on ia64, data and stack do not get mapped executable by default. Also, return addresses (under the discretion of the compiler) are virtually always stored on a separate register stack, making it more difficult to use memory stack overflows to overwrite return addresses.

--daviid

#2 lore raw
In reply to Joseph Pingenot
Quoted 2 lines · Joseph Pingenot

Does the Linux kernel have support for preventing execution of certain
memory regions on those architectures?

It does on x86_64, yes. This can be enabled or disabled via command line options.

	<b