From: Carlos Maiolino <cem@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-xfs@vger.kernel.org
Subject: [GIT PULL] XFS: Fixes for v7.3-rc2
Date: Mon, 31 Aug 2026 07:53:25 +0200 [thread overview]
Message-ID: <apUSmA9aI8wpLyXf@andromeda.toxiclabs.cc> (raw)
Hello Linus,
Could you please pull patches included in the tag below?
An attempt merge against your current TOT has been successful.
This contains a set of fixes for rc-2. I just want to highlight from
this series that it contains a couple patches for capabilities subsystem
and another for the quota subsystem. All three patches have been acked
by the respective maintainers and they agreed for these patches to go
through xfs tree as they are dependencies for a xfs bugfix.
Thanks,
Carlos
"The following changes since commit 818bebeb63dd6bf5f4e07e145f6cdbace520a34c:
drm/xe: Don't hand out the flat CCS storage as usable VRAM (2026-08-20 20:12:39 -0700)
are available in the Git repository at:
gitolite.kernel.org:/pub/scm/fs/xfs/xfs-linux.git tags/xfs-fixes-7.3-rc2
for you to fetch changes up to 412f89fb3988a344175899776c8bc7073524ad84:
capability: unexport has_capability_noaudit (2026-08-21 09:09:55 +0200)
----------------------------------------------------------------
xfs: fixes for 7.3-rc2
Signed-off-by: Carlos Maiolino <cem@kernel.org>
----------------------------------------------------------------
Carlos Maiolino (5):
xfs: fix capability check in xfs
capability: Add new capable_noaudit
quota: Don't issue audit messages on quota enforcing
xfs: replace ns_capable_noaudit
capability: unexport has_capability_noaudit
Christoph Hellwig (9):
xfs: split an assert in xfs_trans_log_buf
xfs: don't flush and invalidate internal RT device twice in xfs_shutdown_devices
xfs: use inode_init_always_gfp with __GFP_NOFAIL in xfs_inode_alloc
xfs: handle NULL open_zone for merged ioends in xfs_ioend_put_open_zones
xfs: fix racy open zone caching
xfs: fix zoned write iomap flags assignments
xfs: factor out a xfs_iomap_set_anon_write helper
xfs: split ioend handling into a separate source file
xfs: restore bi_bdev in xfs_zone_gc_write_chunk
Tal Zussman (1):
xfs: remove kmem_to_page()
Yun Zhou (1):
xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf
fs/quota/dquot.c | 2 +-
fs/xfs/Makefile | 1 +
fs/xfs/libxfs/xfs_rtgroup.h | 6 +-
fs/xfs/libxfs/xfs_sb.c | 37 ++++-----
fs/xfs/xfs_aops.c | 188 +-------------------------------------------
fs/xfs/xfs_aops.h | 1 -
fs/xfs/xfs_file.c | 2 +-
fs/xfs/xfs_fsmap.c | 3 +-
fs/xfs/xfs_icache.c | 16 ++--
fs/xfs/xfs_ioctl.c | 2 +-
fs/xfs/xfs_ioend.c | 184 +++++++++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_ioend.h | 16 ++++
fs/xfs/xfs_iomap.c | 7 +-
fs/xfs/xfs_iomap.h | 14 ++++
fs/xfs/xfs_iops.c | 2 +-
fs/xfs/xfs_platform.h | 11 ---
fs/xfs/xfs_super.c | 2 +-
fs/xfs/xfs_trans_buf.c | 3 +-
fs/xfs/xfs_zone_alloc.c | 66 +++++++++++++---
fs/xfs/xfs_zone_gc.c | 5 ++
include/linux/capability.h | 5 ++
kernel/capability.c | 19 ++++-
22 files changed, 336 insertions(+), 256 deletions(-)
create mode 100644 fs/xfs/xfs_ioend.c
create mode 100644 fs/xfs/xfs_ioend.h"
next reply other threads:[~2026-08-31 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:53 Carlos Maiolino [this message]
2026-08-31 15:52 ` [GIT PULL] XFS: Fixes for v7.3-rc2 Linus Torvalds
2026-08-31 16:22 ` Carlos Maiolino
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=apUSmA9aI8wpLyXf@andromeda.toxiclabs.cc \
--to=cem@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.