From: "Linux kernel regression tracking (#adding)" <regressions@leemhuis.info>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>,
linux-kernel@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Zhaoyang Huang <zhaoyang.huang@unisoc.com>
Subject: Re: INFO: [BISECTED] Regression: A Problem with /sys/kernel/debug/kmemleak output: backtrace not printed since 6.2.0-rc1
Date: Sun, 29 Jan 2023 16:06:00 +0100 [thread overview]
Message-ID: <633ee51b-7f81-c38a-7543-34df69480f1d@leemhuis.info> (raw)
In-Reply-To: <53c2d558-c6a1-38e5-5739-28fff023558d@alu.unizg.hr>
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 12.01.23 20:50, Mirsad Todorovac wrote:
> Hi all,
>
> there seems to be a problem with the output of /sys/kernel/debug/kmemleak:
>
> [root@pc-mtodorov ~]# cat /sys/kernel/debug/kmemleak
> unreferenced object 0xffff951c118568b0 (size 16):
> comm "kworker/u12:2", pid 56, jiffies 4294893952 (age 4356.548s)
> hex dump (first 16 bytes):
> 6d 65 6d 73 74 69 63 6b 30 00 00 00 00 00 00 00 memstick0.......
> backtrace:
> [root@pc-mtodorov ~]#
>
> Apparently, backtrace of called functions on the stack is no longer
> printed with the list of memory leaks.
> [...]
This is already close to being fixed, but I want to have it in this week
report, hence I'm adding it (better late than never):
#regzbot ^introduced 56a61617dd22
#regzbot title mm: stack_depot: Failure during Stack Depot allocating
hash table
#regzbot monitor: https://lore.kernel.org/all/Y8Fq5m0CLfcFLCOY@zn.tnic/
#regzbot fix: mm: use stack_depot_early_init for kmemleak
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-01-29 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 16:08 BUG: Regression: A Problem with /sys/kernel/debug/kmemleak output: backtrace not printed since 6.2.0-rc1 Mirsad Goran Todorovac
2023-01-12 19:39 ` [BISECTED] " Mirsad Todorovac
2023-01-12 19:50 ` INFO: [BISECTED] " Mirsad Todorovac
2023-01-12 21:50 ` Mirsad Goran Todorovac
2023-01-13 1:46 ` 答复: " 黄朝阳 (Zhaoyang Huang)
2023-01-13 7:08 ` Mirsad Goran Todorovac
2023-01-13 6:20 ` 黄朝阳 (Zhaoyang Huang)
2023-01-13 8:41 ` Mirsad Goran Todorovac
2023-01-13 10:14 ` 答复: " 黄朝阳 (Zhaoyang Huang)
2023-01-13 13:40 ` Mirsad Goran Todorovac
2023-01-14 9:32 ` Mirsad Goran Todorovac
2023-01-17 2:03 ` 黄朝阳 (Zhaoyang Huang)
2023-01-17 3:14 ` Mirsad Goran Todorovac
2023-01-29 15:06 ` Linux kernel regression tracking (#adding) [this message]
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=633ee51b-7f81-c38a-7543-34df69480f1d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=regressions@lists.linux.dev \
--cc=zhaoyang.huang@unisoc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).