From: syzbot ci <syzbot+cib68faf1da08cba19@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: hsr: Add additional info to send/ receive skbs
Date: Mon, 09 Mar 2026 18:02:00 -0700 [thread overview]
Message-ID: <69af6d88.050a0220.310d8.0036.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] hsr: Add additional info to send/ receive skbs
https://lore.kernel.org/all/20260309-hsr_ptp-v2-0-798262aad3a4@linutronix.de
* [PATCH RFC net-next v2 1/2] hsr: Allow to send a specific port and with HSR header
* [PATCH RFC net-next v2 2/2] af_packet: Add port specific handling for HSR
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/bd2344c8-000c-4973-9c61-c1487f460d8f
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681
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/8f8db96c-13f9-4426-bdfe-fbfcae8c11cd/config
./include/linux/if_hsr.h:58:12: error: call to undeclared function 'skb_ext_find'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./include/linux/if_hsr.h:58:30: error: use of undeclared identifier 'SKB_EXT_HSR'
./include/linux/if_hsr.h:71:12: error: call to undeclared function 'skb_ext_find'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./include/linux/if_hsr.h:71:30: error: use of undeclared identifier 'SKB_EXT_HSR'
./include/linux/if_hsr.h:85:12: error: call to undeclared function 'skb_ext_find'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./include/linux/if_hsr.h:85:30: error: use of undeclared identifier 'SKB_EXT_HSR'
./include/linux/if_hsr.h:99:12: error: call to undeclared function 'skb_ext_add'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
./include/linux/if_hsr.h:99:29: error: use of undeclared identifier 'SKB_EXT_HSR'
./include/linux/skbuff.h:5034:7: error: conflicting types for 'skb_ext_add'
./include/linux/skbuff.h:5079:21: error: conflicting types for 'skb_ext_find'
***
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:
[andrew@lunn.ch bigeasy@linutronix.de c-vankar@ti.com d-qiu@ti.com danishanwar@ti.com davem@davemloft.net edumazet@google.com fmaurer@redhat.com horms@kernel.org j-rameshbabu@ti.com kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com richardcochran@gmail.com willemdebruijn.kernel@gmail.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-10 1:02 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=69af6d88.050a0220.310d8.0036.GAE@google.com \
--to=syzbot+cib68faf1da08cba19@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