Skip to content

Update blocking syscall handlers to handle being interrupted by a signal #1889

@sporksmith

Description

@sporksmith

A good starting point is probably auditing usage of _syscallhandler_wasBlocked - some handlers assume that if they're running again after being blocked, then it must be the case that either the original blocking condition is somehow satisfied or a timeout expired. This is no longer true.

Metadata

Metadata

Assignees

Labels

Type: BugError or flaw producing unexpected results

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions