From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: Christoph Hellwig
<hch@lst.de>4,cdlscpmv@gmail.com,dchinner@redhat.com,djwong@kernel.org,haowenchao22@gmail.com,hch@lst.de,hsiangkao@linux.alibaba.com,john.g.garry@oracle.com,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org,llfamsec@gmail.com
Subject: [ANNOUNCE] xfs-linux: for-next updated to 3ba3ab1f6719
Date: Tue, 02 Jul 2024 19:16:47 +0530 [thread overview]
Message-ID: <8734orc3cr.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:
3ba3ab1f6719 xfs: enable FITRIM on the realtime device
13 new commits:
Christoph Hellwig (6):
[8626b67acfa4] xfs: move the dio write relocking out of xfs_ilock_for_iomap
[29bc0dd0a2f6] xfs: cleanup xfs_ilock_iocb_for_write
[9092b1de35a4] xfs: simplify xfs_dax_fault
[6a39ec1d3944] xfs: refactor __xfs_filemap_fault
[4e82fa11fbbc] xfs: always take XFS_MMAPLOCK shared in xfs_dax_read_fault
[4818fd60db5f] xfs: fold xfs_ilock_for_write_fault into xfs_write_fault
Darrick J. Wong (1):
[3ba3ab1f6719] xfs: enable FITRIM on the realtime device
Gao Xiang (1):
[d40c2865bdbb] xfs: avoid redundant AGFL buffer invalidation
John Garry (2):
[d3b689d7c711] xfs: Fix xfs_flush_unmap_range() range for RT
[f23660f05947] xfs: Fix xfs_prepare_shift() range for RT
Wenchao Hao (1):
[a330cae8a714] xfs: Remove header files which are included more than once
lei lu (2):
[fb63435b7c7d] xfs: add bounds checking to xlog_recover_process_data
[0c7fcdb6d06c] xfs: don't walk off the end of a directory data block
Code Diffstat:
fs/xfs/libxfs/xfs_alloc.c | 28 +--------
fs/xfs/libxfs/xfs_alloc.h | 6 +-
fs/xfs/libxfs/xfs_dir2_data.c | 31 ++++++++--
fs/xfs/libxfs/xfs_dir2_priv.h | 7 +++
fs/xfs/libxfs/xfs_trans_resv.c | 1 -
fs/xfs/scrub/quota_repair.c | 1 -
fs/xfs/xfs_bmap_util.c | 22 ++++---
fs/xfs/xfs_discard.c | 303 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------
fs/xfs/xfs_extfree_item.c | 4 +-
fs/xfs/xfs_file.c | 141 ++++++++++++++++++++++++--------------------
fs/xfs/xfs_handle.c | 1 -
fs/xfs/xfs_iomap.c | 71 +++++++++++-----------
fs/xfs/xfs_log_recover.c | 5 +-
fs/xfs/xfs_qm_bhv.c | 1 -
fs/xfs/xfs_trace.c | 1 -
fs/xfs/xfs_trace.h | 29 +++++++++
16 files changed, 476 insertions(+), 176 deletions(-)
reply other threads:[~2024-07-02 13:47 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=8734orc3cr.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=hch@lst.de \
/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