public inbox for linux-kernel@vger.kernel.org
 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: bug fixes for 5.7-rc1
Date: Sat, 18 Apr 2020 08:57:02 -0700	[thread overview]
Message-ID: <20200418155702.GV6742@magnolia> (raw)

Hi Linus,

Please pull this handful of fixes for 5.7.  The three commits here fix
some livelocks and other clashes with fsfreeze, a potential corruption
problem, and a minor race between processes freeing and allocating space
when the filesystem is near ENOSPC.

This branch merges cleanly with master as of a few minutes ago, so
please let me know if anything strange happens.

--D

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.7-fixes-3

for you to fetch changes up to f0f7a674d4df1510d8ca050a669e1420cf7d7fab:

  xfs: move inode flush to the sync workqueue (2020-04-16 09:07:42 -0700)

----------------------------------------------------------------
Fixes for 5.7:
- Fix a partially uninitialized variable.
- Teach the background gc threads to apply for fsfreeze protection.
- Fix some scaling problems when multiple threads try to flush the
  filesystem when we're about to hit ENOSPC.

----------------------------------------------------------------
Brian Foster (1):
      xfs: acquire superblock freeze protection on eofblocks scans

Darrick J. Wong (2):
      xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
      xfs: move inode flush to the sync workqueue

 fs/xfs/xfs_icache.c  | 10 ++++++++++
 fs/xfs/xfs_ioctl.c   |  5 ++++-
 fs/xfs/xfs_mount.h   |  6 +++++-
 fs/xfs/xfs_reflink.c |  1 +
 fs/xfs/xfs_super.c   | 40 ++++++++++++++++++++++------------------
 5 files changed, 42 insertions(+), 20 deletions(-)

             reply	other threads:[~2020-04-18 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18 15:57 Darrick J. Wong [this message]
2020-04-18 19:30 ` [GIT PULL] xfs: bug fixes for 5.7-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=20200418155702.GV6742@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