From: syzbot ci <syzbot+cibc074c2fc4a0e4e4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: configfs: enable kernel-space item registration
Date: Tue, 02 Dec 2025 08:13:42 -0800 [thread overview]
Message-ID: <692f1036.a70a0220.d98e3.019e.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] configfs: enable kernel-space item registration
https://lore.kernel.org/all/20251202-configfs_netcon-v1-0-b4738ead8ee8@debian.org
* [PATCH RFC 1/2] configfs: add kernel-space item registration API
* [PATCH RFC 2/2] netconsole: Plug to dynamic configfs item
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d96d193b-5349-4f30-be4c-b8950ecce808
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: 779bcdd4b9ae6566f309043c53c946e8ac0015fd
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/bdd14175-68c7-4ea2-8a84-b64131d9050b/config
drivers/net/netconsole.c:231:1: error: non-void function does not return a value [-Werror,-Wreturn-type]
drivers/net/netconsole.c:1892:10: error: no member named 'group' in 'struct netconsole_target'
drivers/net/netconsole.c:1893:33: error: no member named 'group' in 'struct netconsole_target'
***
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:
[a.hindborg@kernel.org andrew@lunn.ch asantostc@gmail.com calvin@wbinvd.org davem@davemloft.net edumazet@google.com gustavold@gmail.com hch@infradead.org jlbec@evilplan.org kernel-team@meta.com kuba@kernel.org leitao@debian.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org netdev@vger.kernel.org pabeni@redhat.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-12-02 16:13 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=692f1036.a70a0220.d98e3.019e.GAE@google.com \
--to=syzbot+cibc074c2fc4a0e4e4@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