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.16-rc5
Date: Thu, 8 Mar 2018 10:48:00 -0800 [thread overview]
Message-ID: <20180308184800.GA18989@magnolia> (raw)
Hi Linus,
Here's a few more fixes for locking problems and incorrect copy on
write behaviors on 4.16. It should merge cleanly, but please let me
know if it doesn't.
--Darrick
The following changes since commit 5b4c845ea4f4b86c43096eb924354c83a2e26f3c:
xfs: fix potential memory leak in mount option parsing (2018-02-26 10:02:13 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.16-fixes-3
for you to fetch changes up to ff3d8b9c4cb95180ae6ef9eed28409840525b9fa:
xfs: don't block on the ilock for RWF_NOWAIT (2018-03-01 14:12:45 -0800)
----------------------------------------------------------------
Changes since last update:
- Fix some iomap locking problems
- Don't allocate cow blocks when we're zeroing file data
----------------------------------------------------------------
Christoph Hellwig (3):
xfs: don't allocate COW blocks for zeroing holes or unwritten extents
xfs: don't start out with the exclusive ilock for direct I/O
xfs: don't block on the ilock for RWF_NOWAIT
fs/xfs/xfs_iomap.c | 42 ++++++++++++++++++++++++++++++------------
1 file changed, 30 insertions(+), 12 deletions(-)
reply other threads:[~2018-03-08 18:48 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=20180308184800.GA18989@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;
as well as URLs for NNTP newsgroup(s).