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-rc5
Date: Sat, 21 Nov 2020 09:17:10 -0800 [thread overview]
Message-ID: <20201121171710.GA7179@magnolia> (raw)
Hi Linus,
Please pull this branch containing the last of the bug fixes for 5.10.
The critical fixes are for a crash that someone reported in the xattr
code on 32-bit arm last week; and a revert of the rmap key comparison
change from last week as it was totally wrong. I need a vacation. :(
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 2bd3fa793aaa7e98b74e3653fdcc72fa753913b5:
xfs: fix a missing unlock on error in xfs_fs_map_blocks (2020-11-11 08:07:37 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.10-fixes-7
for you to fetch changes up to eb8409071a1d47e3593cfe077107ac46853182ab:
xfs: revert "xfs: fix rmap key and record comparison functions" (2020-11-19 15:17:50 -0800)
----------------------------------------------------------------
Fixes for 5.10-rc5:
- Fix various deficiencies in online fsck's metadata checking code.
- Fix an integer casting bug in the xattr code on 32-bit systems.
- Fix a hang in an inode walk when the inode index is corrupt.
- Fix error codes being dropped when initializing per-AG structures
- Fix nowait directio writes that partially succeed but return EAGAIN.
- Revert last week's rmap comparison patch because it was wrong.
----------------------------------------------------------------
Darrick J. Wong (5):
xfs: fix the minrecs logic when dealing with inode root child blocks
xfs: strengthen rmap record flags checking
xfs: directory scrub should check the null bestfree entries too
xfs: ensure inobt record walks always make forward progress
xfs: revert "xfs: fix rmap key and record comparison functions"
Dave Chinner (1):
xfs: don't allow NOWAIT DIO across extent boundaries
Gao Xiang (1):
xfs: fix forkoff miscalculation related to XFS_LITINO(mp)
Yu Kuai (1):
xfs: return corresponding errcode if xfs_initialize_perag() fail
fs/xfs/libxfs/xfs_attr_leaf.c | 8 +++++++-
fs/xfs/libxfs/xfs_rmap_btree.c | 16 +++++++--------
fs/xfs/scrub/bmap.c | 8 ++++----
fs/xfs/scrub/btree.c | 45 +++++++++++++++++++++++++-----------------
fs/xfs/scrub/dir.c | 27 ++++++++++++++++++-------
fs/xfs/xfs_iomap.c | 29 +++++++++++++++++++++++++++
fs/xfs/xfs_iwalk.c | 27 ++++++++++++++++++++++---
fs/xfs/xfs_mount.c | 11 ++++++++---
8 files changed, 127 insertions(+), 44 deletions(-)
next reply other threads:[~2020-11-21 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 17:17 Darrick J. Wong [this message]
2020-11-21 18:39 ` [GIT PULL] xfs: fixes for 5.10-rc5 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=20201121171710.GA7179@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).