From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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: new bug fixes for 5.17
Date: Fri, 14 Jan 2022 20:19:02 -0800 [thread overview]
Message-ID: <20220115041902.GF90423@magnolia> (raw)
Hi Linus,
Please pull these bug fixes for Linux 5.17. These are the last few
obvious fixes that I found while stress testing online fsck for XFS
prior to initiating a design review of the whole giant machinery.
The branch merges cleanly against upstream as of a few minutes ago.
Please let me know if anything else strange happens during the merge
process. There will definitely be a third pull request coming with a
removal of the recently troublesome ALLOCSP/FREESP ioctl family and the
long dead SGI XFS HSM ioctls.
--D
The following changes since commit 7e937bb3cbe1f6b9840a43f879aa6e3f1a5e6537:
xfs: warn about inodes with project id of -1 (2022-01-06 10:43:30 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.17-merge-3
for you to fetch changes up to 4a9bca86806fa6fc4fbccf050c1bd36a4778948a:
xfs: fix online fsck handling of v5 feature bits on secondary supers (2022-01-12 09:45:21 -0800)
----------------------------------------------------------------
New code for 5.17:
- Fix a minor locking inconsistency in readdir
- Fix incorrect fs feature bit validation for secondary superblocks
----------------------------------------------------------------
Darrick J. Wong (2):
xfs: take the ILOCK when readdir inspects directory mapping data
xfs: fix online fsck handling of v5 feature bits on secondary supers
fs/xfs/scrub/agheader.c | 53 ++++++++++++++++++++--------------------
fs/xfs/scrub/agheader_repair.c | 12 +++++++++
fs/xfs/xfs_dir2_readdir.c | 55 +++++++++++++++++++++++++++---------------
3 files changed, 73 insertions(+), 47 deletions(-)
reply other threads:[~2022-01-15 4:19 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=20220115041902.GF90423@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).