envoyproxy / envoyproxy/envoy

wasm: access log extension point is not thread safe

Open
#41,672 3 comments 0 reactions 0 assignees View on GitHub
area/wasm bug help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 22h
Merged PRs (30d)
430

Description

Access logger instances are shared across all threads, which means `log()` can be called concurrently. It does not seem that Wasm implementation has proper protection against data races (Wasm runtime assumes single threaded caller I believe).

CC @PiotrSikora @mpwarres

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.