linux-kernel - Re: [RFC] Hack to use mkdir/rmdir in debugfs

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]

Message-ID: <20130123045503.GB3309@kroah.com>
Date:	Tue, 22 Jan 2013 20:55:03 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC] Hack to use mkdir/rmdir in debugfs

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