From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] Hack to use mkdir/rmdir in debugfs
Date: Tue, 22 Jan 2013 20:55:03 -0800 [thread overview]
Message-ID: <20130123045503.GB3309@kroah.com> (raw)
In-Reply-To: <1358916249.21576.105.camel@gandalf.local.home>
On Tue, Jan 22, 2013 at 11:44:09PM -0500, Steven Rostedt wrote:
> On Tue, 2013-01-22 at 23:31 -0500, Steven Rostedt wrote:
>
> > >
> > > But again, I'd really not want to do this in debugfs, how about your own
> > > filesystem?
> >
> > I will note that this never modifies the debugfs code. But it does
> > circumvent it. That is, all this code lives in kernel/trace/trace.c. I
> > don't modify any of the debugfs code. I just replace the debugfs
> > dentry->d_inode->i_op with my own ops.
>
> Again, I want to stress that this doesn't touch the debugfs code. Here's
> the real change that I've been testing. It includes the code for the
> "new" and "free" files but those are not created because of an early
> 'return' I added. Notice that it's all contained in
> kernel/trace/trace.c.
Ok, then I'll just forget you ever asked anything about this and wish
you well :)
Have fun,
greg k-h
next prev parent reply other threads:[~2013-01-23 4:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 3:01 [RFC] Hack to use mkdir/rmdir in debugfs Steven Rostedt
2013-01-23 3:47 ` Steven Rostedt
2013-01-23 4:08 ` Greg Kroah-Hartman
2013-01-23 4:31 ` Steven Rostedt
2013-01-23 4:41 ` Greg Kroah-Hartman
2013-01-23 4:52 ` Steven Rostedt
2013-01-23 4:44 ` Steven Rostedt
2013-01-23 4:48 ` Steven Rostedt
2013-01-23 4:55 ` Greg Kroah-Hartman [this message]
2013-01-23 5:05 ` Steven Rostedt
2013-01-24 22:39 ` Valdis.Kletnieks
2013-01-24 23:53 ` Steven Rostedt
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=20130123045503.GB3309@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
/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