From: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
To: linux-kernel@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: BUG: Regression: A Problem with /sys/kernel/debug/kmemleak output: backtrace not printed since 6.2.0-rc1
Date: Wed, 4 Jan 2023 17:08:59 +0100 [thread overview]
Message-ID: <5272a819-ef74-65ff-be61-4d2d567337de@alu.unizg.hr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Hi all,
I hate to bring bad news again, but 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 appeared on Lenovo desktop 10TX000VCR, with AlmaLinux 8.7 and BIOS
version M22KT49A (11/10/2022)
and 6.2-rc1 and 6.2-rc2 builds.
This worked on 6.1 with the same CONFIG_KMEMLEAK=y and MGLRU enabled on
a vanilla mainstream kernel
from Mr. Torvalds' tree. I don't know if this is deliberate feature for
some reason or a bug.
Please find attached the config, lshw and kmemleak output.
Kind regards,
Mirsad
--
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
--
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
[-- Attachment #2: lshw.txt.xz --]
[-- Type: application/x-xz, Size: 4648 bytes --]
[-- Attachment #3: dmesg.log.xz --]
[-- Type: application/x-xz, Size: 17860 bytes --]
[-- Attachment #4: config-6.2.0-rc1-mglru-kmemlk-nokasan+.xz --]
[-- Type: application/x-xz, Size: 57112 bytes --]
[-- Attachment #5: 6.2.0-rc1-kmemleak-nobacktrace.log.xz --]
[-- Type: application/x-xz, Size: 264 bytes --]
next reply other threads:[~2023-01-04 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 16:08 Mirsad Goran Todorovac [this message]
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)
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=5272a819-ef74-65ff-be61-4d2d567337de@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox