summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVolker Lendecke <vl@samba.org>2012-04-26 18:57:01 +0200
committerVolker Lendecke <vl@samba.org>2012-04-26 23:00:03 +0200
commit54a6d7b3b81782bba504e50905a2d0b437b0cae1 (patch)
treeede3b757225aebec2ae52f14e29760f229dc7626
parent21985a7f10d5bea6d80b3063c238f2c38b96e76d (diff)
downloadsamba-54a6d7b3b81782bba504e50905a2d0b437b0cae1.tar.gz
samba-54a6d7b3b81782bba504e50905a2d0b437b0cae1.tar.bz2
samba-54a6d7b3b81782bba504e50905a2d0b437b0cae1.zip
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 <vl@samba.org> Autobuild-Date: Thu Apr 26 23:00:03 CEST 2012 on sn-devel-104
-rw-r--r--source3/smbd/files.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/source3/smbd/files.c b/source3/smbd/files.c
index edcd98cd85..8a9f055530 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);