I have a resmgr that implements a file system and I'm overloading ocb creation/deletion for various reasons. Does 
iofunc_ocb_close()/iofunc_ocb_free() free the the attr structure or must that be handled explicitly? 

I'm assuming iofunc_ocb_close()/iofunc_ocb_free() do not do this as the attr structure lifecycle should match that of 
the underlying file system object and therefore persist until the object is actually deleted (versus closed).

TIA,
Jamie