From owner-freebsd-ipfw@freebsd.org  Sun Jun 18 12:02:45 2017
Return-Path: <owner-freebsd-ipfw@freebsd.org>
Delivered-To: freebsd-ipfw@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 07209D900E7
 for <freebsd-ipfw@mailman.ysv.freebsd.org>;
 Sun, 18 Jun 2017 12:02:45 +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 E953B6ACE0
 for <freebsd-ipfw@FreeBSD.org>; Sun, 18 Jun 2017 12:02:44 +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 v5IC2igr006593
 for <freebsd-ipfw@FreeBSD.org>; Sun, 18 Jun 2017 12:02:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ipfw@FreeBSD.org
Subject: [Bug 220078] [patch] [panic] [ipfw] repeatable kernel panic due to
 unlocked INADDR_TO_IFP usage
Date: Sun, 18 Jun 2017 12:02:45 +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: 11.0-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: eugen@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-ipfw@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-220078-7515-U8eYDgKT7v@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220078-7515@https.bugs.freebsd.org/bugzilla/>
References: <bug-220078-7515@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-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw/>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jun 2017 12:02:45 -0000

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

--- Comment #5 from Eugene Grosbein <eugen@freebsd.org> ---
(In reply to Andrey V. Elsukov from comment #4)

I've just rebuilt the kernel with your version of patch instead of old one =
and
restarted my tests. New version does basically same thing, so I do not expe=
ct
problems. The system exhibited no problems at all during a day with my stre=
ss
test using all patches involving (for kernel, libc and mpd itself). Unless
something bad happens next day, I'm going to put it in "testing production".

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