From: syzbot ci <syzbot+ci56092edae3861569@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: openvswitch: reallocate update replies for mismatched IDs
Date: Sun, 02 Aug 2026 05:28:50 -0700 [thread overview]
Message-ID: <6a6f3802.1aa927e4.17d4bf.0018.GAE@google.com> (raw)
syzbot ci has tested the following series
[v4] net: openvswitch: reallocate update replies for mismatched IDs
https://lore.kernel.org/all/3b76cbe50252a5650c3b69c789ed36481d0bbee4.1785583308.git.zhilinz@nebusec.ai
* [PATCH net v4 1/1] net: openvswitch: reallocate update replies for mismatched IDs
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/65cfa64d-466c-466a-81e7-a083fff39ed7
***
kernel build error
tree: net
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net.git
base: af39eb111ce6b5eba9c08513b62c4868eb7e7fd5
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/effdb6e5-3472-4aee-a5ce-71a91357ee70/config
net/openvswitch/datapath.c:1131:11: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
net/openvswitch/datapath.c:1131:11: error: conflicting types for 'get_current'
***
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:
[aconole@redhat.com davem@davemloft.net dev@openvswitch.org echaudro@redhat.com edumazet@google.com horms@kernel.org i.maximets@ovn.org kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com vega@nebusec.ai zhilinz@nebusec.ai]
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-08-02 12:28 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=6a6f3802.1aa927e4.17d4bf.0018.GAE@google.com \
--to=syzbot+ci56092edae3861569@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