public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Long Li <leo.lilong@huawei.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: <cem@kernel.org>, <linux-xfs@vger.kernel.org>,
	<david@fromorbit.com>, <yi.zhang@huawei.com>,
	<houtao1@huawei.com>, <yangerkun@huawei.com>,
	<lonuxli.64@gmail.com>
Subject: Re: [PATCH 2/4] xfs: factor out xfs_da3_node_entry_remove
Date: Tue, 10 Mar 2026 19:58:23 +0800	[thread overview]
Message-ID: <abAHX977xcOEaqRM@localhost.localdomain> (raw)
In-Reply-To: <20260309164229.GI6033@frogsfrogsfrogs>

On Mon, Mar 09, 2026 at 09:42:29AM -0700, Darrick J. Wong wrote:
> 
> > +	__xfs_da3_node_remove(state->args->trans, state->args->dp,
> > +			state->args->geo, drop_blk);
> > +}
> > +
> > +/*
> > + * Remove an entry from a node at the specified index, this is an exported
> > + * wrapper for removing entries from intermediate nodes.
> > + */
> > +void
> > +xfs_da3_node_entry_remove(
> 
> This only applies to attr(ibute) structures, as evidenced by m_attr_geo
> below.  I think this ought to be named xfs_attr3_node_entry_remove.
> 

Considering that xfs_da_btree.c implements functions related to xfs_da*, 
it might not be appropriate to place xfs_attr3_node_entry_remove here either.
I think we could add an additional `struct xfs_da_geometry *geo` parameter
to xfs_da3_node_entry_remove() and let it be specified externally, which
would increase the function's generality. What do you think?


Thanks,
Long Li

  parent reply	other threads:[~2026-03-10 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  8:27 [PATCH 0/4] xfs: close crash window in attr dabtree inactivation Long Li
2026-03-09  8:27 ` [PATCH 1/4] xfs: only assert new size for datafork during truncate extents Long Li
2026-03-09 16:39   ` Darrick J. Wong
2026-03-09  8:27 ` [PATCH 2/4] xfs: factor out xfs_da3_node_entry_remove Long Li
2026-03-09 16:42   ` Darrick J. Wong
2026-03-10  2:15     ` Long Li
2026-03-10 11:58     ` Long Li [this message]
2026-03-10 14:38       ` Darrick J. Wong
2026-03-09  8:27 ` [PATCH 3/4] xfs: factor out xfs_attr3_leaf_init Long Li
2026-03-09 16:44   ` Darrick J. Wong
2026-03-10  7:42     ` Long Li
2026-03-09  8:27 ` [PATCH 4/4] xfs: close crash window in attr dabtree inactivation Long Li
2026-03-09 16:59   ` Darrick J. Wong
2026-03-10  8:19     ` Long Li
2026-03-10 14:46       ` Darrick J. Wong
2026-03-11  2:34         ` Long Li
2026-03-13 14:46           ` Darrick J. Wong

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=abAHX977xcOEaqRM@localhost.localdomain \
    --to=leo.lilong@huawei.com \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=houtao1@huawei.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lonuxli.64@gmail.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.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