[SCM] Samba Shared Repository - branch v3-3-test updated - release-3-2-0pre2-5050-g89e340e

[Volker Lendecke]

The branch, v3-3-test has been updated
       via  89e340e09fbdc375c0aa85506add525b8ba5dcd0 (commit)
      from  391a391a8bc57f59af627f676d2a507d46bd0832 (commit)

http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-3-test


- Log -----------------------------------------------------------------
commit 89e340e09fbdc375c0aa85506add525b8ba5dcd0
Author: Andrew Tridgell <tridge at samba.org>
Date:   Tue Mar 10 16:45:45 2009 +1100

    fixed a bug in message handling for code the change notify code
    
    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

-----------------------------------------------------------------------

Summary of changes:
 source/lib/messages.c |   18 ++++++++++++++++--
 1 files changed, 16 insertions(+), 2 deletions(-)


Changeset truncated at 500 lines:

diff --git a/source/lib/messages.c b/source/lib/messages.c
index f5933ca..6395cb6 100644
--- a/source/lib/messages.c
+++ b/source/lib/messages.c
@@ -278,7 +278,15 @@ NTSTATUS messaging_register(struct messaging_context *msg_ctx,
 	 */
 
 	for (cb = msg_ctx->callbacks; cb != NULL; cb = cb->next) {
-		if (cb->msg_type == msg_type) {
+		/* we allow a second registration of the same message
+		   type if it has a different private pointer. This is
+		   needed in, for example, the internal notify code,
+		   which creates a new notify context for each tree
+		   connect, and expects to receive messages to each of
+		   them. */
+		if (cb->msg_type == msg_type && private_data == cb->private_data) {
+			DEBUG(5,("Overriding messaging pointer for type %u - private_data=%p\n",
+				  (unsigned)msg_type, private_data));
 			cb->fn = fn;
 			cb->private_data = private_data;
 			return NT_STATUS_OK;
@@ -309,6 +317,8 @@ void messaging_deregister(struct messaging_context *ctx, uint32_t msg_type,
 		next = cb->next;
 		if ((cb->msg_type == msg_type)
 		    && (cb->private_data == private_data)) {
+			DEBUG(5,("Deregistering messaging pointer for type %u - private_data=%p\n",
+				  (unsigned)msg_type, private_data));
 			DLIST_REMOVE(ctx->callbacks, cb);
 			TALLOC_FREE(cb);
 		}
@@ -354,7 +364,11 @@ void messaging_dispatch_rec(struct messaging_context *msg_ctx,
 		if (cb->msg_type == rec->msg_type) {
 			cb->fn(msg_ctx, cb->private_data, rec->msg_type,
 			       rec->src, &rec->buf);
-			return;
+			/* we continue looking for matching messages
+			   after finding one. This matters for
+			   subsystems like the internal notify code
+			   which register more than one handler for
+			   the same message type */
 		}
 	}
 	return;


-- 
Samba Shared Repository