Bug 487362 - cifs: in NT hardlink, target name buffer format byte and pad are swapped
Summary: cifs: in NT hardlink, target name buffer format byte and pad are swapped
Keywords:
Status: CLOSED DUPLICATE of bug 465143
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jeff Layton
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard: cthon09
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-25 16:41 UTC by Jeff Layton
Modified: 2009-04-22 18:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-22 18:57:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch -- fix buffer format endianness (1.07 KB, patch)
2009-02-25 16:59 UTC, Jeff Layton 		no flags Details | Diff
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.