linux-kernel - Re: [PATCH] slub: Trace free objects at KERN

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.10.1701171749090.119060@chino.kir.corp.google.com>
Date:   Tue, 17 Jan 2017 17:49:20 -0800 (PST)
From:   David Rientjes <rientjes@...gle.com>
To:     Daniel Thompson <daniel.thompson@...aro.org>
cc:     Christoph Lameter <cl@...ux.com>,
        Pekka Enberg <penberg@...nel.org>,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, patches@...aro.org
Subject: Re: [PATCH] slub: Trace free objects at KERN_INFO

On Fri, 13 Jan 2017, Daniel Thompson wrote:

> Currently when trace is enabled (e.g. slub_debug=T,kmalloc-128 ) the
> trace messages are mostly output at KERN_INFO. However the trace code
> also calls print_section() to hexdump the head of a free object. This
> is hard coded to use KERN_ERR, meaning the console is deluged with
> trace messages even if we've asked for quiet.
> 
> Fix this the obvious way but adding a level parameter to
> print_section(), allowing calls from the trace code to use the same
> trace level as other trace messages.
> 
> Signed-off-by: Daniel Thompson <daniel.thompson@...aro.org>

Acked-by: David Rientjes <rientjes@...gle.com>