From: Yi Zhang <yi.zhang@redhat.com>
Cc: fsverity@lists.linux.dev, tytso@mit.edu
Subject: Re: [bug report] kmemleak observed after system boots up
Date: Mon, 29 Apr 2024 09:47:19 +0800 [thread overview]
Message-ID: <CAHj4cs8oYFcN6ptCdLjc3vLWRgNHiS8X06OVj_HLbX-wPoT_Mg@mail.gmail.com> (raw)
In-Reply-To: <CAHj4cs8DTSvR698UE040rs_pX1k-WVe7aR6N2OoXXuhXJPDC-w@mail.gmail.com>
Hi Eric
Seems this issue was introduced from 6.6-rc1, do you have a chance to
check it, thanks.
On Wed, Apr 3, 2024 at 10:20 AM Yi Zhang <yi.zhang@redhat.com> wrote:
>
> Hello
> I found this kmemleak after system boots up on the latest
> linux-block/for-next, please help check it and let me know if you need
> any testing/info about it, thanks.
>
> # dmesg | grep kmemleak
> [ 474.750916] kmemleak: 1 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
>
> # cat /sys/kernel/debug/kmemleak
> unreferenced object 0xffff88824046a580 (size 96):
> comm "swapper/0", pid 1, jiffies 4294727564
> hex dump (first 32 bytes):
> a0 c2 0d 9b ff ff ff ff 00 00 00 00 00 00 00 00 ................
> 01 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc e7670296):
> [<ffffffff9412657c>] __kmalloc+0x37c/0x480
> [<ffffffff944cfbf8>] __register_sysctl_table+0x58/0x450
> [<ffffffff98680079>] fsverity_init+0x29/0x50
> [<ffffffff9360371e>] do_one_initcall+0xfe/0x5a0
> [<ffffffff985b70d8>] do_initcalls+0x138/0x1d0
> [<ffffffff985b7aac>] kernel_init_freeable+0x8bc/0xbe0
> [<ffffffff95dba94b>] kernel_init+0x1b/0x1e0
> [<ffffffff936a804d>] ret_from_fork+0x2d/0x70
> [<ffffffff93606e4a>] ret_from_fork_asm+0x1a/0x30
>
> (gdb) l *(fsverity_init+0x29)
> 0xffffffff86080079 is in fsverity_init (fs/verity/init.c:33).
> 28
> 29 static void __init fsverity_init_sysctl(void)
> 30 {
> 31 fsverity_sysctl_header = register_sysctl("fs/verity",
> 32 fsverity_sysctl_table);
> 33 if (!fsverity_sysctl_header)
> 34 panic("fsverity sysctl registration failed");
> 35 }
> 36 #else /* CONFIG_SYSCTL */
> 37 static inline void fsverity_init_sysctl(void)
>
>
> --
> Best Regards,
> Yi Zhang
--
Best Regards,
Yi Zhang
next prev parent reply other threads:[~2024-04-29 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 2:20 [bug report] kmemleak observed after system boots up Yi Zhang
2024-04-29 1:47 ` Yi Zhang [this message]
2024-05-01 2:53 ` [PATCH] fsverity: use register_sysctl_init() to avoid kmemleak warning Eric Biggers
2024-05-03 14:00 ` Joel Granados
2024-05-03 15:30 ` Eric Biggers
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=CAHj4cs8oYFcN6ptCdLjc3vLWRgNHiS8X06OVj_HLbX-wPoT_Mg@mail.gmail.com \
--to=yi.zhang@redhat.com \
--cc=fsverity@lists.linux.dev \
--cc=tytso@mit.edu \
/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.