From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: fixes for 5.10-rc3
Date: Sun, 8 Nov 2020 09:22:35 -0800 [thread overview]
Message-ID: <20201108172235.GA9695@magnolia> (raw)
Hi Linus,
Please pull this branch containing bug fixes for 5.10.
The branch merges cleanly with upstream as of a few minutes ago, so
please let me know if anything strange happens.
--D
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.10-fixes-3
for you to fetch changes up to 46afb0628b86347933b16ac966655f74eab65c8c:
xfs: only flush the unshared range in xfs_reflink_unshare (2020-11-04 17:41:56 -0800)
----------------------------------------------------------------
Fixes for 5.10-rc3:
- Fix an uninitialized struct problem.
- Fix an iomap problem zeroing unwritten EOF blocks.
- Fix some clumsy error handling when writeback fails on
blocksize < pagesize filesystems.
- Fix a retry loop not resetting loop variables properly.
- Fix scrub flagging rtinherit inodes on a non-rt fs, since the kernel
actually does permit that combination.
- Fix excessive page cache flushing when unsharing part of a file.
----------------------------------------------------------------
Brian Foster (3):
xfs: flush new eof page on truncate to avoid post-eof corruption
iomap: support partial page discard on writeback block mapping failure
iomap: clean up writeback state logic on writepage error
Darrick J. Wong (4):
xfs: set xefi_discard when creating a deferred agfl free log intent item
xfs: fix missing CoW blocks writeback conversion retry
xfs: fix scrub flagging rtinherit even if there is no rt device
xfs: only flush the unshared range in xfs_reflink_unshare
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(-)
next reply other threads:[~2020-11-08 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 17:22 Darrick J. Wong [this message]
2020-11-08 18:29 ` [GIT PULL] xfs: fixes for 5.10-rc3 pr-tracker-bot
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=20201108172235.GA9695@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.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).