From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Moving debugfs file systems into sysfs
Date: Mon, 1 Oct 2018 18:18:56 -0700 [thread overview]
Message-ID: <20181002011856.GA10841@kroah.com> (raw)
In-Reply-To: <20181001140402.0799a8f0@gandalf.local.home>
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
next prev parent reply other threads:[~2018-10-02 1:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 18:04 Steven Rostedt
2018-10-02 1:18 ` Greg KH [this message]
2018-10-02 1:26 ` Greg KH
2018-10-02 13:07 ` Steven Rostedt
2018-10-02 14:59 ` Olof Johansson
2018-10-02 16:00 ` Shuah Khan
2018-10-02 16:17 ` Greg Kroah-Hartman
2018-10-02 16:30 ` Greg Kroah-Hartman
2018-10-02 21:37 ` Mauro Carvalho Chehab
2018-10-02 21:57 ` Shuah Khan
2018-10-02 22:22 ` Greg Kroah-Hartman
2018-10-03 12:59 ` Jan Kara
2018-10-03 13:40 ` Greg Kroah-Hartman
2018-10-03 13:44 ` Jiri Kosina
2018-10-03 14:32 ` Greg Kroah-Hartman
2018-10-03 14:33 ` Greg Kroah-Hartman
2018-10-04 11:50 ` Jiri Kosina
2018-10-03 14:53 ` Jan Kara
2018-10-04 16:11 ` Takashi Iwai
2018-10-03 14:11 ` Shuah Khan
2018-10-03 10:06 ` Sudeep Holla
2018-10-03 13:13 ` Mark Brown
2018-10-03 14:52 ` Sudeep Holla
2018-10-02 8:40 ` Jani Nikula
2018-10-02 13:11 ` Steven Rostedt
2018-10-02 21:32 ` Mauro Carvalho Chehab
2018-10-03 6:23 ` Jani Nikula
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=20181002011856.GA10841@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Ksummit-discuss@lists.linuxfoundation.org \
--cc=rostedt@goodmis.org \
/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