From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Filesystem Development <linux-fsdevel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
vladbu@nvidia.com
Subject: Fwd: Memleaks in offset_ctx->xa (shmem)
Date: Tue, 24 Oct 2023 14:55:27 +0700 [thread overview]
Message-ID: <429b452c-2211-436a-9af7-21332f68db7d@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> 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
>
> Memleak trace points to some syscall performed by systemd and none of our tests do anything more advanced with it than 'systemctl restart ovs-vswitchd'. Basically it is a setup with Fedora and an upstream kernel that executes bunch of network offload tests with Open vSwitch, iproute2 tc, Linux bridge, etc.
>
> 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.
See Bugzilla for the full thread.
Anyway, I'm adding it to regzbot:
#regzbot introduced: 6faddda69f623d https://bugzilla.kernel.org/show_bug.cgi?id=218039
#regzbot title: stable offsets directory operation support triggers offset_ctx->xa memory leak
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218039
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-10-24 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 7:55 Bagas Sanjaya [this message]
2023-10-24 14:18 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-25 0:01 ` Bagas Sanjaya
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=429b452c-2211-436a-9af7-21332f68db7d@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=vladbu@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox