[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160701191745.58ba1ef6@gandalf.local.home>
Date: Fri, 1 Jul 2016 19:17:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Trond Myklebust <trondmy@...marydata.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
Jeff Layton <jlayton@...chiereds.net>,
"Eric Dumazet" <eric.dumazet@...il.com>,
Schumaker Anna <anna.schumaker@...app.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Fields Bruce <bfields@...ldses.org>,
Torvalds Linus <torvalds@...ux-foundation.org>
Subject: Re: Revert: SUNRPC: xs_sock_mark_closed() does not need to trigger
socket autoclose
On Fri, 1 Jul 2016 23:02:23 +0000
Trond Myklebust <trondmy@...marydata.com> wrote:
> Can we look into why the socket disconnect is happening in the first
> place? It’s presumably not the server, since that _would_ trigger an
> autoclose when the socket hits TCP_CLOSE_WAIT. That puts the two top
> suspects being the TCP keepalive and the TCP_USER_TIMEOUT. Are there
> any tracepoints we could use to look at whether or not they are
> triggering a close?
There's not many tracepoints, but from my previous emails I added some
trace_printk()s and converted some of your debug prints into
trace_printk():
+#undef dprintk
+#undef dprintk_rcu
+#define dprintk(args...) trace_printk(args)
+#define dprintk_rcu(args...) trace_printk(args)
See my previous email that describes all this (I removed the debugging
from my kernel, and I need to spend time with the family so I can't get
to this again till Tuesday)
http://lkml.kernel.org/r/20160630175618.51a725ee@gandalf.local.home
-- Steve
Powered by blists - more mailing lists