From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [ANNOUNCE] xfs/iomap: for-next updated to 46afb0628b86
Date: Wed, 4 Nov 2020 17:59:04 -0800 [thread overview]
Message-ID: <20201105015904.GO7123@magnolia> (raw)
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.
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. I'm still churning through bug fixes for 5.10, and
sending this to both lists because there's a couple of iomap fixes that
go along with the xfs fixes.
The new head of the for-next branch is commit:
46afb0628b86 xfs: only flush the unshared range in xfs_reflink_unshare
New Commits:
Brian Foster (3):
[869ae85dae64] xfs: flush new eof page on truncate to avoid post-eof corruption
[763e4cdc0f6d] iomap: support partial page discard on writeback block mapping failure
[50e7d6c7a521] iomap: clean up writeback state logic on writepage error
Darrick J. Wong (4):
[2c334e12f957] xfs: set xefi_discard when creating a deferred agfl free log intent item
[c2f09217a430] xfs: fix missing CoW blocks writeback conversion retry
[c1f6b1ac0075] xfs: fix scrub flagging rtinherit even if there is no rt device
[46afb0628b86] xfs: only flush the unshared range in xfs_reflink_unshare
Code Diffstat:
fs/iomap/buffered-io.c | 30 ++++++++++--------------------
fs/xfs/libxfs/xfs_alloc.c | 1 +
fs/xfs/libxfs/xfs_bmap.h | 2 +-
fs/xfs/scrub/inode.c | 3 +--
fs/xfs/xfs_aops.c | 20 ++++++++++++--------
fs/xfs/xfs_iops.c | 10 ++++++++++
fs/xfs/xfs_reflink.c | 3 ++-
include/linux/iomap.h | 2 +-
8 files changed, 38 insertions(+), 33 deletions(-)
reply other threads:[~2020-11-05 1:59 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=20201105015904.GO7123@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).