From: "Darrick J. Wong" <djwong@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
Leah Rumancik <leah.rumancik@gmail.com>,
Dave Chinner <david@fromorbit.com>,
Chris Dunlop <chris@onthe.net.au>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6.1 CANDIDATE 0/3] xfs inodegc fixes for 6.1.y (from v6.4)
Date: Wed, 12 Jul 2023 08:44:53 -0700 [thread overview]
Message-ID: <20230712154453.GE108251@frogsfrogsfrogs> (raw)
In-Reply-To: <20230712094733.1265038-1-amir73il@gmail.com>
On Wed, Jul 12, 2023 at 12:47:30PM +0300, Amir Goldstein wrote:
> Darrick,
>
> These are the patches we discussed that Leah requested for the 5.15.y
> backport of non-blocking inodegc pushes series [1].
>
> They may or may not help the 5.15.y -> 6.1.y regression that was
> reported by Chris [2].
>
> Note that I did not include:
> 2d5f38a31980 ("xfs: disable reaping in fscounters scrub")
> in this backport set, because I generally do not want to deal with
> backporting fixes for experimental features.
I don't agree with this decision because the comment for
xfs_inodegc_stop now says that callers must hold s_umount.
xchk_stop_reaping definitely does /not/ hold that lock, which means it's
now buggy. Someone downstream could be using scrub, even if it's still
experimental.
I've generally said not to bother with scrub fixes, but I don't think
it's correct to introduce a bug in an LTS kernel. Please backport
2d5f38a31980 since all it does is removes the offending call and turns
off code in fscounters.c.
--D
> This series has gone through the usual kdevops testing routine.
>
> Please ACK.
>
> Thanks,
> Amir.
>
> [1] https://www.spinics.net/lists/linux-xfs/msg61813.html
> [2] https://lore.kernel.org/all/ZK4E%2FgGuaBu+qvKL@dread.disaster.area/
>
> Darrick J. Wong (3):
> xfs: explicitly specify cpu when forcing inodegc delayed work to run
> immediately
> xfs: check that per-cpu inodegc workers actually run on that cpu
> xfs: fix xfs_inodegc_stop racing with mod_delayed_work
>
> fs/xfs/xfs_icache.c | 40 +++++++++++++++++++++++++++++++++-------
> fs/xfs/xfs_mount.h | 3 +++
> fs/xfs/xfs_super.c | 3 +++
> 3 files changed, 39 insertions(+), 7 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-12 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:47 [PATCH 6.1 CANDIDATE 0/3] xfs inodegc fixes for 6.1.y (from v6.4) Amir Goldstein
2023-07-12 9:47 ` [PATCH 6.1 CANDIDATE 1/3] xfs: explicitly specify cpu when forcing inodegc delayed work to run immediately Amir Goldstein
2023-07-12 9:47 ` [PATCH 6.1 CANDIDATE 2/3] xfs: check that per-cpu inodegc workers actually run on that cpu Amir Goldstein
2023-07-12 9:47 ` [PATCH 6.1 CANDIDATE 3/3] xfs: fix xfs_inodegc_stop racing with mod_delayed_work Amir Goldstein
2023-07-12 15:44 ` Darrick J. Wong [this message]
2023-07-13 4:47 ` [PATCH 6.1 CANDIDATE 0/3] xfs inodegc fixes for 6.1.y (from v6.4) Amir Goldstein
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=20230712154453.GE108251@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=chris@onthe.net.au \
--cc=david@fromorbit.com \
--cc=leah.rumancik@gmail.com \
--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