On Tue, 2013-01-22 at 20:55 -0800, Greg Kroah-Hartman wrote: > 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, Don't leave me.... I'm afraid.... I only Cc'd you because it was interacting with debugfs, and was hoping that you could shed any light that what I did may cause me issues in the future. But it's my problem not yours. It may bite me in the ass later, but for now, it looks like it may work. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
