From: syzbot ci <syzbot+ci64b8b93d66db86d2@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: hfsplus: validate b-tree fork extents at mount and inode read
Date: Sun, 20 Sep 2026 05:34:59 -0700 [thread overview]
Message-ID: <6aafd2f3.3179f8cd.1e36b2.000f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v6] hfsplus: validate b-tree fork extents at mount and inode read
https://lore.kernel.org/all/20260918085156.920842-1-ngocthang2710.1999@gmail.com
* [PATCH v6] hfsplus: validate b-tree fork extents at mount and inode read
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/1a9ef6de-01d7-4a6e-a590-94670355d046
***
kernel build error
tree: vfs
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/vfs/vfs.git
base: 33d280b462dfabeae3264b462d4e91339320be00
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/a34c3b73-64be-44d9-b975-48f355468b18/config
fs/hfsplus/inode.c:562:5: error: conflicting types for 'hfsplus_inode_read_fork'
fs/hfsplus/inode.c:571:11: error: call to undeclared function 'hfsplus_check_fork'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
fs/hfsplus/inode.c:574:10: error: use of undeclared identifier 'HFSPLUS_I_CORRUPT_TREE'
fs/hfsplus/inode.c:580:33: error: use of undeclared identifier 'HFSPLUS_EXTENT_LAST_IDX'
***
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 fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[frank.li@vivo.com glaubitz@physik.fu-berlin.de linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org ngocthang2710.1999@gmail.com slava@dubeyko.com syzbot@syzkaller.appspotmail.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
next reply other threads:[~2026-09-20 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 12:34 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-20 11:27 [moderation/CI] Re: hfsplus: validate b-tree fork extents at mount and inode read syzbot ci
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=6aafd2f3.3179f8cd.1e36b2.000f.GAE@google.com \
--to=syzbot+ci64b8b93d66db86d2@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.