linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	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: moar new code for 5.6
Date: Wed, 5 Feb 2020 14:43:04 -0800	[thread overview]
Message-ID: <20200205224303.GF6870@magnolia> (raw)

Hi Linus,

Please pull this second batch of new changes for 5.6-rc1.  This contains
the buffer error code refactoring I mentioned last week, now that it has
had extra time to complete the full xfs fuzz testing suite to make sure
there aren't any obvious new bugs.

This merges cleanly against upstream as of about 15 minutes ago.  Note
that the -merge-7 and -merge-8 tags both point to the same ten day old
commit; the message attached to -8 reflects only the changes since last
week's pull.  Please let me know if anything odd happens during the
merge, though it should be clean.

--D

The following changes since commit b3531f5fc16d4df2b12567bce48cd9f3ab5f9131:

  xfs: remove unused variable 'done' (2020-01-23 21:24:50 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.6-merge-8

for you to fetch changes up to cdbcf82b86ea24aa942991b4233cd8ddf13f590c:

  xfs: fix xfs_buf_ioerror_alert location reporting (2020-01-26 14:32:27 -0800)

----------------------------------------------------------------
(More) new code for 5.6:
- Refactor the metadata buffer functions to return the usual int error
value instead of the open coded error checking mess we have now.

----------------------------------------------------------------
Darrick J. Wong (12):
      xfs: make xfs_buf_alloc return an error code
      xfs: make xfs_buf_get_map return an error code
      xfs: make xfs_buf_read_map return an error code
      xfs: make xfs_buf_get return an error code
      xfs: make xfs_buf_get_uncached return an error code
      xfs: make xfs_buf_read return an error code
      xfs: make xfs_trans_get_buf_map return an error code
      xfs: make xfs_trans_get_buf return an error code
      xfs: remove the xfs_btree_get_buf[ls] functions
      xfs: make xfs_*read_agf return EAGAIN to ALLOC_FLAG_TRYLOCK callers
      xfs: remove unnecessary null pointer checks from _read_agf callers
      xfs: fix xfs_buf_ioerror_alert location reporting

 fs/xfs/libxfs/xfs_ag.c          |  21 +++---
 fs/xfs/libxfs/xfs_alloc.c       |  51 ++++++-------
 fs/xfs/libxfs/xfs_attr_remote.c |  22 ++----
 fs/xfs/libxfs/xfs_bmap.c        |  25 ++++---
 fs/xfs/libxfs/xfs_btree.c       |  45 +----------
 fs/xfs/libxfs/xfs_btree.h       |  21 ------
 fs/xfs/libxfs/xfs_da_btree.c    |   8 +-
 fs/xfs/libxfs/xfs_ialloc.c      |  12 +--
 fs/xfs/libxfs/xfs_refcount.c    |   6 --
 fs/xfs/libxfs/xfs_sb.c          |  17 +++--
 fs/xfs/scrub/agheader_repair.c  |   4 -
 fs/xfs/scrub/fscounters.c       |   3 -
 fs/xfs/scrub/repair.c           |  10 ++-
 fs/xfs/xfs_attr_inactive.c      |  17 +++--
 fs/xfs/xfs_buf.c                | 161 ++++++++++++++++++++++++----------------
 fs/xfs/xfs_buf.h                |  33 ++++----
 fs/xfs/xfs_buf_item.c           |   2 +-
 fs/xfs/xfs_discard.c            |   2 +-
 fs/xfs/xfs_dquot.c              |   8 +-
 fs/xfs/xfs_filestream.c         |  11 ++-
 fs/xfs/xfs_inode.c              |  12 +--
 fs/xfs/xfs_log_recover.c        |  30 +++-----
 fs/xfs/xfs_reflink.c            |   2 -
 fs/xfs/xfs_rtalloc.c            |   8 +-
 fs/xfs/xfs_symlink.c            |  37 +++------
 fs/xfs/xfs_trans.h              |  14 ++--
 fs/xfs/xfs_trans_buf.c          |  61 ++++++---------
 27 files changed, 278 insertions(+), 365 deletions(-)

             reply	other threads:[~2020-02-05 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 22:43 Darrick J. Wong [this message]
2020-02-06  8:20 ` [GIT PULL] xfs: moar new code for 5.6 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=20200205224303.GF6870@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 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).