From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround (fwd) Date: Sun, 5 Oct 2008 20:09:22 +0200 (CEST) Message-ID: References: <48e3a4e5.0d1d640a.4cd3.06e9@mx.google.com> <48e3e835.0906c00a.2cd1.2fd1@mx.google.com> <48e4adb8.0807c00a.62b8.ffff87d6@mx.google.com> <48e4d63a.060ec00a.6a4e.ffff95bf@mx.google.com> <48e5364d.0603c00a.6e25.fffff993@mx.google.com> <48e8fef7.0610c00a.5fa2.ffffaab0@mx.google.com> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-851242594-1223230164=:3398" Cc: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= , David Miller , Netdev To: =?ISO-8859-15?Q?D=E2niel_Fraga?= Return-path: Received: from www.tglx.de ([62.245.132.106]:60246 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755140AbYJESJi (ORCPT ); Sun, 5 Oct 2008 14:09:38 -0400 In-Reply-To: <48e8fef7.0610c00a.5fa2.ffffaab0@mx.google.com> Sender: netdev-owner@vger.kernel.org List-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-851242594-1223230164=:3398 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT n Sun, 5 Oct 2008, Dāniel Fraga wrote: > On Fri, 3 Oct 2008 00:19:08 +0300 (EEST) > "Ilpo Järvinen" wrote: > > > On Thu, 2 Oct 2008, Dāniel Fraga wrote: > > > > > On Thu, 2 Oct 2008 23:31:28 +0300 (EEST) > > > "Ilpo Järvinen" wrote: > > > > > > > Ah, I was kind of thinking that you were doing something net related > > > > using some raw socket thing (such as traceroute) when you earlier > > > > mentioned sudo (iirc, we never really discussed what you usually do with > > > > it when you see the stall). > > > > > > I read nntp groups everyday and I use leafnode. The stall on my > > > desktop happens when I run fetchnews (which must be run as user "news" > > > so I have to use sudo). Usually the stall on my desktop happens when > > > I'm using fetchnews or some other command run by sudo. > > > > Yes yes, I'd be specificly interested to have some rough idea what that > > "some other command" includes, especially as some seem to be non-net > > related since you mentioned e.g., that /dev/log thing? > > Here we go folks, good and bad news: > > 1) the good news is that the Thomas' patch detected the stall, but... > > 2) > > Oct 5 14:23:03 teleporto vmunix: Tracer stopped > Oct 5 14:23:13 teleporto last message repeated 2 times > > if it had really stopped, the message wouldn't be repeated 2 > times. > > and > > fraga@teleporto ~$ cat /debug/tracing/tracing_enabled > 1 > > In other words, the tracing wasn't really stopped. > > So I couldn't get what Thomas want. Should I activated the > initial auto-checking of ftrace to see if it's really working? Very > strange the fact it wasn't stopped. > > *** > > I was waiting for 2 days to a stall and I managed to get the > stall by using "sudo" multiple times. It seems that sudo really makes > this bug hit. > > And now? Should we revise Thomas patch? Maybe a bug in ftrace > code that prevents it from being stopped? It seems that: > > ftrace_enabled = 0; > > isn't really stopping the tracing. did you get the content of /debug/tracing/trace nevertheless ? The cat /debug/tracing/tracing_enabled == 1 might be just a user space interface thingy. Thanks, tglx --8323328-851242594-1223230164=:3398--