From: Jeff Layton Date: Wed, 30 Jul 2014 01:37:44 +0000 (-0400) Subject: nfsd: print status when nfsd4_open fails to open file it just created X-Git-Tag: omap-for-v3.17/fixes-against-rc2~101^2~77 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b3fbfe0e7a1d88e3cbaa282c5f6fc50e8c67448c;p=pandora-kernel.git nfsd: print status when nfsd4_open fails to open file it just created It's possible for nfsd to fail opening a file that it has just created. When that happens, we throw a WARN but it doesn't include any info about the error code. Print the status code to give us a bit more info. Our QA group hit some of these warnings under some very heavy stress testing. My suspicion is that they hit the file-max limit, but it's hard to know for sure. Go ahead and add a -ENFILE mapping to nfserr_serverfault to make the error more distinct (and correct). Signed-off-by: Jeff Layton Signed-off-by: J. Bruce Fields --- Reading git-diff-tree failed