summaryrefslogtreecommitdiff
path: root/source3/smbd/service.c
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2004-06-30 01:35:01 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 10:52:05 -0500
commit57c07e27853442e95e19c7f746ef1f4681bda48a (patch)
tree868d1b640fcbe2469884ef78325d9924b31db74d /source3/smbd/service.c
parentb04c782281bcb6a9b13168dacdae59898dd9fe7f (diff)
downloadsamba-57c07e27853442e95e19c7f746ef1f4681bda48a.tar.gz
samba-57c07e27853442e95e19c7f746ef1f4681bda48a.tar.bz2
samba-57c07e27853442e95e19c7f746ef1f4681bda48a.zip
r1304: 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. (This used to be commit 38002bfc1c0981a2dba3f2319624c1ef055a3648)
Diffstat (limited to 'source3/smbd/service.c')
0 files changed, 0 insertions, 0 deletions