># ipfstat -sl | grep asdf
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address
>pos=0xd000d kmemcpy:read: Bad address

Is this not just a case of things changing underneat ipfstat?

Kmem readers do not lock out concurrent activity so they can try to follow
stale pointers.


Casper

Reply via email to