| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080925190149.208ee3a4@daedalus.pq.iki.fi> Date: Thu, 25 Sep 2008 19:01:49 +0300 From: Pekka Paalanen <pq@....fi> To: "Frédéric Weisbecker" <fweisbec@...il.com> Cc: "Steven Rostedt" <rostedt@...dmis.org>, "Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org Subject: Re: [Patch -tip 1/3] Tracing/ftrace: Relay unhandled entry output On Thu, 25 Sep 2008 17:56:32 +0200 "Frédéric Weisbecker" <fweisbec@...il.com> wrote: > 2008/9/25 Pekka Paalanen <pq@....fi>: > > My understanding is that the pipe will be broken only, if the trace > > framework believes tracing is disabled. Recall the discussion about > > tracer_enabled = 0. Which is a bug, and I hoped Steven would have > > commented on how to fix that properly. > > > > Or was it fixed already, and this is a different issue? > > I didn't notice. > > Actually there was two bugs which broke the pipe: > _ As you say the old one when none tracer put tracer_enabled = 0 > _ And the new one I described here. > > I think the first is fixed since none tracer has been replaced by "nop > tracer" (a recently implemented) which doesn't touch > tracer_enabled at all. Oh cool, sounds like I should try linux-next when I can. -- Pekka Paalanen http://www.iki.fi/pq/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists