cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils: mkfs segfault with 4.16 kernel
Date: Fri, 4 May 2018 11:06:59 +0100	[thread overview]
Message-ID: <88c04bee-a2d0-0efd-f856-09d7448c0517@redhat.com> (raw)
In-Reply-To: <20180504095011.GP4608@gavran.carpriv.carnet.hr>

Hi Valentin,

On 04/05/18 10:50, Valentin Vidic wrote:
> On Fri, May 04, 2018 at 11:42:31AM +0200, Valentin Vidic wrote:
>> We are starting to see mkfs segfaults after updating
>> linux-libc-dev from 4.15.17-1 to 4.16.5-1 due to a
>> change in gfs2_ondisk.h.  Hope there is enough info
>> below for a fix? :)

Can you reproduce it with the master branch? Also, what is the size of 
your test file? And what architecture is this on?

Andy

> Here goes another trace:
> 
> (gdb) run -p lock_nolock -b 512 test
> Starting program: /build/gfs2-utils-7xEZHP/gfs2-utils-3.1.10/gfs2/mkfs/mkfs.gfs2 -p lock_nolock -b 512 test
> This will destroy any data on test
> Are you sure you want to proceed? [y/n] y
> Adding journals: Done
> Building resource groups: Done
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x000055555555bdc0 in brelse (bh=0x555555773730) at buf.c:108
> 108     buf.c: No such file or directory.
> (gdb) bt
> #0  0x000055555555bdc0 in brelse (bh=0x555555773730) at buf.c:108
> #1  0x00005555555599f5 in gfs2_rgrp_relse (rgd=rgd at entry=0x5555557723c0) at rgrp.c:206
> #2  0x000055555555d936 in block_alloc (sdp=sdp at entry=0x7fffffffe560, blksreq=blksreq at entry=1, state=state at entry=3, blkno=blkno at entry=0x7fffffffe160, dinode=dinode at entry=1) at fs_ops.c:197
> #3  0x000055555555df77 in lgfs2_dinode_alloc (sdp=sdp at entry=0x7fffffffe560, blksreq=blksreq at entry=1, blkno=blkno at entry=0x7fffffffe160) at fs_ops.c:204
> #4  0x000055555556128f in build_master (sdp=0x7fffffffe560) at structures.c:28
> #5  0x00005555555574fc in main (argc=<optimized out>, argv=<optimized out>) at main_mkfs.c:996
> 



  reply	other threads:[~2018-05-04 10:06 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 [this message]
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
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=88c04bee-a2d0-0efd-f856-09d7448c0517@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).