Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • ci-bump-test
  • abp-queue
  • new-delete-leaks
  • fused-continuation-and-completion-stealing
  • emper-fix-invalid-conv
  • remote-put-get-free-context-cycle
  • linux-version-construct-on-first-use
  • libstdc++-asserts
  • msan
  • libc++
  • completer-strategies
  • cactus_stack_devel_one_commit
  • client-load-change
  • cppcheck
  • flow
  • cast-if-future
  • async_network2
  • thread_safe_log_config
  • burak
  • attic/clang-release-tls-optimization-debug-and-fix
  • attic/continuation-stealing-dev
22 results
Compare
Forked from Lehrstuhl für Informatik 4 (Systemsoftware) / manycore / emper
Source project has a limited visibility.
user avatar
[IoContext] do not use Future after allowing its destruction
Florian Fischer authored 
When using the SINGLE_URING configuration the Future semaphore is used
to ensure that a forgotten Future is dropped after it is prepared and
not needed anymore.

Using the future after signaling its semaphore and thus allowing its
concurrent destruction is obviously broken.

Signal the semaphore after all preparation work is done.

Fixes: 9c0f2143
22f2d6a6
History
user avatar 22f2d6a6
History
Name Last commit Last update