https://bugzilla.kernel.org/show_bug.cgi?id=214001 --- Comment #1 from Linux_Chemist (untaintableangel@xxxxxxxxxxxxx) --- As an addendum, I suppose a slight source of confusion is the info for CONFIG_DEBUG_FS which reads: "debugfs is a virtual file system that kernel developers use to put debugging files into. Enable this option to be able to read and write to these files. For detailed documentation on the debugfs API, see Documentation/filesystems/. If unsure, say N." which implies: a) that it isn't strictly necessary to have enabled in order to boot/run normally (highlighting this bug) and b) that you would have zero need for it if you weren't reading/writing to these debugging files. To then have the option to enable debugfs but only run minimally with CONFIG_DEBUG_FS_ALLOW_NONE: "Access is off. Clients get -PERM when trying to create nodes in debugfs tree and debugfs is not registered as a filesystem. Client can then back-off or continue without debugfs access." leaves the question of 'why have it on and set to "allow none" rather than off completely?' -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
