From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 0/9] xfs: refactor ordered buffer logging code
Date: Wed, 30 Aug 2017 09:08:39 -0700 [thread overview]
Message-ID: <20170830160839.GK4757@magnolia> (raw)
In-Reply-To: <20170829143758.58990-1-bfoster@redhat.com>
On Tue, Aug 29, 2017 at 10:37:49AM -0400, Brian Foster wrote:
> Hi all,
>
> Here's v2 of the ordered buffer / buffer relogging refactoring series.
> Only minor updates in this version. I've also tagged patch 6 for stable
> as it fixes a log recovery regression for bmbt owner change operations.
Seems to have passed testing cycle, queued for next.
--D
>
> Brian
>
> v2:
> - Various cleanups.
> - Rename bmbt scan invalid owner flag.
> - Added stable CC for bmbt owner change log recovery fix (6/9).
> v1: https://marc.info/?l=linux-xfs&m=150367356112090&w=2
> - Drop unnecessary buffer type set in xfs_btree_block_change_owner().
> - Several new cleanup patches.
> - Fix bmbt owner change (extent swap) log recovery.
> - Update buffer ordering to fail on previously dirty buffers.
> - Rework bmbt owner change to use ordered buffers correctly.
> rfc: https://marc.info/?l=linux-xfs&m=150272969407981&w=2
>
> Brian Foster (9):
> xfs: open-code xfs_buf_item_dirty()
> xfs: remove unnecessary dirty bli format check for ordered bufs
> xfs: ordered buffer log items are never formatted
> xfs: refactor buffer logging into buffer dirtying helper
> xfs: don't log dirty ranges for ordered buffers
> xfs: skip bmbt block ino validation during owner change
> xfs: move bmbt owner change to last step of extent swap
> xfs: disallow marking previously dirty buffers as ordered
> xfs: relog dirty buffers during swapext bmbt owner change
>
> fs/xfs/libxfs/xfs_bmap_btree.c | 1 +
> fs/xfs/libxfs/xfs_btree.c | 27 ++++++++----
> fs/xfs/libxfs/xfs_btree.h | 3 +-
> fs/xfs/libxfs/xfs_ialloc.c | 2 -
> fs/xfs/xfs_bmap_util.c | 93 +++++++++++++++++++++++++++++++-----------
> fs/xfs/xfs_buf_item.c | 75 +++++++++++++---------------------
> fs/xfs/xfs_buf_item.h | 2 +-
> fs/xfs/xfs_trace.h | 1 -
> fs/xfs/xfs_trans.h | 6 ++-
> fs/xfs/xfs_trans_buf.c | 79 +++++++++++++++++++++--------------
> 10 files changed, 173 insertions(+), 116 deletions(-)
>
> --
> 2.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-30 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 14:37 [PATCH v2 0/9] xfs: refactor ordered buffer logging code Brian Foster
2017-08-29 14:37 ` [PATCH v2 1/9] xfs: open-code xfs_buf_item_dirty() Brian Foster
2017-08-29 14:37 ` [PATCH v2 2/9] xfs: remove unnecessary dirty bli format check for ordered bufs Brian Foster
2017-08-29 14:37 ` [PATCH v2 3/9] xfs: ordered buffer log items are never formatted Brian Foster
2017-08-29 18:49 ` Darrick J. Wong
2017-08-29 14:37 ` [PATCH v2 4/9] xfs: refactor buffer logging into buffer dirtying helper Brian Foster
2017-08-29 14:37 ` [PATCH v2 5/9] xfs: don't log dirty ranges for ordered buffers Brian Foster
2017-08-29 14:37 ` [PATCH v2 6/9] xfs: skip bmbt block ino validation during owner change Brian Foster
2017-08-29 14:37 ` [PATCH v2 7/9] xfs: move bmbt owner change to last step of extent swap Brian Foster
2017-08-29 14:37 ` [PATCH v2 8/9] xfs: disallow marking previously dirty buffers as ordered Brian Foster
2017-08-29 14:37 ` [PATCH v2 9/9] xfs: relog dirty buffers during swapext bmbt owner change Brian Foster
2017-08-30 16:08 ` Darrick J. Wong [this message]
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=20170830160839.GK4757@magnolia \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.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