Age | Commit message (Collapse) | Author | Files | Lines |
|
the merged variant is renamed to smb_msleep as some platforms already have a
msleep function.
|
|
|
|
MS-CIFS 2.2.7.4.2 states that FILE_NOTIFY_INFORMATION structures in
change notify replies must be aligned to 4-byte boundaries.
This updates s4 client to check for this restriction and also adds a
torture test which should tickle a server into giving unaligned
structures if it doesn't follow the spec.
|
|
Upstream subunit makes a ":" after commands optional, so I've fixed any
places where we might trigger commands accidently. I've filed a bug
about this in subunit.
|
|
This reduces compile time somewhat.
|
|
In order to implement root_fid in the s4 SMB server we need to declare
it as a handle type, just as for other fnum values in SMB. This
required some extensive (but simple) changes in many bits of code.
|
|
|
|
The Samba3 internal notify code doesn't work correctly when there is
more than one tree connect to the same smbd process. This change to
the RAW-NOTIFY test triggers the bug.
|
|
* This adds a test to check the change notify behavior of the SMB server
when more events have been generated than can be returned in a single
change notify response.
* Second test makes sure the server doesn't return notification events
for changes to the watched directory itself
|
|
|
|
Jeremy.
|
|
particular tests start.
Jeremy.
|
|
(This used to be commit 47ffbbf67435904754469544390b67d34c958343)
|
|
(This used to be commit 80a61200508a00d5b16a3e748ce92d54b9fefcd2)
|
|
uses of global_loadparm.
(This used to be commit a33a5530545086b81a3b205aa109dff11c546926)
|
|
(This used to be commit 566aa14139510788548a874e9213d91317f83ca9)
|
|
(This used to be commit fd697d77c9fe67a00939a1f04b35c451316fff58)
|
|
number in more places.
(This used to be commit df9cebcb97e20564359097148665bd519f31bc6f)
|
|
(This used to be commit abe8349f9b4387961ff3665d8c589d61cd2edf31)
|
|
(This used to be commit 08bb1ef643ab906f1645cf6f32763dc73b1884e4)
|
|
(This used to be commit 1319d88c099496be29dd9214fa2492c81e848369)
|
|
There are still a few tidyups of old FSF addresses to come (in both s3
and s4). More commits soon.
(This used to be commit fcf38a38ac691abd0fa51b89dc951a08e89fdafa)
|
|
on an open directory handle, is never changed. (He's right btw :-).
Jeremy.
(This used to be commit bf9242ad4561239fbc6e05c6879726f0df202f56)
|
|
might take a bit for events to propagate from one to another connection,
in particular with a process per connection.
(This used to be commit 0c7a518b2dad83dc78f3e3058fd8e1267d0e928f)
|
|
It seems most opertaions are supported, but that the values are not
consistant. I think these are very much hand-hacked stubs, which is
what they will be on Samba4 too.
I'll need to add some more 'don't fail for...' hacks before this
passes against Win2k3.
Andrew Bartlett
(This used to be commit dcb858d0c716b23be6c5d36b4aa6f155582ada63)
|
|
(This used to be commit f5b2011db9b05fcca82f6a6b3976aa1b4924b0a8)
|
|
(This used to be commit 12ce85aea16379b9946851806c1782272ee1c48f)
|
|
acceptable.
In Samba3 with inotify we have the problem that the MODIFIED action is sent
second. I think this could also happen in Samba4, depending on the order when
the different sockets (unix domain dgram / inotify) are looked at by the
events system.
This patch accepts the NEW/OLD/MODIFIED entries in any order.
Comments welcome!
Volker
(This used to be commit 72a7771b757c3aca637eb632abebab60bdd2da9f)
|
|
Volker
(This used to be commit c9886ce63b8cc085e0032ad2f6193c547336856d)
|
|
(This used to be commit 39458e62f576c551df016a7be4d35175dc21696e)
|
|
RAW-NOTIFY test.
(This used to be commit 81fd19ba3f38ac19d8bcac56210a83fdfc8237de)
|
|
metze
(This used to be commit 49b96ac44a883c020c69df7a12df154dc4faa4d5)
|
|
notify request
metze
(This used to be commit d90313f715e999bb925a154b8431c77638a19a50)
|
|
RAW_NOTIFY_NTTRANS,RAW_NOTIFY_SMB2
- parse SMB2 Notify reponse
metze
(This used to be commit de50e0ccddfad16ad7b254770f4c52c1abe707b9)
|
|
enable the
unclist parameter for all tests that do two connections, to enable cluster
testing.
Volker
(This used to be commit a5d6db09244d444986f8fded3fc6e72c74c8ca1f)
|
|
of events to propogate internally in smbd before asking for them
(the test was failing on slow machines)
(This used to be commit a493539458ff092262667d07b0dab2f2ee1ba7bf)
|
|
per-depth bisection search. This makes the notify_trigger() call
log(N) which makes us scale well for large numbers of outstanding
notifies
(This used to be commit 16fd00925fdbf77e7a403ad501bf6ea429404c76)
|
|
backend
(This used to be commit b80523a631ec57c7d19e9a23dca4594d71036138)
|
|
be more forgiving of matching on extra bits (inotify cannot match on
minimal bits for all events).
(This used to be commit 29de884737ada8c1094b6e0958b54f523a7cdbf4)
|
|
(This used to be commit 659576806fef066203551281cab4dc5cd3234ff7)
|
|
try each bit in the completion filter separately for a wide range of
file operations.
(This used to be commit 81f8b24526515d7a914022859fb03421c3a7611b)
|
|
on a directory handle
(This used to be commit b6e40d9b0832fbab662f9289a30c26e2576b4821)
|
|
(This used to be commit e6abb1ecbaa19e8b4627a279e420f8ecdf776e26)
|
|
handle that already has a notify request pending. It turns out that
they are queued
(This used to be commit 15e9302bcd20a91446b19033333b743f1d257a66)
|
|
(This used to be commit 3c7a5ce29108dd82210dc3e1f00414f545949e1d)
|
|
triggers an empty notify reply with NT_STATUS_OK
metze
(This used to be commit 590dd49207342031fed902701f4214f3b1d6397c)
|
|
(This used to be commit 1e1c5593817e84c59c1a10b5a3c1957e363e5198)
|
|
(This used to be commit 863ca4014d9b821706ee90f58ab5d5cf3899a4c7)
|
|
metze
(This used to be commit 74868726ae4fd8010c2e10d2f300b9725ca7ab33)
|
|
other event
- test mkdir - rmdir - mkdir - rmdir sequence, this gets 4 notify events back
- add some comments to the multiple directory handle and buffered cases
metze
(This used to be commit e2b3816212b9c209d9f74f87c5cd72ca0d38c2e6)
|