From: syzbot ci <syzbot+ci3cb96f1e58ca3851@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: virtio-net: fix for VIRTIO_NET_F_GUEST_HDRLEN
Date: Tue, 18 Nov 2025 22:35:56 -0800 [thread overview]
Message-ID: <691d654c.a70a0220.2ea503.0012.GAE@google.com> (raw)
syzbot ci has tested the following series
[v6] virtio-net: fix for VIRTIO_NET_F_GUEST_HDRLEN
https://lore.kernel.org/all/20251119055522.617-1-xuanzhuo@linux.alibaba.com
* [PATCH net v6 1/2] virtio-net: correct hdr_len handling for VIRTIO_NET_F_GUEST_HDRLEN
* [PATCH net v6 2/2] virtio-net: correct hdr_len handling for tunnel gso
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/9431b637-afd5-413a-9862-69c624b86fb8
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: 5442a9da69789741bfda39f34ee7f69552bf0c56
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/2333941a-fb9e-4de3-b3de-bc15fb81d69a/config
./include/linux/virtio_net.h:218:7: error: use of undeclared identifier 'sinfo'
***
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:
[alvaro.karsz@solid-run.com andrew@lunn.ch davem@davemloft.net edumazet@google.com eperezma@redhat.com jasowang@redhat.com jiri@resnulli.us kuba@kernel.org mst@redhat.com netdev@vger.kernel.org pabeni@redhat.com virtualization@lists.linux.dev willemdebruijn.kernel@gmail.com xuanzhuo@linux.alibaba.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-11-19 6:35 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=691d654c.a70a0220.2ea503.0012.GAE@google.com \
--to=syzbot+ci3cb96f1e58ca3851@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.