Alex,
Just for a sanity check, can you try rebuilding without this 7.2.2 patch:
commit 11eceac4ef54e9bf7d64ce3c96a7454aeb126fd8
Author: Dave Anderson <anderson(a)redhat.com>
Date: Fri Apr 20 14:37:52 2018 -0400
Fixes to address several gcc-8.0.1 compiler warnings that are generated
when building with "make warn". The warnings are all false alarm
messages of type [-Wformat-overflow=], [-Wformat-truncation=] and
[-Wstringop-truncation]; the affected files are extensions.c, task.c,
kernel.c, memory.c, remote.c, symbols.c, filesys.c and xen_hyper.c.
(anderson(a)redhat.com)
It does modify some buffer sizes used by the mount command.
Thanks,
Dave
----- Original Message -----
Well, stepping in GDB line-by-line I can see that we segfault at
#1594 in
filesys.c
1588 if (!one_vfsmount)
(gdb)
1589 FREEBUF(mntlist);
(gdb)
1590 if (VALID_STRUCT(mount))
(gdb)
1593 FREEBUF(vfsmount_buf);
(gdb)
1594 FREEBUF(super_block_buf);
(gdb)
1595 }
(gdb)
0x0000000000000000 in ?? ()
That is, there is definitely memory corruption somewhere and 'mount' is most
probably just a victim.
Alex
On 2018-05-17 09:36 AM, Alex Sidorenko wrote:
crash> mount
VFSMOUNT SUPERBLK TYPE DEVNAME DIRNAME
ffff88101c916080 ffff88081c837400 rootfs rootfs /
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
Python Exception <type 'exceptions.ImportError'> No module named
gdb.frames:
#0 0x0000000000000000 in ?? ()
#1 0x0000000000000000 in ?? ()
--
Alex Sidorenko Expert Technologist
ERT Linux HPE Pointnext asid(a)hpe.com +1 514-941-8030 Mobile
2344 Boulevard Alfred Nobel, Saint-Laurent, QC, Canada
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility