From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: [GIT PULL] xfs: fixes for 4.14-rc3
Date: Thu, 28 Sep 2017 13:19:57 -0700 [thread overview]
Message-ID: <20170928201957.GS5020@magnolia> (raw)
Hi Linus,
Here's the first round of bug fixes for 4.14.
--D
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.14-fixes-2
for you to fetch changes up to 5e5c943c1f257c2b3424fc3f8a7b18570152dab3:
xfs: revert "xfs: factor rmap btree size into the indlen calculations" (2017-09-26 10:55:20 -0700)
----------------------------------------------------------------
Changes since last update:
- fix various problems with the copy-on-write extent maps getting freed
at the wrong time
- fix printk format specifier problems
- report zeroing operation outcomes instead of dropping them on the
floor
- fix some crashes when dio operations partially fail
- fix a race condition between unwritten extent conversion & dio read
- fix some incorrect tests in the inode log item processing
- correct the delayed allocation space reservations on rmap filesystems
- fix some problems checking for dax support
----------------------------------------------------------------
Carlos Maiolino (1):
xfs: Capture state of the right inode in xfs_iflush_done
Chandan Rajendra (1):
iomap_dio_rw: Allocate AIO completion queue before submitting dio
Colin Ian King (1):
xfs: remove redundant re-initialization of total_nr_pages
Darrick J. Wong (4):
xfs: don't unconditionally clear the reflink flag on zero-block files
xfs: evict CoW fork extents when performing finsert/fcollapse
xfs: perag initialization should only touch m_ag_max_usable for AG 0
xfs: revert "xfs: factor rmap btree size into the indlen calculations"
Eryu Guan (3):
xfs: kill meaningless variable 'zero'
xfs: report zeroed or not correctly in xfs_zero_range()
xfs: update i_size after unwritten conversion in dio completion
Helge Deller (1):
fs/xfs: Use %pS printk format for direct addresses
Kenjiro Nakayama (1):
xfs: Output warning message when discard option was enabled even though the device does not support discard
Ross Zwisler (1):
xfs: validate bdev support for DAX inode flag
fs/iomap.c | 14 +++++++-------
fs/xfs/libxfs/xfs_ag_resv.c | 12 ++++++++++--
fs/xfs/libxfs/xfs_bmap.c | 17 ++---------------
fs/xfs/xfs_aops.c | 3 ++-
fs/xfs/xfs_bmap_util.c | 14 +++++++++++++-
fs/xfs/xfs_buf.c | 2 --
fs/xfs/xfs_error.c | 2 +-
fs/xfs/xfs_file.c | 39 +++++++++++++++++++++------------------
fs/xfs/xfs_inode.c | 8 +++++---
fs/xfs/xfs_inode_item.c | 2 +-
fs/xfs/xfs_ioctl.c | 3 ++-
fs/xfs/xfs_iomap.c | 7 +++++--
fs/xfs/xfs_iomap.h | 2 +-
fs/xfs/xfs_pnfs.c | 2 +-
fs/xfs/xfs_super.c | 10 ++++++++++
15 files changed, 81 insertions(+), 56 deletions(-)
reply other threads:[~2017-09-28 20:20 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=20170928201957.GS5020@magnolia \
--to=djwong@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