All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	david@fromorbit.com, linux-kernel@vger.kernel.org,
	sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: more new code for 5.13
Date: Thu, 6 May 2021 17:32:44 -0700	[thread overview]
Message-ID: <20210507003244.GF8582@magnolia> (raw)

Hi Linus,

Please pull this second branch containing new xfs code for 5.13.  Except
for the timestamp struct renaming patches, everything else in here are
bug fixes for 5.13-rc1.

The branch merges cleanly against upstream as of a few minutes ago.
Please let me know if anything else strange happens during the merge
process.

--D

The following changes since commit 76adf92a30f3b92a7f91bb00b28ea80efccd0f01:

  xfs: remove xfs_quiesce_attr declaration (2021-04-16 08:28:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.13-merge-5

for you to fetch changes up to 8e9800f9f2b89e1efe2a5993361fae4d618a6c26:

  xfs: don't allow log writes if the data device is readonly (2021-05-04 08:43:27 -0700)

----------------------------------------------------------------
More new code for 5.13:
- Rename the log timestamp struct.
- Remove broken transaction counter debugging that wasn't working
  correctly on very old filesystems.
- Various fixes to make pre-lazysbcount filesystems work properly again.
- Fix a free space accounting problem where we neglected to consider
  free space btree blocks that track metadata reservation space when
  deciding whether or not to allow caller to reserve space for
  a metadata update.
- Fix incorrect pagecache clearing behavior during FUNSHARE ops.
- Don't allow log writes if the data device is readonly.

----------------------------------------------------------------
Brian Foster (3):
      xfs: unconditionally read all AGFs on mounts with perag reservation
      xfs: introduce in-core global counter of allocbt blocks
      xfs: set aside allocation btree blocks from block reservation

Christoph Hellwig (2):
      xfs: rename xfs_ictimestamp_t
      xfs: rename struct xfs_legacy_ictimestamp

Darrick J. Wong (5):
      xfs: remove obsolete AGF counter debugging
      xfs: don't check agf_btreeblks on pre-lazysbcount filesystems
      xfs: count free space btree blocks when scrubbing pre-lazysbcount fses
      xfs: fix xfs_reflink_unshare usage of filemap_write_and_wait_range
      xfs: don't allow log writes if the data device is readonly

Dave Chinner (1):
      xfs: update superblock counters correctly for !lazysbcount

 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-07  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07  0:32 Darrick J. Wong [this message]
2021-05-07  7:51 ` [GIT PULL] xfs: more new code for 5.13 pr-tracker-bot

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=20210507003244.GF8582@magnolia \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --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.