commit | 96871e30265015938e68c7118b065baaa5732e1b | [log] [tgz] |
---|---|---|
author | David Pursell <dpursell@google.com> | Wed May 22 20:34:44 2019 +0000 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed May 22 20:34:44 2019 +0000 |
tree | f21f5dca1224c0f4f96d98dea912da53db6be802 | |
parent | c37d037faa62a19acddee9f88a8c768999cb378a [diff] |
[kernel][exceptions] fix thread kill/exception race Previously, if a caller killed a thread then immediately resumed from exception (e.g. via closing the exception port), there was a chance that the resume status would take precedence and we would keep processing the exception on a killed thread. This CL adds an additional check so that if the thread is both resumed and killed, the kill will always take precedence. This is difficult to test in an automated unittest so these new tests just run for 1 second and it'll show up as flake in the bots if the bug returns. To test manually, insert a sleep in the kernel between sending the exception and waiting for the response to lengthen the race window. ZX-4105 Test: runtests Test: while runtests -t exception-test; do :; done Change-Id: I3894f0141e7dbcc84242aee1583a031028212f71
Pink + Purple == Fuchsia (a new operating system)
Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.
Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.
See Getting Started.
See the documentation.