[OpenAFS-devel] RE: [OpenAFS] Strange Behavior of Openafs-1.1 .1

[Neulinger, Nathan]

I just took another look over fs.h and osi_vfs.h and I'm confused...

What fields are the extra data that AFS is adding? Looks to me like struct
vnode_t is 100% identical to the existing struct inode, with the exception
that the fs-specific union appears to be alot smaller in the vnode_t one. 

-- Nathan

> -----Original Message-----
> From: Neulinger, Nathan [mailto:nneul@umr.edu]
> Sent: Wednesday, August 08, 2001 2:01 PM
> To: 'Derek Atkins'
> Cc: 'openafs-devel@openafs.org'
> Subject: RE: [OpenAFS-devel] RE: [OpenAFS] Strange Behavior of
> Openafs-1.1 .1
> 
> 
> > Now, we could go back to what I did back in Linux-AFS:
> > 
> > struct vnode_t {
> > 	struct inode v_in;
> > 	<rest of stuff>
> > };
> > 
> > -derek
> 
> Is there any significant negative to that? Seems like it would either
> require some code changes for the field names (v_in.x) 
> instead of (x), or
> alternatively, just casting the (struct vnode_t *) to a 
> (struct inode *)
> prior to using it to access elements of v_in. 
> 
> Seems to me that would simplify things considerably.
> 
> -- Nathan
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>