| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | | |
Guenther
|
| | | |
| | | |
| | | |
| | | | |
Guenther
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This should fix the build on some hosts.
metze
|
| | | |
| | | |
| | | |
| | | | |
Pair programmed over the phone with Andrew :-)
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The short-to-long name canonicalisation rules use the schema, so
clearly they won't work when loading it.
Andrew Bartlett
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was missed in the earlier work to use this in provision-backend
Andrew Bartlett
|
|\ \ \ \
| | |/ /
| |/| | |
|
| | |/
| |/| |
|
| | | |
|
| | |
| | |
| | |
| | | |
I think we eventually need to pass down the debuglevel here.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Callers can use it instead of tevent_req_callback_data()
if they use a non talloc private pointer.
metze
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This function can be called as last action of a _recv()
function, it destroys the data attached to the tevent_req.
metze
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Extended operations return was not going thorugh the same patch as others
leaving the ctx around. Plus we were neutralizing the spy too early so that it
didn't set the request_terminated flag as it should have.
This should hopefully fix the failures in the build farm.
|
| | |
| | |
| | |
| | | |
metze
|
| | |
| | |
| | |
| | | |
metze
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There were the following problems:
1.) if window_size was a multiple of the chunk_size,
we silently dropped the last truncated chunk.
2.) if window_size was 0 pushed only the first chunk
to the server and silently dropped the rest.
3.) we had only transferred state->num_reqs writes,
even if there would be more data to send.
metze
|
| | |
| | |
| | |
| | | |
metze
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The change notify code registered a separate message handler for each
tree connect. This registration uses the global messaging context.
The messaging code would consider a 2nd registration for the same
messaging type as being an 'update' of the handler, rather than a new
handler. It also would only call the first handler in the linked list
for a given message type when dispatching messages.
This patch changes the messaging code to allow for multiple
registrations of the same message type, and allow for multiple calls
to different messaging handler for one incoming message.
This fixes the problem with the test_notify_tcon() test that I
recently committed to the S4 smbtorture
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In some code paths ltdb_context was still referenced even after we were returned
an error by one of the callbacks. Because the interface assumes that once an
error is returned the ldb_request may be freed, and because the ltdb_context was
allocated as a child of the request, this might cause access to freed memory.
Allocate the ltdb_context on ldb, and keep track of what's going on with the
request by adding a spy children on it. This way even if the request is freed
before the ltdb_callback is called, we will safely free the ctx and just quietly
return.
|
|\| | |
|
| | | |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Karolin
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
That is part of the fix for bug #6144.
Thanks to Diego Remolina dijuremo [at] gatech [dot] edu for reporting!
Karolin
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
libreplace always provides the getifaddr() function.
This fixes the build on sles8.
metze
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The internal structure of in6_addr isn't always the same.
metze
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
is ipv4
We only do this if the socket isn't explicit bound yet.
metze
|
| | | |
| | | |
| | | |
| | | | |
metze
|
| | | |
| | | |
| | | |
| | | | |
metze
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Unless higher levels queue themselves somehow, writev will *always* be queued.
So the queueing should be done at the right level.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
if we have LIB_PATH_VAR we should use it, otherwise we'll unobtrusively
complain about not having it and use the most likely LD_LIBRARY_PATH.
Signed-off-by: Jelmer Vernooij <jelmer@samba.org>
|
| | | | |
|
|\ \ \ \
| | |/ /
| |/| | |
|
| | | | |
|
| | | | |
|