Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs

[Olof Johansson <olof@lixom.net>]

On Tue, Oct 2, 2018 at 6:07 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Mon, 1 Oct 2018 18:18:56 -0700
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > 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).
>
> The funny part is, things used for debugging tend to turn into
> something that people want on production systems (tracing,
> perf, powertop, etc).
>
> >
> > 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?
> >
>
> tracefs was one example, but someone was talking to me at Kernel
> Recipes and wanted had another directory in debugfs and wanted it out
> as it was stable and wanted it exposed when debugfs is turned off.
> Unfortunately, this was discussed at an evening event, and I don't
> recall the specifics.

One really useful criteria for graduating some service to sysfs would
be to have namespaces and security aspects sorted out for it. Being in
debugfs you can ignore all of that.

Having something that containers might want for their own use (say,
for example, some trace functionality) move into sysfs but not being
possible to provide to an unprivileged container seems like things
we'd like to avoid.


-Olof