[PATCH] 1/4 Windows BRL: Adding VFS ops
zack.kirsch at isilon.com
Wed Feb 11 12:13:15 MST 2009
>> why uint64_t brl_private and not void *brl_private?
Good question. I actually started out with a void * , but realized that I didn't actually have control of when the blocking_lock_record (BLR) was freed. Is there an easy way to add a VFS-dependent destructor for the data that an implementation might add?
I thought about having the BLR code just free blr_private (if non-NULL), but this won't handle cleaning up for anything beyond a simple malloc.
More information about the samba-technical