From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214001] [bisected][regression] After commit "drm/ttm: Initialize debugfs from ttm_global_init()" kernels without debugfs explicitly set to 'allow all' fail to boot
Date: Sun, 08 Aug 2021 19:18:02 +0000 [thread overview]
Message-ID: <bug-214001-2300-FbLOkMqpjr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214001-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214001
--- Comment #1 from Linux_Chemist (untaintableangel@hotmail.co.uk) ---
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.
next prev parent reply other threads:[~2021-08-08 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 19:09 [Bug 214001] New: [bisected][regression] After commit "drm/ttm: Initialize debugfs from ttm_global_init()" kernels without debugfs explicitly set to 'allow all' fail to boot bugzilla-daemon
2021-08-08 19:09 ` [Bug 214001] " bugzilla-daemon
2021-08-08 19:18 ` bugzilla-daemon [this message]
2021-08-09 11:09 ` bugzilla-daemon
2021-08-13 17:50 ` bugzilla-daemon
2021-08-13 18:24 ` bugzilla-daemon
2021-08-13 19:59 ` bugzilla-daemon
2021-08-22 22:10 ` bugzilla-daemon
2021-08-22 22:19 ` bugzilla-daemon
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=bug-214001-2300-FbLOkMqpjr@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.