Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1710968 - umount.davfs Program received signal SIGSEGV, Segmentation fault (core dumped)
Summary: umount.davfs Program received signal SIGSEGV, Segmentation fault (core dumped)
Keywords:
Status: CLOSED DUPLICATE of bug 1736871
Alias: None
Product: Fedora
Classification: Fedora
Component: davfs2
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Filipe Rosset
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-16 16:16 UTC by markusN
Modified: 2019-12-18 15:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-18 15:06:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description markusN 2019-05-16 16:16:50 UTC
Description of problem:

Unmounting a DAVFS2 network directory leads to segfault:

# fstab
cat /etc/fstab | grep /media/mundialis_projekte
https://mundialis-alfresco.xxxx.de/alfresco/webdav/projekte /media/mundialis_projekte davfs user,noauto 0 0

# the mounted dir
mount | grep /media/mundialis_projekte
https://mundialis-alfresco.xxxx.de/alfresco/webdav/projekte on /media/mundialis_projekte type fuse (rw,nosuid,nodev,noexec,relatime,user_id=1001,group_id=1001,allow_other,max_read=16384,uid=1001,gid=1001,user=mneteler,helper=davfs)

# trying to unmount it:
umount.davfs /media/mundialis_projekte
Segmentation fault (core dumped)

# version
rpm -qf /usr/sbin/umount.davfs
davfs2-1.5.4-9.fc30.x86_64

# debugging
sudo dnf debuginfo-install davfs2-1.5.4-9.fc30.x86_64

gdb umount.davfs 
GNU gdb (GDB) Fedora 8.3-1.fc30
...
Reading symbols from umount.davfs...
Reading symbols from /usr/lib/debug/usr/sbin/umount.davfs-1.5.4-9.fc30.x86_64.debug...
(gdb) r /media/mundialis_projekte
Starting program: /usr/sbin/umount.davfs /media/mundialis_projekte
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments

Program received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
65		VPCMPEQ (%rdi), %ymm0, %ymm1
Missing separate debuginfos, use: dnf debuginfo-install pakchois-0.4-19.fc30.x86_64
(gdb) bt full
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
No locals.
#1  0x00007ffff7f66588 in count_concat (ap=0x7fffffffced0) at ne_string.c:132
        total = 0
        next = 0x46128800 <error: Cannot access memory at address 0x46128800>
        total = <optimized out>
        next = <optimized out>
#2  ne_concat (str=0x555555556095 "ps -p ") at ne_string.c:179
        ap = {{gp_offset = 16, fp_offset = 0, overflow_arg_area = 0x7fffffffcf50, reg_save_area = 0x7fffffffcef0}}
        total = <optimized out>
        slen = 6
        ret = <optimized out>
#3  0x0000555555555608 in main (argc=<optimized out>, argv=0x7fffffffd098) at umount_davfs.c:163
        short_options = 0x55555555601d "Vhflnrt:v"
        options = {{name = 0x5555555560a0 "version", has_arg = 0, flag = 0x0, val = 86}, {name = 0x5555555560a8 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x0, 
            has_arg = 0, flag = 0x0, val = 0}}
        o = <optimized out>
        mpoint = <optimized out>
        umount_command = 0x0
        m = <optimized out>
        mp = <optimized out>
        pidfile = 0x55555556d6c0 "/var/run/mount.davfs/media-mundialis_projekte.pid"
        pid = 0x46128800 <error: Cannot access memory at address 0x46128800>
        file = 0x555555559260
        ps_command = <optimized out>
        ps_in = <optimized out>
        found = <optimized out>
        n = 140737345544448
        ps_line = 0x7ffff77cff54 <std::ios_base::Init::_S_refcount> "\003"


cat /var/run/mount.davfs/media-mundialis_projekte.pid
9378

uname -a
Linux oboe.mundialis 5.0.14-300.fc30.x86_64 #1 SMP Thu May 9 10:43:38 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

# /proc/cpuinfo
model name	: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz

I upgraded the machine from F29 to F30 last week, so the DAVFS stuff is identical and worked with F29. 

At time I cannot unmount DAVFS2 directories any more...

Comment 1 Filipe Rosset 2019-08-05 04:20:56 UTC
I updated davfs2 to 1.5.5 for F31+

Let me know if its working fine for you, so I can go ahead and upgrade also for F30/F29 and maybe EPEL.

https://src.fedoraproject.org/rpms/davfs2/c/b5daac4efa37402af756931cd75ac5bb59ca214a?branch=master

https://koji.fedoraproject.org/koji/taskinfo?taskID=36799564

Comment 2 mathias.habluetzel 2019-08-29 17:08:56 UTC
I installed your proposed davfs2 1.5.5 on F30 and it still crashed.

