From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>
Subject: [GIT PULL] xfs: fixes for 4.14-rc6
Date: Wed, 18 Oct 2017 11:38:06 -0700 [thread overview]
Message-ID: <20171018183806.GD4703@magnolia> (raw)
Hi Linus,
Here's a fourth round of fixes for bugs and other build problems.
--D
The following changes since commit 33d930e59a98fa10a0db9f56c7fa2f21a4aef9b9:
Linux 4.14-rc5 (2017-10-15 21:01:12 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.14-fixes-6
for you to fetch changes up to 785545c8982604fe3ba79d16409e83993be77d5e:
xfs: move two more RT specific functions into CONFIG_XFS_RT (2017-10-16 12:26:50 -0700)
----------------------------------------------------------------
Changes since last update:
- fix some more CONFIG_XFS_RT related build problems
- fix data loss when writeback at eof races eofblocks gc and loses
- invalidate page cache after fs finishes a dio write
- remove dirty page state when invalidating pages so releasepage does
the right thing when handed a dirty page
----------------------------------------------------------------
Arnd Bergmann (1):
xfs: move two more RT specific functions into CONFIG_XFS_RT
Brian Foster (1):
xfs: trim writepage mapping to within eof
Dave Chinner (1):
xfs: cancel dirty pages on invalidation
Eryu Guan (1):
fs: invalidate page cache after end_io() in dio completion
fs/direct-io.c | 20 ++++++++++++--------
fs/iomap.c | 41 ++++++++++++++++++++++++-----------------
fs/xfs/libxfs/xfs_bmap.c | 11 +++++++++++
fs/xfs/libxfs/xfs_bmap.h | 1 +
fs/xfs/xfs_aops.c | 47 +++++++++++++++++++++++++++++++++++------------
fs/xfs/xfs_fsmap.c | 48 ++++++++++++++++++++++++------------------------
6 files changed, 107 insertions(+), 61 deletions(-)
reply other threads:[~2017-10-18 18:38 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=20171018183806.GD4703@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