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 1762083 - davfs2 crashes on umount
Summary: davfs2 crashes on umount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: davfs2
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Felix Schwarz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 00:49 UTC by Artem S. Tashkinov
Modified: 2020-01-12 01:41 UTC (History)
2 users (show)

Fixed In Version: davfs2-1.5.6-1.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-12 01:41:58 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Artem S. Tashkinov 2019-10-16 00:49:59 UTC 
Description of problem: while trying to unmount a davfs filesystem davfs crashes


Version-Release number of selected component (if applicable): davfs2-1.5.4-9.fc30.x86_64


How reproducible: always


systemd-coredump[1456]: Process 1454 (umount.davfs) of user 1000 dumped core.
                                           
                                           Stack trace of thread 1454:
                                           #0  0x00007f1ec9a425e5 __strlen_avx2 (libc.so.6)
                                           #1  0x00007f1ec9abe588 ne_concat (libneon.so.27)
                                           #2  0x000055b5dfc0c608 n/a (umount.davfs)
                                           #3  0x00007f1ec9909f43 __libc_start_main (libc.so.6)
                                           #4  0x000055b5dfc0ca3e n/a (umount.davfs)


Gentoo users have already found this bug and it could be solved by using -std=c89 compilation flag

https://forums.gentoo.org/viewtopic-p-8331344.html?sid=86512aac8febf8259dee6fcee5bf1345
Comment 1 Artem S. Tashkinov 2019-10-16 00:51:41 UTC 
It's a dupe of bug 1710968 however I am curious why it hasn't yet been solved.
Comment 2 Artem S. Tashkinov 2019-10-16 00:52:58 UTC 
Hopefully a barrage of emails will force the fedora developer responsible for this component to finally fix this error for good.
Comment 3 Artem S. Tashkinov 2019-10-16 00:54:03 UTC 
The original bug report was filed on 2019-05-16 16:16:50 UTC, i.e. FIVE MONTHS AGO.

What is going on?
Comment 4 Artem S. Tashkinov 2019-10-16 00:55:29 UTC 
This is yet another comment to attract a modicum of attention.
Comment 5 Artem S. Tashkinov 2019-10-16 00:56:19 UTC 
Hopefully six emails are going to be enough to force someone do something.
Comment 6 Felix Schwarz 2019-11-28 09:26:39 UTC 
Artem: I'm sorry that nobody reacted on your bug report - though I can not help directly. As you noted this is likely the same issue as bug 1710968 you should close it as such. Keeping duplicate bug reports around does not help anyone. Actually the chance of getting a reaction is higher if you keep the communication in one place.

However there is something you do to get this fixed:
1. Try davfs2 1.5.5 (F31 though) which Filipe Rosset created as a response to bug 1736871.

2. The other reporter indicated that unmounting still does not work. If you experience the same issue this is how you can help:
   - file a *support* ticket upstream: http://savannah.nongnu.org/support/?group=davfs2
   - once upstream has confirmed the issue/has committed a fix please ask upstream to release a new version and get back to use so we can push a new version to Fedora.

Unfortunately Fedora maintainers often do not have the time to debug upstream bugs (though I can't speak for Filipe). I hope you can understand that most of us would like to do more but this is only a volunteer activity...

Thank you for helping Fedora :-)
Comment 7 Felix Schwarz 2019-11-28 09:39:08 UTC 
btw: please check https://bugzilla.redhat.com/show_bug.cgi?id=1710968#c4 if you are willing to try a test build.
Comment 8 Felix Schwarz 2019-12-18 15:04:37 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 9 Fedora Update System 2019-12-28 10:31:48 UTC 
FEDORA-2019-d2b5b244ee has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d2b5b244ee
Comment 10 Felix Schwarz 2019-12-28 10:36:19 UTC 
Please try the linked update from the updates-testing repo and give karma if this update fixes the bug for you.
Comment 11 Fedora Update System 2020-01-04 22:23:36 UTC 
davfs2-1.5.6-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d2b5b244ee
Comment 12 Fedora Update System 2020-01-12 01:41:58 UTC 
davfs2-1.5.6-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.