Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Dec 2015 19:44:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 205194] Changing MTU higher than 1500 on the interface pfsync0 causes panic
Message-ID:  <bug-205194-2472-VTWxgRyuqq@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205194-2472@https.bugs.freebsd.org/bugzilla/>
References:  <bug-205194-2472@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205194

--- Comment #2 from commit-hook@freebsd.org ---
A commit references this bug:

Author: kp
Date: Mon Dec 14 19:44:49 UTC 2015
New revision: 292219
URL: https://svnweb.freebsd.org/changeset/base/292219

Log:
  inet6: Do not assume every interface has ip6 enabled.

  Certain interfaces (e.g. pfsync0) do not have ip6 addresses (in other words,
  ifp->if_afdata[AF_INET6] is NULL). Ensure we don't panic when the MTU is
  updated.

  pfsync interfaces will never have ip6 support, because it's explicitly
disabled
  in in6_domifattach().

  PR:        205194
  Reviewed by:    melifaro, hrs
  Differential Revision:    https://reviews.freebsd.org/D4522

Changes:
  head/sys/netinet6/in6.c
  head/sys/netinet6/nd6.c

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205194-2472-VTWxgRyuqq>