$ uname -a
Linux hostname 5.2.9-200.fc30.x86_64 #1 SMP Fri Aug 16 21:37:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ sudo gdb umount.davfs
GNU gdb (GDB) Fedora 8.3-6.fc30
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from umount.davfs...
Reading symbols from /usr/lib/debug/usr/sbin/umount.davfs-1.5.5-1.fc31.x86_64.debug...
(gdb) r /home/me/nextcloud
Starting program: /usr/sbin/umount.davfs /home/me/nextcloud
Missing separate debuginfos, use: dnf debuginfo-install glibc-2.29-15.fc30.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7f012b5 in __strlen_avx2 () from /lib64/libc.so.6
Missing separate debuginfos, use: dnf debuginfo-install expat-2.2.7-1.fc30.x86_64 keyutils-libs-1.6-2.fc30.x86_64 krb5-libs-1.17-14.fc30.x86_64 libcom_err-1.44.6-1.fc30.x86_64 libgcc-9.1.1-1.fc30.x86_64 libmodman-2.0.1-19.fc30.x86_64 libproxy-0.4.15-13.fc30.x86_64 libselinux-2.9-1.fc30.x86_64 libstdc++-9.1.1-1.fc30.x86_64 neon-0.30.2-10.fc30.x86_64 openssl-libs-1.1.1c-2.fc30.x86_64 pakchois-0.4-19.fc30.x86_64 pcre2-10.33-10.fc30.x86_64 zlib-1.2.11-17.fc30.x86_64
(gdb) bt full
#0  0x00007ffff7f012b5 in __strlen_avx2 () from /lib64/libc.so.6
No symbol table info available.
#1  0x00007ffff7f7d588 in ne_concat () from /lib64/libneon.so.27
No symbol table info available.
#2  0x000055555555560b in main (argc=<optimized out>, argv=0x7fffffffe4b8) at umount_davfs.c:163
        short_options = 0x55555555601d "Vhflnrt:v"
        options = {{name = 0x5555555560a0 "version", has_arg = 0, flag = 0x0, val = 86}, {name = 0x5555555560a8 "help", has_arg = 0, flag = 0x0, 
            val = 104}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
        o = <optimized out>
        mpoint = <optimized out>
        umount_command = <optimized out>
        m = <optimized out>
        mp = <optimized out>
        pidfile = 0x55555556d090 "/var/run/mount.davfs/home-me-nextcloud.pid"
        pid = 0x45f8c000 <error: Cannot access memory at address 0x45f8c000>
        file = 0x55555556d0d0
        ps_command = <optimized out>
        ps_in = <optimized out>
        found = <optimized out>
        n = 140737345634560
        ps_line = 0x7ffff77e5f54 "\003"

Comment 3 mathias.habluetzel 2019-09-02 12:18:06 UTC
Apparently it would be sufficient to compile davfs2 with the -std=c89 switch:

https://forums.gentoo.org/viewtopic-p-8333376.html#8333376

Comment 4 Felix Schwarz 2019-11-28 09:37:27 UTC
(In reply to mathias.habluetzel from comment #3)
> Apparently it would be sufficient to compile davfs2 with the -std=c89 switch:
> 
> https://forums.gentoo.org/viewtopic-p-8333376.html#8333376

Mathias: Did you try to rebuild davfs2 with that change?

@everyone: I could create a COPR pretty quickly and push an updated build IF there are some testers who are willing to try these builds. Please reply here if you are interested.

Comment 5 Felix Schwarz 2019-11-28 09:50:46 UTC
I think this bug could become a duplicate of bug 1736871 (or the other way round).

Until that is done I'll just copy my comment to keep everyone updated (https://bugzilla.redhat.com/show_bug.cgi?id=1736871#c21):

quoting upstream's Werner Baumann https://savannah.nongnu.org/bugs/?56286#comment5
> The bug is fixed in the CVS-sources. I intend to do a bugfix release soon, but first want to fix at least one other bug. 

Maybe it is the easiest thing to wait a bit more or someone would have to extract the patch from CVS (*shudder*) so Fedora could ship that one on top of 1.5.5.

Comment 6 Felix Schwarz 2019-12-18 15:02:55 UTC
I talked to the upstream developer: A bugfix release is expected to be released within two weeks. I'll try to get this into Fedora shortly afterwards but I could use some testers (you'll be notified in this bug about a new update in updates-testing).

Comment 7 Felix Schwarz 2019-12-18 15:06:43 UTC
likely a duplicate of bug 1736871 - trying to keep the discussion in one place.

*** This bug has been marked as a duplicate of bug 1736871 ***


Note You need to log in before you can comment on or make changes to this bug.