linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20080426185403.GA22522@Krystal>
Date:	Sat, 26 Apr 2008 14:54:03 -0400
From:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To:	Greg Kroah-Hartman <gregkh@...e.de>, Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: ftrace and debugfs weird interaction

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

The debugfs file has been created with

        entry = debugfs_create_file("tracing_enabled", 0644, d_tracer,
                                    &global_trace, &tracing_ctrl_fops);
        if (!entry)
                pr_warning("Could not create debugfs 'tracing_enabled' entry\n");

I wonder what kind of weird debugfs interaction we might have here ?

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/