diff options
author | Aaron Thompson <dev@aaront.org> | 2025-07-04 00:19:49 +0300 |
---|---|---|
committer | Danilo Krummrich <dakr@kernel.org> | 2025-07-04 00:56:33 +0300 |
commit | 78f88067d5c56d9aed69f27e238742841461cf67 (patch) | |
tree | 86cfca6bc7f27d6acc8ffd98905277959b6cbb70 /net/lapb/lapb_timer.c | |
parent | 226862f50a7a88e4e4de9abbf36c64d19acd6fd0 (diff) | |
download | linux-78f88067d5c56d9aed69f27e238742841461cf67.tar.xz |
drm/nouveau: Do not fail module init on debugfs errors
If CONFIG_DEBUG_FS is enabled, nouveau_drm_init() returns an error if it
fails to create the "nouveau" directory in debugfs. One case where that
will happen is when debugfs access is restricted by
CONFIG_DEBUG_FS_ALLOW_NONE or by the boot parameter debugfs=off, which
cause the debugfs APIs to return -EPERM.
So just ignore errors from debugfs. Note that nouveau_debugfs_root may
be an error now, but that is a standard pattern for debugfs. From
include/linux/debugfs.h:
"NOTE: it's expected that most callers should _ignore_ the errors
returned by this function. Other debugfs functions handle the fact that
the "dentry" passed to them could be an error and they don't crash in
that case. Drivers should generally work fine even if debugfs fails to
init anyway."
Fixes: 97118a1816d2 ("drm/nouveau: create module debugfs root")
Cc: stable@vger.kernel.org
Signed-off-by: Aaron Thompson <dev@aaront.org>
Acked-by: Timur Tabi <ttabi@nvidia.com>
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/r/20250703211949.9916-1-dev@aaront.org
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions