From: Steven Rostedt <rostedt@goodmis.org>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Jeff Layton <jlayton@poochiereds.net>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
Schumaker Anna <anna.schumaker@netapp.com>,
Andrew Morton <akpm@linux-foundation.org>,
Fields Bruce <bfields@fieldses.org>,
Torvalds Linus <torvalds@linux-foundation.org>
Subject: Re: Revert: SUNRPC: xs_sock_mark_closed() does not need to trigger socket autoclose
Date: Fri, 1 Jul 2016 19:17:45 -0400 [thread overview]
Message-ID: <20160701191745.58ba1ef6@gandalf.local.home> (raw)
In-Reply-To: <CB98840B-1CEE-48C6-9ABB-82DA8D213BAF@primarydata.com>
On Fri, 1 Jul 2016 23:02:23 +0000
Trond Myklebust <trondmy@primarydata.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
next prev parent reply other threads:[~2016-07-01 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 21:24 Steven Rostedt
2016-07-01 22:34 ` Trond Myklebust
2016-07-01 22:39 ` Steven Rostedt
2016-07-01 23:02 ` Trond Myklebust
2016-07-01 23:17 ` Steven Rostedt [this message]
2016-07-01 23:19 ` Steven Rostedt
2016-07-01 23:14 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160701191745.58ba1ef6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=eric.dumazet@gmail.com \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trondmy@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®