From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v5 2/3] GFS2: Introduce new gfs2_log_header_v2
Date: Fri, 19 Jan 2018 20:06:07 +0000 [thread overview]
Message-ID: <849d5940-dd06-b528-4195-e7d1eeeb1b76@redhat.com> (raw)
In-Reply-To: <b0dd0d59-d6f2-10bb-5b31-719cf320036e@redhat.com>
On 19/01/18 14:31, Andrew Price wrote:> I've pushed a gfs2-utils patch
with basic support for the new log header
> format to the andyp-lhv2 branch. I need to test it some more but it
> should be useful for testing these patches already. I'll finalise it
> once the v2 patches are in for-next.
So the gfs2-utils patch is completely broken in that it isn't using
crc32c for lh_crc. I'm looking into finding a userspace crc32c
implementation now.
On a related note: unless I'm mistaken, we'll need to add 'select
CRYPTO_CRC32C' in gfs2's Kconfig now.
Andy
next prev parent reply other threads:[~2018-01-19 20:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 16:04 [Cluster-devel] [PATCH v5 0/3] GFS2: Introduce new gfs2_log_header_v2 Andreas Gruenbacher
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 [this message]
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=849d5940-dd06-b528-4195-e7d1eeeb1b76@redhat.com \
--to=anprice@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.