Author: jra Date: 2004-06-30 01:34:55 +0000 (Wed, 30 Jun 2004) New Revision: 1303
Modified: trunk/source/smbd/open.c Log: Turns out non-io opens that cause oplock breaks are a *different* set of desired access flags from those that cause sharing violations. Oplock breaks are caused by : ~(SYNCHRONIZE_ACCESS|FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES) Sharing violations are caused by : ~(SYNCHRONIZE_ACCESS|READ_CONTROL_ACCESS|FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES) We now pass the torture rename test again. I still need to work out if subsequent opens will cause sharing violations with an existing open mode of SYNCHRONIZE_ACCESS|READ_CONTROL_ACCESS|FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES; Jeremy. WebSVN: http://websvn.samba.org/websvn/changeset.php?rep=samba&path=/&rev=1303&nolog=1
