linux-kernel - Re: [PATCH] trace : use kvmalloc instead of kmalloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200730100126.410b3fb1@oasis.local.home>
Date:   Thu, 30 Jul 2020 10:01:26 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Zhaoyang Huang <huangzhaoyang@...il.com>
Cc:     Ingo Molnar <mingo@...hat.com>, chunyan.zhang@...soc.com,
        Zhaoyang Huang <zhaoyang.huang@...soc.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] trace : use kvmalloc instead of kmalloc


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 <huangzhaoyang@...il.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. 
>