Skip to contentSkip to conversation

__init poisoning for i386, too

DISCUSSION Andi Kleen 1 participant 1 message Oct 7, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#2 lore raw
Quoted 8 lines · William Lee Irwin III
Quoted 3 lines · Pavel Machek

Overwrite __init section so calls to __init functions from normal code are catched, reliably. I wonder if this should be configurable... but it is configurable on x86-64 so I copied it. Please apply,

Any chance we could:
(a) set the stuff to 0x0f0b so illegal instructions come of it; jumps are most often aligned to something > 16 bits anyway

0xcc is an int3, that already causes an oops.

Quoted 1 line

(b) poison __initdata, memsetting to some bit pattern oopsable to dereference

Would be a good idea yes. I will add it to x86-64.

-Andi