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

[Jonathan Nieder <jrnieder@gmail.com>]

Rik Theys wrote:

> I compiled the 2.6.32 kernel from squeeze with these patches on a
> sid box and it seems to fix the bug. I haven't fully testing any
> other NFS functionality now.

Yay. :)

Because I'm a little paranoid, here's a reminder for the kernel team:

 This bug is tagged "patch" for the sake of sid.  In other words:

  Release      Proposed action         Notes
  -------      ---------------         -----
  wheezy       apply v3.3-rc~116^2~1   Good, straightforward patch
  squeeze      do nothing for now      3-patch series needs review

> How do you determine which other patches are required to backport a
> specific patch (in general)? Is there some magic git command for
> that?

I did it the low-tech way --- try to apply the patch and compile-test,
run into obstacles, and use path-limited "git log -S" or "git log -G"
to find the patches that explain the difference between the two
codebases.

I hear darcs has more sophisticated code that can do something
similar automatically, though only for textual conflicts.