| commit | 04287f975e68038051eb9c79896866d36610b8e0 | |
| author | Al Viro <viro@ZenIV.linux.org.uk> | |
| Wed, 7 Apr 2010 23:06:07 +0000 (8 00:06 +0100) | ||
| committer | Linus Torvalds <torvalds@linux-foundation.org> | |
| Wed, 7 Apr 2010 23:10:16 +0000 (7 16:10 -0700) | ||
| tree | e87af9a47942a187a06b63aa3600511f4bc11ad8 | treesnapshot (tar.gz zip) |
| parent | 48de8cb7847d040c8892701c1ff3c55eff1f46b4 | commitdiff |
Have nfs ->d_revalidate() report errors properly
If nfs atomic open implementation ends up doing open request from
->d_revalidate() codepath and gets an error from server, return that error
to caller explicitly and don't bother with lookup_instantiate_filp() at all.
->d_revalidate() can return an error itself just fine...
See
http://bugzilla.kernel.org/show_bug.cgi?id=15674
http://marc.info/?l=linux-kernel&m=126988782722711&w=2
for original report.
Reported-by: Daniel J Blueman <daniel.blueman@gmail.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
If nfs atomic open implementation ends up doing open request from
->d_revalidate() codepath and gets an error from server, return that error
to caller explicitly and don't bother with lookup_instantiate_filp() at all.
->d_revalidate() can return an error itself just fine...
See
http://bugzilla.kernel.org/show_bug.cgi?id=15674
http://marc.info/?l=linux-kernel&m=126988782722711&w=2
for original report.
Reported-by: Daniel J Blueman <daniel.blueman@gmail.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
| fs/nfs/nfs4proc.c | diffblobblamehistory |