From: Harald Freudenberger <freude@linux.ibm.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: linux-s390@vger.kernel.org, dengler@linux.ibm.com
Subject: Re: [bug report] kmemleak observed on zcrypt module after system boots up
Date: Wed, 04 Feb 2026 11:18:12 +0100 [thread overview]
Message-ID: <f08b53ccdfc069f4e8c49511b04171bc@linux.ibm.com> (raw)
In-Reply-To: <CAHj4cs_GH0O7-nkh=8EhwscjzesawBJ+6b0MxuWZOOsp4B7HsA@mail.gmail.com>
On 2026-01-30 09:23, Yi Zhang wrote:
> Hi
> I found this kmemleak issue after the system boots up with
> linux-block/for-next, please help check it and let me know if you need
> any test/info.
>
> # uname -r
> 6.19.0-rc7+
> # dmesg | grep kmemleak
> [ 1648.765780] kmemleak: 1 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
> [ 6148.698090] kmemleak: 2 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
> [10419.366662] kmemleak: 3 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
> [14843.424498] kmemleak: 2 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
> [20987.442195] kmemleak: 2 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
>
> # cat /sys/kernel/debug/kmemleak
> unreferenced object 0x990d0000 (size 12288):
> comm "dnf", pid 48539, jiffies 4296356469
> hex dump (first 32 bytes):
> 00 00 00 00 99 0d 36 30 00 00 bb af 00 f7 1d 60 ......60.......`
> 00 00 00 00 99 0d 00 10 00 00 00 00 99 0d 00 10 ................
> backtrace (crc 9893fb1d):
> kmemleak_alloc+0x6c/0xc0
> ___kmalloc_large_node+0x106/0x160
> __kmalloc_large_node_noprof+0x32/0x170
> __kmalloc_noprof+0x6d8/0xa00
> ap_init_apmsg+0xf6/0x190
> zcrypt_rsa_modexpo+0x15c/0x1310 [zcrypt]
> icarsamodexpo_ioctl+0x110/0x270 [zcrypt]
> zcrypt_unlocked_ioctl+0xc60/0x10e0 [zcrypt]
> __s390x_sys_ioctl+0x178/0x1e0
> __do_syscall+0x166/0x460
> system_call+0x6e/0x90
> unreferenced object 0xae148000 (size 12288):
> comm "dnf", pid 48539, jiffies 4296356470
> hex dump (first 32 bytes):
> 00 00 00 00 ae 14 b6 30 00 00 bb af 00 f7 1d 60 .......0.......`
> 00 00 00 00 ae 14 80 10 00 00 00 00 ae 14 80 10 ................
> backtrace (crc 41938ebb):
> kmemleak_alloc+0x6c/0xc0
> ___kmalloc_large_node+0x106/0x160
> __kmalloc_large_node_noprof+0x32/0x170
> __kmalloc_noprof+0x6d8/0xa00
> ap_init_apmsg+0xf6/0x190
> zcrypt_rsa_modexpo+0x15c/0x1310 [zcrypt]
> icarsamodexpo_ioctl+0x110/0x270 [zcrypt]
> zcrypt_unlocked_ioctl+0xc60/0x10e0 [zcrypt]
> __s390x_sys_ioctl+0x178/0x1e0
> __do_syscall+0x166/0x460
> system_call+0x6e/0x90
> unreferenced object 0x87dd4000 (size 12288):
> comm "dnf", pid 48633, jiffies 4296914470
> hex dump (first 32 bytes):
> 00 00 00 00 94 c7 20 00 00 00 00 00 00 fe 90 80 ...... .........
> ff ff ff ff ff ff ff ff 00 10 63 c9 1e a5 48 b8 ..........c...H.
> backtrace (crc fb3113e3):
> kmemleak_alloc+0x6c/0xc0
> ___kmalloc_large_node+0x106/0x160
> __kmalloc_large_node_noprof+0x32/0x170
> __kmalloc_noprof+0x6d8/0xa00
> ap_init_apmsg+0xf6/0x190
> zcrypt_rsa_modexpo+0x15c/0x1310 [zcrypt]
> icarsamodexpo_ioctl+0x110/0x270 [zcrypt]
> zcrypt_unlocked_ioctl+0xc60/0x10e0 [zcrypt]
> __s390x_sys_ioctl+0x178/0x1e0
> __do_syscall+0x166/0x460
> system_call+0x6e/0x90
> unreferenced object 0x8e65c000 (size 12288):
> comm "dnf", pid 48633, jiffies 4296914470
> hex dump (first 32 bytes):
> 00 00 00 00 aa 22 2e 00 00 00 00 00 00 fe 90 80 ....."..........
> ff ff ff ff ff ff ff ff 00 10 63 c9 1e a5 48 b8 ..........c...H.
> backtrace (crc 1b33772d):
> kmemleak_alloc+0x6c/0xc0
> ___kmalloc_large_node+0x106/0x160
> __kmalloc_large_node_noprof+0x32/0x170
> __kmalloc_noprof+0x6d8/0xa00
> ap_init_apmsg+0xf6/0x190
> zcrypt_rsa_modexpo+0x15c/0x1310 [zcrypt]
> icarsamodexpo_ioctl+0x110/0x270 [zcrypt]
> zcrypt_unlocked_ioctl+0xc60/0x10e0 [zcrypt]
> __s390x_sys_ioctl+0x178/0x1e0
> __do_syscall+0x166/0x460
> system_call+0x6e/0x90--
>
>
>
> Best Regards,
> Yi Zhang
I pulled exactly the repo you mentioned with the "for-linux" branch. But
again
there is no kmemleak reported regardless on how I play around with that.
Can you please describe the environment you ran for this issue in more
detail?
I assume you ran a "real" s390 LPAR or zVM and there must have been some
kind of crypto card in your system. Could you please give me the output
of
"lszcrypt -V" for that system?
Thanks
Harald Freudenberger
to send a request down to the kernel.
next prev parent reply other threads:[~2026-02-04 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 8:23 [bug report] kmemleak observed on zcrypt module after system boots up Yi Zhang
2026-02-02 16:44 ` Harald Freudenberger
2026-02-04 10:18 ` Harald Freudenberger [this message]
2026-02-04 11:47 ` Yi Zhang
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=f08b53ccdfc069f4e8c49511b04171bc@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=yi.zhang@redhat.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 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.