Skip to contentSkip to conversation

CLONE_SIGHAND w/o CLONE_VM

DISCUSSION Albert Cahalan 2 participants 2 messages Sep 22, 2003

lore
Share & tools
lore
#0 lore raw

Does CLONE_SIGHAND without CLONE_VM ever make sense?

Note that the arch-specific kernel_thread() implementations add CLONE_VM, so kernel_thread() usage doesn't count unless you can point to an arch that doesn't add the CLONE_VM flag. (BTW, the user-mode port is missing CLONE_UNTRACED. Bug?)

#1 lore raw
Quoted 8 lines · Albert Cahalan

Does CLONE_SIGHAND without CLONE_VM ever make sense?

Note that the arch-specific kernel_thread() implementations add CLONE_VM, so kernel_thread() usage doesn't count unless you can point to an arch that doesn't add the CLONE_VM flag. (BTW, the user-mode port is missing CLONE_UNTRACED. Bug?)

Minor bug, but yes, it's a bug. kernel threads should always be CLONE_UNTRACED; UML wasn't in the tree when I added it.

Signature · 2 lines
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer