From: syzbot ci <syzbot+cib336e2e741d62bc8@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: devlink: unify devlink_shd_get_priv() into devlink_priv()
Date: Mon, 23 Mar 2026 09:58:29 -0700 [thread overview]
Message-ID: <69c17135.050a0220.3bf4de.00a1.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] devlink: unify devlink_shd_get_priv() into devlink_priv()
https://lore.kernel.org/all/20260323132136.13191-1-przemyslaw.kitszel@intel.com
* [PATCH net-next] devlink: unify devlink_shd_get_priv() into devlink_priv()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/a5e25c77-cfa0-4c94-8379-67dc864c6daa
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: fb78a629b4f0eb399b413f6c093a3da177b3a4eb
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/4b09e49d-7703-4394-a8ec-ab88fab69e81/config
net/devlink/sh_dev.c:36:9: error: incompatible pointer types returning 'char (*)[]' from a function with result type 'struct devlink_shd *' [-Werror,-Wincompatible-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:
[anthony.l.nguyen@intel.com davem@davemloft.net edumazet@google.com horms@kernel.org intel-wired-lan@lists.osuosl.org jiri@resnulli.us kuba@kernel.org mschmidt@redhat.com netdev@vger.kernel.org pabeni@redhat.com przemyslaw.kitszel@intel.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-23 16:58 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=69c17135.050a0220.3bf4de.00a1.GAE@google.com \
--to=syzbot+cib336e2e741d62bc8@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