From: syzbot ci <syzbot+ci69006877028fe598@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: fs: remove stale and duplicate forward declarations
Date: Mon, 29 Dec 2025 00:16:08 -0800 [thread overview]
Message-ID: <695238c8.a70a0220.90d62.0031.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] fs: remove stale and duplicate forward declarations
https://lore.kernel.org/all/20251229071401.98146-1-ytohnuki@amazon.com
* [PATCH] fs: remove stale and duplicate forward declarations
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/ad51ab29-ea25-4a27-9aa2-d6f51fbde5cd
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/e0921965-abbe-44c3-86e3-54af83a1ad11/config
block/ioctl.c:565:33: error: incompatible pointer types passing 'struct hd_geometry *' to parameter of type 'struct hd_geometry *' [-Werror,-Wincompatible-pointer-types]
block/ioctl.c:599:33: error: incompatible pointer types passing 'struct hd_geometry *' to parameter of type 'struct hd_geometry *' [-Werror,-Wincompatible-pointer-types]
drivers/block/rnbd/rnbd-clt.c:965:13: error: incompatible function pointer types initializing 'int (*)(struct gendisk *, struct hd_geometry *)' with an expression of type 'int (struct gendisk *, struct hd_geometry *)' [-Wincompatible-function-pointer-types]
***
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:
[brauner@kernel.org jack@suse.cz linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org viro@zeniv.linux.org.uk ytohnuki@amazon.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-12-29 8:16 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=695238c8.a70a0220.90d62.0031.GAE@google.com \
--to=syzbot+ci69006877028fe598@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