From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: djwong@kernel.org, linux-xfs@vger.kernel.org
Subject: [GIT PULL] xfs: bug fixes for 6.4-rc2
Date: Thu, 11 May 2023 12:01:07 +1000 [thread overview]
Message-ID: <20230511020107.GI2651828@dread.disaster.area> (raw)
In-Reply-To: <20230511015846.GH2651828@dread.disaster.area>
[ and now with the correct cc's. DOH! ]
Hi Linus,
Can you please pull the latest XFS updates fixes from the tag below?
The are largely minor bug fixes and cleanups, th emost important of
which are probably the fixes for regressions in the extent
allocation code. It merges cleanly with your current tree as of a
few minutes ago, so I don't expect you to see anything weird from
it.
The only thing worth noting is that turning off the counter scrub
code temporarily may produce a new warning about eliding unreachable
code on some compilers. I have not seen this myself (using gcc-12)
but it is harmless and will go away with the kernel-side exclusive
freeze infrastructure that we are hoping will get merged in the next
cycle.
Cheers,
Dave.
---
The following changes since commit 9419092fb2630c30e4ffeb9ef61007ef0c61827a:
xfs: fix livelock in delayed allocation at ENOSPC (2023-04-27 09:02:11 +1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.4-rc1-fixes
for you to fetch changes up to 2254a7396a0ca6309854948ee1c0a33fa4268cec:
xfs: fix xfs_inodegc_stop racing with mod_delayed_work (2023-05-02 09:16:14 +1000)
----------------------------------------------------------------
xfs: bug fixes for 6.4-rc2
o fixes for inode garbage collection shutdown racing with work queue
updates
o ensure inodegc workers run on the CPU they are supposed to
o disable counter scrubbing until we can exclusively freeze the
filesystem from the kernel
o Regression fixes for new allocation related bugs
o a couple of minor cleanups
----------------------------------------------------------------
Darrick J. Wong (9):
xfs: don't unconditionally null args->pag in xfs_bmap_btalloc_at_eof
xfs: set bnobt/cntbt numrecs correctly when formatting new AGs
xfs: flush dirty data and drain directios before scrubbing cow fork
xfs: don't allocate into the data fork for an unshare request
xfs: fix negative array access in xfs_getbmap
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/libxfs/xfs_ag.c | 19 +++++++++----------
fs/xfs/libxfs/xfs_bmap.c | 5 +++--
fs/xfs/scrub/bmap.c | 4 ++--
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/scrub/trace.h | 1 -
fs/xfs/xfs_bmap_util.c | 4 +++-
fs/xfs/xfs_icache.c | 40 +++++++++++++++++++++++++++++++++-------
fs/xfs/xfs_iomap.c | 5 +++--
fs/xfs/xfs_mount.h | 3 +++
fs/xfs/xfs_super.c | 3 +++
14 files changed, 65 insertions(+), 63 deletions(-)
--
Dave Chinner
david@fromorbit.com
next parent reply other threads:[~2023-05-11 2:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230511015846.GH2651828@dread.disaster.area>
2023-05-11 2:01 ` Dave Chinner [this message]
2023-05-11 2:49 ` [GIT PULL] xfs: bug fixes for 6.4-rc2 Linus Torvalds
2023-05-11 3:12 ` Linus Torvalds
2023-05-11 16:50 ` Darrick J. Wong
2023-05-11 17:47 ` Linus Torvalds
2023-05-11 18:04 ` Linus Torvalds
2023-05-11 18:08 ` Darrick J. Wong
2023-05-12 1:28 ` Dave Chinner
2023-05-11 22:04 ` pr-tracker-bot
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=20230511020107.GI2651828@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.