summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Wilcox (Oracle) <willy@infradead.org>2026-08-28 21:54:21 +0100
committerChristian Brauner <brauner@kernel.org>2026-09-10 09:27:27 +0200
commitc7ea7fb6095b758608fd2aaf63f24b62175dc93b (patch)
tree312e8af4ea030bb1ca04a25738c5c5df160a061b
parent00db7c70bf7c6a79a548f484c76af60563a7736e (diff)
downloadlinux-next-c7ea7fb6095b758608fd2aaf63f24b62175dc93b.tar.gz
linux-next-c7ea7fb6095b758608fd2aaf63f24b62175dc93b.zip
buffer: Remove reference to unmap_buffer()
unmap_buffer() was removed 25 years ago in v2.4.10.0.1. We don't need to mention it in a comment any more. Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org> Link: https://patch.msgid.link/20260828205429.3678204-2-willy@infradead.org Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
-rw-r--r--fs/buffer.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/fs/buffer.c b/fs/buffer.c
index a43f3c9ecaa0..b5d406933712 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -1615,9 +1615,7 @@ EXPORT_SYMBOL(create_empty_buffers);
* moment when something will explicitly mark the buffer dirty (hopefully that
* will not happen until we will free that block ;-) We don't even need to mark
* it not-uptodate - nobody can expect anything from a newly allocated buffer
- * anyway. We used to use unmap_buffer() for such invalidation, but that was
- * wrong. We definitely don't want to mark the alias unmapped, for example - it
- * would confuse anyone who might pick it with bread() afterwards...
+ * anyway.
*
* Also.. Note that bforget() doesn't lock the buffer. So there can be
* writeout I/O going on against recently-freed buffers. We don't wait on that