Date: Tue, 12 Jan 2016 20:17:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 205743] null pointer dereference in PF running a vimage jail Message-ID: <bug-205743-6-DgrhQos5Fs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205743-6@https.bugs.freebsd.org/bugzilla/> References: <bug-205743-6@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=3D205743 --- Comment #9 from gila <ing.gila@gmail.com> --- 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 on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205743-6-DgrhQos5Fs>