Bug 18591 - Update request: davfs2 to 1.5.4
Summary: Update request: davfs2 to 1.5.4
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL: http://savannah.nongnu.org/projects/d...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-31 05:50 CEST by Curtis Hildebrand
Modified: 2017-02-05 03:23 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Curtis Hildebrand 2016-05-31 05:50:25 CEST
Please update davfs2 to the latest version 1.5.4.  I suspect I've encountered the bugs that it fixes.

From the update description:
Just after releasing 1.5.3 two important bugs showed up that needed fixing.
- mount.davfs frequently reads /proc/mounts. This is necessary with coda but not with fuse. When running two instances of mount.davfs using fuse these reads may trigger a kernel bug and create a deadlock.
- when mount.davfs receives SIGTERM it stops reading from the fuse device. In this case kernel fuse will make umount(8) hang forever.
Both bugs are fixed in release 1.5.4.
Comment 1 Marja Van Waes 2016-05-31 19:11:56 CEST
(In reply to Curtis Hildebrand from comment #0)
> Please update davfs2 to the latest version 1.5.4.  I suspect I've
> encountered the bugs that it fixes.
> 
> From the update description:
> Just after releasing 1.5.3 two important bugs showed up that needed fixing.
> - mount.davfs frequently reads /proc/mounts. This is necessary with coda but
> not with fuse. When running two instances of mount.davfs using fuse these
> reads may trigger a kernel bug and create a deadlock.
> - when mount.davfs receives SIGTERM it stops reading from the fuse device.
> In this case kernel fuse will make umount(8) hang forever.
> Both bugs are fixed in release 1.5.4.

This sounds valid for a freeze push, assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => shlomif

Comment 2 Curtis Hildebrand 2017-02-05 03:23:55 CET
Update was done July, 2016

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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