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

To: 659111@bugs.debian.org, control@bugs.debian.org, Jonathan Nieder <jrnieder@gmail.com>
Subject: Bug#659111: [2.6.31 -> 2.6.32 regression] Files on NFS4 become unwritable,, but OK after explicit stat
From: Rik Theys <Rik.Theys@esat.kuleuven.be>
Date: Wed, 21 Mar 2012 15:42:24 +0100
Message-id: <[🔎] 4F69E8D0.4070006@esat.kuleuven.be>
Reply-to: Rik Theys <Rik.Theys@esat.kuleuven.be>, 659111@bugs.debian.org

fixed-upstream 659111
fixed 659111 linux-2.6/3.3~rc6-1~experimental.1
quit

Hi,

The commit that fixes this bug is now part of the upstream 3.3 kernel. Iverified it on the 3.3-rc6 kernel from experimental.


Can this commit be backported to the 3.2 kernel in sid?
It applies and I have tested it in the past against the 3.2.4 kernel.

I agree that fixing it in squeeze might be a stretch, but it would benice to have it in Wheezy.


Regards,

Rik

Reply to:

Follow-Ups:
- Processed (with 1 errors): Re: [2.6.31 -> 2.6.32 regression] Files on NFS4 become unwritable,, but OK after explicit stat
  - From: owner@bugs.debian.org (Debian Bug Tracking System)
- Bug#659111: [2.6.31 -> 2.6.32 regression] Files on NFS4 become unwritable,, but OK after explicit stat
  - From: Jonathan Nieder <jrnieder@gmail.com>