Bug 487207

Summary: cifs: open-file renames require that FH should be opened with SYNCHRONIZE bit set
Product: Red Hat Enterprise Linux 5 Reporter: Jeff Layton <jlayton>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: 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-03-04 14:16:57 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:

Description Jeff Layton 2009-02-24 19:13:57 UTC
Discovered while testing at connectathon. When testing busy file rename code, the test would fail against bluearc servers. The bluearc guys turned on tracing and determined that it was failing because the SYNCHRONIZE bit wasn't being set on open.

Testing with that bit set seems to fix it against their servers. We'll need to test more extensively, but they claimed that win2k also requires it (there were some comments in their code to that effect).

Comment 1 Jeff Layton 2009-03-04 14:16:57 UTC
It turns out that this is actually a bug in BlueArc's stuff. The MS docs explicitly state that SYNCHRONIZE should not be set by clients and should be ignored by servers. I think it really only has meaning in opens on local filesystems.

I've contacted bluearc to let them know that we think this is a bug in their server code.