From: syzbot ci <syzbot+cid1cf8302c418c0f4@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: A series of minor optimizations of the bonding module
Date: Tue, 25 Nov 2025 01:56:56 -0800 [thread overview]
Message-ID: <69257d68.a70a0220.d98e3.00a4.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] A series of minor optimizations of the bonding module
https://lore.kernel.org/all/20251125084451.11632-1-tonghao@bamaicloud.com
* [PATCH net-next v1 1/5] net: bonding: use workqueue to make sure peer notify updated in lacp mode
* [PATCH net-next v1 2/5] net: bonding: move bond_should_notify_peers, e.g. into rtnl lock block
* [PATCH net-next v1 3/5] net: bonding: skip the 2nd trylock when first one fail
* [PATCH net-next v1 4/5] net: bonding: add the READ_ONCE/WRITE_ONCE for outside lock accessing
* [PATCH net-next v1 5/5] net: bonding: combine rtnl lock block for arp monitor in activebackup mode
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/7cb17fee-8e79-4633-a4dc-95fb83f26928
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: e2c20036a8879476c88002730d8a27f4e3c32d4b
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/592413ec-7f74-4f30-96ea-06d1dd8c8e3c/config
drivers/net/bonding/bond_main.c:1207:2: error: unterminated function-like macro invocation
drivers/net/bonding/bond_main.c:6577:37: error: expected '}'
***
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 corbet@lwn.net davem@davemloft.net edumazet@google.com horms@kernel.org jv@jvosburgh.net kuba@kernel.org liuhangbin@gmail.com netdev@vger.kernel.org pabeni@redhat.com razor@blackwall.org tonghao@bamaicloud.com]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-11-25 9:56 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=69257d68.a70a0220.d98e3.00a4.GAE@google.com \
--to=syzbot+cid1cf8302c418c0f4@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