From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH v2 0/3] xfs: miscellaneous log recovery fixes
Date: Wed, 25 Oct 2017 14:57:02 -0400 [thread overview]
Message-ID: <20171025185705.64983-1-bfoster@redhat.com> (raw)
Hi all,
Here's v2 of the log recovery fixups for filesystems with undersized
logs and the v4 NULL buffer verifier problem. The most significant
change is that patch 1 is rewritten to take a different approach to
sanity check the log block addresses used during log recovery cycle and
record verification. Specifically, it validates the log block number
used for each buffer on read or write. Also, I've dropped patch 4 for
now since I've not heard anything to suggest it's really necessary.
Brian
v2:
- Use xlog buffer validation rather than explicit checks.
- Don't push AIL on log recovery error.
- Drop patch 4 (rfc).
- Fix up commit logs.
v1: https://marc.info/?l=linux-xfs&m=150877001230751&w=2
Brian Foster (3):
xfs: more robust recovery xlog buffer validation
xfs: fix log block underflow during recovery cycle verification
xfs: drain the buffer LRU on mount
fs/xfs/xfs_log.c | 16 ++++++++++++++++
fs/xfs/xfs_log_recover.c | 40 +++++++++++++++++++++++++---------------
2 files changed, 41 insertions(+), 15 deletions(-)
--
2.9.5
next reply other threads:[~2017-10-25 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 18:57 Brian Foster [this message]
2017-10-25 18:57 ` [PATCH v2 1/3] xfs: more robust recovery xlog buffer validation Brian Foster
2017-10-25 22:12 ` Darrick J. Wong
2017-10-26 10:21 ` Brian Foster
2017-10-26 13:27 ` [PATCH v3] " Brian Foster
2017-10-26 15:59 ` Darrick J. Wong
2017-10-25 18:57 ` [PATCH v2 2/3] xfs: fix log block underflow during recovery cycle verification Brian Foster
2017-10-25 18:57 ` [PATCH v2 3/3] xfs: drain the buffer LRU on mount Brian Foster
2017-10-26 16:31 ` Darrick J. Wong
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=20171025185705.64983-1-bfoster@redhat.com \
--to=bfoster@redhat.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