Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> We're awake now but soon to be in meetings.
> Stubbing out xfs_xlatesb is fine in the mount, but later on it gets
> used to copy selected fields between two superblocks, so you'll need
> it to work.
> When you say it loops in xfs_xlatesb, do you mean it loops _forever_?
> Because it should loop quite a few times (once for each field) but
> obviously should terminate.
> If it loops forever, I suspect there must be an endian issue with
> xfs_lowbit64. Could you print out the value "f" returned by this
> each time around and let me know what you get? You should get
> "0", "1", "2"... "42" and then the function should exit
> The only way I can see it getting stuck is if xfs_lowbit64 has issues
> and ends up returning the wrong number, never letting the while terminate.
> You'll need xfs_lowbit64 to be correct for everything to work, so it
> would be worth checking it out...
> Let me know how you get on.
ok - i now switched back to use xlatesb again and added a printk for
f and the result is: it runs from 0 to 33 and then loops at 33 - looks
a bit like some 64bit issue ... what to look for next ?
t
--
thomas.graichen@xxxxxxxxxxxxx
technical director innominate AG
clustering & security networking people
tel: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tgr
|