Skip to contentSkip to conversation

stack -> PROT_EXEC/why?

DISCUSSION [email protected] 2 participants 3 messages Aug 5, 2002

lore
Share & tools
lore
#0 lore raw

hi,
casually looking at files like this:
glibc-2.2.3/linuxthreads/manager.c

 |       res_addr = mmap(map_addr, stacksize + guardsize,
 | 		      PROT_READ | PROT_WRITE | PROT_EXEC,
 | 		      MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);

it appears PROT_EXEC is also given to the per thread
stack(?) pages -- why is it the case? that is - if we consider things like buffer overflow (security) problems, isn't it better not give PROT_EXEC unless abslutely necessary? [so -- maybe there *is* some absolute necessity I'm not aware of,... :(]
(stepping back) is PROT_EXEC also given to ordinally
stack segment of single threaded programs? was there any API to retrieve page protection bits given only arbitrary VM addresses?
regards,
kenji

#1 lore raw
Quoted 5 lines · [email protected] wrote:

casually looking at files like this:
glibc-2.2.3/linuxthreads/manager.c

 |       res_addr = mmap(map_addr, stacksize + guardsize,
 | 		      PROT_READ | PROT_WRITE | PROT_EXEC,
 | 		      MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
Quoted 8 lines

it appears PROT_EXEC is also given to the per thread
stack(?) pages -- why is it the case?

that is - if we
consider things like buffer overflow (security) problems, isn't it better not give PROT_EXEC unless abslutely necessary? [so -- maybe there *is* some absolute necessity I'm not aware of,... :(]

It is sometimes necessary to execute dynamically generated code which is placed on the stack. The most common cases are in handling signals, in a technique called a "trampoline" (this is mentioned in the gcc Info file), and some emulators (e.g. Executor, the Mac emulator).

Quoted 2 lines

(stepping back) is PROT_EXEC also given to ordinally
stack segment of single threaded programs?

Yes. There is a patch available to change this, but in the standard kernel, the primary stack is executable.

Quoted 2 lines

was there any API to retrieve page protection bits given only arbitrary VM addresses?

It isn't portable, but you can get this information from /proc/<pid>/maps.

Signature · 1 line
Glynn Clements <[email protected]>
#2 lore raw
Quoted 4 lines

It is sometimes necessary to execute dynamically generated code which is placed on the stack. The most common cases are in handling signals, in a technique called a "trampoline" (this is mentioned in the gcc Info file), and some emulators (e.g. Executor, the Mac emulator).

thank you very much - this helps me a lot.

Quoted 2 lines

Yes. There is a patch available to change this, but in the standard kernel, the primary stack is executable.

I'll try {locate/}take a look :)

Quoted 2 lines

It isn't portable, but you can get this information from /proc/<pid>/maps.

tested with my mini-test program - serves the purpose fine :)

thanks again!
kenji