Bug 11410 - [71825.497337] CIFS VFS: search entry ffff8805ecade384 began after end of SMB ffff8805eca938dc old entry ffff8805eca92384
Summary: [71825.497337] CIFS VFS: search entry ffff8805ecade384 began after end of SMB...
Status: NEW
Alias: None
Product: CifsVFS
Classification: Unclassified
Component: kernel fs (show other bugs)
Version: 3.x
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Steve French
QA Contact: cifs QA contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-23 07:35 UTC by Johann Fock
Modified: 2020-07-16 00:12 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johann Fock 2015-07-23 07:35:02 UTC
I am Using RHEL 7.1
Since i have increase the mounted Windows Partition i get teh following
error 
[71789.175641] CIFS VFS: past SMB end,  num to fill 150 i 95
[71789.175766] CIFS VFS: search entry ffff8805e9b4a3b2 began after end of SMB ffff8805e940b884 old entry ffff8805e940a384
[71791.129342] CIFS VFS: bad search response length 30241705 past smb end
[71791.129393] CIFS VFS: search entry ffff88055e17a9b2 began after end of SMB ffff88055dacbe00 old entry ffff88055daca940
[71791.129523] CIFS VFS: search entry ffff88055e17a9b2 began after end of SMB ffff88055dacbe00 old entry ffff88055daca940
[71799.739427] CIFS VFS: bad search response length 3014729 past smb end
[71799.741519] CIFS VFS: search entry ffff880a7ac527ab began after end of SMB ffff8809c29b3e40 old entry ffff8809c29b0cf0
[71799.743729] CIFS VFS: search entry ffff880a7ac527ab began after end of SMB ffff8809c29b3e40 old entry ffff8809c29b0cf0
[71825.492392] CIFS VFS: bad search response length 30131302 past smb end
[71825.494862] CIFS VFS: bad search response length 30316552 past smb end
Mount options
mount.cifs //172.16.10.92/FZ$ /mnt1/FZ -o sec=ntlmssp -o user=abas,pass=asdFgh1,dom=jwfroehlich,uid=erp,gid=users,iocharset=utf8
Comment 1 Steve French 2015-07-23 12:57:02 UTC
Does it fail with mount option vers=3.0?

Do you have a wireshark trace of the failure so we can verify that it is a malformed response from the server not a client bug.