Hello, On Thu, Apr 13, 2017 at 9:36 AM, Murali Karicheri <m-kariche...@ti.com> wrote: > On 03/22/2017 11:04 AM, Murali Karicheri wrote: >> This is going directly to the slave Ethernet interface. >> >> When I put a WARN_ONCE, I found this is coming directly from >> mld_ifc_timer_expire() -> mld_sendpack() -> ip6_output() >> >> Do you think this is fixed in latest kernel at master? If so, could >> you point me to some commits. >> >> > Ping... I see this behavior is also seen on v4.9.x Kernel. Any clue if > this is fixed by some commit or I need to debug? I see IGMPv6 has some > fixes on the list to make it similar to IGMPv4. So can someone clarify this is > is a bug at IGMPv6 code or I need to look into the HSR driver code? > Since IGMPv4 is going over the HSR interface I am assuming this is a > bug in the IGMPv6 code. But since I have not experience with this code > can some expert comment please? >
How did you configure your network interfaces and IPv4/IPv6 multicast? IOW, how did you reproduce this? For example, did you change your HSR setup when this happened since you mentioned NETDEV_CHANGEUPPER?
