From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUCE] xfs: for-next updated to 2254a7396a0c
Date: Fri, 5 May 2023 09:32:09 +1000 [thread overview]
Message-ID: <20230504233209.GK3223426@dread.disaster.area> (raw)
Hi folks,
I just pushed out a new for-next branch to the xfs kernel tree
with Darrick's set of fixes for issues found since the merge window
opened. These address the inodegc UAF problems and some of the
issues found by testing stripe aligned filesystems. There is nothing
big here, and if nothign goes wrong after a few days in linux-next
I'll ask Linus to pull them next week.
Cheers,
Dave.
----------------------------------------------------------------
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
Head Commit: 2254a7396a0ca6309854948ee1c0a33fa4268cec
xfs: fix xfs_inodegc_stop racing with mod_delayed_work (2023-05-02 09:16:14 +1000)
----------------------------------------------------------------
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
reply other threads:[~2023-05-04 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230504233209.GK3223426@dread.disaster.area \
--to=david@fromorbit.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