From 9a4e1254689a593835ab0bd80c8c396366e1b2e0 Mon Sep 17 00:00:00 2001 From: Ben Wiederhake Date: Sat, 30 Oct 2021 00:54:21 +0200 Subject: [PATCH] Kernel: Remove misleading FIXME in DevTmpFS This FIXME does not seem to apply anymore. Yes, symbolic links in all filesystems appear to be slightly broken, but that has nothing to do with File::absolute_path. Let's remove the wrong FIXME instead of adding to the confusion. --- Kernel/FileSystem/DevTmpFS.cpp | 5 ----- 1 file changed, 5 deletions(-) diff --git a/Kernel/FileSystem/DevTmpFS.cpp b/Kernel/FileSystem/DevTmpFS.cpp index 8552bb2eaa..6793152bb5 100644 --- a/Kernel/FileSystem/DevTmpFS.cpp +++ b/Kernel/FileSystem/DevTmpFS.cpp @@ -126,11 +126,6 @@ InodeMetadata DevTmpFSInode::metadata() const break; case Type::Link: metadata.inode = { fsid(), index() }; - // FIXME: For now, it might not be possible to change the m_mode due to - // it pointing to another device node which its absolute_path() is not - // recognizable by the VirtualFileSystem. - // When we resolve the issues with the clunky absolute_path() interface, - // this should work out of the box... metadata.mode = S_IFLNK | m_mode; break; default: