[BUG] wasm 插件 memory overflow 导致agent pod 重启

[wuzongling]

Search before asking

• I had searched in the issues and found no similar feature requirement.

DeepFlow Component

Agent

What you expected to happen

in_fn: "vm_read_ctx_base" memory overflow, mem size is 3221225472 but bias to -2073970768

How to reproduce

No response

DeepFlow version

No response

DeepFlow agent list

No response

Kubernetes CNI

No response

Operation-System/Kernel version

No response

Anything else

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[sharang]

The pointer addresses passed in the wasm plugin should have a value range of uint64.

After calling the import method of the wasm plugin, deepflow-agent will check the memory boundary and perform check_memory. The memory limit in wasm is 4G (the limit for 32-bit programs). When we perform check_memory, we receive a pointer address, the original parameter type is i32, but it should actually be u32.