Re: fr1-2.16 patch for 2.6.10 kernel

[email protected] wrote:
> > The enbd code is not invasive.  Such real nontrivial patches as there
> > are in the distributed archive are only to the kernel Makefiles and
> > Kconfig files.
> Will try it soon...

I forgot to say that the 2.6 enbd patch still has one issue that often
bites me .... whenever I hibernate my laptop with an enbd client
running, on resume the enbd client dies through timeout (or the server
does, I don't know which goes first!) and a new client is started to
replace it, but the new client can't get into the kernel to register
until I "echo 0 >/proc/nbdinfo". Then the old client finally "really
really" dies and the new one starts up.

Whenever I've looked rather than supply the workaround, it seems that
the client is not in my code, but rather is in a semaphore somewhere
else in the kernel. I suspect that the "echo 0 >/proc/nbdinfo" clears
the lock by running invalidate_buffers.

I would like to experiment, but if anyone sees issues like that that
can be resolved as I describe, could you let me know? I don't know if
it is an artifact of my kernel version (2.6.3) or compile (SMP).

I would move my kernel version up but 2.6.8.1 was not very stable on my
laptop. I'll try 2.6.11.

Peter