From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v5 0/3] GFS2: Introduce new gfs2_log_header_v2
Date: Thu, 18 Jan 2018 17:04:42 +0100 [thread overview]
Message-ID: <20180118160445.12732-1-agruenba@redhat.com> (raw)
Here's a revised version of Bob's gfs2_log_header_v2 patches from
January 4:
The first patch cleanus up get_log_header in a preliminary step.
The second patch incorporates the following chages:
* Fix a NULL pointer access when recovering a node's own journal
(sdp->sd_qc_inode is NULL in gfs2_write_log_header in that case).
* Move the call to gfs2_log_bmap out of gfs2_log_write. With that,
lh_crc can be computed in gfs2_write_log_header and no separate
gfs2_set_log_csum function is needed anymore.
* Change lh_crc to only cover the rest of the block excluding the v1
log header: there is no point in crc-protecting the v1 header a
second time.
* Since lh_crc covers the rest of the block and not only a few header
fields, it makes sense to use crc32c, which is much faster on
architectures that implement it in hardware.
The third patch is unchanged from Bob's last version.
Thanks,
Andreas
Andreas Gruenbacher (1):
gfs2: Get rid of gfs2_log_header_in
Bob Peterson (2):
GFS2: Introduce new gfs2_log_header_v2
GFS2: Log the reason for log flushes in every log header
fs/gfs2/aops.c | 3 +-
fs/gfs2/file.c | 4 +-
fs/gfs2/glops.c | 19 ++++++---
fs/gfs2/incore.h | 1 -
fs/gfs2/log.c | 83 +++++++++++++++++++++++++++++-----------
fs/gfs2/log.h | 12 ++----
fs/gfs2/lops.c | 16 ++++----
fs/gfs2/lops.h | 3 ++
fs/gfs2/ops_fstype.c | 2 +-
fs/gfs2/quota.c | 3 +-
fs/gfs2/recovery.c | 57 ++++++++++++---------------
fs/gfs2/rgrp.c | 3 +-
fs/gfs2/super.c | 13 +++++--
fs/gfs2/trace_gfs2.h | 11 ++++--
fs/gfs2/trans.c | 3 +-
include/uapi/linux/gfs2_ondisk.h | 46 +++++++++++++++++++++-
16 files changed, 187 insertions(+), 92 deletions(-)
--
2.14.3
next reply other threads:[~2018-01-18 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 16:04 Andreas Gruenbacher [this message]
2018-01-18 16:04 ` [Cluster-devel] [PATCH v5 1/3] gfs2: Get rid of gfs2_log_header_in Andreas Gruenbacher
2018-01-18 16:04 ` [Cluster-devel] [PATCH v5 2/3] GFS2: Introduce new gfs2_log_header_v2 Andreas Gruenbacher
2018-01-19 10:47 ` Andrew Price
2018-01-19 10:53 ` Steven Whitehouse
2018-01-19 12:19 ` Andrew Price
2018-01-19 14:35 ` Andreas Gruenbacher
2018-01-19 14:31 ` Andrew Price
2018-01-19 14:39 ` Steven Whitehouse
2018-01-19 15:06 ` Andrew Price
2018-01-19 20:06 ` Andrew Price
2018-01-19 22:23 ` Andrew Price
2018-01-18 16:04 ` [Cluster-devel] [PATCH v5 3/3] GFS2: Log the reason for log flushes in every log header Andreas Gruenbacher
2018-01-18 16:23 ` [Cluster-devel] [PATCH v5 0/3] GFS2: Introduce new gfs2_log_header_v2 Steven Whitehouse
2018-01-19 14:40 ` [Cluster-devel] [PATCH v6] " Andreas Gruenbacher
2018-01-19 15:14 ` Andrew Price
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=20180118160445.12732-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.