From: Dave Chinner <david@fromorbit.com>
To: torvalds@linux-foundation.org
Cc: linux-xfs@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] xfs, iomap: fixes for 4.8-rc5
Date: Fri, 2 Sep 2016 08:27:02 +1000 [thread overview]
Message-ID: <20160901222702.GX22388@dastard> (raw)
Hi Linus,
Can you please pull this XFS and iomap update from the tag below?
Most of these changes are small regression fixes that address
problems introduced in the 4.8-rc1 window. The two fixes that aren't
(IO completion fix and superblock inprogress check) are fixes for
problems introduced some time ago and need to be pushed back to
stable kernels.
Thanks!
Dave.
--
The following changes since commit 32438cf9d54bd53b531f6d98814e84dd278360c1:
Merge branch 'iomap-fixes-4.8-rc3' into for-next (2016-08-17 11:13:37 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git tags/xfs-iomap-for-linus-4.8-rc5
for you to fetch changes up to ea78d80866ce375defb2fdd1c8a3aafec95e0f85:
xfs: track log done items directly in the deferred pending work item (2016-08-30 13:51:39 +1000)
----------------------------------------------------------------
xfs: updates for 4.8-rc5
Changes in this update:
o iomap FIEMAP_EXTENT_MERGED usage fix
o additional mount-time feature restrictions
o rmap btree query fixes
o freeze/unmount io completion workqueue fix
o memory corruption fix for deferred operations handling
----------------------------------------------------------------
Brian Foster (1):
xfs: prevent dropping ioend completions during buftarg wait
Christoph Hellwig (1):
iomap: don't set FIEMAP_EXTENT_MERGED for extent based filesystems
Darrick J. Wong (6):
xfs: don't perform lookups on zero-height btrees
xfs: disallow mounting of realtime + rmap filesystems
xfs: don't log the entire end of the AGF
xfs: fix some key handling problems in _btree_simple_query_range
xfs: simple btree query range should look right if LE lookup fails
xfs: track log done items directly in the deferred pending work item
Dave Chinner (1):
xfs: fix superblock inprogress check
fs/iomap.c | 5 ++++-
fs/xfs/libxfs/xfs_alloc.c | 2 ++
fs/xfs/libxfs/xfs_btree.c | 14 +++++++++++++-
fs/xfs/libxfs/xfs_defer.c | 17 ++++-------------
fs/xfs/libxfs/xfs_defer.h | 2 +-
fs/xfs/libxfs/xfs_format.h | 6 ++++--
fs/xfs/libxfs/xfs_sb.c | 3 ++-
fs/xfs/xfs_buf.c | 2 +-
fs/xfs/xfs_super.c | 9 ++++++++-
fs/xfs/xfs_trace.h | 2 +-
include/linux/iomap.h | 8 +++++++-
11 files changed, 47 insertions(+), 23 deletions(-)
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2016-09-01 22:27 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=20160901222702.GX22388@dastard \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.com \
/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).