public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: xfs-5.5-merge updated to 722da9485033
Date: Sat, 19 Oct 2019 11:07:03 -0700	[thread overview]
Message-ID: <20191019180703.GD6719@magnolia> (raw)

Hi folks,

** NOT-STABLE INTERIM BRANCH ANNOUNCEMENT **

The xfs-5.5-merge 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 branch is built atop the proposed iomap 5.5 merge branch, for which
I have given everyone until 22 Oct 2019 00:00 UTC to complain if there
are any serious problems.  Until then, please consider this branch
potentially subject to being rebased.  It does not include Christoph's
v3 iomap cleanups, since that'll take a day or two to test anyway.

The new head of the xfs-5.5-merge branch is commit:

722da9485033 xfs: fix inode fork extent count overflow

New Commits:

Brian Foster (11):
      [367caf641367] xfs: track active state of allocation btree cursors
      [aa056ce95480] xfs: introduce allocation cursor data structure
      [2d762b01e0c7] xfs: track allocation busy state in allocation cursor
      [2dc7a360e9f2] xfs: track best extent from cntbt lastblock scan in alloc cursor
      [1c004aefbc49] xfs: refactor cntbt lastblock scan best extent logic into helper
      [8850f861b841] xfs: reuse best extent tracking logic for bnobt scan
      [d12c9a9807a1] xfs: refactor allocation tree fixup code
      [3ef17289f316] xfs: refactor and reuse best extent scanning logic
      [ad2e96cbc3d2] xfs: refactor near mode alloc bnobt scan into separate function
      [9c16806d4643] xfs: factor out tree fixup logic into helper
      [3d899229624f] xfs: optimize near mode bnobt scans with concurrent cntbt lookups

Christoph Hellwig (9):
      [4326f199ff95] xfs: ignore extent size hints for always COW inodes
      [cf59fa63c45a] xfs: pass the correct flag to xlog_write_iclog
      [ca42659bcd68] xfs: remove the unused ic_io_size field from xlog_in_core
      [d960600958ec] xfs: move the locking from xlog_state_finish_copy to the callers
      [dc4ac1fc2182] xfs: call xlog_state_release_iclog with l_icloglock held
      [59693d649f91] xfs: remove dead ifdef XFSERRORDEBUG code
      [355f1bfffb6d] xfs: remove the unused XLOG_STATE_ALL and XLOG_STATE_UNUSED flags
      [87562be8a3fb] xfs: turn ic_state into an enum
      [ec1fe9d7b77e] xfs: remove the XLOG_STATE_DO_CALLBACK state

Dave Chinner (1):
      [722da9485033] xfs: fix inode fork extent count overflow

yu kuai (1):
      [a6026a86ce7f] xfs: include QUOTA, FATAL ASSERT build options in XFS_BUILD_OPTIONS


Code Diffstat:

 fs/xfs/libxfs/xfs_alloc.c       | 897 +++++++++++++++++++++++-----------------
 fs/xfs/libxfs/xfs_alloc_btree.c |   1 +
 fs/xfs/libxfs/xfs_attr_leaf.c   |  18 +-
 fs/xfs/libxfs/xfs_btree.h       |   3 +
 fs/xfs/libxfs/xfs_dir2_sf.c     |   2 +-
 fs/xfs/libxfs/xfs_iext_tree.c   |   2 +-
 fs/xfs/libxfs/xfs_inode_fork.c  |   8 +-
 fs/xfs/libxfs/xfs_inode_fork.h  |  14 +-
 fs/xfs/xfs_inode.c              |   6 +
 fs/xfs/xfs_log.c                | 428 ++++++++-----------
 fs/xfs/xfs_log_cil.c            |   2 +-
 fs/xfs/xfs_log_priv.h           |  25 +-
 fs/xfs/xfs_super.h              |  10 +
 fs/xfs/xfs_trace.h              |  33 +-
 14 files changed, 769 insertions(+), 680 deletions(-)

                 reply	other threads:[~2019-10-19 18:07 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=20191019180703.GD6719@magnolia \
    --to=darrick.wong@oracle.com \
    --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