From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: iomap-5.9-merge updated to 66143873c6a0
Date: Fri, 31 Jul 2020 16:02:06 -0700 [thread overview]
Message-ID: <20200731230206.GA67805@magnolia> (raw)
Hi folks,
The iomap-5.9-merge branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update. This was one last rebase to pick up a few more late
reviews on the head commit in the branch.
The new head of the iomap-5.9-merge branch is commit:
66143873c6a0 iomap: fall back to buffered writes for invalidation failures
New Commits:
Andreas Gruenbacher (1):
[d1b4f507d71d] iomap: Make sure iomap_end is called after iomap_begin
Christoph Hellwig (2):
[00dccd7bf406] xfs: use ENOTBLK for direct I/O to buffered I/O fallback
[66143873c6a0] iomap: fall back to buffered writes for invalidation failures
Dave Chinner (1):
[6fa1c383e783] iomap: Only invalidate page cache pages on direct IO writes
Code Diffstat:
fs/ext4/file.c | 2 ++
fs/gfs2/file.c | 3 ++-
fs/iomap/apply.c | 13 +++++++++----
fs/iomap/direct-io.c | 37 +++++++++++++++++++++----------------
fs/iomap/trace.h | 1 +
fs/xfs/xfs_file.c | 8 ++++----
fs/zonefs/super.c | 7 +++++--
7 files changed, 44 insertions(+), 27 deletions(-)
reply other threads:[~2020-07-31 23:02 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=20200731230206.GA67805@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).