What I gathered from the bug report is that the allocation will take place but the data is still in limbo when the rename is written to disk.
So you end up with:
1. Space allocated for the new file.
2. Directory written to disk with new filename.
---- CRASH HAPPENS HERE
3. New file contents written to disk.
The sequence of events above is hardly better than it was before the fix.
Did I miss something in the sequence?
Just don't allow step 2 to happen before step 3 and everyone would have been happy.