[moderation/CI] Re: mm: improve write performance with RWF_DONTCACHE

[syzbot ci]

syzbot ci has tested the following series

[v1] mm: improve write performance with RWF_DONTCACHE
https://lore.kernel.org/all/20260401-dontcache...@kernel.org
* [PATCH 1/4] mm: fix IOCB_DONTCACHE write performance with rate-limited writeback
* [PATCH 2/4] mm: add atomic flush guard for IOCB_DONTCACHE writeback
* [PATCH 3/4] testing: add nfsd-io-bench NFS server benchmark suite
* [PATCH 4/4] testing: add dontcache-bench local filesystem benchmark suite

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/396c3465-92e3-4ff8-a5e9-66d94e62ecc5

***

kernel build error

tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 9147566d801602c9e7fc7f85e989735735bf38ba
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/8b297e42-3cc8-4d9c-80b6-5a95cd2044ef/config

mm/filemap.c:485:4: error: too many arguments to function call, expected 5, have 6

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@googlegroups.com.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[ak...@linux-foundation.org bra...@kernel.org chuck...@oracle.com da...@kernel.org ja...@suse.cz jla...@kernel.org liam.h...@oracle.com linux-...@vger.kernel.org linux-...@vger.kernel.org linu...@kvack.org linu...@vger.kernel.org l...@kernel.org mho...@suse.com msni...@kernel.org rp...@kernel.org sur...@google.com vba...@kernel.org vi...@zeniv.linux.org.uk wi...@infradead.org]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid