From: syzbot ci <syzbot+ci3d4ed50867fca5f4@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: Tue, 29 Sep 2026 08:55:14 -0700 [thread overview]
Message-ID: <6abbdf62.64639fcc.9812d.0006.GAE@google.com> (raw)
syzbot ci has tested the following series
[v7] hsr: Add additional info to send/ receive skbs
https://lore.kernel.org/all/20260928-hsr_ptp-v7-0-d55d304d9a7e@linutronix.de
* [PATCH net-next v7 1/8] hsr: Add header_ops::parse_protocol
* [PATCH net-next v7 2/8] hsr: Use skb_clone() while adding the HSR header
* [PATCH net-next v7 3/8] hsr: Add a magic header for sending PTP packets
* [PATCH net-next v7 4/8] hsr: Drop received PTP packets
* [PATCH net-next v7 5/8] hsr: Use the port and header information in hsr_forward_skb()
* [PATCH net-next v7 6/8] hsr: Assign a socket for cloned skbs
* [PATCH net-next v7 7/8] hsr: Move struct hsr_ethhdr to a global header
* [PATCH net-next v7 8/8] selftests: hsr: Add test for the inline PTP header on HSR
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/49195b5c-63d1-47db-a41e-70e392d93ff4
***
kernel build error
tree: axboe
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/axboe/linux.git
base: 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e
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/b2ca0665-6838-493e-9938-989fa2b2a25f/config
./include/linux/if_hsr.h:43:16: error: field has incomplete type 'struct ethhdr'
***
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:
[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 neelima@ti.com netdev@vger.kernel.org pabeni@redhat.com praneeth@ti.com pratheesh@ti.com richardcochran@gmail.com vigneshr@ti.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
next reply other threads:[~2026-09-29 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 15:55 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-10 1:02 [moderation/CI] Re: hsr: Add additional info to send/ receive skbs 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=6abbdf62.64639fcc.9812d.0006.GAE@google.com \
--to=syzbot+ci3d4ed50867fca5f4@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