Hi, I've asked about this before, but I still don't see the reason;
In 9/port/sysproc.c:sysrfork(), after a new process has been created, dupseg is called on each of the donor process's segments; why is the new process's p->seglock locked for this duration? The new process hasn't been published yet, no one else could serialize on that lock... Am I missing something? -- vs
