From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 8e9800f9f2b8
Date: Tue, 4 May 2021 09:28:29 -0700 [thread overview]
Message-ID: <20210504162829.GB8582@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. This is the last push of this merge window; I decided
to add one more fix to prevent the log from covering itself when the
data device is readonly but the log device itself is not.
The new head of the for-next branch is commit:
8e9800f9f2b8 xfs: don't allow log writes if the data device is readonly
New Commits:
Brian Foster (3):
[2675ad3890db] xfs: unconditionally read all AGFs on mounts with perag reservation
[16eaab839a92] xfs: introduce in-core global counter of allocbt blocks
[fd43cf600cf6] xfs: set aside allocation btree blocks from block reservation
Christoph Hellwig (2):
[6fc277c7c935] xfs: rename xfs_ictimestamp_t
[732de7dbdbd3] xfs: rename struct xfs_legacy_ictimestamp
Darrick J. Wong (5):
[1aec7c3d0567] xfs: remove obsolete AGF counter debugging
[e6c01077ec2d] xfs: don't check agf_btreeblks on pre-lazysbcount filesystems
[e147a756ab26] xfs: count free space btree blocks when scrubbing pre-lazysbcount fses
[d4f74e162d23] xfs: fix xfs_reflink_unshare usage of filemap_write_and_wait_range
[8e9800f9f2b8] xfs: don't allow log writes if the data device is readonly
Dave Chinner (1):
[6543990a168a] xfs: update superblock counters correctly for !lazysbcount
Code Diffstat:
fs/xfs/libxfs/xfs_ag_resv.c | 34 +++++++++++++++++++++++-----------
fs/xfs/libxfs/xfs_alloc.c | 17 ++++++++++++++---
fs/xfs/libxfs/xfs_alloc_btree.c | 4 ++--
fs/xfs/libxfs/xfs_log_format.h | 12 ++++++------
fs/xfs/libxfs/xfs_rmap_btree.c | 2 --
fs/xfs/libxfs/xfs_sb.c | 16 +++++++++++++---
fs/xfs/scrub/agheader.c | 7 ++++++-
fs/xfs/scrub/fscounters.c | 40 +++++++++++++++++++++++++++++++++++++++-
fs/xfs/xfs_fsops.c | 2 --
fs/xfs/xfs_inode_item.c | 8 ++++----
fs/xfs/xfs_inode_item_recover.c | 6 +++---
fs/xfs/xfs_log.c | 10 ++++++----
fs/xfs/xfs_mount.c | 15 ++++++++++++++-
fs/xfs/xfs_mount.h | 6 ++++++
fs/xfs/xfs_ondisk.h | 4 ++--
fs/xfs/xfs_reflink.c | 3 ++-
fs/xfs/xfs_trans.c | 10 +++-------
fs/xfs/xfs_trans.h | 15 ---------------
18 files changed, 143 insertions(+), 68 deletions(-)
reply other threads:[~2021-05-04 16:28 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=20210504162829.GB8582@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