From: syzbot ci <syzbot+cif9a7bc6a33a84782@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: exfat: convert to iomap
Date: Thu, 26 Mar 2026 06:51:23 -0700 [thread overview]
Message-ID: <69c539db.a70a0220.3d5e5.0002.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] exfat: convert to iomap
https://lore.kernel.org/all/20260326115045.9525-1-linkinjeon@kernel.org
* [PATCH 1/5] exfat: add iomap support
* [PATCH 2/5] exfat: add iomap direct I/O support
* [PATCH 3/5] exfat: add iomap buffered I/O support
* [PATCH 4/5] exfat: add support for multi-cluster allocation
* [PATCH 5/5] exfat: add support for SEEK_HOLE and SEEK_DATA in llseek
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/5555e218-5f5c-42aa-8bdb-21f5916323af
***
kernel build error
tree: linux-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next
base: 66ba480978ce390e631e870b740a3406e3eb6b01
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/26c05536-db43-4f15-a55b-23d03dea6957/config
fs/exfat/file.c:843:6: error: call to undeclared function 'vma_desc_test_flags'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
***
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.
The email will later be sent to:
[anmuxixixi@gmail.com chizhiling@kylinos.cn dxdt@dev.snart.me hch@lst.de linkinjeon@kernel.org linux-fsdevel@vger.kernel.org sj1557.seo@samsung.com yuezhang.mo@sony.com]
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-03-26 13:51 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=69c539db.a70a0220.3d5e5.0002.GAE@google.com \
--to=syzbot+cif9a7bc6a33a84782@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.