From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/4] xfs-4.19: superblock verifier cleanups
Date: Mon, 30 Jul 2018 20:55:37 -0700 [thread overview]
Message-ID: <153300933773.5164.7520087911614107147.stgit@magnolia> (raw)
Hi all,
This series refactors the superblock verification routines into three
predicates: one to handle checks that are only done at read time,
another for write time checks, and a third for checks common to both.
We then add some sanity checks for the summary counters to the write
verifier (a reworked version of Bill O'Donnell's earlier patch), and end
by addding a verifier for inode counts and adding that into the
superblock write checks. A fourth patch adds feature bit sanity checks
for the write verifier.
Comments and questions are, as always, welcome.
--D
next reply other threads:[~2018-07-31 5:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 3:55 Darrick J. Wong [this message]
2018-07-31 3:55 ` [PATCH 1/4] xfs: refactor superblock verifiers Darrick J. Wong
2018-07-31 3:55 ` [PATCH 2/4] libxfs: add more bounds checking to sb sanity checks Darrick J. Wong
2018-07-31 3:55 ` [PATCH 3/4] xfs: verify icount in superblock write Darrick J. Wong
2018-07-31 3:57 ` Eric Sandeen
2018-07-31 3:56 ` [PATCH 4/4] xfs: check for unknown v5 feature bits in superblock write verifier Darrick J. Wong
2018-07-31 4:07 ` Eric Sandeen
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=153300933773.5164.7520087911614107147.stgit@magnolia \
--to=darrick.wong@oracle.com \
--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).