linux-kernel - Re: ftrace and debugfs weird interaction

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]

Date:	Mon, 28 Apr 2008 22:35:35 +0300
From:	Pekka Paalanen <pq@....fi>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Ingo Molnar <mingo@...e.hu>, Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: ftrace and debugfs weird interaction

> * Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
> 
> > Hi,
> > 
> > When trying to figure out what was going on with the sched tracer
> > "tracing_enabled" file (sched-devel.git tree), I fell on this strange
> > behavior :
> > 
> > echo 1>tracing_enabled seems _not_ to send 1 to the tracing_ctrl_write

Wait a minute, are you literally running the command:
echo 1>tracing_enabled

If you are, you just echoed only a newline and directed stdout, stream 1,
to the file. No? :-)

Could you try with a space:
echo 1 > tracing_enabled

> > callback. However, sending garbage, e.g. echo s> tracing_enabled,
> > correctly sends the 's' character down the chain. echo 0>tracing_enabled
> > sometimes results in the callback not even being called.

Stream 0 is stdin, so... not sure what this would do. Probably nothing,
just like you experienced.


Thanks.

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