From c7ea7fb6095b758608fd2aaf63f24b62175dc93b Mon Sep 17 00:00:00 2001 From: "Matthew Wilcox (Oracle)" Date: Fri, 28 Aug 2026 21:54:21 +0100 Subject: [PATCH] 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) Link: https://patch.msgid.link/20260828205429.3678204-2-willy@infradead.org Reviewed-by: Jan Kara Signed-off-by: Christian Brauner (Amutable) --- fs/buffer.c | 4 +--- 1 file changed, 1 insertion(+), 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