Bug 27632 - [util-linux] 2.36.1-1 break fstab cifs mount
Summary: [util-linux] 2.36.1-1 break fstab cifs mount
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-18 20:53 CET by GG HH
Modified: 2020-11-19 12:56 CET (History)
2 users (show)

See Also:
Source RPM: util-linux-2.36.1-3.mga8.src.rpm, cifs-utils-6.11-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description GG HH 2020-11-18 20:53:42 CET
mounting a cifs fs from fstab fails icine util-linux 2.36.1 because of 
https://github.com/karelzak/util-linux/issues/1193

# mount /mnt/nas/dir
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

and in /var/log/messages:
Nov 18 20:52:11 uranus kernel: [2807678.243554] CIFS: Attempting to mount //nas/dir
Nov 18 20:52:11 uranus kernel: [2807678.243581] CIFS: Unknown mount option "symfollow"
GG HH 2020-11-18 20:54:01 CET

CC: (none) => boulshet

Comment 1 Lewis Smith 2020-11-18 21:45:20 CET
Thank you for the report, and the valuable pointer. This indicates:
 util-linux/libmount/src/context_mount.c
The SRPM includes libmount1. It does not look as if cifs-utils is in question.

Other useful follow-on URLs:
 https://www.linuxquestions.org/questions/slackware-14/util-linux-2-36-1-breaks-fuse-sshfs-4175685400/                 [esp #7]
 https://bugs.archlinux.org/task/68660

Assigning to the base system group; CC'ing tv as committer of util-linux 2.36.1.

Source RPM: (none) => util-linux-2.36.1-3.mga8.src.rpm, cifs-utils-6.11-1.mga8.src.rpm
Assignee: bugsquad => basesystem
CC: (none) => thierry.vignaud

Comment 2 David Walser 2020-11-19 02:38:52 CET
Should be fixed in util-linux-2.36.1-4.mga8.

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

Comment 3 GG HH 2020-11-19 12:56:34 CET
i confirm that it solved my issue. Thanks

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