summaryrefslogtreecommitdiff
path: root/Kernel/Heap/kmalloc.cpp
diff options
context:
space:
mode:
authorBrian Gianforcaro <bgianf@serenityos.org>2021-10-01 23:48:07 -0700
committerAndreas Kling <kling@serenityos.org>2021-10-02 18:16:15 +0200
commit92844a6af6c5943eeb50aaea51002d83de10d6f4 (patch)
tree5df376b9e3d57c769b6a983753bb9f4e7e22b214 /Kernel/Heap/kmalloc.cpp
parent0223faf6f443ab57d8e151227b7a9bdc4fef3e0f (diff)
downloadserenity-92844a6af6c5943eeb50aaea51002d83de10d6f4.zip
Kernel: Access Processor static methods statically
SonarCloud flagged this "Code Smell", where we are accessing these static methods as if they are instance methods. While it is technically possible, it is very confusing to read when you realize they are static functions.
Diffstat (limited to 'Kernel/Heap/kmalloc.cpp')
-rw-r--r--Kernel/Heap/kmalloc.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/Kernel/Heap/kmalloc.cpp b/Kernel/Heap/kmalloc.cpp
index 49eadb7571..8e3fbbadce 100644
--- a/Kernel/Heap/kmalloc.cpp
+++ b/Kernel/Heap/kmalloc.cpp
@@ -87,7 +87,7 @@ struct KmallocGlobalHeap {
// heap expansion may have been triggered while holding some
// other spinlock. If the expansion happens to need the same
// spinlock we would deadlock. So, if we're in any lock, defer
- Processor::current().deferred_call_queue(kmalloc_allocate_backup_memory);
+ Processor::deferred_call_queue(kmalloc_allocate_backup_memory);
});
// Now that we added our backup memory, check if the backup heap