From bce17d06f50ee993439a3caa049190bc2fcea21a Mon Sep 17 00:00:00 2001 From: Liav A Date: Fri, 26 May 2023 13:13:18 +0300 Subject: [PATCH] Kernel: Don't lock SysFS filesystem mutex calling traverse_as_directory This locking is simply not needed because the associated SysFS component will use proper and more "atomic" locking on its own. --- Kernel/FileSystem/SysFS/DirectoryInode.cpp | 2 -- 1 file changed, 2 deletions(-) diff --git a/Kernel/FileSystem/SysFS/DirectoryInode.cpp b/Kernel/FileSystem/SysFS/DirectoryInode.cpp index 8167fe4b30..9661074ded 100644 --- a/Kernel/FileSystem/SysFS/DirectoryInode.cpp +++ b/Kernel/FileSystem/SysFS/DirectoryInode.cpp @@ -38,13 +38,11 @@ InodeMetadata SysFSDirectoryInode::metadata() const ErrorOr SysFSDirectoryInode::traverse_as_directory(Function(FileSystem::DirectoryEntryView const&)> callback) const { - MutexLocker locker(fs().m_lock); return m_associated_component->traverse_as_directory(fs().fsid(), move(callback)); } ErrorOr> SysFSDirectoryInode::lookup(StringView name) { - MutexLocker locker(fs().m_lock); auto component = m_associated_component->lookup(name); if (!component) return ENOENT;