From owner-freebsd-bugs@FreeBSD.ORG  Fri Mar  6 18:01:19 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 50105451
 for <freebsd-bugs@FreeBSD.org>; Fri,  6 Mar 2015 18:01:19 +0000 (UTC)
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 361F1BCC
 for <freebsd-bugs@FreeBSD.org>; Fri,  6 Mar 2015 18:01:19 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t26I1Jpd029714
 for <freebsd-bugs@FreeBSD.org>; Fri, 6 Mar 2015 18:01:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195407] relayd crashes kernel after update to 10.1-RELEASE
Date: Fri, 06 Mar 2015 18:01:19 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: jjasen@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-195407-8-hUlN7xvsmP@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195407-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195407-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 18:01:19 -0000

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

jjasen@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mm@FreeBSD.org

--- Comment #2 from jjasen@gmail.com ---
I can confirm the original posters opinion: "My guess was that some data
structure has changed between 10.0 and 10.1 kernels. So a recompile of relayd
should fix that. It did. I compiled it from the ports and it worked."

a) A fresh installation of FreeBSD-10.1, updated to p6, and pkg install relayd
will crash relayd. restarting relayd will cause a kernel panic.

b) A fresh installation of FreeBSD-10.1, updated to p6, with relayd compiled
from ports does NOT experience either issue.

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