FWIW, here's the ptrace(2) explanation of the PTRACE_O_TRACECLONE
option:
This option may not catch clone(2) calls in all cases.
If the
child calls clone(2) with the CLONE_VFORK flag,
PTRACE_EVENT_VFORK will be delivered instead if
PTRACE_O_TRACEVFORK is set; otherwise if the child calls
clone(2) with the exit signal set to SIGCHLD,
PTRACE_EVENT_FORK will be delivered if
PTRACE_O_TRACEFORK is set.
So we should only need to trace clone() if we care about clones that
neither set CLONE_VFORK nor have the exit signal set to SIGCHLD. And
all such clones are *not* separate processes for our purposes, but
threads, AFAICS.
So I agree that this is most likely invalid. Clint, did you manage to
get corosync sorted out?
** Changed in: upstart (Ubuntu Precise)
Status: Triaged => Incomplete
** Changed in: upstart
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681071
Title:
init: PTRACE_EVENT_CLONE not handled in fork tracking
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/681071/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
