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-rc4
Date: Fri, 13 Nov 2020 15:17:38 -0800 [thread overview]
Message-ID: <20201113231738.GX9695@magnolia> (raw)
Hi Linus,
Please pull this branch containing a few more bug fixes for 5.10. I'm
going to have a couple more fixes for you some time next week.
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 46afb0628b86347933b16ac966655f74eab65c8c:
xfs: only flush the unshared range in xfs_reflink_unshare (2020-11-04 17:41:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.10-fixes-5
for you to fetch changes up to 2bd3fa793aaa7e98b74e3653fdcc72fa753913b5:
xfs: fix a missing unlock on error in xfs_fs_map_blocks (2020-11-11 08:07:37 -0800)
----------------------------------------------------------------
Fixes for 5.10-rc4:
- Fix a fairly serious problem where the reverse mapping btree key
comparison functions were silently ignoring parts of the keyspace when
doing comparisons.
- Fix a thinko in the online refcount scrubber.
- Fix a missing unlock in the pnfs code.
----------------------------------------------------------------
Christoph Hellwig (1):
xfs: fix a missing unlock on error in xfs_fs_map_blocks
Darrick J. Wong (4):
xfs: fix flags argument to rmap lookup when converting shared file rmaps
xfs: set the unwritten bit in rmap lookup flags in xchk_bmap_get_rmapextents
xfs: fix rmap key and record comparison functions
xfs: fix brainos in the refcount scrubber's rmap fragment processor
fs/xfs/libxfs/xfs_rmap.c | 2 +-
fs/xfs/libxfs/xfs_rmap_btree.c | 16 ++++++++--------
fs/xfs/scrub/bmap.c | 2 ++
fs/xfs/scrub/refcount.c | 8 +++-----
fs/xfs/xfs_pnfs.c | 2 +-
5 files changed, 15 insertions(+), 15 deletions(-)
next reply other threads:[~2020-11-13 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 23:17 Darrick J. Wong [this message]
2020-11-14 0:15 ` [GIT PULL] xfs: fixes for 5.10-rc4 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=20201113231738.GX9695@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).