- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for pidWait (0.2 sec)
-
src/os/exec_unix.go
// Which type of Process do we have? switch p.mode { case modeHandle: // pidfd return p.pidfdWait() case modePID: // Regular PID return p.pidWait() default: panic("unreachable") } } func (p *Process) pidWait() (*ProcessState, error) { // TODO(go.dev/issue/67642): When there are concurrent Wait calls, one // may wait on the wrong process if the PID is reused after the // completes its wait.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Jun 10 22:06:47 UTC 2024 - 4.1K bytes - Viewed (0) -
src/os/pidfd_linux.go
// because the PID recycle issue doesn't exist (IOW, pidfd, unlike PID, // is guaranteed to refer to one particular process). Thus, there is no // need for the workaround (blockUntilWaitable + sigMu) from pidWait. // // We _do_ need to be careful about reuse of the pidfd FD number when // closing the pidfd. See handle for more details. handle, status := p.handleTransientAcquire() switch status { case statusDone:
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Jun 11 18:08:44 UTC 2024 - 4.2K bytes - Viewed (0) -
src/runtime/netpoll.go
// rg, wg are accessed atomically and hold g pointers. // (Using atomic.Uintptr here is similar to using guintptr elsewhere.) rg atomic.Uintptr // pdReady, pdWait, G waiting for read or pdNil wg atomic.Uintptr // pdReady, pdWait, G waiting for write or pdNil lock mutex // protects the following fields closing bool rrun bool // whether rt is running wrun bool // whether wt is running
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Wed May 15 19:57:43 UTC 2024 - 20.7K bytes - Viewed (0)