[PATCH] 1/4 Windows BRL: Adding VFS ops

[Zack Kirsch]

>> why uint64_t brl_private and not void *brl_private?
>> 
>> metze

Hi Metze,

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.

Thanks!
Zack