Summary: | [panic] page fault in mld_v2_cancel_link_timers() on boot | ||
---|---|---|---|
Product: | Base System | Reporter: | Andrey V. Elsukov <ae> |
Component: | kern | Assignee: | freebsd-net (Nobody) <net> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | mmacy, mmacy, sbruno, shurd |
Priority: | --- | ||
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
Andrey V. Elsukov
2018-06-13 12:43:59 UTC
This looks a lot more like it's tied to my deferred deletion of multicast addresses. Could you test with a kernel prior to my epoch changes? Also, could you give me a specific configuration that is most likely to produce the issue? Thankse (In reply to Matthew Macy from comment #1) > This looks a lot more like it's tied to my deferred deletion of multicast > addresses. Could you test with a kernel prior to my epoch changes? Also, > could you give me a specific configuration that is most likely to produce > the issue? I update this host periodically, and never seen such panics before epoch changes. I can test some prior revision, but as I said it happens rarely. I think relevant settings are: cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport em0 laggport re0 DHCP" ifconfig_em0="up" # this port is unplugged ifconfig_re0="up" ipv6_activate_all_interfaces="YES" And my local network usually have some IPv6 activity, at least IPv6 is enabled. A commit references this bug: Author: ae Date: Thu Jun 14 09:36:25 UTC 2018 New revision: 335129 URL: https://svnweb.freebsd.org/changeset/base/335129 Log: Add NULL check like the rest of code has. It is possible that ifma_protospec becomes NULL in this function for some entry, but it is still referenced and thus it will not unlinked from the list. Then "restart" condition triggers and this entry with NULL ifma_protospec will lead to page fault. PR: 228982 Changes: head/sys/netinet6/mld6.c |