* [bug report] kmemleak observed on zcrypt module after system boots up
@ 2026-01-30 8:23 Yi Zhang
2026-02-02 16:44 ` Harald Freudenberger
2026-02-04 10:18 ` Harald Freudenberger
0 siblings, 2 replies; 4+ messages in thread
From: Yi Zhang @ 2026-01-30 8:23 UTC (permalink / raw)
To: linux-s390; +Cc: freude, dengler
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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [bug report] kmemleak observed on zcrypt module after system boots up
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
1 sibling, 0 replies; 4+ messages in thread
From: Harald Freudenberger @ 2026-02-02 16:44 UTC (permalink / raw)
To: Yi Zhang; +Cc: linux-s390, dengler
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
Hello Yi Zhang
I tried to reproduce this on the linux-next kernel as of today and on
the (IBM internal current development kernel). In both cases I could
not reproduce this. You mention linux-block, did you see this on
linux-next also ?
Thanks
Harald Freudenberger
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bug report] kmemleak observed on zcrypt module after system boots up
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
2026-02-04 11:47 ` Yi Zhang
1 sibling, 1 reply; 4+ messages in thread
From: Harald Freudenberger @ 2026-02-04 10:18 UTC (permalink / raw)
To: Yi Zhang; +Cc: linux-s390, dengler
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bug report] kmemleak observed on zcrypt module after system boots up
2026-02-04 10:18 ` Harald Freudenberger
@ 2026-02-04 11:47 ` Yi Zhang
0 siblings, 0 replies; 4+ messages in thread
From: Yi Zhang @ 2026-02-04 11:47 UTC (permalink / raw)
To: freude; +Cc: linux-s390, dengler
On Wed, Feb 4, 2026 at 6:18 PM Harald Freudenberger
<freude@linux.ibm.com> wrote:
>
> 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?
Hi
Sorry for the late response, the original environment was destroyed.
And the kernel I used was not linux-block/for-next, it's
6.19.0-0.rc7.47.eln154.s390x+debug and can be downloaded here[1].
I also tried to reinstall the server with
6.19.0-0.rc7.47.eln154.s390x+debug, but with no luck in reproducing it
now.
[1]
https://kojipkgs.fedoraproject.org//packages/kernel/6.19.0/0.rc7.47.eln154/s390x/
[root@ibm-z-516 ~]# uname -r
6.19.0-0.rc7.47.eln154.s390x+debug
[root@ibm-z-516 ~]# lszcrypt -V
CARD.DOM TYPE MODE STATUS REQUESTS PENDING HWTYPE QDEPTH
FUNCTIONS DRIVER
--------------------------------------------------------------------------------------------
01 CEX7C CCA-Coproc online 0 0 13 09
---D--N--R cex4card
01.0001 CEX7C CCA-Coproc online 0 0 13 09
---D--N--R cex4queue
[root@ibm-z-516 ~]# cat /proc/cpuinfo
vendor_id : IBM/S390
> 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.
>
--
Best Regards,
Yi Zhang
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-02-04 11:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-02-04 11:47 ` Yi Zhang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox