linux-kernel - Re: [PATCH 2/2] kmemleak: add checksum to backtrace report

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 for Android: free password hash cracker in your pocket

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

Message-ID: <ZVj2CRI7452gm6lH@arm.com>
Date:   Sat, 18 Nov 2023 17:36:09 +0000
From:   Catalin Marinas <catalin.marinas@....com>
To:     Jim Cromie <jim.cromie@...il.com>
Cc:     linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH 2/2] kmemleak: add checksum to backtrace report

On Thu, Nov 16, 2023 at 03:43:18PM -0700, Jim Cromie wrote:
> Change /sys/kernel/debug/kmemleak report format slightly, adding
> "(extra info)" to the backtrace header:
> 
> from: "  backtrace:"
> to:   "  backtrace (crc <cksum>):"
> 
> The <cksum> allows a user to see recurring backtraces without
> detailed/careful reading of multiline stacks.  So after cycling
> kmemleak-test a few times, I know some leaks are repeating.
> 
>   bash-5.2# grep backtrace /sys/kernel/debug/kmemleak | wc
>      62     186    1792
>   bash-5.2# grep backtrace /sys/kernel/debug/kmemleak | sort -u | wc
>      37     111    1067
> 
> syzkaller parses kmemleak for "unreferenced object" only, so is
> unaffected by this change.  Other github repos are moribund.
> 
> Signed-off-by: Jim Cromie <jim.cromie@...il.com>

Reviewed-by: Catalin Marinas <catalin.marinas@....com>