From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to 4eb559dd1567
Date: Tue, 1 Nov 2022 09:59:07 -0700 [thread overview]
Message-ID: <Y2FQW0KZTUOsAkyr@magnolia> (raw)
Hi folks,
The for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update. The for-next branch now contains all the stability
fixes that I am aware of and have completed review.
The new head of the for-next branch is commit:
4eb559dd1567 Merge tag 'refcount-cow-domain-6.1_2022-10-31' of git://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.1-fixesA
14 new commits:
Darrick J. Wong (14):
[f850995f60e4] xfs: make sure aglen never goes negative in xfs_refcount_adjust_extents
[b65e08f83b11] xfs: create a predicate to verify per-AG extents
[8edbe0cf8b4b] xfs: check deferred refcount op continuation parameters
[9e7e2436c159] xfs: move _irec structs to xfs_types.h
[5a8c345ca8b9] xfs: refactor refcount record usage in xchk_refcountbt_rec
[9a50ee4f8db6] xfs: track cow/shared record domains explicitly in xfs_refcount_irec
[571423a162cd] xfs: report refcount domain in tracepoints
[f492135df0aa] xfs: refactor domain and refcount checking
[68d0f389179a] xfs: remove XFS_FIND_RCEXT_SHARED and _COW
[f62ac3e0ac33] xfs: check record domain when accessing refcount records
[f1fdc8207840] xfs: fix agblocks check in the cow leftover recovery function
[c1ccf967bf96] xfs: fix uninitialized list head in struct xfs_refcount_recovery
[8b972158afca] xfs: rename XFS_REFC_COW_START to _COWFLAG
[4eb559dd1567] Merge tag 'refcount-cow-domain-6.1_2022-10-31' of git://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.1-fixesA
Code Diffstat:
fs/xfs/libxfs/xfs_ag.h | 15 ++
fs/xfs/libxfs/xfs_alloc.c | 6 +-
fs/xfs/libxfs/xfs_format.h | 22 +--
fs/xfs/libxfs/xfs_refcount.c | 286 ++++++++++++++++++++++++++-----------
fs/xfs/libxfs/xfs_refcount.h | 40 +++++-
fs/xfs/libxfs/xfs_refcount_btree.c | 15 +-
fs/xfs/libxfs/xfs_rmap.c | 9 +-
fs/xfs/libxfs/xfs_types.h | 30 ++++
fs/xfs/scrub/alloc.c | 4 +-
fs/xfs/scrub/ialloc.c | 5 +-
fs/xfs/scrub/refcount.c | 72 ++++------
fs/xfs/xfs_trace.h | 48 +++++--
12 files changed, 368 insertions(+), 184 deletions(-)
reply other threads:[~2022-11-01 16:59 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=Y2FQW0KZTUOsAkyr@magnolia \
--to=djwong@kernel.org \
--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