From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] xfs: use kfree_rcu_mightsleep to free the perag structures
Date: Wed, 21 Aug 2024 09:19:39 -0700 [thread overview]
Message-ID: <20240821161939.GC865349@frogsfrogsfrogs> (raw)
In-Reply-To: <20240821063901.650776-2-hch@lst.de>
On Wed, Aug 21, 2024 at 08:38:28AM +0200, Christoph Hellwig wrote:
> Using the kfree_rcu_mightsleep is simpler and removes the need for a
> rcu_head in the perag structure.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/xfs/libxfs/xfs_ag.c | 12 +-----------
> fs/xfs/libxfs/xfs_ag.h | 3 ---
> 2 files changed, 1 insertion(+), 14 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_ag.c b/fs/xfs/libxfs/xfs_ag.c
> index 7e80732cb54708..4b5a39a83f7aed 100644
> --- a/fs/xfs/libxfs/xfs_ag.c
> +++ b/fs/xfs/libxfs/xfs_ag.c
> @@ -235,16 +235,6 @@ xfs_initialize_perag_data(
> return error;
> }
>
> -STATIC void
> -__xfs_free_perag(
> - struct rcu_head *head)
> -{
> - struct xfs_perag *pag = container_of(head, struct xfs_perag, rcu_head);
> -
> - ASSERT(!delayed_work_pending(&pag->pag_blockgc_work));
> - kfree(pag);
> -}
> -
> /*
> * Free up the per-ag resources associated with the mount structure.
> */
> @@ -270,7 +260,7 @@ xfs_free_perag(
> xfs_perag_rele(pag);
> XFS_IS_CORRUPT(pag->pag_mount,
> atomic_read(&pag->pag_active_ref) != 0);
> - call_rcu(&pag->rcu_head, __xfs_free_perag);
> + kfree_rcu_mightsleep(pag);
I started wondering, have you seen any complaints from might_sleep when
freeing pags after a failed growfs? Then I wondered if growfs_data
could actually take any locks that would prevent sleeping, which led me
to another question: why do growfs_{data,log} hold m_growlock but
growfs_rt doesn't? Is that actually safe?
I think the kfree_rcu_mightsleep conversion is ok, but I want to see if
anything blows up with the rtgroups variant.
--D
> }
> }
>
> diff --git a/fs/xfs/libxfs/xfs_ag.h b/fs/xfs/libxfs/xfs_ag.h
> index 35de09a2516c70..d62c266c0b44d5 100644
> --- a/fs/xfs/libxfs/xfs_ag.h
> +++ b/fs/xfs/libxfs/xfs_ag.h
> @@ -63,9 +63,6 @@ struct xfs_perag {
> /* Blocks reserved for the reverse mapping btree. */
> struct xfs_ag_resv pag_rmapbt_resv;
>
> - /* for rcu-safe freeing */
> - struct rcu_head rcu_head;
> -
> /* Precalculated geometry info */
> xfs_agblock_t block_count;
> xfs_agblock_t min_block;
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-08-21 16:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 6:38 convert XFS perag lookup to xarrays v2 Christoph Hellwig
2024-08-21 6:38 ` [PATCH 1/5] xfs: use kfree_rcu_mightsleep to free the perag structures Christoph Hellwig
2024-08-21 16:19 ` Darrick J. Wong [this message]
2024-08-22 3:42 ` Christoph Hellwig
2024-08-21 6:38 ` [PATCH 2/5] xfs: move the tagged perag lookup helpers to xfs_icache.c Christoph Hellwig
2024-08-21 16:34 ` Darrick J. Wong
2024-08-22 3:47 ` Christoph Hellwig
2024-08-28 6:28 ` Christoph Hellwig
2024-08-28 16:10 ` Darrick J. Wong
2024-08-29 3:48 ` Christoph Hellwig
2024-08-21 6:38 ` [PATCH 3/5] xfs: simplify tagged perag iteration Christoph Hellwig
2024-08-21 16:30 ` Darrick J. Wong
2024-08-21 6:38 ` [PATCH 4/5] xfs: convert perag lookup to xarray Christoph Hellwig
2024-08-21 16:28 ` Darrick J. Wong
2024-08-22 3:45 ` Christoph Hellwig
2024-08-27 22:51 ` Dave Chinner
2024-08-21 6:38 ` [PATCH 5/5] xfs: use xas_for_each_marked in xfs_reclaim_inodes_count Christoph Hellwig
2024-08-21 16:22 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2024-08-29 4:08 convert XFS perag lookup to xarrays v3 Christoph Hellwig
2024-08-29 4:08 ` [PATCH 1/5] xfs: use kfree_rcu_mightsleep to free the perag structures Christoph Hellwig
2024-08-29 21:19 ` 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=20240821161939.GC865349@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chandan.babu@oracle.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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