From: Catalin Marinas <catalin.marinas@arm.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] kmemleak: add checksum to backtrace report
Date: Sat, 18 Nov 2023 17:36:09 +0000 [thread overview]
Message-ID: <ZVj2CRI7452gm6lH@arm.com> (raw)
In-Reply-To: <20231116224318.124209-3-jim.cromie@gmail.com>
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@gmail.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2023-11-18 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 22:43 [PATCH 0/2] tweak kmemleak report format Jim Cromie
2023-11-16 22:43 ` [PATCH 1/2] kmemleak: drop (age <increasing>) from leak record Jim Cromie
2023-11-18 17:35 ` Catalin Marinas
2023-11-16 22:43 ` [PATCH 2/2] kmemleak: add checksum to backtrace report Jim Cromie
2023-11-18 17:36 ` Catalin Marinas [this message]
2023-11-26 6:44 ` jim.cromie
2023-11-16 23:22 ` [PATCH 0/2] tweak kmemleak report format jim.cromie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZVj2CRI7452gm6lH@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.