From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils: mkfs segfault with 4.16 kernel
Date: Wed, 9 May 2018 17:53:19 +0100 [thread overview]
Message-ID: <694e275f-3fee-4d3c-07aa-d0d1f460e5ff@redhat.com> (raw)
In-Reply-To: <20180504140055.GB4608@gavran.carpriv.carnet.hr>
(Sorry for the delay, I've been away.)
On 04/05/18 15:00, Valentin Vidic wrote:> 29. libgfs2.at:3: testing
meta.c ...
> ./libgfs2.at:3: test x"$ENABLE_UNIT_TESTS" = "xyes" || exit 77
> ./libgfs2.at:4: check_meta
> stderr:
> gfs2_rgrp: rg_reserved: offset is 68, expected 48
> gfs2_rgrp: size mismatch between struct 128 and fields 108
> gfs2_log_header: size mismatch between struct 120 and fields 48
> stdout:
> Running suite(s): libgfs2
> 0%: Checks: 1, Failures: 1, Errors: 0
> check_meta.c:9:F:Meta:test_lgfs2_meta:0: Assertion 'lgfs2_selfcheck() == 0' failed
> ./libgfs2.at:4: exit code was 1, expected 0
> 29. libgfs2.at:3: 29. meta.c (libgfs2.at:3): FAILED (libgfs2.at:4)
You should be able to fix this by using the configure.ac and
gfs2/libgfs2/meta.c files from master. The diff should be very small.
It'll need an ./autogen.sh to rebuild the configure script.
The downside of that approach is that the new fields will be recognised
but not used in the utils. The next release of gfs2-utils will add that
functionality.
Andy
next prev parent reply other threads:[~2018-05-09 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 9:42 [Cluster-devel] gfs2-utils: mkfs segfault with 4.16 kernel Valentin Vidic
2018-05-04 9:50 ` Valentin Vidic
2018-05-04 10:06 ` Andrew Price
2018-05-04 10:21 ` Valentin Vidic
2018-05-04 10:27 ` Andrew Price
2018-05-04 10:42 ` Valentin Vidic
2018-05-04 10:46 ` Andrew Price
2018-05-04 10:54 ` Valentin Vidic
2018-05-04 11:07 ` Andrew Price
2018-05-04 12:01 ` Valentin Vidic
2018-05-04 13:01 ` Andrew Price
2018-05-04 13:16 ` Andrew Price
2018-05-04 14:00 ` Valentin Vidic
2018-05-09 16:53 ` Andrew Price [this message]
2018-05-10 19:47 ` Valentin Vidic
2018-05-13 9:13 ` Valentin Vidic
2018-05-14 13:24 ` Andrew Price
2018-05-14 13:48 ` Valentin Vidic
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=694e275f-3fee-4d3c-07aa-d0d1f460e5ff@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 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).