From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 8c110d43c6bc
Date: Wed, 21 Nov 2018 10:36:50 -0800 [thread overview]
Message-ID: <20181121183650.GT6792@magnolia> (raw)
In-Reply-To: <20181121183515.GS6792@magnolia>
[cc fsdevel this time...]
Hi folks,
The for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated. These are all the reflink, mmap, and blocksize <
pagesize corruption fixes that I've collected and tested over the past
couple of weeks.
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.
The new head of the for-next branch is commit:
8c110d43c6bc iomap: readpages doesn't zero page tail beyond EOF
New Commits:
Brian Foster (1):
[59e429314910] xfs: fix shared extent data corruption due to missing cow reservation
Dave Chinner (11):
[d61fa8cbf3da] xfs: uncached buffer tracing needs to print bno
[d43aaf1685aa] xfs: fix transient reference count error in xfs_buf_resubmit_failed_buffers
[c08768977b9a] xfs: finobt AG reserves don't consider last AG can be a runt
[7f9f71be84bc] xfs: extent shifting doesn't fully invalidate page cache
[2c307174ab77] xfs: flush removing page cache in xfs_reflink_remap_prep
[9230a0b65b47] xfs: delalloc -> unwritten COW fork allocation can go wrong
[0929d8580071] iomap: FUA is wrong for DIO O_DSYNC writes into unwritten extents
[b450672fb66b] iomap: sub-block dio needs to zeroout beyond EOF
[4721a6010990] iomap: dio data corruption and spurious errors when pipes fill
[494633fac789] vfs: vfs_dedupe_file_range() doesn't return EOPNOTSUPP
[8c110d43c6bc] iomap: readpages doesn't zero page tail beyond EOF
Eric Biggers (1):
[da034bcc6aaa] xfs: make xfs_file_remap_range() static
Code Diffstat:
fs/iomap.c | 53 +++++++++++++++++++++++++++++++---------
fs/read_write.c | 15 ++++++------
fs/xfs/libxfs/xfs_bmap.c | 5 +++-
fs/xfs/libxfs/xfs_ialloc_btree.c | 11 ++++++---
fs/xfs/xfs_bmap_util.c | 10 ++------
fs/xfs/xfs_bmap_util.h | 3 +++
fs/xfs/xfs_buf_item.c | 28 +++++++++++++++------
fs/xfs/xfs_file.c | 2 +-
fs/xfs/xfs_reflink.c | 18 +++++++++++---
fs/xfs/xfs_trace.h | 5 +++-
10 files changed, 104 insertions(+), 46 deletions(-)
parent reply other threads:[~2018-11-22 5:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20181121183515.GS6792@magnolia>]
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=20181121183650.GT6792@magnolia \
--to=darrick.wong@oracle.com \
--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).