From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 1 Oct 2018 18:18:56 -0700 From: Greg KH To: Steven Rostedt Message-ID: <20181002011856.GA10841@kroah.com> References: <20181001140402.0799a8f0@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181001140402.0799a8f0@gandalf.local.home> Cc: Ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Oct 01, 2018 at 02:04:02PM -0400, Steven Rostedt wrote: > At Kernel Recipes, I talked with some people that have mature > interfaces in the debugfs directory, but they can not access them on > systems that have debugfs disabled. What would be the process to have > these systems move out of debugfs? Should they create their own fs and > be mounted in /sys/kernel, with a dedicated directory if the file system > is enabled in the kernel (I had tracefs do that). > > Is this something we should discuss at Maintainers Summit? What is the > process for mature debugfs directories? What's the justification to > have them moved? Is there a better answer for this? It's a technical topic, so maintainers summit doesn't make sense. Stuff in debugfs should NEVER be used for anything "real" or anything other than debugging. So I would argue that that code needs to be fixed up now anyway, as most distros are disabling debugfs for the obvious reasons (and Android is also turning it off). As for where to put it, it all depends on exactly what it is, and what it does and who uses it. So it's almost always a case-by-case basis. Any specific examples you wish to share of code that needs this? thanks, greg k-h