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: <CAJfuBxyjMgxR3+oAuLUK7nrM36S9MEQ67ppQTM_ibOdS4QNysQ@mail.gmail.com>
Date:   Thu, 16 Nov 2023 16:22:04 -0700
From:   jim.cromie@...il.com
To:     linux-kernel@...r.kernel.org
Cc:     catalin.marinas@....com, akpm@...ux-foundation.org
Subject: Re: [PATCH 0/2] tweak kmemleak report format

On Thu, Nov 16, 2023 at 3:43 PM Jim Cromie <jim.cromie@...il.com> wrote:
>
> These 2 patches make minor changes to the report:
>
> 1st strips "age <increasing>" from output.  This makes the output
> idempotent; unchanging until a new leak is reported.
>
> 2nd adds the backtrace.checksum to the "backtrace:" line.  This lets a
> user see repeats without actually reading the whole backtrace.  So now
> the backtrace line looks like this:
>
>   backtrace (ck 603070071):

meh, in the actual patch, thats

backtrace (crc <%x format>)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