Bug#659111: [2.6.31 -> 2.6.32.y regression] Files on NFS4 become unwritable, but OK after explicit stat

[Rik Theys <Rik.Theys@esat.kuleuven.be>]

Hi,

Thanks Jonathan for looking into this bug, and the many other bugs filed 
against the Debian kernels.

I did a git bisect between 2.6.31 and 2.6.32 and the first bad commit is...

80e52aced138bb41b045a8595a87510f27d8d8c5 is first bad commit
commit 80e52aced138bb41b045a8595a87510f27d8d8c5
Author: Trond Myklebust <Trond.Myklebust@netapp.com>
Date:   Sun Aug 9 15:06:19 2009 -0400

    NFSv4: Don't do idmapper upcalls for asynchronous RPC calls

    We don't want to cause rpciod to hang...

    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Wel duh. I could have guessed that if I had read through the changelog :-/.

Anyway, I'm glad the git bisect thing worked.

On 02/08/2012 07:31 PM, Jonathan Nieder wrote:
> Please try v3.3-rc1 or newer from upstream, or try the following patch
> against stable/linux-3.2.y.  Instructions for building a custom
> kernel can be found at [1] or the corresponding file in the
> debian-kernel-handbook package.
>
> [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package
>
> Which 3.2.y kernel did you test?

I will upgrade the lenny test system to sid and try building a kernel 
with this patch.

Regards,

Rik



--
Rik Theys
Senior System Engineer
KU Leuven - Dept. Elektrotechniek (ESAT)
Kasteelpark Arenberg 10
B-3001 LEUVEN - HEVERLEE
Tel.: +32(0)16/32.11.07
----------------------------------------------------------------
<<Any errors in spelling, tact or fact are transmission errors>>