From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: aalbersh@redhat.com,bfoster@redhat.com,dchinner@redhat.com,djwong@kernel.org,hch@lst.de,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,samsun1006219@gmail.com
Subject: [ANNOUNCE] xfs-linux: for-next updated to 25576c5420e6
Date: Sat, 04 May 2024 19:52:33 +0530 [thread overview]
Message-ID: <87o79lejvd.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi folks,
The for-next branch of the xfs-linux repository at:
https://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 new head of the for-next branch is commit:
25576c5420e6 xfs: simplify iext overflow checking and upgrade
13 new commits:
Chandan Babu R (1):
[0370f9bb49f1] Merge tag 'xfs-cleanups-6.10_2024-05-02' of https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into xfs-6.10-mergeF
Christoph Hellwig (7):
[45cf976008dd] xfs: fix log recovery buffer allocation for the legacy h_size fixup
[67a841f9d724] xfs: clean up buffer allocation in xlog_do_recovery_pass
[f7b9ee784511] xfs: consolidate the xfs_quota_reserve_blkres definitions
[cc3c92e7e79e] xfs: xfs_quota_unreserve_blkres can't fail
[99fb6b7ad1f2] xfs: upgrade the extent counters in xfs_reflink_end_cow_extent later
[86de848403ab] xfs: remove a racy if_bytes check in xfs_reflink_end_cow_extent
[25576c5420e6] xfs: simplify iext overflow checking and upgrade
Darrick J. Wong (5):
[a86f8671d03e] xfs: use unsigned ints for non-negative quantities in xfs_attr_remote.c
[a5714b67cad5] xfs: turn XFS_ATTR3_RMT_BUF_SPACE into a function
[204a26aa1d5a] xfs: create a helper to compute the blockcount of a max sized remote value
[3791a053294b] xfs: minor cleanups of xfs_attr3_rmt_blocks
[1a3f1afb2532] xfs: widen flags argument to the xfs_iflags_* helpers
Code Diffstat:
fs/xfs/libxfs/xfs_attr.c | 7 ++-----
fs/xfs/libxfs/xfs_attr_remote.c | 90 +++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------
fs/xfs/libxfs/xfs_attr_remote.h | 8 +++++++-
fs/xfs/libxfs/xfs_bmap.c | 21 ++++++---------------
fs/xfs/libxfs/xfs_bmap.h | 2 +-
fs/xfs/libxfs/xfs_da_format.h | 4 +---
fs/xfs/libxfs/xfs_inode_fork.c | 57 +++++++++++++++++++++++++--------------------------------
fs/xfs/libxfs/xfs_inode_fork.h | 6 ++----
fs/xfs/scrub/reap.c | 4 ++--
fs/xfs/xfs_aops.c | 6 +-----
fs/xfs/xfs_bmap_item.c | 4 +---
fs/xfs/xfs_bmap_util.c | 32 ++++++++------------------------
fs/xfs/xfs_bmap_util.h | 2 +-
fs/xfs/xfs_dquot.c | 5 +----
fs/xfs/xfs_icache.c | 4 +---
fs/xfs/xfs_inode.h | 14 +++++++-------
fs/xfs/xfs_iomap.c | 13 ++++---------
fs/xfs/xfs_log_recover.c | 33 ++++++++++++++++++++-------------
fs/xfs/xfs_quota.h | 23 +++++++++--------------
fs/xfs/xfs_reflink.c | 34 +++++++++-------------------------
fs/xfs/xfs_rtalloc.c | 5 +----
21 files changed, 160 insertions(+), 214 deletions(-)
reply other threads:[~2024-05-04 14:23 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=87o79lejvd.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=aalbersh@redhat.com \
--cc=bfoster@redhat.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=samsun1006219@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).