[ENBD] 2.5.64 port?

[Peter T. Breuer]

"A month of sundays ago Ciprian Paunescu wrote:"
> Once I try a "fsdisk /dev/nb/a/0", the client crashes.
> 
> So, what did I do wrong? I didn't apply the 2.5.64 patch,

To be more exact in my sanaser, I don't know what you did wrong, but on
the other hand I don't know what you did .. that you tried to link 
the enbd_ioctl module together with ethe enbd module is already so
strange that I cannot understand how you could have arrived at that ...
you didn't try to compile both IN to the kernel did you?

That might cause it!  They're writetn as modules and I certainly haven't
tested any other compile configuration.

> since the kernel I had was 2.5.65, I just copied the
> "nbd/linux-2.5.64" subtree over /usr/src/linux, an unpatched
> 2.5.65 kernel tree.

As to what might cause what you observed given that the rest wasn't
already bollixed, nbd_info output might tell me. There was wrong
accounting code in end_request for some time, which would have caused
extremely slow dropthrough of requests to the device, and VM backup
might crash your kernel. I can tell if you show me /proc/nbdinfo .. the
accounting numbers will run negative in one counter if the code you
picked up has that problem. The cure is to pick up the fixed code.

Peter