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

To: Rik Theys <Rik.Theys@esat.kuleuven.be>
Cc: 659111@bugs.debian.org
Subject: 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>
Date: Thu, 1 Mar 2012 23:15:00 -0600
Message-id: <[🔎] 20120302051500.GA407@burratino>
Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 659111@bugs.debian.org
In-reply-to: <20120209172625.GB6249@burratino>
References: <20120208125157.11211.34223.reportbug@lena.esat.kuleuven.be> <20120208183100.GB7734@burratino> <4F338D51.5070105@esat.kuleuven.be> <4F33A856.4080507@esat.kuleuven.be> <20120209172625.GB6249@burratino>

forwarded 659111 http://thread.gmane.org/gmane.linux.nfs/45995/focus=47436
quit

Jonathan Nieder wrote:

>               I suspect the patch is too big for the upstream stable
> series[*], but it should be safe to apply to sid, unless someone comes up
> with something more minimal to replace it.

Requested help upstream, since I'd like to see this fix in 2.6.32.y.
It should be possible to split the fix into more easily digestible
pieces for -stable if necessary.

Thanks again for a pleasant report.

Sincerely,
Jonathan

Reply to:

Follow-Ups:
- Processed: 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)

Prev by Date: Linux kernel hardening - link restrictions
Next by Date: Processed: Re: [2.6.31 -> 2.6.32 regression] Files on NFS4 become unwritable, but OK after explicit stat
Previous by thread: Re: Linux kernel hardening - link restrictions
Next by thread: Processed: Re: [2.6.31 -> 2.6.32 regression] Files on NFS4 become unwritable, but OK after explicit stat
Index(es):
- Date
- Thread