From: Vlad Buslov <vladbu@nvidia.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: <linux-fsdevel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
Gal Pressman <gal@nvidia.com>
Subject: memleak in libfs report
Date: Wed, 11 Oct 2023 18:15:58 +0300 [thread overview]
Message-ID: <87y1g9xjre.fsf@nvidia.com> (raw)
Hello Chuck,
We have been getting memleaks in offset_ctx->xa in our networking tests:
unreferenced object 0xffff8881004cd080 (size 576):
comm "systemd", pid 1, jiffies 4294893373 (age 1992.864s)
hex dump (first 32 bytes):
00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
38 5c 7c 02 81 88 ff ff 98 d0 4c 00 81 88 ff ff 8\|.......L.....
backtrace:
[<000000000f554608>] xas_alloc+0x306/0x430
[<0000000075537d52>] xas_create+0x4b4/0xc80
[<00000000a927aab2>] xas_store+0x73/0x1680
[<0000000020a61203>] __xa_alloc+0x1d8/0x2d0
[<00000000ae300af2>] __xa_alloc_cyclic+0xf1/0x310
[<000000001032332c>] simple_offset_add+0xd8/0x170
[<0000000073229fad>] shmem_mknod+0xbf/0x180
[<00000000242520ce>] vfs_mknod+0x3b0/0x5c0
[<000000001ef218dd>] unix_bind+0x2c2/0xdb0
[<0000000009b9a8dd>] __sys_bind+0x127/0x1e0
[<000000003c949fbb>] __x64_sys_bind+0x6e/0xb0
[<00000000b8a767c7>] do_syscall_64+0x3d/0x90
[<000000006132ae0d>] entry_SYSCALL_64_after_hwframe+0x46/0xb0
It looks like those may be caused by recent commit 6faddda69f62 ("libfs:
Add directory operations for stable offsets") but we don't have a proper
reproduction, just sometimes arbitrary getting the memleak complains
during/after the regression run.
Regards,
Vlad
next reply other threads:[~2023-10-11 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 15:15 Vlad Buslov [this message]
2023-10-11 15:34 ` memleak in libfs report Chuck Lever III
2023-10-11 15:52 ` Vlad Buslov
2023-10-11 16:06 ` Chuck Lever III
2023-10-22 23:28 ` Chuck Lever III
2023-10-23 7:07 ` Vlad Buslov
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=87y1g9xjre.fsf@nvidia.com \
--to=vladbu@nvidia.com \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=gal@nvidia.com \
--cc=linux-fsdevel@vger.kernel.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 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.