From 8173331150482b78e85c005fcea2c7d80f430f65 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 19 Apr 2012 10:20:27 +0200 Subject: s3: Fix Coverity ID 2747: FORWARD_NULL For the notify cleanup process we have a notify context without a messaging entry. We will never call notify_add/remove for this, but the code should protect against this. --- source3/smbd/notify_internal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source3/smbd/notify_internal.c b/source3/smbd/notify_internal.c index 27fe21214b..aa02e32a2f 100644 --- a/source3/smbd/notify_internal.c +++ b/source3/smbd/notify_internal.c @@ -393,7 +393,7 @@ NTSTATUS notify_remove(struct notify_context *notify, void *private_data) struct db_record *notify_rec; NTSTATUS status; - if (notify == NULL) { + if ((notify == NULL) || (notify->msg == NULL)) { return NT_STATUS_NOT_IMPLEMENTED; } -- cgit