From 54a6d7b3b81782bba504e50905a2d0b437b0cae1 Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Thu, 26 Apr 2012 18:57:01 +0200 Subject: [PATCH] s3: oplock_timeout is a talloc child of fsp Jeremy, I know you like it explicit, but I stumbled across this explicit TALLOC_FREE and asked myself about a potentially wrong talloc hierarchy. Autobuild-User: Volker Lendecke Autobuild-Date: Thu Apr 26 23:00:03 CEST 2012 on sn-devel-104 --- source3/smbd/files.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/source3/smbd/files.c b/source3/smbd/files.c index edcd98cd85e..8a9f0555308 100644 --- a/source3/smbd/files.c +++ b/source3/smbd/files.c @@ -454,9 +454,6 @@ void file_free(struct smb_request *req, files_struct *fsp) } /* Ensure this event will never fire. */ - TALLOC_FREE(fsp->oplock_timeout); - - /* Ensure this event will never fire. */ TALLOC_FREE(fsp->update_write_time_event); bitmap_clear(sconn->file_bmap, fsp->fnum - FILE_HANDLE_OFFSET); -- 2.11.4.GIT