linux-kernel - Re: [PATCH 3/3] ftrace: trace single pid for function graph tracer

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0812031551360.29045@gandalf.stny.rr.com>
Date:	Wed, 3 Dec 2008 15:52:24 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, fweisbec@...il.com,
	peterz@...radead.org, arjan@...radead.org, dave@...ux.vnet.ibm.com,
	containers@...ts.osdl.org, ebiederm@...ssion.com,
	sukadev@...ux.vnet.ibm.com, serue@...ibm.com, srostedt@...hat.com
Subject: Re: [PATCH 3/3] ftrace: trace single pid for function graph tracer


On Wed, 3 Dec 2008, Andrew Morton wrote:

> On Wed, 03 Dec 2008 15:36:59 -0500
> Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > This patch makes the changes to set_ftrace_pid apply to the function
> > graph tracer.
> 
> That sentence needs help.

Medic!

> 
> >  # echo $$ > /debugfs/tracing/set_ftrace_pid
> >  # echo function_graph > /debugfs/tracing/current_tracer
> > 
> > Will cause only the current task to be traced. Note, the trace flags are
> > also inherited by child processes, so the children of the shell
> > will also be traced.
> 
> Where did we end up on the pids-arent-unique issue?  Gave up?

Nah, patch 2 opens the door for a solution. I'm just pawning the work off 
to the container folks ;-)

-- Steve

--
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/