linux-kernel - Re: [PATCH RT] kmemleak: Change the lock of kmemleak_object to raw_spinlock

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]

Date:   Mon, 7 Oct 2019 18:15:39 +0200
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     Yongxin Liu <yongxin.liu@...driver.com>
Cc:     linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org,
        tglx@...utronix.de, rostedt@...dmis.org, haitao.liu@...driver.com,
        zhe.he@...driver.com
Subject: Re: [PATCH RT] kmemleak: Change the lock of kmemleak_object to
 raw_spinlock_t

On 2019-09-27 16:22:30 [+0800], Yongxin Liu wrote:
> From: Liu Haitao <haitao.liu@...driver.com>
> 
> The following call trace would be triggered as kmemleak is running.
> 
…

Applied.

Sebastian