From: "Darrick J. Wong" <djwong@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Chinner <david@fromorbit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
Brian Foster <bfoster@redhat.com>
Subject: [GIT PULL] xfs: fixes for 4.11-rc2
Date: Thu, 9 Mar 2017 14:05:54 -0800 [thread overview]
Message-ID: <20170309220554.GT5280@birch.djwong.org> (raw)
Hi Linus,
Here are some bug fixes for -rc2 to clean up the copy on write handling
and to remove a cause of hangs. Could you pull them, please?
--Darrick
The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.11-fixes-1
for you to fetch changes up to 2fcc319d2467a5f5b78f35f79fd6e22741a31b1e:
xfs: try any AG when allocating the first btree block when reflinking (2017-03-08 10:38:53 -0800)
----------------------------------------------------------------
Changes since last update:
- Fix various iomap bugs
- Fix overly aggressive CoW preallocation garbage collection
- Fixes to CoW endio error handling
- Fix some incorrect geometry calculations
- Remove a potential system hang in bulkstat
- Try to allocate blocks more aggressively to reduce ENOSPC errors
----------------------------------------------------------------
Brian Foster (1):
xfs: use iomap new flag for newly allocated delalloc blocks
Chandan Rajendra (1):
xfs: Use xfs_icluster_size_fsb() to calculate inode alignment mask
Christoph Hellwig (3):
xfs: only reclaim unwritten COW extents periodically
xfs: fix and streamline error handling in xfs_end_io
xfs: try any AG when allocating the first btree block when reflinking
Darrick J. Wong (1):
xfs: remove kmem_zalloc_greedy
Eryu Guan (1):
iomap: invalidate page caches should be after iomap_dio_complete() in direct write
fs/iomap.c | 17 +++++++-----
fs/xfs/kmem.c | 18 -------------
fs/xfs/kmem.h | 2 --
fs/xfs/libxfs/xfs_bmap.c | 34 ++++++++++++++----------
fs/xfs/libxfs/xfs_bmap_btree.c | 6 ++---
fs/xfs/xfs_aops.c | 59 +++++++++++++++++++-----------------------
fs/xfs/xfs_icache.c | 2 +-
fs/xfs/xfs_inode.c | 2 +-
fs/xfs/xfs_iomap.c | 25 +++++++++++++-----
fs/xfs/xfs_itable.c | 6 ++---
fs/xfs/xfs_mount.c | 3 +--
fs/xfs/xfs_reflink.c | 23 +++++++++++-----
fs/xfs/xfs_reflink.h | 4 +--
fs/xfs/xfs_super.c | 2 +-
14 files changed, 103 insertions(+), 100 deletions(-)
reply other threads:[~2017-03-09 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170309220554.GT5280@birch.djwong.org \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.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
all inboxes | Powered by JetHome®