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.
This commit is contained in:
parent
c05c5a7ff4
commit
9a4e125468
Notes:
sideshowbarker
2024-07-18 01:43:01 +09:00
Author: https://github.com/BenWiederhake Commit: https://github.com/SerenityOS/serenity/commit/9a4e1254689 Pull-request: https://github.com/SerenityOS/serenity/pull/10707
1 changed files with 0 additions and 5 deletions
|
@ -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:
|
||||
|
|
Loading…
Add table
Reference in a new issue