summaryrefslogtreecommitdiff
path: root/Kernel/Ext2FileSystem.cpp
diff options
context:
space:
mode:
authorAndreas Kling <awesomekling@gmail.com>2019-01-30 19:32:54 +0100
committerAndreas Kling <awesomekling@gmail.com>2019-01-30 19:32:54 +0100
commit3a4207b863954249e1436eccb69e4d865b75970c (patch)
treec3eadeb9a52f1fe358d692e66ba7ea23a1310bfd /Kernel/Ext2FileSystem.cpp
parent2b4374d08e9ad8c6a057c635be03a18feea4bacc (diff)
downloadserenity-3a4207b863954249e1436eccb69e4d865b75970c.zip
Fix dumb bug in HashTable::clear().
We forgot to clear the m_buckets pointer. This meant that multiple calls to clear() would cause trouble.
Diffstat (limited to 'Kernel/Ext2FileSystem.cpp')
-rw-r--r--Kernel/Ext2FileSystem.cpp3
1 files changed, 0 insertions, 3 deletions
diff --git a/Kernel/Ext2FileSystem.cpp b/Kernel/Ext2FileSystem.cpp
index 0ebac398f6..e24b7a573e 100644
--- a/Kernel/Ext2FileSystem.cpp
+++ b/Kernel/Ext2FileSystem.cpp
@@ -373,9 +373,6 @@ void Ext2FSInode::flush_metadata()
// Unless we're about to go away permanently, invalidate the lookup cache.
if (m_raw_inode.i_links_count != 0) {
LOCKER(m_lock);
- // FIXME: Something isn't working right when we hit this code path.
- // I've seen crashes inside HashMap::clear() all the way down in DoublyLinkedList::clear().
- // My guess would be a HashTable bug.
// FIXME: This invalidation is way too hardcore. It's sad to throw away the whole cache.
m_lookup_cache.clear();
}