s3:smbd:vfs_acl: fix a PANIC when setting an ACL fails with ACCESS_DENIED

Omission to free the talloc frame causes a panic (at least in developer mode)
in the next main event loop due to "Frame not freed in order."
(Freed frame ../source3/smbd/process.c:3617, expected ../source3/modules/vfs_acl_common.c:534.)

Signed-off-by: Michael Adam <obnox@samba.org>
Reviewed-by: Stefan Metzmacher <metze@samba.org>

diff --git a/source3/modules/vfs_acl_common.c b/source3/modules/vfs_acl_common.c
index 59ced2922f34306e3add9f61c91fa54d558a053b..4e3aa72d378194a8595ce7d1cd904d038dd5e7db 100644 (file)
--- a/source3/modules/vfs_acl_common.c
+++ b/source3/modules/vfs_acl_common.c
@@ -590,6 +590,7 @@ static NTSTATUS fset_nt_acl_common(vfs_handle_struct *handle, files_struct *fsp,
                if (get_current_uid(handle->conn) == 0 ||
                                chown_needed == false ||
                                !(fsp->access_mask & SEC_STD_WRITE_OWNER)) {
+                       TALLOC_FREE(frame);
                        return NT_STATUS_ACCESS_DENIED;
                }