* Sergio Gelato [2014-08-22 07:29:32 -0000]:
> I'm now testing my one-line patch from comment #5 on top of 3.2.0-67.101
> (amd64, generic kernel flavour). So far it doesn't seem to make things
> worse, but since I don't have a sure-fire way of triggering the bug it
> may take a while to get experimental confirmation that it cures the issue.
I've now got >9 days of uptime on two NFS servers with that patch (both servers
had been previously affected by the bug) without any trouble; not a single
nfsd thread has been lost.
Unfortunately the fix didn't make it into 3.2.0-68.102 so I'm having to
build my own kernels once more. What are the chances of this fix (or an
equivalent/better one, of course) being included in 3.2.63? I'm attaching
the patch again in diff form for clarity and convenience.
* Sergio Gelato [2014-08-22 07:29:32 -0000]:
> I'm now testing my one-line patch from comment #5 on top of 3.2.0-67.101
> (amd64, generic kernel flavour). So far it doesn't seem to make things
> worse, but since I don't have a sure-fire way of triggering the bug it
> may take a while to get experimental confirmation that it cures the issue.
I've now got >9 days of uptime on two NFS servers with that patch (both servers
had been previously affected by the bug) without any trouble; not a single
nfsd thread has been lost.
Unfortunately the fix didn't make it into 3.2.0-68.102 so I'm having to
build my own kernels once more. What are the chances of this fix (or an
equivalent/better one, of course) being included in 3.2.63? I'm attaching
the patch again in diff form for clarity and convenience.