diff options
| author | Xiaotian Feng <[email protected]> | 2009-12-31 02:52:36 +0000 |
|---|---|---|
| committer | J. Bruce Fields <[email protected]> | 2010-01-06 22:38:04 +0000 |
| commit | b292cf9ce70d221c3f04ff62db5ab13d9a249ca8 (patch) | |
| tree | 00da53660b4b14d9310905d4cae9c63ec6588054 /fs/jbd/commit.c | |
| parent | nfsd: make sure data is on disk before calling ->fsync (diff) | |
| download | kernel-b292cf9ce70d221c3f04ff62db5ab13d9a249ca8.tar.gz kernel-b292cf9ce70d221c3f04ff62db5ab13d9a249ca8.zip | |
sunrpc: fix peername failed on closed listener
There're some warnings of "nfsd: peername failed (err 107)!"
socket error -107 means Transport endpoint is not connected.
This warning message was outputed by svc_tcp_accept() [net/sunrpc/svcsock.c],
when kernel_getpeername returns -107. This means socket might be CLOSED.
And svc_tcp_accept was called by svc_recv() [net/sunrpc/svc_xprt.c]
if (test_bit(XPT_LISTENER, &xprt->xpt_flags)) {
<snip>
newxpt = xprt->xpt_ops->xpo_accept(xprt);
<snip>
So this might happen when xprt->xpt_flags has both XPT_LISTENER and XPT_CLOSE.
Let's take a look at commit b0401d72, this commit has moved the close
processing after do recvfrom method, but this commit also introduces this
warnings, if the xpt_flags has both XPT_LISTENER and XPT_CLOSED, we should
close it, not accpet then close.
Signed-off-by: Xiaotian Feng <[email protected]>
Cc: J. Bruce Fields <[email protected]>
Cc: Neil Brown <[email protected]>
Cc: Trond Myklebust <[email protected]>
Cc: David S. Miller <[email protected]>
Cc: [email protected]
Signed-off-by: J. Bruce Fields <[email protected]>
Diffstat (limited to 'fs/jbd/commit.c')
0 files changed, 0 insertions, 0 deletions
