[OpenAFS-devel] Re: 2.6.16 linux and d_cache
chas williams - CONTRACTOR
chas@cmf.nrl.navy.mil
Mon, 27 Feb 2006 21:13:51 -0500
In message <1141077237.3849.10.camel@BillMurray>,William John Murray writes:
>Thanks Marc...this fixes the d_child.
marc?
>There is another oddity. The routine uses AFSTOI and ITOAFS,
>but these don't seem to exist. I THINK AFSTOV and VTOAFS replace them I
>think? But how come no one else has trouble with them?
i suspect this is something broken on the tree (1.5.0?) you are using.
and yes, AFSTOI/ITOAFS went away in favor of AFSTOV/VTOAFS just for
consistency (linux calls it an inode and everyone else uses vnode).
> Anyway, this brings me back to my problem of a couple of weeks ago:
>
>libafs: falsely claims to have parameter sys_call_table_addr
>
>on inserting the library...I still have no idea what to do with that.
i guess i would just ignore this. it means that afs couldnt find
the bits it needs for pag support. this broken on later kernels
when the sys_call_table became read only and "unpatchable".