ext_proc fuzzer test trigger ENVOY_BUG when clear route cache #27657
ext_proc fuzzer test trigger ENVOY_BUG when clear route cache #27657yanavlasov merged 9 commits intoenvoyproxy:mainfrom
Conversation
…tream response Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
/assign @tyxia As codeowner /wait For CI |
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
…roc_clear_route_cache Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
/assign @yanavlasov @htuch @mpwarres @stevenzzzz |
|
This is the OSS fuzzer report: Here is the crash trace back decode: Command: /mnt/scratch0/clusterfuzz/bot/builds/clusterfuzz-g3-builds_third_party-envoy-src-test-extensions-filters-http-ext_proc_libfuzzer_memory_ext_proc_grpc_fuzz_test_77651789446b3c3a04b9f492ff141f003d437347/revisions/ext_proc_grpc_fuzz_test -runs=100 /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/input.test | Time ran: 57.5866904258728 Command: /mnt/scratch0/clusterfuzz/bot/builds/clusterfuzz-g3-builds_third_party-envoy-src-test-extensions-filters-http-ext_proc_libfuzzer_memory_ext_proc_grpc_fuzz_test_77651789446b3c3a04b9f492ff141f003d437347/revisions/ext_proc_grpc_fuzz_test -runs=100 /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/input.test |
|
This is the fuzzer test case: ext_proc_data: "scterpc_cre:csp_yilooo0\n\000*!pV1:ae!FoFFF,F\n" |
Nope, the refresh in response phase still may changes the roue and effects the per filter config/metadata... etc that filters may need to use. Apparently it's wrong, so, we should never do this refresh in the response phase. |
Yes, per filter config can be used in response path. What I meant about "no-op" is that before your PR #26045, such behavior will not trigger the Envoy_Bug. Thanks for sharing more context! |
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
@envoyproxy/api-shepherds PTAL |
… it completely anyway Signed-off-by: Yanjun Xiang <yanjunxiang@google.com>
|
Kind ping! |
|
LGTM |
|
Kind ping! |
…roxy#27657) * ext_proc fuzzer test trigger ENVOY_BUG when clear route cache for upstream response Signed-off-by: Yanjun Xiang <yanjunxiang@google.com> Signed-off-by: asheryer <asheryer@amazon.com>
…roxy#27657) * ext_proc fuzzer test trigger ENVOY_BUG when clear route cache for upstream response Signed-off-by: Yanjun Xiang <yanjunxiang@google.com> Signed-off-by: Ryan Eskin <ryan.eskin89@protonmail.com>
This PR is to address an ENVOY_BUG crash exposed by ext_proc fuzzer test reported by:
https://clusterfuzz.corp.google.com/testcase-detail/4756668218736640
The steps to trigger this ENVOY_BUG is below:
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]