From: syzbot ci <syzbot+ci626063cba9f23b64@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: vsock/virtio: fix accept queue count leak on transport mismatch in recv_listen
Date: Mon, 13 Apr 2026 04:00:21 -0700 [thread overview]
Message-ID: <69dcccc5.a00a0220.468cb.0045.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] vsock/virtio: fix accept queue count leak on transport mismatch in recv_listen
https://lore.kernel.org/all/20260413085243.73200-1-phx0fer@gmail.com
* [PATCH] vsock/virtio: fix accept queue count leak on transport mismatch in recv_listen
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/4a69d8ad-177b-41c6-b720-ae224d592fb3
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 5758be283ff8b37beed49e270b908a251d5ca2d7
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/a8f5e3a5-21b0-45df-937f-4580396e0566/config
net/vmw_vsock/virtio_transport_common.c:1:2: error: type specifier missing, defaults to 'int'; ISO C99 and later do not support implicit int [-Wimplicit-int]
net/vmw_vsock/virtio_transport_common.c:1:19: error: a parameter list without types is only allowed in a function definition
***
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 patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[jasowang@redhat.com mst@redhat.com netdev@vger.kernel.org phx0fer@gmail.com sgarzare@redhat.com stefanha@redhat.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-04-13 11:00 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=69dcccc5.a00a0220.468cb.0045.GAE@google.com \
--to=syzbot+ci626063cba9f23b64@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.