From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Allison Henderson <allison.henderson@oracle.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/4] xfs: don't leak da state when freeing the attr intent item
Date: Fri, 20 May 2022 13:38:29 +1000 [thread overview]
Message-ID: <20220520033829.GC1098723@dread.disaster.area> (raw)
In-Reply-To: <165290008177.1646028.17009669440155484683.stgit@magnolia>
On Wed, May 18, 2022 at 11:54:41AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> kmemleak reported that we lost an xfs_da_state while removing xattrs in
> generic/020:
>
> unreferenced object 0xffff88801c0e4b40 (size 480):
> comm "attr", pid 30515, jiffies 4294931061 (age 5.960s)
> hex dump (first 32 bytes):
> 78 bc 65 07 00 c9 ff ff 00 30 60 1c 80 88 ff ff x.e......0`.....
> 02 00 00 00 00 00 00 00 80 18 83 4e 80 88 ff ff ...........N....
> backtrace:
> [<ffffffffa023ef4a>] xfs_da_state_alloc+0x1a/0x30 [xfs]
> [<ffffffffa021b6f3>] xfs_attr_node_hasname+0x23/0x90 [xfs]
> [<ffffffffa021c6f1>] xfs_attr_set_iter+0x441/0xa30 [xfs]
> [<ffffffffa02b5104>] xfs_xattri_finish_update+0x44/0x80 [xfs]
> [<ffffffffa02b515e>] xfs_attr_finish_item+0x1e/0x40 [xfs]
> [<ffffffffa0244744>] xfs_defer_finish_noroll+0x184/0x740 [xfs]
> [<ffffffffa02a6473>] __xfs_trans_commit+0x153/0x3e0 [xfs]
> [<ffffffffa021d149>] xfs_attr_set+0x469/0x7e0 [xfs]
> [<ffffffffa02a78d9>] xfs_xattr_set+0x89/0xd0 [xfs]
> [<ffffffff812e6512>] __vfs_removexattr+0x52/0x70
> [<ffffffff812e6a08>] __vfs_removexattr_locked+0xb8/0x150
> [<ffffffff812e6af6>] vfs_removexattr+0x56/0x100
> [<ffffffff812e6bf8>] removexattr+0x58/0x90
> [<ffffffff812e6cce>] path_removexattr+0x9e/0xc0
> [<ffffffff812e6d44>] __x64_sys_lremovexattr+0x14/0x20
> [<ffffffff81786b35>] do_syscall_64+0x35/0x80
>
> I think this is a consequence of xfs_attr_node_removename_setup
> attaching a new da(btree) state to xfs_attr_item and never freeing it.
> I /think/ it's the case that the remove paths could detach the da state
> earlier in the remove state machine since nothing else accesses the
> state. However, let's future-proof the new xattr code by adding a
> catch-all when we free the xfs_attr_item to make sure we never leak the
> da state.
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
> ---
> fs/xfs/libxfs/xfs_attr.c | 22 ++++++++++++++--------
> fs/xfs/xfs_attr_item.c | 15 ++++++++++++---
> 2 files changed, 26 insertions(+), 11 deletions(-)
Looks ok.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-05-20 3:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 18:54 [PATCHSET v2 0/4] xfs: fix leaks and validation errors in logged xattr updates Darrick J. Wong
2022-05-18 18:54 ` [PATCH 1/4] xfs: don't leak da state when freeing the attr intent item Darrick J. Wong
2022-05-20 3:38 ` Dave Chinner [this message]
2022-05-18 18:54 ` [PATCH 2/4] xfs: don't leak the retained da state when doing a leaf to node conversion Darrick J. Wong
2022-05-19 1:38 ` Dave Chinner
2022-05-18 18:54 ` [PATCH 3/4] xfs: reject unknown xattri log item operation flags during recovery Darrick J. Wong
2022-05-19 1:37 ` Dave Chinner
2022-05-18 18:54 ` [PATCH 4/4] xfs: reject unknown xattri log item filter " Darrick J. Wong
2022-05-19 1:37 ` Dave Chinner
2022-05-19 20:34 ` Alli
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 3:31 [PATCHSET 0/4] xfs: fix leaks and validation errors in logged xattr updates Darrick J. Wong
2022-05-16 3:31 ` [PATCH 1/4] xfs: don't leak da state when freeing the attr intent item Darrick J. Wong
2022-05-16 23:55 ` Alli
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=20220520033829.GC1098723@dread.disaster.area \
--to=david@fromorbit.com \
--cc=allison.henderson@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox