From: syzbot ci <syzbot+ci3566e8df2fb29fc1@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm: improve write performance with RWF_DONTCACHE
Date: Wed, 01 Apr 2026 22:01:34 -0700 [thread overview]
Message-ID: <69cdf82e.050a0220.fcd29.0000.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] mm: improve write performance with RWF_DONTCACHE
https://lore.kernel.org/all/20260401-dontcache-v1-0-1f5746fab47a@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: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@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:
[akpm@linux-foundation.org brauner@kernel.org chuck.lever@oracle.com david@kernel.org jack@suse.cz jlayton@kernel.org liam.howlett@oracle.com linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org linux-nfs@vger.kernel.org ljs@kernel.org mhocko@suse.com msnitzer@kernel.org rppt@kernel.org surenb@google.com vbabka@kernel.org viro@zeniv.linux.org.uk willy@infradead.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
reply other threads:[~2026-04-02 5:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69cdf82e.050a0220.fcd29.0000.GAE@google.com \
--to=syzbot+ci3566e8df2fb29fc1@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox