Kernel Bug Tracker – Bug 30752
NFS sillyrenamed files are not being deleted after close
Last modified: 2011-03-16 21:47:53 UTC
I'm opening this bug to ensure that 2.6.38 doesn't ship with sillyrenames still broken. If someone has already done so, please feel free to close this one as a duplicate.
This is a regression introduced by patch 949854d0. Trond has a proposed patch to fix it here, but there are other possible approaches:
Patch : http://git.linux-nfs.org/?p=trondmy/nfs-2.6.git;a=commit;h=674d01f97d0094e8c383f7dbdf0782a304f6348b
Handled-By : firstname.lastname@example.org
First-Bad-Commit : 949854d02455080d20cd3e1db28a3a18daf7599d
Author: Nick Piggin <email@example.com>
Date: Fri Jan 7 17:49:37 2011 +1100
fs: Use rename lock and RCU for multi-step operations
Should be fixed by commit c83ce989cb5ff86575821992ea82c4df5c388ebc (VFS: Fix the
nfs sillyrename regression in kernel 2.6.38).
The patch has been queued for the 2.6.38 stable series.
Confirmed. It seems to fix the issue.
I think we can go ahead and close this bug.