* memory leaks reported during xfstests
@ 2019-06-21 21:58 Chuck Lever
2019-06-23 7:32 ` Ido Schimmel
0 siblings, 1 reply; 3+ messages in thread
From: Chuck Lever @ 2019-06-21 21:58 UTC (permalink / raw)
To: Linux NFS Mailing List
For unrelated reasons I've enabled kmemleak in my client's kernel.
While running xfstests, I get these reports on several of the tests.
I've seen them on a few recent kernels as well.
They do not look related to NFS. Anyone know where I should report
this?
[cel@manet ~]$ cat src/xfstests/results/generic/013.kmemleak
EXPERIMENTAL kmemleak reported some memory leaks! Due to the way kmemleak
works, the leak might be from an earlier test, or something totally unrelated.
unreferenced object 0xffff88886963c4c0 (size 168):
comm "mount", pid 3471, jiffies 4296003082 (age 161.789s)
hex dump (first 32 bytes):
03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000fd30522a>] kmem_cache_alloc+0xc4/0x1cb
[<0000000008f8eac6>] prepare_creds+0x21/0xc7
[<000000006e9e3064>] prepare_exec_creds+0xb/0x3a
[<000000001b408d7e>] __do_execve_file.isra.31+0x103/0x818
[<000000004096f0a3>] do_execve+0x25/0x29
[<0000000008a9aa1c>] __x64_sys_execve+0x26/0x2b
[<00000000599d3d33>] do_syscall_64+0x5a/0x68
[<00000000005d29f3>] entry_SYSCALL_64_after_hwframe+0x49/0xbe
unreferenced object 0xffff888867a4f708 (size 32):
comm "mount", pid 3471, jiffies 4296003082 (age 161.789s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<000000004c53b46c>] __kmalloc+0xfc/0x14a
[<000000002ff13bd8>] lsm_cred_alloc.isra.5+0x24/0x32
[<000000009eb979ec>] security_prepare_creds+0x21/0x61
[<0000000086789f15>] prepare_creds+0xb3/0xc7
[<000000006e9e3064>] prepare_exec_creds+0xb/0x3a
[<000000001b408d7e>] __do_execve_file.isra.31+0x103/0x818
[<000000004096f0a3>] do_execve+0x25/0x29
[<0000000008a9aa1c>] __x64_sys_execve+0x26/0x2b
[<00000000599d3d33>] do_syscall_64+0x5a/0x68
[<00000000005d29f3>] entry_SYSCALL_64_after_hwframe+0x49/0xbe
[cel@manet ~]$
--
Chuck Lever
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: memory leaks reported during xfstests
2019-06-21 21:58 memory leaks reported during xfstests Chuck Lever
@ 2019-06-23 7:32 ` Ido Schimmel
2019-06-24 15:50 ` Chuck Lever
0 siblings, 1 reply; 3+ messages in thread
From: Ido Schimmel @ 2019-06-23 7:32 UTC (permalink / raw)
To: Chuck Lever; +Cc: Linux NFS Mailing List
On Fri, Jun 21, 2019 at 05:58:48PM -0400, Chuck Lever wrote:
> For unrelated reasons I've enabled kmemleak in my client's kernel.
> While running xfstests, I get these reports on several of the tests.
> I've seen them on a few recent kernels as well.
>
> They do not look related to NFS. Anyone know where I should report
> this?
Most likely fixed by:
https://patchwork.kernel.org/patch/11006849/
See this report:
https://lore.kernel.org/linux-nfs/20190614185237.GA550@splinter/#t
>
>
> [cel@manet ~]$ cat src/xfstests/results/generic/013.kmemleak
> EXPERIMENTAL kmemleak reported some memory leaks! Due to the way kmemleak
> works, the leak might be from an earlier test, or something totally unrelated.
> unreferenced object 0xffff88886963c4c0 (size 168):
> comm "mount", pid 3471, jiffies 4296003082 (age 161.789s)
> hex dump (first 32 bytes):
> 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<00000000fd30522a>] kmem_cache_alloc+0xc4/0x1cb
> [<0000000008f8eac6>] prepare_creds+0x21/0xc7
> [<000000006e9e3064>] prepare_exec_creds+0xb/0x3a
> [<000000001b408d7e>] __do_execve_file.isra.31+0x103/0x818
> [<000000004096f0a3>] do_execve+0x25/0x29
> [<0000000008a9aa1c>] __x64_sys_execve+0x26/0x2b
> [<00000000599d3d33>] do_syscall_64+0x5a/0x68
> [<00000000005d29f3>] entry_SYSCALL_64_after_hwframe+0x49/0xbe
> unreferenced object 0xffff888867a4f708 (size 32):
> comm "mount", pid 3471, jiffies 4296003082 (age 161.789s)
> hex dump (first 32 bytes):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace:
> [<000000004c53b46c>] __kmalloc+0xfc/0x14a
> [<000000002ff13bd8>] lsm_cred_alloc.isra.5+0x24/0x32
> [<000000009eb979ec>] security_prepare_creds+0x21/0x61
> [<0000000086789f15>] prepare_creds+0xb3/0xc7
> [<000000006e9e3064>] prepare_exec_creds+0xb/0x3a
> [<000000001b408d7e>] __do_execve_file.isra.31+0x103/0x818
> [<000000004096f0a3>] do_execve+0x25/0x29
> [<0000000008a9aa1c>] __x64_sys_execve+0x26/0x2b
> [<00000000599d3d33>] do_syscall_64+0x5a/0x68
> [<00000000005d29f3>] entry_SYSCALL_64_after_hwframe+0x49/0xbe
> [cel@manet ~]$
>
> --
> Chuck Lever
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: memory leaks reported during xfstests
2019-06-23 7:32 ` Ido Schimmel
@ 2019-06-24 15:50 ` Chuck Lever
0 siblings, 0 replies; 3+ messages in thread
From: Chuck Lever @ 2019-06-24 15:50 UTC (permalink / raw)
To: Ido Schimmel; +Cc: Linux NFS Mailing List
> On Jun 23, 2019, at 3:32 AM, Ido Schimmel <idosch@idosch.org> wrote:
>
> On Fri, Jun 21, 2019 at 05:58:48PM -0400, Chuck Lever wrote:
>> For unrelated reasons I've enabled kmemleak in my client's kernel.
>> While running xfstests, I get these reports on several of the tests.
>> I've seen them on a few recent kernels as well.
>>
>> They do not look related to NFS. Anyone know where I should report
>> this?
>
> Most likely fixed by:
> https://patchwork.kernel.org/patch/11006849/
>
> See this report:
> https://lore.kernel.org/linux-nfs/20190614185237.GA550@splinter/#t
Confirmed that this patch (now in v5.2-rc6) addresses the prepare_creds leak.
Thanks, Ido.
>> [cel@manet ~]$ cat src/xfstests/results/generic/013.kmemleak
>> EXPERIMENTAL kmemleak reported some memory leaks! Due to the way kmemleak
>> works, the leak might be from an earlier test, or something totally unrelated.
>> unreferenced object 0xffff88886963c4c0 (size 168):
>> comm "mount", pid 3471, jiffies 4296003082 (age 161.789s)
>> hex dump (first 32 bytes):
>> 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> backtrace:
>> [<00000000fd30522a>] kmem_cache_alloc+0xc4/0x1cb
>> [<0000000008f8eac6>] prepare_creds+0x21/0xc7
>> [<000000006e9e3064>] prepare_exec_creds+0xb/0x3a
>> [<000000001b408d7e>] __do_execve_file.isra.31+0x103/0x818
>> [<000000004096f0a3>] do_execve+0x25/0x29
>> [<0000000008a9aa1c>] __x64_sys_execve+0x26/0x2b
>> [<00000000599d3d33>] do_syscall_64+0x5a/0x68
>> [<00000000005d29f3>] entry_SYSCALL_64_after_hwframe+0x49/0xbe
>> unreferenced object 0xffff888867a4f708 (size 32):
>> comm "mount", pid 3471, jiffies 4296003082 (age 161.789s)
>> hex dump (first 32 bytes):
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>> backtrace:
>> [<000000004c53b46c>] __kmalloc+0xfc/0x14a
>> [<000000002ff13bd8>] lsm_cred_alloc.isra.5+0x24/0x32
>> [<000000009eb979ec>] security_prepare_creds+0x21/0x61
>> [<0000000086789f15>] prepare_creds+0xb3/0xc7
>> [<000000006e9e3064>] prepare_exec_creds+0xb/0x3a
>> [<000000001b408d7e>] __do_execve_file.isra.31+0x103/0x818
>> [<000000004096f0a3>] do_execve+0x25/0x29
>> [<0000000008a9aa1c>] __x64_sys_execve+0x26/0x2b
>> [<00000000599d3d33>] do_syscall_64+0x5a/0x68
>> [<00000000005d29f3>] entry_SYSCALL_64_after_hwframe+0x49/0xbe
>> [cel@manet ~]$
>>
>> --
>> Chuck Lever
>>
>>
>>
--
Chuck Lever
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-06-24 15:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-21 21:58 memory leaks reported during xfstests Chuck Lever
2019-06-23 7:32 ` Ido Schimmel
2019-06-24 15:50 ` Chuck Lever
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.