linux-xfs.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: fixes for 5.4-rc1
Date: Thu, 26 Sep 2019 09:02:07 -0700	[thread overview]
Message-ID: <20190926160206.GB9916@magnolia> (raw)

Hi Linus,

Please pull this second set of changes for 5.4-rc1.  There are a couple
of bug fixes and some small code cleanups that came in recently.

It has survived a couple of days of xfstests runs and merges cleanly
with this morning's master.  Please let me know if anything strange
happens.

--D

The following changes since commit 14e15f1bcd738dc13dd7c1e78e4800e8bc577980:

  xfs: push the grant head when the log head moves forward (2019-09-05 21:36:13 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 88d32d3983e72f2a7de72a49b701e2529c48e9c1:

  xfs: avoid unused to_mp() function warning (2019-09-24 09:40:19 -0700)

----------------------------------------------------------------
Changes since last update:
- Minor code cleanups.
- Fix a superblock logging error.
- Ensure that collapse range converts the data fork to extents format
  when necessary.
- Revert the ALLOC_USERDATA cleanup because it caused subtle
  behavior regressions.

----------------------------------------------------------------
Aliasgar Surti (1):
      xfs: removed unneeded variable

Austin Kim (1):
      xfs: avoid unused to_mp() function warning

Brian Foster (1):
      xfs: convert inode to extent format after extent merge due to shift

Darrick J. Wong (1):
      xfs: revert 1baa2800e62d ("xfs: remove the unused XFS_ALLOC_USERDATA flag")

Eric Sandeen (1):
      xfs: log proper length of superblock

 fs/xfs/libxfs/xfs_alloc.h |  7 ++++---
 fs/xfs/libxfs/xfs_bmap.c  | 13 +++++++++++--
 fs/xfs/libxfs/xfs_sb.c    |  2 +-
 fs/xfs/scrub/alloc.c      |  3 +--
 fs/xfs/xfs_sysfs.c        | 13 -------------
 5 files changed, 17 insertions(+), 21 deletions(-)

             reply	other threads:[~2019-09-26 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 16:02 Darrick J. Wong [this message]
2019-09-26 20:10 ` [GIT PULL] xfs: fixes for 5.4-rc1 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=20190926160206.GB9916@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).