From: syzbot ci <syzbot+ci4a2a4cdfde16d4bb@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: net: bridge: take care of p->flags accesses
Date: Tue, 09 Jun 2026 09:05:32 -0700 [thread overview]
Message-ID: <6a2839cc.39669fcc.33b062.0098.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] net: bridge: take care of p->flags accesses
https://lore.kernel.org/all/20260609080839.2506801-1-edumazet@google.com
* [PATCH net-next 1/5] bridge: use atomic ops to read/change p->flags in sysfs
* [PATCH net-next 2/5] bridge: use atomic ops to read/change p->flags in br_netlink.c
* [PATCH net-next 3/5] net: bridge: use atomic ops to read/change p->flags (I)
* [PATCH net-next 4/5] net: bridge: use atomic ops to read/change p->flags (II)
* [PATCH net-next 5/5] net: bridge: use atomic ops to read/change p->flags (III)
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/af3c270e-aed1-483d-aca2-8e328e1d9aa9
***
kernel build error
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 67ad35a58a88c360136d893cbc4c7f5b14100bb9
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/866adee7-16cc-49c4-bfec-0fb43ebb02b2/config
net/bridge/br_mrp.c:1249:23: error: use of undeclared identifier 'BR_MRP_AWARE_BI'; did you mean 'BR_MRP_AWARE_BIT'?
***
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:
[davem@davemloft.net edumazet@google.com eric.dumazet@gmail.com horms@kernel.org idosch@nvidia.com kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com razor@blackwall.org]
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-06-09 16:05 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=6a2839cc.39669fcc.33b062.0098.GAE@google.com \
--to=syzbot+ci4a2a4cdfde16d4bb@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