release 6.15.4

debian/patches/patchset-pf/fixes/0002-mm-filemap-unify-read-write-dropbehind-naming.patch

@@ -0,0 +1,36 @@
+From 0b8d9b7ae677a03629218f69037be3f342c5ee81 Mon Sep 17 00:00:00 2001
+From: Jens Axboe <axboe@kernel.dk>
+Date: Tue, 27 May 2025 07:28:55 -0600
+Subject: mm/filemap: unify read/write dropbehind naming
+
+The read side is filemap_end_dropbehind_read(), while the write side
+used folio_ as the prefix rather than filemap_. The read side makes more
+sense, unify the naming such that the write side follows that.
+
+Signed-off-by: Jens Axboe <axboe@kernel.dk>
+Link: https://lore.kernel.org/20250527133255.452431-5-axboe@kernel.dk
+Signed-off-by: Christian Brauner <brauner@kernel.org>
+---
+ mm/filemap.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/mm/filemap.c
++++ b/mm/filemap.c
+@@ -1604,7 +1604,7 @@ static void filemap_end_dropbehind(struc
+  * completes. Do that now. If we fail, it's likely because of a big folio -
+  * just reset dropbehind for that case and latter completions should invalidate.
+  */
+-static void folio_end_dropbehind_write(struct folio *folio)
++static void filemap_end_dropbehind_write(struct folio *folio)
+ {
+ 	/*
+ 	 * Hitting !in_task() should not happen off RWF_DONTCACHE writeback,
+@@ -1659,7 +1659,7 @@ void folio_end_writeback(struct folio *f
+ 	acct_reclaim_writeback(folio);
+ 
+ 	if (folio_dropbehind)
+-		folio_end_dropbehind_write(folio);
++		filemap_end_dropbehind_write(folio);
+ 	folio_put(folio);
+ }
+ EXPORT_SYMBOL(folio_end_writeback);