Age | Commit message (Collapse) | Author | Files | Lines |
|
(This used to be commit 55035b8984c135ddd2c4e3be18caf8833975841d)
|
|
difference to the result.
(This used to be commit 9e28b7220bc293e386fec30c2d2e7e401b61b1f7)
|
|
maths to
(This used to be commit 0ad62f128d1c26b8f7e71bc045c6f4a584f8d374)
|
|
added DENY2 test that checks all 648 deny combinations for the case
of two opens on the same connection
(This used to be commit 01d4c4784dd26bdfc9883907b3170e8b0ea0cd6f)
|
|
(This used to be commit d9c3e0e61f315ad4d9c3ea6bb6acc8500befe6b4)
|
|
I've finally got the access table code right for the case where the
two opens are on the same connection. It is _incredibly_ complex, but
now all 1296 test cases pass.
I'll be very surprised if anyone by MS and us gets this right at
CIFS2000
(This used to be commit 31a5857ce4f03eb53ff8ea96c5f1ce335941336d)
|
|
(This used to be commit d72c98a931ff05a7f8b74b98cd7ebd025a87d249)
|
|
(This used to be commit ab492d46942e9c43e6b61a04f9db75d9fc3f40d6)
|
|
DENY_DOS and DENY_FCB as the same thing anymore (the difference
matters for *.exe files)
(This used to be commit 8f3ff09283db87083a81a943909ae047cdd9e48b)
|
|
*.sym and *.com files. I still find it incredible that SMB treats file
locking differently depending on the file name - that is so ugly it
stinks.
anyway, we now behave the same way as NT, except for the
same-connection case which I'm still working on.
(This used to be commit 5b9be3feca26f1f20fe3f32ba90769cc78f9bb6b)
|
|
bug pointed out by Richard
(This used to be commit 070f49397ff24e4d6ba7c2c1cfaef2dfa0944bd0)
|
|
this is used with "smbstatus -B" to dump the lock list
(This used to be commit 5f022629146701e6d543f77007dc944e4277ab0c)
|
|
(This used to be commit 10d9d81e8b7eba588526a5d479be74ce8f86fc55)
|
|
use string_set() instead, to avoid the bug Richard discovered
(This used to be commit fdcbf6b52d8373bf8f35718a9649788415c23342)
|
|
(This used to be commit 0751a0ea4cdb7f5db0aa6f359dd3e4f744fc0689)
|
|
Bugfix from Marc_Jacobsen@hp.com.
Jeremy.
(This used to be commit eb06c199163232453e2d9ca50d00765c90f8f3e2)
|
|
Jeremy.
(This used to be commit fd8582cc0a751618f4699f435d561f5de54bf7f4)
|
|
Jeremy.
(This used to be commit 4914d2f161b6a82789f3a9decccb636fb21264c5)
|
|
(This used to be commit 77cf152c02b445f4b6e9de393936dd6e54e6f442)
|
|
changed it to "enum brl_type"
(This used to be commit 6b9ee7662c7afa70f6b20889e6b0ae1dcd677f9f)
|
|
the last piece was to use a smb timeout slightly larger than the
locking timeout in bloking locks to prevent a race
(This used to be commit 1b54cb4a33a65e62c2e3189b78ef073869a60c75)
|
|
Jeremy.
(This used to be commit 4fbc7358d21f541b7a6e27f768a88007bf390da5)
|
|
Fixed locking bug found by Andrew.
Jeremy.
(This used to be commit 38dffd360dc2e44bfc9e751f017e24f81ff0f2fa)
|
|
note the ugly global_smbpid - I hope that won't bethere for long, I
just didn't want to do two lots of major surgery at the one time.
Using global_smbpid avoids the big change of getting rid of our
inbuf/outbuf interface to reply routines. I'll do that once the
locking stuff passes all tests.
(This used to be commit f8bebf91abcaa5bda3ec8701f9242f220da8943a)
|
|
- that should be fixed soon.
(This used to be commit 23bb936e1fdeab2ad697ed946c945ef5ce87357d)
|
|
(This used to be commit 44117df2c908d473b3e1a1020b22af6d584809ef)
|
|
it doesn't map to posix locks yet, that will come later.
(This used to be commit 7f2a493095887cb0aae915ac36b9cded71d3a7a7)
|
|
we now don't pass the lock type at all for unlocks.
I was surprised to discover that NT totally ignores the lock type in
unlocks. It unlocks a matching write lock if there is one, otherwise
it removes the first matching read lock.
(This used to be commit 1bbc1ce18b8ccb92b5a78ee648539a591a452118)
|
|
(This used to be commit 6927aa19052baba2dcfcdec7564dad1a17f4c562)
|
|
(This used to be commit 671e52cec2f254a11f9dcef9ef692afa3b86c679)
|
|
as SMB_OFF_T, we need to do some autoconf changes to generate a 64 bit
int whenever possible (eg. long long on 32 bit i386)
(This used to be commit 09dbe8bccec244c8ea0893a7d8ca4fe85d5420f7)
|
|
(This used to be commit 67b7b2a5a68fd22222bd54771c779f752ff59917)
|
|
Jeremy.
(This used to be commit 465c5a830827b82f0535d4507b3432c2df6de658)
|
|
Jeremy.
(This used to be commit 95d37a1d25d56316c80eec54aea1f358cd621d4c)
|
|
Jeremy.
(This used to be commit b0a5ba9e01e71a64c7e693b6bf3f9bd499d3e095)
|
|
Jeremy.
(This used to be commit 6b61f2fe66a62082fdab998ec7bbb1184b9583d7)
|
|
Jeremy.
(This used to be commit 20d72e8959fc800836369e4c970f7cb84b95ac9a)
|
|
Jeremy.
(This used to be commit f5fedf80bce84dba1468631202337077511bcd25)
|
|
is *missing* from samba cvs main, therefore it is set to all zeros.
this will cause, amongst other things, administrator-changing-user-passwords,
and setting up new accounts, to fail, as the user's password can only be
decoded with the session key (in this case, the administrator's usr sess key).
it's never a perfect world, is it?
(This used to be commit 3362fcdfa492cfd1d9d4ec35ef2108192302b984)
|
|
that will make us match NT semantics exactly and do away with the
horrible fd multiplexing in smbd.
this is some diag stuff to get me started.
- added the ability to do read or write locks in clientgen.c
- added a LOCK4 test to smbtorture. This produces a report on the server
and its locking capabilities. For example, NT4 gives this:
the same process cannot set overlapping write locks
the same process can set overlapping read locks
a different connection cannot set overlapping write locks
a different connection can set overlapping read locks
a different pid cannot set overlapping write locks
a different pid can set overlapping read locks
the same process can set the same read lock twice
the same process cannot set the same write lock twice
the same process cannot override a read lock with a write lock
the same process can override a write lock with a read lock
a different pid cannot override a write lock with a read lock
the same process cannot coalesce read locks
this server does strict write locking
this server does strict read locking
whereas Samba currently gives this:
the same process can set overlapping write locks
the same process can set overlapping read locks
a different connection cannot set overlapping write locks
a different connection can set overlapping read locks
a different pid can set overlapping write locks
a different pid can set overlapping read locks
the same process can set the same read lock twice
the same process can set the same write lock twice
the same process can override a read lock with a write lock
the same process can override a write lock with a read lock
a different pid can override a write lock with a read lock
the same process can coalesce read locks
this server does strict write locking
this server does strict read locking
win95 gives this - I don't understand why!
the same process cannot set overlapping write locks
the same process cannot set overlapping read locks
a different connection cannot set overlapping write locks
a different connection cannot set overlapping read locks
a different pid cannot set overlapping write locks
a different pid cannot set overlapping read locks
the same process cannot set the same read lock twice
the same process cannot set the same write lock twice
the same process cannot override a read lock with a write lock
the same process cannot override a write lock with a read lock
a different pid cannot override a write lock with a read lock
the same process cannot coalesce read locks
this server does strict write locking
this server does strict read locking
(This used to be commit 49637936b6e9478df248c4ef73d818870c73b597)
|
|
reply!
(This used to be commit 45b8f1c92cf7ecae35240e72741e5ac952587c58)
|
|
(This used to be commit dd2ce575047eb57288bff11669512132fd347fda)
|
|
now exactly match NT for normal files. We still don't match for *.exe files though
(This used to be commit 3f7fea58e8da6d98acadaabf0498ea2e88ea5678)
|
|
After fixing that I needed to use O_RDWR instead of O_WRONLY in
several places to avoid the silly bug in MS servers that doesn't allow
getattrE on a file opened with O_WRONLY
(This used to be commit e21aa4cb088f348139309d29c85c48c8b777cff5)
|
|
of 324 lines (6*6*3*3) of all possible deny mode behaviour. This
allows us to compare with NT. We currently don't match :)
(This used to be commit 2071105b439e87cb1c7c3a8c1b2046441eb46270)
|
|
(This used to be commit 2a152998a1489dead0edadb06f78b0ad6ede1a3a)
|
|
(This used to be commit eeb9482f0816558f22e47b1ea4c4272453d467ac)
|
|
smbd/negprot.c: Tidyup of static initializers.
smbd/server.c: Fix -l option.
Jeremy.
(This used to be commit d120f22fefde21b38e43ea5ad0180bf27304d2eb)
|
|
: If a file is resident on NT and the first user opens it read/write with DENY_READ then a subsequent
: attempt by a second user (running under Windows 95) to open it read/write DENY_NONE fails.
: Under samba 2.0.5a the second open succeeds but the file is write only.
Jeremy.
(This used to be commit 974af581fe428fd0233c2516b16a5132b0e1b583)
|
|
(This used to be commit 32f29c490e6265c8a383ce771943f937c49bfabc)
|