Bug 841113 - CIFS: Unknown mount option "UID=500" - error(22): Invalid argument
Summary: CIFS: Unknown mount option "UID=500" - error(22): Invalid argument
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jeff Layton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-18 08:11 UTC by dwyatt
Modified: 2014-06-18 07:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-18 11:55:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dwyatt 2012-07-18 08:11:23 UTC
Description of problem:
  mount.cifs fails when "UID=500" arg is included


Version-Release number of selected component (if applicable):
  works with kernel-3.3.8-1.fc16.x86_64 and previous, fails with
  kernel-3.4.2-1.fc16.x86_64 and kernel-3.4.4-4.fc16.x86_64


How reproducible:
  always


Steps to Reproduce:
1. invoke mount.cifs with UID=500 option, it fails
2. invoke mount.cifs without UID=500 option, it succeeds

  
Actual results:
  share not mounted


Expected results:
  share mounted


Additional info:
  /etc/fstab entry looks like this:
  //salient/backup01  /mnt/Salient/backup01  cifs  credentials=/root/.smbcredentials,_netdev,UID=500,users,rw	1 1

Comment 1 Jeff Layton 2012-07-18 11:55:05 UTC
"UID=" is not a valid mount option. "uid=" is. In the past, cifs.ko ignored invalid mount options, but that changed in 3.4 kernels.

I'll go ahead and close this as NOTABUG, but feel free to reopen if you want to discuss it further.

Comment 2 dwyatt 2012-07-18 15:32:54 UTC
Confirmed, uid=500 arg to mount.cifs works as it should.  Thanks.
Worth noting, though, is that UID=500, under kernel-3.3.8-1.fc16.x86_64, was not ignored.  In that case, shared files had user_500:root owner:group.  With UID=500 excluded from the mount.cifs options, files were root:root on Win shares.

Comment 3 Jeff Layton 2012-07-18 16:08:06 UTC
Yes, my mistake...

The older mount option parser was case insensitive (ugh), which we couldn't replicate when we moved to the standard kernel option parser. Moving to using the format we advertise in the mount.cifs manpage (lowercase) is still the best option going forward.


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