From: syzbot@syzkaller.appspotmail.com
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ipv6: Drop RTNL from mcast.c and anycast.c
Date: Thu, 10 Jul 2025 02:22:32 -0700 [thread overview]
Message-ID: <686f8658.a00a0220.26a83e.0009.GAE@google.com> (raw)
syzbot ci has processed the following series
[v3] ipv6: Drop RTNL from mcast.c and anycast.c
* [PATCH v3 net-next 01/15] ipv6: ndisc: Remove __in6_dev_get() in pndisc_{constructor,destructor}().
* [PATCH v3 net-next 02/15] ipv6: mcast: Replace locking comments with lockdep annotations.
* [PATCH v3 net-next 03/15] ipv6: mcast: Check inet6_dev->dead under idev->mc_lock in __ipv6_dev_mc_inc().
* [PATCH v3 net-next 04/15] ipv6: mcast: Remove mca_get().
* [PATCH v3 net-next 05/15] ipv6: mcast: Use in6_dev_get() in ipv6_dev_mc_dec().
* [PATCH v3 net-next 06/15] ipv6: mcast: Don't hold RTNL for IPV6_ADD_MEMBERSHIP and MCAST_JOIN_GROUP.
* [PATCH v3 net-next 07/15] ipv6: mcast: Don't hold RTNL for IPV6_DROP_MEMBERSHIP and MCAST_LEAVE_GROUP.
* [PATCH v3 net-next 08/15] ipv6: mcast: Don't hold RTNL in ipv6_sock_mc_close().
* [PATCH v3 net-next 09/15] ipv6: mcast: Don't hold RTNL for MCAST_ socket options.
* [PATCH v3 net-next 10/15] ipv6: mcast: Remove unnecessary ASSERT_RTNL and comment.
* [PATCH v3 net-next 11/15] ipv6: anycast: Don't use rtnl_dereference().
* [PATCH v3 net-next 12/15] ipv6: anycast: Don't hold RTNL for IPV6_LEAVE_ANYCAST and IPV6_ADDRFORM.
* [PATCH v3 net-next 13/15] ipv6: anycast: Unify two error paths in ipv6_sock_ac_join().
* [PATCH v3 net-next 14/15] ipv6: anycast: Don't hold RTNL for IPV6_JOIN_ANYCAST.
* [PATCH v3 net-next 15/15] ipv6: Remove setsockopt_needs_rtnl().
and found the following issues:
* failed to build the kernel
The series was applied to the following base tree:
* Tree:
* Commit:
Full report is available here:
***
failed to build the kernel
---
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:
[]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-07-10 9:22 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=686f8658.a00a0220.26a83e.0009.GAE@google.com \
--to=syzbot@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.