summaryrefslogtreecommitdiff
path: root/Kernel/VM/InodeVMObject.h
diff options
context:
space:
mode:
authorAndreas Kling <kling@serenityos.org>2021-03-04 15:08:37 +0100
committerAndreas Kling <kling@serenityos.org>2021-03-04 15:42:51 +0100
commit2871df6f0d131f4777847665d9cbc0ca93e3e752 (patch)
treeca48c01c10acaa5a588d2a330bf67726deb661c2 /Kernel/VM/InodeVMObject.h
parent9547846a1855d5c3da580c49d0f3d73157e6562e (diff)
downloadserenity-2871df6f0d131f4777847665d9cbc0ca93e3e752.zip
Kernel: Stop trying to keep InodeVMObject in sync with disk changes
As it turns out, Dr. POSIX doesn't require that post-mmap() changes to a file are reflected in the memory mappings. So we don't actually have to care about the file size changing (or the contents.) IIUC, as long as all the MAP_SHARED mappings that refer to the same inode are in sync, we're good. This means that VMObjects don't need resizing capabilities. I'm sure there are ways we can take advantage of this fact.
Diffstat (limited to 'Kernel/VM/InodeVMObject.h')
-rw-r--r--Kernel/VM/InodeVMObject.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/Kernel/VM/InodeVMObject.h b/Kernel/VM/InodeVMObject.h
index 035663aa12..d00c8538b8 100644
--- a/Kernel/VM/InodeVMObject.h
+++ b/Kernel/VM/InodeVMObject.h
@@ -39,9 +39,6 @@ public:
Inode& inode() { return *m_inode; }
const Inode& inode() const { return *m_inode; }
- void inode_contents_changed(Badge<Inode>, off_t, ssize_t, const UserOrKernelBuffer&);
- void inode_size_changed(Badge<Inode>, size_t old_size, size_t new_size);
-
size_t amount_dirty() const;
size_t amount_clean() const;