Bug 1380383

Summary: CIFS VFS: cifs_mount failed w/return code = -2 with kernel-4.7.4-200.fc24.x86_64
Product: [Fedora] Fedora Reporter: falke1337
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 17:14:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description falke1337 2016-09-29 12:35:44 UTC 
Description of problem:
After upgrading from kernel 4.6.7-300 to 4.7.4-200 my cifs mounts no longer works.

The mount itself seems successfull, but dmesg tells me the following:
CIFS VFS: cifs_mount failed w/return code = -2

and when I try to list the directory, I get this error:
ls: das Verzeichnis '/mnt/foo/bar/' wird gelesen: Object is remote



Version-Release number of selected component (if applicable):
- Fedora 24
- kernel-4.7.4-200.fc24.x86_64 (problem)
- kernel-4.6.7-300.fc24.x86_64 (working)
- cifs-utils-6.6-1.fc24.x86_64


How reproducible:


Steps to Reproduce:
1. Install kernel-4.7.4-200.fc24.x86_64
2. ount a Windows share which is located on a domain wide fileserver with DFS enabled (with mount.cifs -o username=XXX,password=XXX,domain=XXX.XX,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 //SERVER/foo/bar /mnt/foo/bar
3. try to ls the content of the mountpoint

Actual results:
# ls /mnt/foo/bar
ls: das Verzeichnis '/mnt/foo/bar/' wird gelesen: Object is remote
insgesamt 0


Expected results:
List of files on this share


Additional info:
Starting the older kernel (4.6.7-300) resolves the issue.
Comment 1 Justin M. Forbes 2017-04-11 14:42:42 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 2 Justin M. Forbes 2017-04-28 17:14:06 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.