From: Greg KH <gregkh@suse.de>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: ftrace and debugfs weird interaction
Date: Sat, 26 Apr 2008 17:36:45 -0700 [thread overview]
Message-ID: <20080427003645.GA19827@suse.de> (raw)
In-Reply-To: <20080426185403.GA22522@Krystal>
On Sat, Apr 26, 2008 at 02:54:03PM -0400, Mathieu Desnoyers 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
> 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 ?
I don't know. Are you sure your _fops is not getting called at all?
How about using a "default" operation for such a simple file, like
debugfs_create_bool() as that is all you care about for this kind of
value?
That should save you some code at the very least :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-04-27 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 18:54 ftrace and debugfs weird interaction Mathieu Desnoyers
2008-04-27 0:36 ` Greg KH [this message]
2008-04-28 15:39 ` Ingo Molnar
2008-04-28 19:27 ` Steven Rostedt
2008-04-28 19:35 ` Pekka Paalanen
2008-04-28 20:34 ` Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080427003645.GA19827@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox