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 v2 0/4] xfs inodegc fixes for 6.1.y (from v6.4)
Date: Fri, 14 Jul 2023 07:10:08 -0700 [thread overview]
Message-ID: <20230714141008.GT108251@frogsfrogsfrogs> (raw)
In-Reply-To: <20230714064509.1451122-1-amir73il@gmail.com>
On Fri, Jul 14, 2023 at 09:45:05AM +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].
>
> This v2 series has gone through 3 rounds of kdevops loop on top
> of the testing already run on v1.
>
> Please ACK.
Looks good to me,
Acked-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> Thanks,
> Amir.
>
> Changed since v1:
> - include: 2d5f38a31980 ("xfs: disable reaping in fscounters scrub")
>
> [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 (4):
> 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: disable reaping in fscounters scrub
> xfs: fix xfs_inodegc_stop racing with mod_delayed_work
>
> fs/xfs/scrub/common.c | 26 -------------------------
> fs/xfs/scrub/common.h | 2 --
> fs/xfs/scrub/fscounters.c | 13 ++++++-------
> fs/xfs/scrub/scrub.c | 2 --
> fs/xfs/scrub/scrub.h | 1 -
> fs/xfs/xfs_icache.c | 40 ++++++++++++++++++++++++++++++++-------
> fs/xfs/xfs_mount.h | 3 +++
> fs/xfs/xfs_super.c | 3 +++
> 8 files changed, 45 insertions(+), 45 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-07-14 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 6:45 [PATCH 6.1 CANDIDATE v2 0/4] xfs inodegc fixes for 6.1.y (from v6.4) Amir Goldstein
2023-07-14 6:45 ` [PATCH 6.1 CANDIDATE v2 1/4] xfs: explicitly specify cpu when forcing inodegc delayed work to run immediately Amir Goldstein
2023-07-14 6:45 ` [PATCH 6.1 CANDIDATE v2 2/4] xfs: check that per-cpu inodegc workers actually run on that cpu Amir Goldstein
2023-07-14 6:45 ` [PATCH 6.1 CANDIDATE v2 3/4] xfs: disable reaping in fscounters scrub Amir Goldstein
2023-07-14 6:45 ` [PATCH 6.1 CANDIDATE v2 4/4] xfs: fix xfs_inodegc_stop racing with mod_delayed_work Amir Goldstein
2023-07-14 14:10 ` Darrick J. Wong [this message]
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=20230714141008.GT108251@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