This is also the second version of the patch. Please add a v2 to the subject, otherwise it gets confusing to know which one to pull in.
"[PATCH v2] ..." -- Steve On Thu, 30 Jul 2020 19:04:12 +0800 Zhaoyang Huang <huangzhaoy...@gmail.com> wrote: > High order memory stuff within trace could introduce OOM, use kvmalloc > instead. > > Please find the bellowing for the call stack we run across in an android > system. The scenario happens when traced_probes is woken up to get a large > quantity of trace even if free memory is even higher than watermark_low. >
