From owner-freebsd-amd64@freebsd.org  Wed Jun 22 06:37:10 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE792AC5EFA
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 22 Jun 2016 06:37:10 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id BEC1E1B9D
 for <freebsd-amd64@FreeBSD.org>; Wed, 22 Jun 2016 06:37:10 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5M6b9QI020557
 for <freebsd-amd64@FreeBSD.org>; Wed, 22 Jun 2016 06:37:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 210379] [panic] in6_lltable_dump_entry bcopy page fault
Date: Wed, 22 Jun 2016 06:37:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: ae@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-210379-6-oZwQsctq1J@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210379-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-210379-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 22 Jun 2016 11:28:48 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2016 06:37:10 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210379

--- Comment #8 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to Mark Johnston from comment #7)
> I think this is a regression from r292978. Before that change, entries
> created
> by nd6_cache_lladdr() without a specified lladdr would have reported an
> address
> consisting of zeroes; now we leave ll_addr set to NULL, which causes the
> problem.

It looks like inet6 code also needs to handle LLE_VALID flag like here
https://svnweb.freebsd.org/base/head/sys/netinet/in.c?view=3Dmarkup#l1412

--=20
You are receiving this mail because:
You are on the CC list for the bug.=