linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v4 0/3] xfs: bli refcount fixups
Date: Fri, 31 Aug 2018 11:13:24 -0400	[thread overview]
Message-ID: <20180831151327.41225-1-bfoster@redhat.com> (raw)

v4:
- Add a space to xfs_buf_item_unlock().
- Move xfs_buf_item_put() and add a comment.
v3: https://marc.info/?l=linux-xfs&m=153556359604256&w=2
- Rename xfs_buf_item_unref() to xfs_buf_item_put()
- Minor logic and comment fixups.
v2: https://marc.info/?l=linux-xfs&m=153537995111772&w=2
- Refactor stale bli unlock logic to more closely resemble original.
- Use bool for 'freed' variable and clean up type casting.
- Reorder asserts/tracepoints and remove unused stale tracepoint.
- Added patches 2 and 3.
v1: https://marc.info/?l=linux-xfs&m=153486008127962&w=2

Brian Foster (3):
  xfs: don't unlock invalidated buf on aborted tx commit
  xfs: clean up xfs_trans_brelse()
  xfs: refactor xfs_buf_log_item reference count handling

 fs/xfs/xfs_buf_item.c  | 119 ++++++++++++++++++++++-------------------
 fs/xfs/xfs_buf_item.h  |   1 +
 fs/xfs/xfs_trace.h     |   1 -
 fs/xfs/xfs_trans_buf.c |  99 +++++++++-------------------------
 4 files changed, 89 insertions(+), 131 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-08-31 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 15:13 Brian Foster [this message]
2018-08-31 15:13 ` [PATCH v4 1/3] xfs: don't unlock invalidated buf on aborted tx commit Brian Foster
2018-08-31 15:13 ` [PATCH v4 2/3] xfs: clean up xfs_trans_brelse() Brian Foster
2018-08-31 15:13 ` [PATCH v4 3/3] xfs: refactor xfs_buf_log_item reference count handling Brian Foster

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=20180831151327.41225-1-bfoster@redhat.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).