All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentin Vidic <Valentin.Vidic@CARNet.hr>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils: mkfs segfault with 4.16 kernel
Date: Thu, 10 May 2018 21:47:06 +0200	[thread overview]
Message-ID: <20180510194706.GU28554@gavran.carpriv.carnet.hr> (raw)
In-Reply-To: <694e275f-3fee-4d3c-07aa-d0d1f460e5ff@redhat.com>

On Wed, May 09, 2018 at 05:53:19PM +0100, Andrew Price wrote:
> 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.

Thanks for the help, the testsuite is working now with a small patch
like you suggested.  I still want to check if there are any issues
mounting a filesystem created with the tools and hopefully this can
be used until the release :)

-- 
Valentin



  reply	other threads:[~2018-05-10 19:47 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
2018-05-10 19:47                           ` Valentin Vidic [this message]
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=20180510194706.GU28554@gavran.carpriv.carnet.hr \
    --to=valentin.vidic@carnet.hr \
    /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.