diff options
author | Yihang Li <liyihang9@huawei.com> | 2024-10-08 10:18:11 +0800 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2024-10-15 22:33:34 -0400 |
commit | 436a97c5d2882c09f44d3255ac47f641860faeea (patch) | |
tree | e9ab2d6fc3533b2ff9acfb5bfa2658ff274a88a0 /tools/perf/scripts/python/task-analyzer.py | |
parent | e6702e3919328b24757872cbf7f02c51894624d7 (diff) | |
download | linux-436a97c5d2882c09f44d3255ac47f641860faeea.tar.gz linux-436a97c5d2882c09f44d3255ac47f641860faeea.tar.bz2 linux-436a97c5d2882c09f44d3255ac47f641860faeea.zip |
scsi: hisi_sas: Create trigger_dump at the end of the debugfs initialization
In the current debugfs initialization process, the interface
trigger_dump is created first, and then the dump directory is created to
store the register dump information.
The issue is that after the trigger_dump interface is created, users can
access the interface to trigger dump and call
debugfs_create_files_v3_hw(). In debugfs_create_files_v3_hw(), if
.debugfs_dump_dentry is NULL, the file for storing dump information is
created under /sys/kernel/debug, and the memory and information cannot
be released after the driver is uninstalled.
Therefore, the creation of the trigger_dump interface is placed at the
end of debugfs initialization.
Signed-off-by: Yihang Li <liyihang9@huawei.com>
Link: https://lore.kernel.org/r/20241008021822.2617339-3-liyihang9@huawei.com
Reviewed-by: Xiang Chen <chenxiang66@hisilicon.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions