From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 01728b44ef1b
Date: Sun, 20 Mar 2022 09:08:54 -0700 [thread overview]
Message-ID: <20220320160854.GH8224@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. Just some more bug fixes; I would like to get the
alloc_set_aside bugfixes and cleanups into this release.
The new head of the for-next branch is commit:
01728b44ef1b xfs: xfs_is_shutdown vs xlog_is_shutdown cage fight
15 new commits:
Darrick J. Wong (7):
[eba0549bc7d1] xfs: don't generate selinux audit messages for capability testing
[e014f37db1a2] xfs: use setattr_copy to set vfs inode attributes
[dd3b015dd806] xfs: refactor user/group quota chown in xfs_setattr_nonsize
[871b9316e7a7] xfs: reserve quota for dir expansion when linking/unlinking files
[41667260bc84] xfs: reserve quota for target dir expansion when renaming files
[996b2329b20a] xfs: constify the name argument to various directory functions
[744e6c8ada5d] xfs: constify xfs_name_dotdot
Dave Chinner (7):
[a9a4bc8c76d7] xfs: log worker needs to start before intent/unlink recovery
[dbd0f5299302] xfs: check buffer pin state after locking in delwri_submit
[941fbdfd6dd0] xfs: xfs_ail_push_all_sync() stalls when racing with updates
[70447e0ad978] xfs: async CIL flushes need pending pushes to be made stable
[d86142dd7c4e] xfs: log items should have a xlog pointer, not a mount
[8eda87211097] xfs: AIL should be log centric
[01728b44ef1b] xfs: xfs_is_shutdown vs xlog_is_shutdown cage fight
Gao Xiang (1):
[1a39ae415c1b] xfs: add missing cmap->br_state = XFS_EXT_NORM update
Code Diffstat:
fs/xfs/libxfs/xfs_dir2.c | 36 +++++++------
fs/xfs/libxfs/xfs_dir2.h | 8 +--
fs/xfs/libxfs/xfs_dir2_priv.h | 5 +-
fs/xfs/xfs_bmap_item.c | 2 +-
fs/xfs/xfs_buf.c | 45 ++++++++++++----
fs/xfs/xfs_buf_item.c | 5 +-
fs/xfs/xfs_extfree_item.c | 2 +-
fs/xfs/xfs_fsmap.c | 4 +-
fs/xfs/xfs_icache.c | 10 +++-
fs/xfs/xfs_inode.c | 100 ++++++++++++++++++++++-------------
fs/xfs/xfs_inode.h | 2 +-
fs/xfs/xfs_inode_item.c | 12 +++++
fs/xfs/xfs_ioctl.c | 2 +-
fs/xfs/xfs_iops.c | 118 +++++++++---------------------------------
fs/xfs/xfs_log.c | 5 +-
fs/xfs/xfs_log_cil.c | 24 +++++++--
fs/xfs/xfs_pnfs.c | 3 +-
fs/xfs/xfs_qm.c | 8 +--
fs/xfs/xfs_refcount_item.c | 2 +-
fs/xfs/xfs_reflink.c | 5 +-
fs/xfs/xfs_rmap_item.c | 2 +-
fs/xfs/xfs_trace.h | 8 +--
fs/xfs/xfs_trans.c | 90 +++++++++++++++++++++++++++++++-
fs/xfs/xfs_trans.h | 6 ++-
fs/xfs/xfs_trans_ail.c | 47 ++++++++++-------
fs/xfs/xfs_trans_priv.h | 3 +-
kernel/capability.c | 1 +
27 files changed, 344 insertions(+), 211 deletions(-)
reply other threads:[~2022-03-20 16:09 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=20220320160854.GH8224@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