Bug 487362

Summary: cifs: in NT hardlink, target name buffer format byte and pad are swapped
Product: Red Hat Enterprise Linux 5 Reporter: Jeff Layton <jlayton>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: rwheeler, smfltc, staubach, steved
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: cthon09
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-22 18:57:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch -- fix buffer format endianness none

Description Jeff Layton 2009-02-25 16:41:05 UTC 
CIFS testing failed against a netapp server. The server supports unicode. When we format the buffer, the buffer format byte for the second name is ending up in the wrong place. This makes NT renames fail against netapp servers. Wireshark seems to agree that it's our bug and not Netapp's

I did a quick test patch that fixes the problem against that server but I'm not yet sure if it's correct, need to double check the alignment.
Comment 1 Jeff Layton 2009-02-25 16:59:07 UTC 
Created attachment 333179 [details]
patch -- fix buffer format endianness

I believe this is the correct fix. It at least makes this SMB match the format used in SMB rename calls. It also makes wireshark and the netapp happy.
Comment 4 Jeff Layton 2009-04-22 18:57:20 UTC 

*** This bug has been marked as a duplicate of bug 465143 ***