From owner-freebsd-pf@freebsd.org Tue Jan 12 20:17:51 2016 Return-Path: Delivered-To: freebsd-pf@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 B6C11A80D1A for ; Tue, 12 Jan 2016 20:17:51 +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 8EBE213A6 for ; Tue, 12 Jan 2016 20:17:51 +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 u0CKHpIm081891 for ; Tue, 12 Jan 2016 20:17:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 205743] null pointer dereference in PF running a vimage jail Date: Tue, 12 Jan 2016 20:17:51 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ing.gila@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-pf@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-pf@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2016 20:17:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205743 --- Comment #9 from gila --- Hi, It seems there was a paste error icmp_types=3D"echoreq"=20 Is what should be there. I just grabbed the latest image from 11-CURRENT and verified the bug is still -- and I have not applied the patch. The second panic (after patch) is indeed related to pfsync. I have no use f= or pfsync however, and I don't really know why it shows up.=20 Whats new in this release is when I create the jail; i get a lor message: #0 0xffffffff80a7c5f0 at witness_debugger+0x70 #1 0xffffffff80a7c4f1 at witness_checkorder+0xe71 #2 0xffffffff809fd99b at __lockmgr_args+0xd3b #3 0xffffffff80ac5fcc at vop_stdlock+0x3c #4 0xffffffff80fd3860 at VOP_LOCK1_APV+0x100 #5 0xffffffff80ae6eca at _vn_lock+0x9a #6 0xffffffff80ad7333 at vget+0x63 #7 0xffffffff808f8fcd at devfs_allocv+0xcd #8 0xffffffff808f8a93 at devfs_root+0x43 #9 0xffffffff80ace631 at vfs_donmount+0x1521 #10 0xffffffff80acd0e2 at sys_nmount+0x72 #11 0xffffffff80e8615b at amd64_syscall+0x2db #12 0xffffffff80e6515b at Xfast_syscall+0xfb lock order reversal: 1st 0xffffffff81cf4038 allprison (allprison) @ /usr/src/sys/kern/kern_jail.c:1020 2nd 0xffffffff81d19b10 vnet_sysinit_sxlock (vnet_sysinit_sxlock) @ /usr/src/sys/net/vnet.c:573 stack backtrace: #0 0xffffffff80a7c5f0 at witness_debugger+0x70 #1 0xffffffff80a7c4f1 at witness_checkorder+0xe71 #2 0xffffffff80a29533 at _sx_slock+0x73 #3 0xffffffff80b1ccce at vnet_alloc+0x10e #4 0xffffffff809ed3f3 at kern_jail_set+0x1d33 #5 0xffffffff809eede1 at sys_jail_set+0x41 #6 0xffffffff80e8615b at amd64_syscall+0x2db #7 0xffffffff80e6515b at Xfast_syscall+0xfb The jail does start though. Then in the jail, starting PF trigger the panic mentioned earlier. Let me k= now if there is anything else I can do to help. --=20 You are receiving this mail because: You are the assignee for the bug.=